On Thu, Mar 17, 2022 at 05:02:04PM +0100, Mario Marietto wrote: > I've already tried on Linux and it works well. Only if Windows is the guest > OS,it does not work. > > bhyve -S -c sockets=1,cores=2,threads=2 -m 4G -w -H -A \ > -s 0,hostbridge \ > -s 1,ahci-hd,/dev/nvd0 \ > -s 2,virtio-blk,/dev/da4 \ > -s 3,virtio-blk,/dev/da2 \ > -s 4:0,passthru,2/0/0 \ > -s 4:1,passthru,2/0/1 \ > -s 4:2,passthru,2/0/2 \ > -s 4:3,passthru,2/0/3 \ > -s 8,virtio-net,tap2 \ > -s 9,virtio-9p,sharename=/ \ > -s 10,hda,play=/dev/dsp,rec=/dev/dsp \ > -s 29,fbuf,tcp=0.0.0.0:5902,w=1440,h=900 \ > -s 30,xhci,tablet \ > -s 31,lpc \ > -l bootrom,/usr/local/share/uefi-firmware/BHYVE_BHF_CODE.fd \ > vm2 < /dev/null & sleep 2 && vncviewer 0:2 > > > Using the whole disks in bhyve the da4 and da2 disks are recognized by > fdisk and by Ubuntu. > > So,the problem is in the virtio-win driver. I wasn't wrong ! Can you give > me their bug tracker ? I believe filing an issue against https://github.com/virtio-win/kvm-guest-drivers-windows will work. > So,take note. Even asking to the wrong place,the > wrong person is redirecting me to the right path ? So I'm totally in the > right place. ;D Can't argue with that :) -- Andrea Bolognani / Red Hat / Virtualization
