Re: Bhyve passthrough problems (update)

[Mario Lobo]

2018-02-07 20:19 GMT-03:00 Peter Grehan :

> Hi Mario,
>
> Well, now, even without setting up passthrough, the VM doesn't start
>>> (which it did, before I svned up /usr/src).
>>>
>> ...
>
>> working:   321652
>>> not working (current): 328163
>>>
>> ...
>
>> Any updates on this issue?
>>
>
>  Can you verify if the issue still occurrs if you destroy the guest before
> re-invoking it ? (i.e. bhyvectl --destroy --vm=WIN-764 )
>
> later,
>
> Peter.
>

Yes, I verified that. It still occurs even after destroying the VM.

I also recompiled bhyve from the working (321652) release and the same
error messages are still there. I even recreated a new disk.img and
followed the same steps that worked before (1 cpu) to reinstall the VM from
ISO to no avail.
Bhyve doesn't even start any longer and exits with one of the error
messages above.

What previously worked now doesn't.

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio YET!!]
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve passthrough problems (update)

[Peter Grehan]

Hi Mario,


Well, now, even without setting up passthrough, the VM doesn't start
(which it did, before I svned up /usr/src).

...

working:   321652
not working (current): 328163

...

Any updates on this issue?


 Can you verify if the issue still occurrs if you destroy the guest 
before re-invoking it ? (i.e. bhyvectl --destroy --vm=WIN-764 )


later,

Peter.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve passthrough problems (update)

[Mario Lobo]

On Fri, 19 Jan 2018 17:52:57 -0300
Mario Lobo  wrote:

> On Thu, 18 Jan 2018 00:58:08 -0800
> Peter Grehan  wrote:
> 
> > Hi Mario,
> >   
> > > I'm trying to passthrough a firewire pci card to a windows 7 64
> > > guest.
> > 
> >   First, you'll need to verify if that card supports MSI or MSI-x
> > since that is required by bhyve for passthru support. This can be
> > seen with 'pciconf -lbc' on the FreeBSD host.
> >   
> > > VM exits with:
> > > 
> > > Assertion failed: (mr->name == memp->name), function
> > > unregister_mem, file /usr/src/usr.sbin/bhyve/mem.c, line 265.
> > > Abort trap
> > 
> >   This is bug in bhyve when running Windows with PCI devices that
> > have more than 1 memory BAR (e.g. Intel igb ethernet devices), due
> > to the order that Windows determines BAR sizes. I've been meaning
> > to fix this for a long time so will try and get to it.
> > 
> > later,
> > 
> > Peter.  
> 
> Hi there:
> 
> Well, now, even without setting up passthrough, the VM doesn't start
> (which it did, before I svned up /usr/src).
> 
> With vnc:
> 
> bhyve  -c 4   -s 0,amd_hostbridge   
> -s 3,ahci-hd,/Vmachines/disk.img,sectorsize=512   
> -s 4,ahci-cd,/Extra/Isos/Windows/Windows_7/null_dvd.iso   
> -s 10,virtio-net,tap0   
> -s 11,fbuf,tcp=0.0.0.0:5900,,w=1600,h=900,wait   
> -s 20,xhci,tablet   
> -s 31,lpc   
> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd   
> -m 4G -H -w WIN-764
> fbuf frame buffer base: 0x942e0 [sz 16777216]
> 
> error:
> Assertion failed: (error == 0), function modify_bar_registration,
> file /usr/src/usr.sbin/bhyve/pci_emul.c, line 491. Abort trap
> 
> 
> Without vnc:
> 
> bhyve  -c 4   -s 0,amd_hostbridge   
> -s 3,ahci-hd,/Vmachines/disk.img,sectorsize=512   
> -s 4,ahci-cd,/Extra/Isos/Windows/Windows_7/null_dvd.iso   
> -s 10,virtio-net,tap0   
> -s 20,xhci,tablet   
> -s 31,lpc   
> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd   
> -m 4G -H -w WIN-764
> 
> error:
> Assertion failed: (mr->name == memp->name), function unregister_mem,
> file /usr/src/usr.sbin/bhyve/mem.c, line 265. Abort trap
> 
> 
> Revisions (/usr/src 11-STABLE):
> 
> working:   321652
> not working (current): 328163
> 
> 

