> I don't think live migration is particularly difficult. You > need a APIs > to read and write the PIC+LAPIC states, and you write the > state into the
This is partily true party not. Like what did in Xen, a live migration in kernel side need to consider not only device state, but also cpu state. Especially when live migration happens when a VCPU get valid IDT_Vectoring, we need to save all various cpu states, (What current code did to "push back" an vector can't service us with apic in kernel), and we have NMI state to save too. I didn't look into user level migration yet, it may be covered or not, but kernel level migration makes it different. Anyway I know your position now. > qemu device model, which already supports migration. You can > even live > migrate from a userspace PIC+LAPIC to a kernel PIC+LAPIC as the format > is the same. CPU registers work the same way in kvm/qemu. > > -- > error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
