Date: Fri, 17 Jun 2022 09:49:03 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 260148] passthru stopped working Message-ID: <bug-260148-27103-ywVzjEND8j@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260148-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-260148-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260148 mario felicioni <marietto2008@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marietto2008@gmail.com --- Comment #13 from mario felicioni <marietto2008@gmail.com> --- I've just upgraded my Windows 11 VM and it does not boot anymore. I see an interesting error,never seen before : root@marietto:/home/marietto/bhyve # ./win11-phy-nvd0-vm4.sh vm_open: vm4 could not be opened: No such file or directory vm_open: vm4 could not be opened: No such file or directory da5 nvd0 da2 da4 ada2 [1] 8326 bhyve: Failed to map MSI-X table BAR on 1/0/0: Device busy bhyve: failed to initialize BARs for PCI 1/0/0 device emulation initialization error: Device busy these are the bhyve parameters that I've used : bhyve -S -c sockets=3D1,cores=3D2,threads=3D2 -m 4G -w -H -A \ -s 0,hostbridge \ -s 1,ahci-hd,/dev/nvd0,bootindex=3D1 \ -s 5,passthru,1/0/0 \ -s 6,passthru,5/0/0 \ -s 7,virtio-net,tap4 \ -s 10,hda,play=3D/dev/dsp,rec=3D/dev/dsp \ -s 29,fbuf,tcp=3D0.0.0.0:5904,w=3D1440,h=3D900 \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_BHF_CODE.fd \ vm4 < /dev/null & sleep 2 && vncviewer 0:4 before to launch the windows 11 vm,I've ran this script : setxkbmap it bhyvectl --vm=3Dvm0 --force-reset bhyvectl --vm=3Dvm0 --destroy bhyvectl --vm=3Dvm1 --force-reset bhyvectl --vm=3Dvm1 --destroy bhyvectl --vm=3Dvm2 --force-reset bhyvectl --vm=3Dvm2 --destroy bhyvectl --vm=3Dvm3 --force-reset bhyvectl --vm=3Dvm3 --destroy bhyvectl --vm=3Dvm4 --force-reset bhyvectl --vm=3Dvm4 --destroy bhyvectl --vm=3Dvm5 --force-reset bhyvectl --vm=3Dvm5 --destroy bhyvectl --vm=3Dvm6 --force-reset bhyvectl --vm=3Dvm6 --destroy bhyvectl --vm=3Dvm7 --force-reset bhyvectl --vm=3Dvm7 --destroy bhyvectl --vm=3Dvm8 --force-reset bhyvectl --vm=3Dvm8 --destroy bhyvectl --vm=3Dvm9 --force-reset bhyvectl --vm=3Dvm9 --destroy bhyvectl --vm=3Dvm10 --force-reset bhyvectl --vm=3Dvm10 --destroy bhyvectl --vm=3Dvm11 --force-reset bhyvectl --vm=3Dvm11 --destroy bhyvectl --vm=3Dvm12 --force-reset bhyvectl --vm=3Dvm12 --destroy bhyvectl --vm=3Dvm13 --force-reset bhyvectl --vm=3Dvm13 --destroy bhyvectl --vm=3Dvm14 --force-reset bhyvectl --vm=3Dvm14 --destroy bhyvectl --vm=3Dvm15 --force-reset bhyvectl --vm=3Dvm15 --destroy bhyvectl --vm=3Dvm16 --force-reset bhyvectl --vm=3Dvm16 --destroy bhyvectl --vm=3Dvm17 --force-reset bhyvectl --vm=3Dvm17 --destroy bhyvectl --vm=3Dvm18 --force-reset bhyvectl --vm=3Dvm18 --destroy bhyvectl --vm=3Dvm19 --force-reset bhyvectl --vm=3Dvm19 --destroy bhyvectl --vm=3Dvm20 --force-reset bhyvectl --vm=3Dvm20 --destroy I have no disks attached to the 1/0/0... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260148-27103-ywVzjEND8j>