Any updates on this issue?

Thanks,

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
 
"UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things."
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve passthrough problems

[Andriy Gapon]

On 22/01/2018 16:54, Harry Schmalzbauer wrote:
> Inderictly related, but also a big improvement for bhyve, could you have
> a minute on that too:
> https://lists.freebsd.org/pipermail/freebsd-virtualization/2017-November/005875.html

What you request, has already been committed once and then reverted:
https://svnweb.freebsd.org/base?view=revision=282922
https://svnweb.freebsd.org/base?view=revision=283168

Unfortunately, an 'upcoming commit' hasn't come yet.


-- 
Andriy Gapon
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve passthrough problems

[Harry Schmalzbauer]

 Bezüglich Peter Grehan's Nachricht vom 18.01.2018 09:58 (localtime):
> Hi Mario,
>
>> I'm trying to passthrough a firewire pci card to a windows 7 64 guest.
>
>  First, you'll need to verify if that card supports MSI or MSI-x since
> that is required by bhyve for passthru support. This can be seen with
> 'pciconf -lbc' on the FreeBSD host.
>
>> VM exits with:
>>
>> Assertion failed: (mr->name == memp->name), function
>> unregister_mem, file /usr/src/usr.sbin/bhyve/mem.c, line 265.
>> Abort trap
>
>  This is bug in bhyve when running Windows with PCI devices that have
> more than 1 memory BAR (e.g. Intel igb ethernet devices), due to the
> order that Windows determines BAR sizes. I've been meaning to fix this
> for a long time so will try and get to it.

Thanks in advance, Peter!

Inderictly related, but also a big improvement for bhyve, could you have
a minute on that too:
https://lists.freebsd.org/pipermail/freebsd-virtualization/2017-November/005875.html

Thanks,

-harry
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve passthrough problems (update)

[Mario Lobo]

On Thu, 18 Jan 2018 00:58:08 -0800
Peter Grehan  wrote:

> Hi Mario,
> 
> > I'm trying to passthrough a firewire pci card to a windows 7 64
> > guest.  
> 
>   First, you'll need to verify if that card supports MSI or MSI-x
> since that is required by bhyve for passthru support. This can be
> seen with 'pciconf -lbc' on the FreeBSD host.
> 
> > VM exits with:
> > 
> > Assertion failed: (mr->name == memp->name), function
> > unregister_mem, file /usr/src/usr.sbin/bhyve/mem.c, line 265.
> > Abort trap  
> 
>   This is bug in bhyve when running Windows with PCI devices that
> have more than 1 memory BAR (e.g. Intel igb ethernet devices), due to
> the order that Windows determines BAR sizes. I've been meaning to fix
> this for a long time so will try and get to it.
> 
> later,
> 
> Peter.

Hi there:

Well, now, even without setting up passthrough, the VM doesn't start
(which it did, before I svned up /usr/src).

With vnc:

bhyve  -c 4   -s 0,amd_hostbridge   
-s 3,ahci-hd,/Vmachines/disk.img,sectorsize=512   
-s 4,ahci-cd,/Extra/Isos/Windows/Windows_7/null_dvd.iso   
-s 10,virtio-net,tap0   
-s 11,fbuf,tcp=0.0.0.0:5900,,w=1600,h=900,wait   
-s 20,xhci,tablet   
-s 31,lpc   
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd   
-m 4G -H -w WIN-764
fbuf frame buffer base: 0x942e0 [sz 16777216]

error:
Assertion failed: (error == 0), function modify_bar_registration,
file /usr/src/usr.sbin/bhyve/pci_emul.c, line 491. Abort trap


Without vnc:

bhyve  -c 4   -s 0,amd_hostbridge   
-s 3,ahci-hd,/Vmachines/disk.img,sectorsize=512   
-s 4,ahci-cd,/Extra/Isos/Windows/Windows_7/null_dvd.iso   
-s 10,virtio-net,tap0   
-s 20,xhci,tablet   
-s 31,lpc   
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd   
-m 4G -H -w WIN-764

