Why is converting a VirtualBox image to Hyper-V such a PITA? Why can't VirtualBox just use Hyper-V as the underlying hypervisor? Why can't Hyper-V use the VirtualBox image format directly? Or at least OVA format? *sigh*
-
Show this thread
-
Replying to @andreasdotorg
"Why can't Linux just use the Windows as the underlying kernel" I mean, don't get me wrong, they built WSL but there was no "just" to that.
2 replies 0 retweets 5 likes -
Replying to @dakami
Virtualization is much less of a surface than a whole whopping kernel. But it was a mostly rhetorical question anyways...
1 reply 0 retweets 0 likes -
Replying to @andreasdotorg
Sort of. Think of something like USB forwarding, where you might have an ioctl in one hypervisor and it's just a virtual PCIe device in another with the rest in userspace. This is just a messy thing to abstract.
1 reply 0 retweets 0 likes -
Replying to @dakami
As nothing like this is handled in the hypervisor itself, but rather in the guest and host VMs, you'd think there should be a way to abstract that. *handwaving a lot*
1 reply 0 retweets 0 likes -
Replying to @andreasdotorg
I mostly live in QEMU, where kvm is this itty bitty thing. Virtualbox and Hyper-V have these huge kernel-side support mechanisms.
1 reply 0 retweets 0 likes -
-
Replying to @dakami @andreasdotorg
I haven't looked that closely at Hyper-V, though its vGPU support is super interesting.
1 reply 0 retweets 0 likes -
Replying to @dakami @andreasdotorg
I think you might always be in Hyper-V, if it's on.
1 reply 0 retweets 0 likes
Yes, you are. That kind of is the reason why I want it, because this way some hypervisor based security features are enabled. But of course you can spawn more VMs from there.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.