D
Deleted member 63539
Guest
On that category, we should have forums for VirtualBox and Bhyve. Currently, if we have questions about Bhyve, we can only post it on Off-Topic.
This means I have mistakenly use Off-Topic for my Bhyve threads for a while. Sorry.Bhyve is part of the base OS, so general would be more appropriate. Off-topic is for non-FreeBSD questions or general chit-chat.
It make sense to have a dedicated category for VM. But I guess it will fill with topics similar to "jail vs docker", "jail is not docker", "where is docker" etc!
Then we just open another forums for "OS Level Virtualization" or "Containers". Please do not include jails, focker,... in that Virtualization category. Only Bhyve and VirtualBox, please.
qemu without kvm acceleration shouldn't be included in Virtualization but Emulation. Unless somehow we could get qemu with Bhyve acceleration. I have seen the NetBSD guys have both qemu with the HAXM acceleration and qemu with the NVMM acceleration so I think it's entirely possible. But I do not expect it to be happen because it seemed there is no interests from the Bhyve or qemu developers.What about Qemu? It seems it's never mentioned in a FreeBSD context. For some time i actually thought it was unsupported but from what i can tell it is in the ports collection. How comes it is so unpopular?
I prefer VirtualBox and Bhyve as separate. They serve two completely different purpose. Bhyve is for enterprise virtualization and VirtualBox is for people simply want to run other OSes virtualized. Mixing the two is not something we should do.I'm suggesting a "Virtualization" section, under "Server and networking". That would cover bhyve, Virtualbox, qemu, etc. both as guest and as host. Jails would be included too, as that's also a form of virtualization. There's no point in further splitting it up, you'd end up with nearly empty sections.
No. Bhyve is Bhyve and VirtualBox is VirtualBox. They are completely different products. So please don't mix them.bhyve and virtualbox belong together. Because, a general user does not care if it is in base or not.
Likewise sendmail and postfix belong together.
qemu without kvm acceleration shouldn't be included in Virtualization but Emulation. Unless somehow we could get qemu with Bhyve acceleration. I have seen the NetBSD guys have both qemu with the HAXM acceleration and qemu with the NVMM acceleration so I think it's entirely possible. But I do not expect it to be happen because it seemed there is no interests from the Bhyve or qemu developers.
Irrelevant distinction, they both serve the same purpose and have the same basic principles regardless of their usage. Besides that, I know some of our members use Virtualbox in an enterprise environment.I prefer VirtualBox and Bhyve as separate. They serve two completely different purpose. Bhyve is for enterprise virtualization and VirtualBox is for people simply want to run other OSes virtualized. Mixing the two is not something we should do.
Oh. This is the first time I hear this.Irrelevant distinction, they both serve the same purpose and have the same basic principles regardless of their usage. Besides that, I know some of our members use Virtualbox in an enterprise environment.
VBox utilizes of basic virtualization features of the CPU. There might be a highly optimized version available that uses more VM features of the hardware, for enterprise customers who are willing to pay a license & support fee. Who knows, maybe in the future they will integrate bhyve as a backend.Oh. This is the first time I hear this.