From: Anthony Liguori <aliguori@us.ibm.com>
To: "Andreas Färber" <afaerber@suse.de>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: marcel.a@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-1.6] pc: fix up pc initialization
Date: Tue, 13 Aug 2013 11:12:46 -0500 [thread overview]
Message-ID: <87bo517eo1.fsf@codemonkey.ws> (raw)
In-Reply-To: <520A575F.7040302@suse.de>
Andreas Färber <afaerber@suse.de> writes:
> Am 13.08.2013 17:27, schrieb Paolo Bonzini:
>> Il 13/08/2013 17:11, Andreas Färber ha scritto:
>>>
>>> mst suggested to patch stable-1.5 to disable it there, too. I am not
>>> against but have doubts as to how well that works with migration, since
>>> 1.5.3 is still a bit off and I would expect 1.5.2 -> 1.6.0 migration to
>>> work without guest-visible changes... We could argue that having to use
>>> -M pc-i440fx-1.5 we can also expect users to add -device pvpanic;
>>> question would be how to convey that knowledge of
>>> if-you-use-pc-x.y-then-you-also-need-to-do-Z to users, which
>>> compat_props usually handle under the hood. We could misuse
>>> pvpanic.ioport=0 for that purpose until we have a better solution.
>>
>> pvpanic has no vmstate though, has it? So it won't break migration
>> (needs testing of course).
>
> Just checked, you're right, it doesn't. I somehow assumed it would.
>
>> All that should happen is that after migration you will not get panic
>> notifications on the destination.
>
> Well, how does the Linux driver cope with pvpanic device present on boot
> but not present on panic? ISA PIO is not usually expected to be
> hot-unplugged. ;)
Yeah, disappearing doesn't seem acceptable to me.
We made a mistake with 1.5, now we have to live with it.
Regards,
Anthony Liguori
>
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-08-13 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 12:53 [Qemu-devel] [PATCH for-1.6] pc: fix up pc initialization Michael S. Tsirkin
2013-08-13 13:28 ` Eric Blake
2013-08-13 14:11 ` Anthony Liguori
2013-08-13 14:54 ` Paolo Bonzini
2013-08-13 15:11 ` Andreas Färber
2013-08-13 15:18 ` Michael S. Tsirkin
2013-08-13 15:27 ` Paolo Bonzini
2013-08-13 15:57 ` Andreas Färber
2013-08-13 16:12 ` Anthony Liguori [this message]
2013-08-18 14:46 ` Paolo Bonzini
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=87bo517eo1.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=afaerber@suse.de \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).