Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

VirtualBox KVM Public Release

cyberus-technology.de

Post reply on HN
Print view View original

31–40 of 205 posts

Re: VirtualBox KVM Public Release

#31

Post by prmoustache »

blitzclone wrote: post #21
bradwood wrote: post #13

What does this give me that I don't already get from KVM and virt-manager on Linux? Not getting it.

The out-of-the-box performance of Windows in VirtualBox is very good and usually better than virt-manager (Qemu). You can tune Qemu to great performance as well, but it takes some fiddling. VirtualBox is in general very user friendly. Guest integration (drag'n'drop, clipboard), USB passhthrough and audio support is also top-notch in VBox.

> The out-of-the-box performance of Windows in VirtualBox is very good and usually better than virt-manager (Qemu). You can tune Qemu to great performance as well, but it takes some fiddling. VirtualBox is in general very user friendly.

I haven't found a significative difference but if you have found one and can tune qemu to same level,why don't you share the xml template of your machine to the world and to upstream's virt-manager project?

> Guest integration (drag'n'drop, clipboard), USB passhthrough and audio support is also top-notch in VBox.

These things works well with libvirt too provided you are using the spice-guest-tools.

Re: VirtualBox KVM Public Release

#33

Post by wtf_is_up »

I think this should solve a current issue I have with virtualbox dealing with nested VMs. For example, nested QEMU VM running in a Virtualbox Linux guest causes the guest to lock up. According to virtualbox forum thread, only virtualbox-in-virtualbox nesting is supported, so to get around this I use virt-manager. But I think this kvm backend should solve it.

Re: VirtualBox KVM Public Release

#35

Post by davb »

blitzclone wrote: post #23
davb wrote: post #20

Earlier quoted context omitted.

That appears to be the VirtualBox OSE license, copied from the original Oracle package, not the license for this specific release. It’s unclear how this new derivative or work is licensed.

The intention is to have this under the same license as the VBox open source release. If there is a way to clarify this more on the Github page, please advise. :)

Thanks for the clarification, that’s really helpful. I think a paragraph under a “License” header in the README just reiterating what you said in that reply would be pretty clear.

I’m sure some people would make the assumption that it’s under the same license as the upstream package but in some environments absolutely clarity around licenses is really appreciated.

Re: VirtualBox KVM Public Release

#37

Post by blitzclone »

ImPleadThe5th wrote: post #32

I'm quite inexperienced with Virtualization. Are there benefits to kernel based virtual machines beyond (what I assume is the primary benefit) performance?

The name KVM is a bit confusing. It doesn't do anything fundamental different than VirtualBox. The difference is that KVM comes by default with any Linux. VirtualBox ships it's own Linux kernel module for that. That has drawbacks. You typically can't use the newest Linux or the newest features.

KVM also always has the hottest new (performance-relevant) features, because Intel and AMD will always build their hot stuff into KVM first.

Re: VirtualBox KVM Public Release

#38

Post by blitzclone »

wtf_is_up wrote: post #33

I think this should solve a current issue I have with virtualbox dealing with nested VMs. For example, nested QEMU VM running in a Virtualbox Linux guest causes the guest to lock up. According to virtualbox forum thread, only virtualbox-in-virtualbox nesting is supported, so to get around this I use virt-manager. But I think this kvm backend should solve it.

The KVM backend doesn't have nesting enabled just yet. We're on it.

Re: VirtualBox KVM Public Release

#39

Post by gonzodaruler »

blitzclone wrote: post #38
wtf_is_up wrote: post #33

I think this should solve a current issue I have with virtualbox dealing with nested VMs. For example, nested QEMU VM running in a Virtualbox Linux guest causes the guest to lock up. According to virtualbox forum thread, only virtualbox-in-virtualbox nesting is supported, so to get around this I use virt-manager. But I think this kvm backend should solve it.

The KVM backend doesn't have nesting enabled just yet. We're on it.

Running VirtualBox-KVM in a QEMU-VM with enabled nesting should work though.

Re: VirtualBox KVM Public Release

#40

Post by [deleted] »

ilogik wrote: post #18
codemusings wrote: post #11

Earlier quoted context omitted.

I mean it's Oracle we're talking about here.

"What you think of Oracle, is even truer than you think it is. There has been no entity in human history with less complexity or nuance to it than Oracle." Bryan Cantrill https://www.youtube.com/watch?v=-zRN7XLCRhc&t=1980s

[deleted]
Post reply on HN