Re: vtnet cannot allocate interrupts
Hi Marat, On Mon, Feb 11, 2013 at 10:56 AM, Marat Bakeev wrote: > 11.02.2013 22:34, Bryan Venteicher пишет: > >> Recent bhyve changed to use MSIX instead of MSI. I wonder if that >> is causing this. If you do: >> >> $ BHYVE_USE_MSI=true 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="BHYVE" > console="userboot" > hw.pci.honor_msi_blacklist="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-unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: vtnet cannot allocate interrupts
11.02.2013 22:34, Bryan Venteicher пишет: Recent bhyve changed to use MSIX instead of MSI. I wonder if that is causing this. If you do: $ BHYVE_USE_MSI=true 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. Do I need other options in loader.conf, like these?: smbios.bios.vendor="BHYVE" console="userboot" hw.pci.honor_msi_blacklist="0" ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: vtnet cannot allocate interrupts
Hi, - Original Message - > From: "Marat Bakeev" > To: freebsd-virtualization@freebsd.org > Sent: Monday, February 11, 2013 6:30:51 AM > Subject: vtnet cannot allocate interrupts > > Hello. > > After updating from http://svn.freebsd.org/base/projects/bhyve to > http://svn.freebsd.org/base/head i cannot use vtnet device inside bhyve > guests, both 10 and 9 freebsd. > > I`m getting these errors at boot, and no vtnet device: > > guest 9.1-RELEASE + virtio > virtio_pci0: cannot allocate interrupts > vtnet0: cannot allocate virtqueues > (guest system boots, but no vtnet device) > > guest 10.0-CURRENT > virtio_pci0: port 0x2000-0x201f mem > 0x4000-0x40001fff at device 1.0 on pci0 > vtnet0: on virtio_pci0 > virtio_pci0: host features: 0x18020 > virtio_pci0: negotiated features: 0x18020 > vtnet0: Ethernet address: 00:a0:98:e0:a7:44 > virtio_pci0: exhausted all interrupt allocation attempts > vtnet0: cannot setup virtqueue interrupts > (guest system hangs) > > How to fix these errors? > Recent bhyve changed to use MSIX instead of MSI. I wonder if that is causing this. If you do: $ BHYVE_USE_MSI=true bhyve ... does it work? > Thanks. > ___ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" > ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
lagg panic
Hi, I just noticed this is not committed. Could somebody commit it? http://lists.freebsd.org/pipermail/freebsd-net/2011-November/030526.html Thanks, Nikos ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
vtnet cannot allocate interrupts
Hello. After updating from http://svn.freebsd.org/base/projects/bhyve to http://svn.freebsd.org/base/head i cannot use vtnet device inside bhyve guests, both 10 and 9 freebsd. I`m getting these errors at boot, and no vtnet device: guest 9.1-RELEASE + virtio virtio_pci0: cannot allocate interrupts vtnet0: cannot allocate virtqueues (guest system boots, but no vtnet device) guest 10.0-CURRENT virtio_pci0: port 0x2000-0x201f mem 0x4000-0x40001fff at device 1.0 on pci0 vtnet0: on virtio_pci0 virtio_pci0: host features: 0x18020 virtio_pci0: negotiated features: 0x18020 vtnet0: Ethernet address: 00:a0:98:e0:a7:44 virtio_pci0: exhausted all interrupt allocation attempts vtnet0: cannot setup virtqueue interrupts (guest system hangs) How to fix these errors? Thanks. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Current problem reports assigned to freebsd-virtualization@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o kern/170096 virtualization[vimage] Dynamically-attached network interface will c o kern/169991 virtualization[run] [vimage] panic after device plugged in o kern/165252 virtualization[vimage] [pf] [panic] kernel panics with VIMAGE and PF o kern/161094 virtualization[vimage] [pf] [panic] kernel panic with pf + VIMAGE wh o kern/160541 virtualization[vimage][pf][patch] panic: userret: Returning on td 0x o kern/160496 virtualization[vimage] [pf] [patch] kernel panic with pf + VIMAGE o kern/148155 virtualization[vimage] [pf] Kernel panic with PF/IPFilter + VIMAGE k a kern/147950 virtualization[vimage] [carp] VIMAGE + CARP = kernel crash s kern/143808 virtualization[pf] pf does not work inside jail a kern/141696 virtualization[rum] [vimage] [panic] rum(4)+ vimage = kernel panic 10 problems total. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
