https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293470
Bug ID: 293470
Summary: bhyve: VMs with NUMA configuration fail to start with
certain devices
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bhyve
Assignee: [email protected]
Reporter: [email protected]
Initial test:
bhyve -c 8 -n id=0,size=2048,cpus=0-3 -n id=1,size=2048,cpus=4-7 -m 4096 \
-u -H -P \
-s 0:0,hostbridge \
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
-s 1:0,lpc -s 4:0,e1000,slirp,open \
-s 5:0,virtio-blk,/data/img/fedora.img \
-s 6:0,fbuf,tcp=127.0.0.1:5944 \
-l com1,stdio fedora
This boots fine.
Just for the info, `numactl --hardware` shows the following:
available: 2 nodes (0-1)
node 0 cpus: 0 1 2 3
node 0 size: 2013 MB
node 0 free: 1093 MB
node 1 cpus: 4 5 6 7
node 1 size: 1890 MB
node 1 free: 1035 MB
node distances:
node 0 1
0: 10 20
1: 20 10
Configurations that do not boot:
1. Replacing e1000 with virtio-net.
bhyve prints:
fbuf frame buffer base: 0x1728d7200000 [sz 33554432]
I can connect with VNC, but only see a black screen.
When running `bhyvectl --destroy` on it, it prints:
vm_run error -1, errno 6
vm_run error -1, errno 6
vm_run error -1, errno 6
vm_run error -1, errno 6
vm_run error -1, errno 6
vm_run error -1, errno 6
vm_run error -1, errno 6
2. Same command, keeping e1000, but adding "-s 2:0,xhci,tablet" leads to the
same result.
3. Same command, keeping e1000, but adding "-s 2:0,virtio-rnd" leads to the
same result.
I'm running -CURRENT as of end of January. I didn't use this feature
previously, so don't know if it worked previously with these devices.
--
You are receiving this mail because:
You are the assignee for the bug.
