Folks,
It seemed to be easy:
- Copied the vmdx to my freebsd box
- Converted to raw with qemu
- Create a new VM with vm-bhyve, using the converted raw disk
Now the fun starts.
I assume, keep me honest here, the vm conf file uses the UUID to boot, i.e.:
as it boots and can't find the partition to boot from:
Looking at the other server in single mode, glabel status give me:
Any ideas how I can make that VM work with vm-bhyve?
Thanks!
It seemed to be easy:
- Copied the vmdx to my freebsd box
- Converted to raw with qemu
- Create a new VM with vm-bhyve, using the converted raw disk
Now the fun starts.
I assume, keep me honest here, the vm conf file uses the UUID to boot, i.e.:
loader="bhyveload"
cpu=4
memory=2048M
network0_type="virtio-net"
network0_switch="public"
disk0_type="virtio-blk"
disk0_name="disk0.img"
network0_mac="58:9c:fc:0d:35:2e"
uuid="b3f44132-dedd-11e8-a568-0cc47a306164"
as it boots and can't find the partition to boot from:
Trying to mount root from ufs:/dev/da0s1a [rw]...
mountroot: waiting for device /dev/da0s1a...
Mounting from ufs:/dev/da0s1a failed with error 19.
Loader variables:
vfs.root.mountfrom=ufs:/dev/da0s1a
vfs.root.mountfrom.options=rw
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:tank
cd9660:/dev/cd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
mountroot>
Looking at the other server in single mode, glabel status give me:
Name Status Component
ufsid/5acf74a5c6bfdbaa N/A da0s1a
Any ideas how I can make that VM work with vm-bhyve?
Thanks!