Current problem reports assigned to freebsd-virtualization@FreeBSD.org

2013-02-11 Thread FreeBSD bugmaster
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

vtnet cannot allocate interrupts

2013-02-11 Thread Marat Bakeev
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 interrupt

lagg panic

2013-02-11 Thread Nikos Vassiliadis
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/f

Re: vtnet cannot allocate interrupts

2013-02-11 Thread Bryan Venteicher
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/bas

Re: vtnet cannot allocate interrupts

2013-02-11 Thread Marat Bakeev
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.emuls

Re: vtnet cannot allocate interrupts

2013-02-11 Thread Neel Natu
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