|
From: | Gerd Hoffmann |
Subject: | Re: [Qemu-devel] migration: new sections and backward compatibility. |
Date: | Thu, 07 Jul 2011 09:14:01 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Red Hat/3.1.11-2.el6_1 Thunderbird/3.1.11 |
Hi,
We don't have a hard policy about not merging devices that don't support migration. Since migration must be supported forever, I'd rather see a device get some solid testing before it starts doing live migration. That said, we should probably do this consciously by explicitly marking the device non-migrateable.Can't we just implicitly fail migration whenever there's a device in the tree that doesn't have VMSTATE?
There are cases where the device doesn't need to save state, so that alone doesn't cut it.
cheers, Gerd
[Prev in Thread] | Current Thread | [Next in Thread] |