Zachary Amsden wrote:
If I had a gentoo install,
Yes, but then you'd be a gentoo user. ;)
I would probably go so far as to want to recompile everything after migration across CPU vendors; things like NMIs, MSRs, thermal controls and sleep states are also vendor dependent and either need to be emulated both ways, re-invented in a new way entirely, or just dropped.
Many of those things are meaningless for a guest to see or control.
I don't think cross-CPU vendor hot migration is particularly compelling, although it certainly is possible, the payoff doesn't seem worth the implementation cost and you will find a maze of brambly thorns blocking your path.
We see people trying to do it, and for good reasons. The selling point of VMs is that they can install their thingy once, and it becomes independent from its hardware environment, to the extent that they can update their hardware without having to worry about its effects on their guests. With a stable OS and live migration, its reasonable to consider a guest VM undergoing multiple hardware upgrade transitions with no downtime.
I think the general approach is to have a compatible<->performance slider which disables/enables non-portable features. Migrating between Intel/AMD is just a slightly more extreme point on the continuum of allowing people to migrate between different models within one manufacturer's line.
J _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
