From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/1] s390x/css: catch section mismatch on load
Date: Tue, 23 May 2017 14:55:21 +0200 [thread overview]
Message-ID: <23e0910b-a2bc-e571-804d-1c0f033dd1e7@de.ibm.com> (raw)
In-Reply-To: <20170523141821.79db6b2b.cornelia.huck@de.ibm.com>
On 05/23/2017 02:18 PM, Cornelia Huck wrote:
> On Thu, 18 May 2017 13:14:05 +0200
> Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
>
>> Prior to the virtio-ccw-2.7 machine (and commit 2a79eb1a), our virtio
>> devices residing under the virtual-css bus do not have qdev_path based
>> migration stream identifiers (because their qdev_path is NULL). The ids
>> are instead generated when the device is registered as a composition of
>> the so called idstr, which takes the vmsd name as its value, and an
>> instance_id, which is which is calculated as a maximal instance_id
>> registered with the same idstr plus one, or zero (if none was registered
>> previously).
>>
>> That means, under certain circumstances, one device might try, and even
>> succeed, to load the state of a different device. This can lead to
>> trouble.
>>
>> Let us fail the migration if the above problem is detected during load.
>>
>> How to reproduce the problem:
>> 1) start qemu-system-s390x making sure you have the following devices
>> defined on your command line:
>> -device virtio-rng-ccw,id=rng1,devno=fe.0.0001
>> -device virtio-rng-ccw,id=rng2,devno=fe.0.0002
>> 2) detach the devices and reattach in reverse order using the monitor:
>> (qemu) device_del rng1
>> (qemu) device_del rng2
>> (qemu) device_add virtio-rng-ccw,id=rng2,devno=fe.0.0002
>> (qemu) device_add virtio-rng-ccw,id=rng1,devno=fe.0.0001
>> 3) save the state of the vm into a temporary file and quit QEMU:
>> (qemu) migrate "exec:gzip -c > /tmp/tmp_vmstate.gz"
>> (qemu) q
>> 4) use your command line from step 1 with
>> -incoming "exec:gzip -c -d /tmp/tmp_vmstate.gz"
>> appended to reproduce the problem (while trying to to load the saved vm)
>>
>> CC: qemu-stable@nongnu.org
>> Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
>> Reviewed-by: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
>
> Hum, missed that one for my pull request, sorry.
>
> Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
>
> Christian, can you please pick for the next set of s390x patches?
applied to my tree, Thanks.
prev parent reply other threads:[~2017-05-23 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 11:14 [Qemu-devel] [PATCH v2 1/1] s390x/css: catch section mismatch on load Halil Pasic
2017-05-23 12:18 ` Cornelia Huck
2017-05-23 12:55 ` Christian Borntraeger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23e0910b-a2bc-e571-804d-1c0f033dd1e7@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dgilbert@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).