Date: Mon, 16 Aug 2021 21:58:07 +0000 (UTC) From: Kostya Berger via freebsd-virtualization <freebsd-virtualization@freebsd.org> To: "freebsd-virtualization@FreeBSD.org" <freebsd-virtualization@freebsd.org> Subject: Re: debug crash Message-ID: <966160298.1289476.1629151087763@mail.yahoo.com> In-Reply-To: <1464014049.1262174.1629143810702@mail.yahoo.com> References: <1719430894.822301.1629094618334.ref@mail.yahoo.com> <1719430894.822301.1629094618334@mail.yahoo.com> <272551640.837942.1629097084918@mail.yahoo.com> <1464014049.1262174.1629143810702@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_1289475_384571049.1629151087761
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
OK, went back to BIOS and reset to defaults, that fixed it.Too bad we won't=
be able now to figure out the problem... But then, I doubt that anyone wil=
l use this combination of hardware anyway...
With kindest regards,
Kostya Berger
=20
=20
On Monday, 16 August 2021, 22:57:19 GMT+3, Kostya Berger via freebsd-vi=
rtualization <freebsd-virtualization@freebsd.org> wrote: =20
=20
OK, here is another part of the crash message:vm exit[0]
reason=C2=A0 =C2=A0 =C2=A0 =C2=A0 VMX
ip=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000000015eaa03
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 inst_length=C2=A0 =C2=
=A0 2
status=C2=A0 =C2=A0 =C2=A0 =C2=A0 0
exit_reason=C2=A0 =C2=A0 2 (Triple fault)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 qualification=C2=A0 =C2=A0 0x=
0000000000000000
inst_type=C2=A0 =C2=A0 =C2=A0 =C2=A0 0
inst_error=C2=A0 0Additional information: this ONLY happens to Windows-10 b=
ased VMs -- whether existing one or just a Win-10 Pro installation ISO boot=
ed for initial setup.Tried to boot Ubuntu on the same machine -- all boots =
fine.
With kindest regards,
Kostya Berger
=20
=20
=C2=A0 =C2=A0 On Monday, 16 August 2021, 09:58:54 GMT+3, Kostya Berger via =
freebsd-virtualization <freebsd-virtualization@freebsd.org> wrote:=C2=A0=20
=20
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
=20
=20
=C2=A0 =C2=A0 On Monday, 16 August 2021, 09:16:58 GMT+3, Kostya Berger <ber=
gerkos@yahoo.co.uk> wrote:=C2=A0=20
=20
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, i=
t goes as far as offer to type in BitLocker password, after which starts bo=
oting 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: =C2=A02954=
Abort trap =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bhyve -S -c soc=
kets=3D1,cores=3D4,threads=3D2 -m 8G -H -w -s 0,hostbridge -s 4,virtio-blk,=
win-alt.img,sectorsize=3D512/4096 -s 5,ahci-cd,Win10_21H1_English_x64.iso -=
s 29,fbuf,tcp=3D0.0.0.0:5900,w=3D1600,h=3D900,wait -s 30,xhci,tablet -s 31,=
lpc -l com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd w=
indows-10
For the purity of experiment, I tried it with a fresh installation on the s=
ame machine -- same thing. So I assume it is hardware related. As such, I r=
ecall in the past there was a patch=20
NOTE: in the past, pre-13.0, I had similar crash related to a PCI-e card wi=
th multiple bars, as described here:https://forums.freebsd.org/threads/bhyv=
e-pci-passthru-windows-10-problem.74265/
However, the patch cured that, and it has long been incorporated into the b=
hyve 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 hav=
e 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=20
With kindest regards,
Kostya Berger
=20
=C2=A0=C2=A0 =20
------=_Part_1289475_384571049.1629151087761--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?966160298.1289476.1629151087763>