* Laszlo Ersek (ler...@redhat.com) wrote: > The interesting question is, what happens when you power down the VM on > the destination host (= post migration), and launch it again there, from > zero. In that case, the firmware executable file comes from the > *destination host* (it was never persistently migrated from the source > host, i.e. never written out on the dst). It simply comes from the OVMF > package that had been installed on the destination host, by the > sysadmin. However, the varstore pflash does reflect the permanent result > of the previous migration. So this is where things can fall apart, if > both firmware binaries (on the src host and on the dst host) don't agree > about the internal structure of the varstore pflash.
My guess is that overtime we're going to need to find a way to handle this, otherwise we're going to find people having to maintain old versions of OVMF just to keep variable store compatiiblity. Dave > Thanks > Laszlo -- Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
