On 7/15/25 03:02, Dan McDonald wrote:
On Jul 14, 2025, at 5:22 PM, Marcel Telka <[email protected]> wrote:
Hi,
I'm trying to explore bhyve for the first time and so I tried some basic
example from the bhyve(8) man page. Surprisingly, it does not work.
# mkfile -n 1g image
# bhyve -c 2 -s 0,hostbridge -s 1,lpc -s 2,virtio-blk,image \
-l com1,stdio -H -P -m 1G vm
virtual machine cannot be booted
# bhyve -c 2 -s 0,hostbridge -s 1,lpc -s 2,virtio-blk,image \
-l com1,stdio -H -P -m 1G vm
vm exit[0]
1.) Check for bhyve processes?
2.) You aren't specifying a boot rom? SHould you be?
Here's a pargs for a bhyve running on SmartOS. Some of it is clearly
SmartOS-specific, but perhaps a vew things here might help, esp. `-l
bootrom,/path/to/boot/rom` ?
[root@nuc ~]# pargs `pgrep bhyve`
4449: bhyve -H -U 170e57f0-4ffe-4fad-af11-c235d04ee16d -B
1,manufacturer=Joyent,produ
argv[0]: bhyve
argv[1]: -H
argv[2]: -U
argv[3]: 170e57f0-4ffe-4fad-af11-c235d04ee16d
argv[4]: -B
argv[5]: 1,manufacturer=Joyent,product=SmartDC
HVM,version=7.20250710T000436Z,serial=170e57f0-4ffe-4fad-af11-c235d04ee16d,sku=001,family=Virtual
Machine
argv[6]: -s
argv[7]: 31,lpc
argv[8]: -l
argv[9]: bootrom,/usr/share/bhyve/uefi-rom.bin
argv[10]: -l
argv[11]: com1,/dev/zconsole
argv[12]: -l
argv[13]: com2,socket,/tmp/vm.ttyb
argv[14]: -s
argv[15]: 0,hostbridge,model=i440fx
argv[16]: -c
argv[17]: 4
argv[18]: -m
argv[19]: 8192
argv[20]: -s
argv[21]:
0:4:0,virtio-blk,/dev/zvol/rdsk/zones/170e57f0-4ffe-4fad-af11-c235d04ee16d/disk0
argv[22]: -s
argv[23]: 6:0,virtio-net-viona,net0
argv[24]: -s
argv[25]: 30:0,fbuf,vga=off,unix=/tmp/vm.vnc
argv[26]: -s
argv[27]: 30:1,xhci,tablet
argv[28]: SYSbhyve-3
[root@nuc ~]#
Dan
Hi Marcel!
Recently i have been playing around with bhyve commands.
Your error message may be raising because youve left the 'old' test
running, be shure to destroy it with bhavectl.
i do it this way:
# cat testubuntu_nvidia.OK.sh
/usr/sbin/bhyve -U bd60bf59-0ed6-61a1-f0ed-b17e99ada165 -A -H \
-B
1,manufacturer=OpenIndiana,product=OpenIndianaHVM,version=1.0,serial=69a18a85-c1df-c266-f620-a99a632d3c11,sku=001,family=VirtualMachine
\
-c 8 -m 16G -w \
-s 31:0,lpc -l bootrom,/usr/share/bhyve/firmware/BHYVE.fd \
-s 0,hostbridge,model=i440fx \
-s 4:0,nvme,/dev/zvol/dsk/rpool1/zones/ubuntu \
-s 6:0,virtio-net-viona,vnic0 \
-s 30:0,fbuf,tcp=0.0.0.0:5905,w=1900,h=900 \
-s 30:1,xhci,tablet \
-S -s 8:0,passthru,/dev/ppt2,rom=/home2/vm/GP108.rom \
-s 8:1,passthru,/dev/ppt3 \
ubuntu
bhyvectl --destroy --vm=ubuntu
i personally like the fbuf vnc device here
"fbuf,tcp=0.0.0.0:5905,w=1900,h=900",
to which you can connect to via "vncviewer host:5905" easily.
Whilst in the vm installation process it may be good to add the nowait
option to it "fbuf,tcp=0.0.0.0:5905,nowait",
this way bhyve waits for a vnc client to connect before it procedes, so
you can see the options in the early boot process,
i think of cdrom install images
-s 3,ahci-cd,/export/ISO/Ubuntu-20.10-mini.iso
Have fun :-)
Stephan
------------------------------------------
illumos: illumos-discuss
Permalink:
https://illumos.topicbox.com/groups/discuss/T0a2ef97770149180-M34ef30a4f0737fed9e046523
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
