From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 12 01:21:35 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6E5E29C0 for ; Tue, 12 Feb 2013 01:21:35 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-ia0-x22d.google.com (mail-ia0-x22d.google.com [IPv6:2607:f8b0:4001:c02::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 1C15CAEC for ; Tue, 12 Feb 2013 01:21:35 +0000 (UTC) Received: by mail-ia0-f173.google.com with SMTP id h37so7009345iak.32 for ; Mon, 11 Feb 2013 17:21:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=ccqIHXkHe46VgebgAQkAjTUlYGGoTdFu8EWDzblLVmw=; b=tG/T/1qaUSLdrE9dfB1NQ5afbmHVhVDHdjWhMhqSb1VYdG2MbrmkAMX5oRXTJG1pG7 zECPm2tvHd+Ud+rOAIYfYd1DlEQT+d6d9yhJDNAzpTeumH8g9DtxDA3rs8xgdF0P2PMu DreRmbmqaMKztvvLD6i8dXAOyAWCVbcLnpNXNwOMajE1Q+C10TTdfupj7SYshfMq9vv1 xUWj/iW1SBKOZt3bQE2cNi0G7VkZ9Zc3ZkdG3F3vJZUFGNzI6uB2ec6tPr1t7G5oiwK5 qIcxurebkkNBIRiAwMX2Y/BcYjhiAuLKWypeqK09R1jOZIxFIOEUSV49rL80wAHnLY9L eU/w== MIME-Version: 1.0 X-Received: by 10.50.170.69 with SMTP id ak5mr15653270igc.56.1360632094292; Mon, 11 Feb 2013 17:21:34 -0800 (PST) Received: by 10.42.23.132 with HTTP; Mon, 11 Feb 2013 17:21:34 -0800 (PST) In-Reply-To: <51193EED.2070004@hawara.com> References: <5118E47B.9020807@Hawara.com> <1399173350.4891.1360607669873.JavaMail.root@daemoninthecloset.org> <51193EED.2070004@hawara.com> Date: Mon, 11 Feb 2013 17:21:34 -0800 Message-ID: Subject: Re: vtnet cannot allocate interrupts From: Neel Natu To: Marat Bakeev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 01:21:35 -0000 Hi Marat, On Mon, Feb 11, 2013 at 10:56 AM, Marat Bakeev wrote: > 11.02.2013 22:34, Bryan Venteicher =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >> Recent bhyve changed to use MSIX instead of MSI. I wonder if that >> is causing this. If you do: >> >> $ BHYVE_USE_MSI=3Dtrue bhyve ... >> >> does it work? >> > > No, it won`t work, but it seems i had msix disabled in loader.conf, as in > example from here - http://www.emulsoft.com/bhyve-ufs.txt. > I enabled msix, and the vtnet device is now loading fine. > Glad to hear. > Do I need other options in loader.conf, like these?: > > smbios.bios.vendor=3D"BHYVE" > console=3D"userboot" > hw.pci.honor_msi_blacklist=3D"0" > No, you don't need these anymore. Here is a simple set of instructions that should get you started: http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt They do not have all the bells-and-whistles as some of the other HOWTOs but it should get you a working VM in a short amount of time. best Neel > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org"