Hi Marat,
On Thu, Feb 14, 2013 at 1:03 AM, Marat Bakeev wrote:
> On 14/02/2013 06:20, Neel Natu wrote:
>> You'll need to set 'hw.pci.honor_msi_blacklist' to '0' at the loader
>> prompt or in /boot/loader.conf.
> Great! This fixes the 9.1-release guest! Thank you.
>
Once you update your host to r
On 14/02/2013 06:20, Neel Natu wrote:
> You'll need to set 'hw.pci.honor_msi_blacklist' to '0' at the loader
> prompt or in /boot/loader.conf.
Great! This fixes the 9.1-release guest! Thank you.
>
> I am working on a fix to bhyve that should let you boot the guest
> without needing the workaround.
On 2/13/13 6:20 PM, Neel Natu wrote:
You'll need to set 'hw.pci.honor_msi_blacklist' to '0' at the loader
prompt or in /boot/loader.conf.
I am having these same issues with an 8.3-stable NanoBSD kernel I built.
I tried it with and without all of the "depreciated" loader.conf
variables like 'h
Hi Marat,
On Tue, Feb 12, 2013 at 11:44 PM, Marat Bakeev wrote:
> On 13/02/2013 07:34, Neel Natu wrote:
>> 'bridge0' needs to be 'up'. Try doing 'ifconfig bridge0 up' and that
>> should get the packets flowing to the guest.
>>
>> best
>> Neel
> Oh, my mistake, that really helped 10-CURRENT guest.
On 13/02/2013 07:34, Neel Natu wrote:
> Hi Marat,
>
> On Tue, Feb 12, 2013 at 1:35 AM, Marat Bakeev wrote:
> 'bridge0' needs to be 'up'. Try doing 'ifconfig bridge0 up' and that
> should get the packets flowing to the guest. best Neel
Oh, my mistake, that really helped 10-CURRENT guest.
But stil
On 13/02/2013 07:34, Neel Natu wrote:
> 'bridge0' needs to be 'up'. Try doing 'ifconfig bridge0 up' and that
> should get the packets flowing to the guest.
>
> best
> Neel
Oh, my mistake, that really helped 10-CURRENT guest.
But still, i can`t get 9.1-RELEASE to work inside guest.
If i disable msi
Hi Marat,
On Tue, Feb 12, 2013 at 1:35 AM, Marat Bakeev wrote:
> On 12/02/2013 05:21, Neel Natu wrote:
>> 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
On 12/02/2013 05:21, Neel Natu wrote:
> 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 ...
>
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
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
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
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
12 matches
Mail list logo