Am 15.02.2013 11:23, schrieb Gordan Bobic: > Why on earth would you want to stack two layers of virtualization? Is one virtualization layer not slow enough for > you? to put a complex infrastructure "as it is" in a deploayable and saveable image and test even VMotion/HA and network migrations between different clusters while virtualize them all with their real IP-addresses to test, adapt and migrate configurations? and no, nested virtualization is not that slow a Fedora 17 x86_64 guest boots here in 10 seconds inside a ESXi5 running on top of VMware Workstation with a Fedora 18 x86_64 host on the bare metal KVM is way behind VMware here, but starts to support it in general, but that does not mean ESXi will run fine while the other way around works these days > I suspect you can only nest virtualization like this if your inner virtualization layer doesn't require hardware > virtualization extensions (e.g. 32-bit kqemu inside a VM). I don't know off the top of my head if the > virtualization hardware extensions can be leveraged when nesting VMs, and most modern solutions require hardware > virtualization extensions why do you not use google if you know the term "nested virtualization"? that is why EPT was invented http://www.windowsitpro.com/article/virtual-machine-vm-virtualizationserver/workstation-8-nested-virtualization-141250
Attachment:
signature.asc
Description: OpenPGP digital signature
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
