Avi Kivity <avi@xxxxxxxxxx> writes: > On 01/07/2010 02:33 PM, Anthony Liguori wrote: >> >> There's another option. >> >> Make cpuid information part of live migration protocol, and then >> support something like -cpu Xeon-3550. We would remember the exact >> cpuid mask we present to the guest and then we could validate that >> we can obtain the same mask on the destination. > > Currently, our policy is to only migrate dynamic (from the guest's > point of view) state, and specify static state on the command line > [1]. > > I think your suggestion makes a lot of sense, but I'd like to expand > it to move all guest state, whether dynamic or static. So '-m 1G' > would be migrated as well (but not -mem-path). Similarly, in -drive > file=...,if=ide,index=1, everything but file=... would be migrated. Becomes a bit clearer with the new way to configure stuff: -drive if=none,id=DRIVE-ID,... <--- host, don't migrate -device ide=drive,drive=DRIVE-ID,... <--- guest, do migrate [...] -- 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
