On Mon, Sep 01, 2008 at 01:57:52PM +0200, Alexander Graf wrote: > The current generation of virtualization extensions only supports one VM > layer. > While we can't change that, it is pretty easy to emulate the CPU's behavior > and implement the virtualization opcodes ourselves. > > This patchset does exactly this for SVM. Using this, a KVM can run within a > VM. > Since we're emulating the real CPU's behavior, this should also enable other > VMMs to run within KVM. > So far I've only tested to run KVM inside the VM though. > > This was created with help from Joerg Roedel. I don't really know how put this > information in the patchset though. Maybe set him on signed-off-by? > > As always, comments and suggestions are highly welcome.
Very useful work - I need exactly this capability for building a libvirt integration test harness. Running xen within kvm was not letting me test libvirt's Xen HVM handling, and kvm/xen within qemu was too slow to be viable. Hopefully xen/kvm within kvm will suit my test suite perfectly. I'm guessing this requires that you have AMD cpus for the host ? Would it be much more work to support VMX for those with Intel cpus too... Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
