From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: pkrempa@redhat.com, marcel.a@redhat.com, libvir-list@redhat.com,
lersek@redhat.com, mst@redhat.com, armbru@redhat.com,
lcapitulino@redhat.com, rhod@redhat.com, kraxel@redhat.com,
anthony@codemonkey.ws, hutao@cn.fujitsu.com, afaerber@suse.de
Subject: [Qemu-devel] [RFC PATCH v2 0/3] Start fixing the pvpanic mess
Date: Wed, 21 Aug 2013 18:43:13 +0200 [thread overview]
Message-ID: <1377103396-24307-1-git-send-email-pbonzini@redhat.com> (raw)
The pvpanic mess is even bigger than anticipated. Let's fix the monitor's
behavior (patch 1), get rid of all traces that the broken pvpanic existed
(patch 2), and give it a new name so that libvirt can detect a design
that works (patch 3).
All downstreams are urged to apply patches 1+2 as soon as they are
merged in QEMU.
Still, there are still other problems to solve.
In QEMU, exposing "-device isa-pvpanic" in the ACPI tables. Quite frankly
I don't have the time to fix this. We have ~3 months though. Patch 3
should not be applied until it is fixed.
Also, libvirt needs to know under which circumstances to add "-device
isa-pvpanic", besides obviously the availability of the device.
IMHO it is just too complicated to retrofit all complications in
<on_crash>. In fact, I suspect <on_crash> would match more closely QEMU's
"internal error" state, and it would be quite useful to add that to the
QEMU driver.
Thus, libvirt could add support for an <on_panic> element with the
following values:
- default, which depends on the hypervisor and is "crash" for Xen,
"ignore" for everything else
- "crash", which is the only supported value on Xen and means "use
the value of <on_crash>"
- ignore, which is the behavior of old libvirt that don't know pvpanic
- restart, destroy, preserve, rename-restart as for <on_crash>. In
particular, preserve can still use the crashed_guest_panicked status,
thus keeping the API compatible.
- pause, to pause the VM (with a new substatus)
<on_panic> would also have a coredump='yes/no' attribute, where yes
is only valid if the element is *not* one of default/crash/ignore.
Only "default" and "ignore" would be accepted for QEMU that does not
support the isa-pvpanic device.
Ideally, the coredump attribute would be added to <on_crash> too
for simplicity (Xen would refuse coredump + rename-restart and
coredump + preserve).
Paolo
Paolo Bonzini (3):
vl: allow "cont" from panicked state
pc: get rid of builtin pvpanic
pvpanic: rename to isa-pvpanic
gdbstub.c | 3 ---
hw/i386/pc_piix.c | 8 --------
hw/i386/pc_q35.c | 6 ------
hw/misc/pvpanic.c | 16 +++-------------
include/hw/i386/pc.h | 3 ---
vl.c | 6 ++----
6 files changed, 5 insertions(+), 37 deletions(-)
--
1.8.3.1
next reply other threads:[~2013-08-21 16:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 16:43 Paolo Bonzini [this message]
2013-08-21 16:43 ` [Qemu-devel] [PATCH 1/3] vl: allow "cont" from panicked state Paolo Bonzini
2013-08-21 16:43 ` [Qemu-devel] [PATCH 2/3] pc: get rid of builtin pvpanic Paolo Bonzini
2013-08-21 17:03 ` Michael S. Tsirkin
2013-08-21 17:02 ` Paolo Bonzini
2013-08-21 17:07 ` Andreas Färber
2013-08-21 17:04 ` Michael S. Tsirkin
2013-08-21 17:33 ` Michael S. Tsirkin
2013-08-21 16:43 ` [Qemu-devel] [PATCH 3/3] pvpanic: rename to isa-pvpanic Paolo Bonzini
2013-08-21 17:01 ` Michael S. Tsirkin
2013-08-21 17:01 ` Paolo Bonzini
2013-08-21 17:07 ` Michael S. Tsirkin
2013-08-21 17:06 ` Paolo Bonzini
2013-08-21 17:31 ` Michael S. Tsirkin
2013-08-22 12:43 ` Laszlo Ersek
2013-08-22 12:41 ` Paolo Bonzini
2013-08-25 10:44 ` Michael S. Tsirkin
2013-08-22 16:50 ` Anthony Liguori
2013-08-25 10:29 ` Michael S. Tsirkin
2013-08-21 17:35 ` Andreas Färber
2013-08-21 17:46 ` Paolo Bonzini
2013-08-21 16:48 ` [Qemu-devel] [RFC PATCH v2 0/3] Start fixing the pvpanic mess Daniel P. Berrange
2013-08-21 16:51 ` Paolo Bonzini
2013-08-21 16:55 ` Daniel P. Berrange
2013-08-21 16:56 ` Paolo Bonzini
2013-08-21 17:10 ` Eric Blake
2013-08-21 17:11 ` Paolo Bonzini
2013-08-22 9:17 ` Daniel P. Berrange
2013-08-21 17:02 ` Eric Blake
2013-08-21 17:10 ` Paolo Bonzini
2013-08-21 17:26 ` Michael S. Tsirkin
2013-08-21 17:30 ` 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=1377103396-24307-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=kraxel@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lersek@redhat.com \
--cc=libvir-list@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rhod@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).