error:
Assertion failed: (mr->name == memp->name), function unregister_mem,
file /usr/src/usr.sbin/bhyve/mem.c, line 265. Abort trap


Revisions (/usr/src 11-STABLE):

working:   321652
not working (current): 328163


-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
 
"UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things."
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve passthrough problems

[Peter Grehan]

Hi Mario,


I'm trying to passthrough a firewire pci card to a windows 7 64 guest.


 First, you'll need to verify if that card supports MSI or MSI-x since 
that is required by bhyve for passthru support. This can be seen with 
'pciconf -lbc' on the FreeBSD host.



VM exits with:

Assertion failed: (mr->name == memp->name), function
unregister_mem, file /usr/src/usr.sbin/bhyve/mem.c, line 265.
Abort trap


 This is bug in bhyve when running Windows with PCI devices that have 
more than 1 memory BAR (e.g. Intel igb ethernet devices), due to the 
order that Windows determines BAR sizes. I've been meaning to fix this 
for a long time so will try and get to it.


later,

Peter.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Bhyve passthrough problems

[Mario Lobo]

Hello;

I'm trying to passthrough a firewire pci card to a windows 7 64 guest.

Without passthrough, the vm boots with everything working normally.

Here are my specs:

uname -a:
FreeBSD 11.1-STABLE #0 r328025M: Wed Jan 17 18:30:26 -03 2018
root@Papi.lobos:/usr/obj/usr/src/sys/LOBO amd64

x86info: 
x86info v1.31pre
Found 8 identical CPUs
Extended Family: 6 Extended Model: 0 Family: 15 Model: 2 Stepping: 0
CPU Model (x86info's best guess): AMD FX Series Processor (OR-C0)
Processor name string (BIOS programmed): AMD FX-8320E Eight-Core
Processor

dmesg | grep ivhd
ivhd0:  on acpi0
ivhd0: Flag:3e
ivhd0: max supported paging level:7 restricting to: 4
ivhd0: device supported range [0x0 - 0x4ff]
ivhd0: device [0xa0 - 0xa0]config:d7
ivhd0: PCI cap 0x10b540f@0x40 feature:1

PCI card (already attached to ppt0)

ppt0@pci0:4:7:0:class=0x0c0010 card=0x30441106 chip=0x30441106
rev=0xc0 hdr=0x00 vendor = 'VIA Technologies, Inc.'
device = 'VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller'
class  = serial bus
subclass   = FireWire

Starting the vm with VNC:

bhyve -A -P -H  -c 4   -S   -s 0,amd_hostbridge   -s
3,ahci-hd,/Vmachines/disk.img,sectorsize=512   -s
4,ahci-cd,/Extra/Isos/Windows/Windows_7/null_dvd.iso   -s
7,passthru,4/7/0   -s 10,virtio-net,tap0   -s
11,fbuf,tcp=0.0.0.0:5900,,w=1600,h=900,wait   -s
20,xhci,tablet   -s 31,lpc   -l
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd   -m 8G -H -w
WIN-764 
fbuf frame buffer base: 0xa42e0 [sz 16777216] Assertion

As soon as I try to connect, the VM aborts with:

failed: (error == 0), function modify_bar_registration,
file /usr/src/usr.sbin/bhyve/pci_emul.c, line 491. Abort trap

Starting the vm without VNC:

bhyve -A -H -P  -c 4   -S   -s 0,amd_hostbridge   -s
3,ahci-hd,/Vmachines/disk.img,sectorsize=512   -s
4,ahci-cd,/Extra/Isos/Windows/Windows_7/null_dvd.iso   -s
7,passthru,4/7/0   -s 10,virtio-net,tap0   -s
20,xhci,tablet   -s 31,lpc   -l
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd   -m 8G -H -w
WIN-764 

VM exits with:

Assertion failed: (mr->name == memp->name), function
unregister_mem, file /usr/src/usr.sbin/bhyve/mem.c, line 265. 
Abort trap


Same thing happens without "-A -H -P" on bhyve command line.

Would anybody have any suggestions on what else I could try?

Thanks,

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
 
"UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things."
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"