FreeBSD Bhyve Virtualization
vermaden.wordpress.com
FreeBSD Bhyve Virtualization
1–10 of 30 posts
Re: FreeBSD Bhyve Virtualization
#2The 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.
Re: FreeBSD Bhyve Virtualization
#3Hey vermaden, great article! I saw you had some problems with virt-manager, and I did too! There is a solution your problem:
> I was able to start FreeBSD 13.2 installation … but it got frozen at the kernel messages and nothing more happened.
If you notice at the bootloader screen, it says something like "5. Cons: Dual (Serial primary)"
Pressing the 5 key at the bootloader screen will toggle the output from "Serial primary" to "Video primary" or something to that effect. Once you toggle this setting, it should fix the output hanging and you should get a login prompt.
The other way to fix this problem, is through the virt-manager menu, you can simply switch the view from Graphical Console, to the Serial Console. Under View -> Consoles -> Serial 1
Hope this helps make your experience a little better under virt-manager.
Re: FreeBSD Bhyve Virtualization
#4There was a bunch of discussion about the live migration features of bhyve on a recent episode of “Oxide and Friends”
Re: FreeBSD Bhyve Virtualization
#5The 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.
Nested virtualization?
Re: FreeBSD Bhyve Virtualization
#6The 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.
Nested virtualization?
True 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.
Re: FreeBSD Bhyve Virtualization
#7vermaden's site is a must stop for all FreeBSD users. A lot of information and great articles! I'll take a look at bhyve at some point. Thanks for the article, it does seem to be a comprehensive guide to bhyve!
Re: FreeBSD Bhyve Virtualization
#8I check every now and then to see if there is MacOS guest support, I would really like to use BSD as a host and completely drop Apple hardware since they started soldering SSDs. I have the last Intel MBP, and sure ARM is powerful, but in 5 years of heavy use it will be a brick in need of a new mainboard and that makes no sense to me.
I guess the reality is in a year or two I'll land on fedora and proxmox or something. I have seen plenty of interesting content on proxmox and PCIE passthrough, but very little showing actual pro users with this kind of set up so the MacOS workstation VM idea might not be as practical as I'm hoping.
Re: FreeBSD Bhyve Virtualization
#9Great article! As a FreeBSD user (albeit server-side only), I always enjoy reading articles like this. Keep up the good work vermaden, your blog is a real treat!
Bhyve virtualization is of special interest to me, as I'm in the process of writing my own little (small-time, amateur-use only) wrapper for bhyve. Essentially a re-implementation of a subset of churchers/vm-bhyve in python.
I was under the impression that virtio-blk + zvols were the best option for storage (although I didn't do any tests so far, just a naive assumption)! Will definitely explore the nvme + raw-file route now.
Re: FreeBSD Bhyve Virtualization
#10I check every now and then to see if there is MacOS guest support, I would really like to use BSD as a host and completely drop Apple hardware since they started soldering SSDs. I have the last Intel MBP, and sure ARM is powerful, but in 5 years of heavy use it will be a brick in need of a new mainboard and that makes no sense to me. I guess the reality is in a year or two I'll land on fedora and proxmox or something…
Why do you need macOS guest support? IIRC none of the official reasons (like the forced developing/releasing of App Store apps only from macOS) would work in a non-supported virtualised environment due to Apple shenanigans with the hardware and software checks thereof.