On Thu, Nov 26, 2009 at 09:56:42AM +0200, Gleb Natapov wrote: > On Thu, Nov 26, 2009 at 02:48:46AM -0500, Kevin O'Connor wrote: > > That would significantly complicate the code, and it wouldn't truly > > solve the issue as some data needs to be stored in the f-segment (eg, > > smbios anchor). > And I don't think support of switching to rm with triple fault worth > complication at all.
I agree. > > IMO, migrating to a new bios doesn't make sense - the bios is an > > application with state - one can't just replace the code. > > > You don't migrate to a new BIOS. You migrate to a new QEMU that happens > to have a new BIOS. And ability to migrate to a newer QEMU is a must. IMO, the ram at 0xf0000 needs to get migrated just like the rest of the ram. Silly example - Linux and APM. On Linux init, it finds the APM vectors from bios and periodically calls them to sleep machine. On migration, a new bios could have a different code location for apm - if Linux calls sleep after migration it jumps into random code and blows up. -Kevin