qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Migration issues and possible solutions (Very long)


From: Gerd Hoffmann
Subject: Re: [Qemu-devel] Migration issues and possible solutions (Very long)
Date: Fri, 27 Nov 2009 15:23:00 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4

  Hi,

- Dor/mst proposal of optional features

   This came from previous discussions, Dor want to put optional fields
   in the savevm protocol that target can just discard.

Taking that one to the next level: Simply save all fields with name and size. qemu can skip and ignore unknown fields load time. No version numbers are needed any more (except for loading old images), and all the issues with non-linear version numbering of devices are suddenly gone.

The big drawback: it only helps for 0.12+ because that pretty much depends on having vmstate on both sending and receiving side.

If qemu-0.12 should be able to save qemu-0.11 too, we could go for something simple, like a static list of device+savevm versions, without creating a maintainance nightmare because it has to handle only the single migrate-to-0.11 special case.

cheers,
  Gerd





reply via email to

[Prev in Thread] Current Thread [Next in Thread]