On 01/11/2011 04:09 PM, Anthony Liguori wrote:
Disadvantages:
1) you lose migration / savevm between KVM and non-KVM VMs
This doesn't work today and it's never worked. KVM exposes things
that TCG cannot emulate (like pvclock).
If you run kvm without pvclock, or implement pvclock in qemu, it works
fine. It should work fine for the PIT, PIC, and IOAPIC (never tried it
myself).
If we decide to have a kernel hpet implementation, for example, it would
be good to be able to live migrate from a version without kernel hpet,
to a version with kernel hpet, and have the kernel hpet enabled.
Even as two devices, nothing prevents it from working. Both devices
just have to support each other's savevm format. If they use the same
code, it makes it very easy. Take a look at how the KVM PIT is
implemented for an example of this.
They need to use the same device id then. And if they share code, that
indicates that they need to be the same device even more.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
