Il 13/08/2013 17:11, Andreas Färber ha scritto: > > mst suggested to patch stable-1.5 to disable it there, too. I am not > against but have doubts as to how well that works with migration, since > 1.5.3 is still a bit off and I would expect 1.5.2 -> 1.6.0 migration to > work without guest-visible changes... We could argue that having to use > -M pc-i440fx-1.5 we can also expect users to add -device pvpanic; > question would be how to convey that knowledge of > if-you-use-pc-x.y-then-you-also-need-to-do-Z to users, which > compat_props usually handle under the hood. We could misuse > pvpanic.ioport=0 for that purpose until we have a better solution.
pvpanic has no vmstate though, has it? So it won't break migration (needs testing of course). All that should happen is that after migration you will not get panic notifications on the destination. Paolo
