Combining Xenner, Xen and KVM into a giant furball


One Line Summary

Making the world a better place by enabling people to switch between Xen, Qemu and KVM as they wish.


Currently a user can either use Xen to run Xen PV/HVM guests or KVM to run KVM HVM guests. But why does it have to be that way? We’re all using Qemu in the background anyways, right?

This will be a discussion on how to integrate Xen PV stubs into Qemu, so we get the chance of using Xen PV guests in Qemu/KVM/Xen HVM. But I don’t want to stop there – maybe there’s even more potential of cooperation. Why not use Xen HVM PV drivers in KVM? Imagine a world where one is all and all is one. Amazing, eh?


virtualization kvm xen qemu xenner paravirtualization hvm


  • Biography

    Alexander started working for Novell about 3 years ago. Since then he worked on fancy things like mkinitrd, qemu and KVM.

    Whenever something really useful comes to his mind, he tends to implement it. Among his more well-known projects are Mac OS X virtualization, the modular SUSE initrd and nested SVM. He is also the official maintainer of KVM for PowerPC and Qemu for S390x.

    On the publicly invisible side he worked on SUSE Studio backend parts, keeping appliance building secure and fast.

Leave a private comment to organizers about this proposal