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*
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*
-
-
I mostly live in QEMU, where kvm is this itty bitty thing. Virtualbox and Hyper-V have these huge kernel-side support mechanisms.
-
*host* kernel-side.
-
I haven't looked that closely at Hyper-V, though its vGPU support is super interesting.
-
I think you might always be in Hyper-V, if it's on.
-
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.
End of conversation
New conversation -
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.