From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: somlo@cmu.edu, kraxel@redhat.com
Subject: [Qemu-devel] fw cfg files cross-version migration races
Date: Mon, 1 Jun 2015 16:10:54 +0200 [thread overview]
Message-ID: <20150601141054.GA11304@redhat.com> (raw)
Hi all,
At the moment we have devices adding and removing fw cfg file entries.
One problem is that this makes the contents of fw cfg
depend on order of device initialization.
Since the fw cfg file list is not migrated, this means that
guest will break if it is migrated between qemu versions
which generate the list diferently, and if migration triggers
while guest happens to read fw cfg.
As there are plans to extend the use of fw cfg, I think it's
important to fix this issue sooner rather than later.
Ideas:
- sort fw cfg files by name before exposing them to guest
- keep doing what we did for compat machine types,
hope that things don't break too often
More ideas? Comments? Anyone wants to try implementing this?
--
MST
next reply other threads:[~2015-06-01 14:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 14:10 Michael S. Tsirkin [this message]
2015-06-01 14:13 ` [Qemu-devel] fw cfg files cross-version migration races Daniel P. Berrange
2015-06-01 15:32 ` Gabriel L. Somlo
2015-06-01 15:44 ` Michael S. Tsirkin
2015-06-01 18:00 ` Gabriel L. Somlo
2015-06-01 20:31 ` Gabriel L. Somlo
2015-06-02 7:04 ` Laszlo Ersek
2015-06-02 7:11 ` Gerd Hoffmann
2015-06-03 8:31 ` Paolo Bonzini
2015-06-03 16:03 ` Michael S. Tsirkin
2015-06-05 16:05 ` Gabriel L. Somlo
2015-06-08 7:21 ` Gerd Hoffmann
2015-06-08 9:43 ` Michael S. Tsirkin
2015-06-08 11:19 ` Gerd Hoffmann
2015-06-08 11:44 ` Paolo Bonzini
2015-06-08 12:23 ` Gabriel L. Somlo
2015-06-08 12:28 ` Paolo Bonzini
2015-06-08 12:33 ` Gerd Hoffmann
2015-06-08 13:32 ` Gabriel L. Somlo
2015-06-08 15:53 ` Michael S. Tsirkin
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=20150601141054.GA11304@redhat.com \
--to=mst@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
/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).