qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] Re: [PATCH 11/11] test-vmstate: add test case to verify


From: Jan Kiszka
Subject: Re: [Qemu-devel] Re: [PATCH 11/11] test-vmstate: add test case to verify we don't change VMState
Date: Wed, 23 Mar 2011 17:36:52 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

On 2011-03-23 17:27, Anthony Liguori wrote:
> On 03/23/2011 10:00 AM, Peter Maydell wrote:
>> On 23 March 2011 14:52, Anthony Liguori<address@hidden>  wrote:
>>> I think we ought to merge VMStateDescription into DeviceInfo.  For
>>> compatibility, we probably need a vmstate_alias name since the device names
>>> don't always map 1-1 with the qdev names.  But this should eliminate the
>>> problem of reusing VMStateDescriptions for multiple devices.
>> That's a feature, not a bug. Consider eg hw/pl110.c -- there
>> are two different DeviceInfo devices but since the underlying
>> implementation is the same you definitely don't want to have
>> two separate VMStateDescription structures to get out of sync.
> 
> No, it's a bug.
> 
> Migration uses the VMStateDescription name as a section identifier.  The 
> section identifiers MUST be unique for a given device.  Otherwise, if 
> both devices are present, migration fails miserably.  It also means that 
> if the wrong devices are created on the destination, instead of 
> predictable failure, you get unpredictable guest corruption.

This is true for incompatible devices, but not for those that are
perfectly exchangeable (like in-kernel vs. user-space irqchip).

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux



reply via email to

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