What's wrong with what we have in paravirt_ops? Just agreeing on CPUID
doesn't help very much. You still need a mechanism for doing hypercalls
to implement anything meaningful. We aren't going to agree on a
hypercall mechanism. KVM uses direct hypercall instructions, Xen uses a
hypercall page, VMware uses VMI, Hyper-V uses MSR writes. We all have
already defined the hypercall namespace in a certain way.
We've already gone down the road of trying to make standard paravirtual
interfaces (via virtio). No one was sufficiently interested in
collaborating. I don't see why other paravirtualizations are going to
be much different.
Regards,
Anthony Liguori
--
