Forgot to mention, I'm using 2 passthrough PCI-e cards. But the problem is, it
crashes even without passthrough enabled.
With kindest regards,
Kostya Berger
On Monday, 16 August 2021, 09:16:58 GMT+3, Kostya Berger
<[email protected]> wrote:
Hello, dear friends :)
I"m on 13.0-p3. Suddenly, after some hardware reconfiguration (PCI-e cards
exchanged slots) my bhyve stopped working.In particular, in my Win 10 VM, it
goes as far as offer to type in BitLocker password, after which starts booting
and immediately crashes. However, I tried to start afresh without ANY disks
attached, except Win 10 installation ISO. Gets as far as 'type a key to boot
from CD', then crashes on an attempt to boot.
This is the message that I see on the screen:./bhyve-1: line 11: 2954 Abort
trap bhyve -S -c sockets=1,cores=4,threads=2 -m 8G -H -w -s
0,hostbridge -s 4,virtio-blk,win-alt.img,sectorsize=512/4096 -s
5,ahci-cd,Win10_21H1_English_x64.iso -s
29,fbuf,tcp=0.0.0.0:5900,w=1600,h=900,wait -s 30,xhci,tablet -s 31,lpc -l
com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd windows-10
For the purity of experiment, I tried it with a fresh installation on the same
machine -- same thing. So I assume it is hardware related. As such, I recall in
the past there was a patch
NOTE: in the past, pre-13.0, I had similar crash related to a PCI-e card with
multiple bars, as described
here:https://forums.freebsd.org/threads/bhyve-pci-passthru-windows-10-problem.74265/
However, the patch cured that, and it has long been incorporated into the bhyve
code... But the card is still in my machine, it's a 4-port Intel NIC. I haven't
yet tried removing this or that card from my system... didn't have the time
yet. But I'd like to keep having it, of course...
My question is, how can I debug this crash? In dmesg it only says:pid 2954
(bhyve), jid 0, uid 0: exited on signal 6
With kindest regards,
Kostya Berger
