Bug 243297

Summary:	bhyve - FreeBSD guest won't boot after update to 12.1 on E5-2620 v4
Product:	Base System	Reporter:	Armin Pirkovitsch <sperber>
Component:	bhyve	Assignee:	freebsd-virtualization (Nobody) <virtualization>
Status:	New ---
Severity:	Affects Only Me	CC:	benoitc, markj
Priority:	---
Version:	12.1-RELEASE
Hardware:	amd64
OS:	Any

Description Armin Pirkovitsch freebsd_committer

2020-01-12 18:26:03 UTC

After updating to 12.1 (with and without p1) (as well as clean 12.1 install) my FreeBSD guests fail to boot.

CPU: Xeon E5-2620 v4 (2x) (I mention this as it works fine on my i7 server)

It always stops exactly with / after this line:
/boot/entropy size=0x1000

The same guests work fine on a clean 12.0-p12 install.

Any hints how I could debug that problem? (btw. due to bug 241079 I can't test stable)

Comment 1 Mark Johnston freebsd_committer

2020-01-12 20:01:58 UTC

Can you share the bhyve invocation you're using?  Does the other server also run 12.1?

Comment 2 Armin Pirkovitsch freebsd_committer

2020-01-12 20:09:55 UTC

I use vm-bhyve and a pretty basic config

> loader="bhyveload"
> cpu=sockets=2,cores=4,threads=2
> memory=80G
> network0_type="virtio-net"
> network0_switch="public"
> network0_mac="...."
> disk0_type="virtio-blk"
> disk0_name="disk0.img"
> uuid="..."

Log entry:
> Jan 12 19:12:26: bhyveload -m 80G -e autoboot_delay=3 -d /tank/vm/FreeBSD-Builder/disk0.img FreeBSD-Builder
> Jan 12 19:12:30:  [bhyve options: -c sockets=2,cores=4,threads=2 -m 80G -AHP -U .... -u]
> Jan 12 19:12:30:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/tank/vm/FreeBSD-Builder/disk0.img -s 5:0,virtio-net,tap1,mac=....]
> Jan 12 19:12:30:  [bhyve console: -l com1,stdio]

yes - both machines have been updated on the same day to 12.1

Comment 3 Armin Pirkovitsch freebsd_committer

2020-03-23 15:57:32 UTC

Just tested stable/12 and the bug is gone there - so from my understanding it should be solved with 12.2-RELEASE.

Comment 4 benoitc 2022-04-03 08:06:35 UTC

i reproduce it with freebsd 13.0p8 . The other appliance is provided as a qcow image with freebsd 12. I have no contol on this appliance. I s there a way to bypass it?