3 ms·
The only thing missing is migration from old iohyve saved zfs images to vm-bhyve or libvirt Otherwise, a super and very complete guide. Well worth bookmarking
by ggm 3y ago
The only thing missing is migration from old iohyve saved zfs images to vm-bhyve or libvirt
Otherwise, a super and very complete guide. Well worth bookmarking if you want to do virtualised os on FreeBSD.
- moondev 3y agoNested virtualization?
- ggm 3y agoTrue it would be interesting to know how well WSL works. And some of the complex multiple network device configurations, I had iohyve administered virtuals with a backend filestore network as well as a front door. Iohyve used zfs environment vars embedded in the FS to hold configuration which was clever, arguably too clever.
- crest 3y agoThe problem with nested virtualisation is that it isn't fully hardware accelerated. The missing features (shadow paging, etc.) have to emulated in software. Such emulation requires lots of delicate error prone code.
- vermaden 3y agoFrom what I checked the iohyve puts disk images as ZFS zvol volumes like: - /dev/zvol/zroot/iohyve/VMNAME/disk0 So the migration would be: - create your new VM with disk of the same size - check your new VM disk place at 'vm-bhyve': # vm info VM | grep system-path system-path: /vm/VM/disk0.img - copy contents of 'iohyve' disk into VM disk # dd bs=1m if=/dev/zvol/zroot/iohyve/VMNAME/disk0 of=/vm/VM/disk0.img - start your new VM This should work. Same with libvirt/virt-manager - just copy your VM image from /var/lib/libvirt/images/ dir and it should work the same. Hope that helps. Hope that helps.