qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: pkrempa@redhat.com, marcel.a@redhat.com, libvir-list@redhat.com,
	mst@redhat.com, qemu-devel@nongnu.org, rhod@redhat.com,
	anthony@codemonkey.ws, Paolo Bonzini <pbonzini@redhat.com>,
	afaerber@suse.de
Subject: Re: [Qemu-devel] [libvirt] pvpanic plans?
Date: Thu, 22 Aug 2013 14:02:48 -0600	[thread overview]
Message-ID: <52166E68.5070609@redhat.com> (raw)
In-Reply-To: <52166974.4030703@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]

On 08/22/2013 01:41 PM, Laszlo Ersek wrote:
> On 08/22/13 21:19, Paolo Bonzini wrote:
>> Il 22/08/2013 19:15, Laszlo Ersek ha scritto:
>>>> 2) On all versions, <on_crash> will only work if the element is there.
>>>
>>> I like this, because, if on_crash doesn't work without panic_notifier
>>> *at all*, then we can just drop panic_notifier, and make on_crash mean
>>> (on_crash && panic_notifier) in the original sense.
>>>
>>> IOW, drop "panic_notifier", and make "on_crash" work *always*.
>>
>> No, we cannot because of backwards compatibility.  VMs could have no
>> on_crash element (which means <on_crash>destroy</on_crash>) and yet the
>> guest admin could expect them to reboot on panic.
> 
> Ah. I thought "no on_crash" meant <on_crash>ignore</on_crash>, or
> something like that -- if on_crash was absent, the guest wouldn't see a
> working pvpanic device in ACPI, and wouldn't trigger the event in qemu.

Unfortunately, <on_crash>ignore</on_crash> does not exist in current
libvirt codebase, and <on_crash> is always present on output (if omitted
on input, it is present as <on_crash>destroy</on_crash> on output; but
MOST vms have it as <on_crash>restart</on_crash> thanks to
virt-install's defaults).

In short, libvirt's problem is that older libvirt basically ignored the
setting (whether default of destroy or set by virt-manager to restart),
BOTH of those common options are most sensibly implemented by having a
panic device, but adding a panic device is guest visible, and therefore
must be controlled by some NEW piece of XML.  If we add
<on_crash>ignore</on_crash, and teach virt-install to start using it,
that will help new guests, but won't change the problem for existing guests.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  reply	other threads:[~2013-08-22 20:03 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 16:10 [Qemu-devel] pvpanic plans? Paolo Bonzini
2013-08-22 16:44 ` Anthony Liguori
2013-08-22 17:53   ` Laszlo Ersek
2013-08-22 18:25     ` Anthony Liguori
2013-08-27  8:42       ` Richard W.M. Jones
2013-08-22 19:16     ` Paolo Bonzini
2013-08-22 20:09       ` Anthony Liguori
2013-08-22 20:36         ` Laszlo Ersek
2013-08-22 20:39           ` Anthony Liguori
2013-08-23  8:52             ` Paolo Bonzini
2013-08-22 21:08         ` Peter Maydell
2013-08-27  8:06         ` Richard W.M. Jones
2013-08-27 13:08           ` Ronen Hod
2013-08-27 13:20             ` Richard W.M. Jones
2013-08-27 13:26               ` Anthony Liguori
2013-08-27 13:57                 ` Richard W.M. Jones
2013-08-27 13:13       ` [Qemu-devel] [libvirt] " Daniel P. Berrange
2013-08-27 13:17         ` Anthony Liguori
2013-08-27 13:21         ` Richard W.M. Jones
2013-08-22 17:15 ` [Qemu-devel] " Laszlo Ersek
2013-08-22 18:33   ` Anthony Liguori
2013-08-22 19:44     ` Christian Borntraeger
2013-08-22 19:19   ` Paolo Bonzini
2013-08-22 19:41     ` Laszlo Ersek
2013-08-22 20:02       ` Eric Blake [this message]
2013-10-24  2:39 ` Hu Tao
2013-10-29 16:01   ` Markus Armbruster
2013-10-31 14:30   ` Michael S. Tsirkin
2013-10-31 14:32     ` Eric Blake
2013-10-31 14:34       ` Anthony Liguori
2013-10-31 14:39       ` Paolo Bonzini
2013-10-31 14:52         ` Michael S. Tsirkin
2013-10-31 14:56           ` Paolo Bonzini
2013-10-31 15:09             ` Michael S. Tsirkin
2013-10-31 15:26               ` Paolo Bonzini
2013-10-31 15:45                 ` Michael S. Tsirkin
2013-10-31 15:56                   ` Paolo Bonzini
2013-10-31 16:14                     ` Michael S. Tsirkin
2013-10-31 16:17                       ` Paolo Bonzini
2013-10-31 16:26                         ` Michael S. Tsirkin
2013-10-31 16:38                           ` Paolo Bonzini
2013-10-31 16:48                             ` Michael S. Tsirkin
2013-10-31 16:52                               ` Paolo Bonzini
2013-10-31 17:00                                 ` Michael S. Tsirkin
2013-10-31 17:09                                   ` Paolo Bonzini
2013-10-31 17:01                             ` Michael S. Tsirkin
2013-10-31 17:10                               ` Paolo Bonzini
2013-10-31 17:18                                 ` Michael S. Tsirkin
2013-10-31 18:03                                   ` Paolo Bonzini
2013-10-31 16:28                         ` Michael S. Tsirkin
2013-10-31 14:47       ` Michael S. Tsirkin
2013-10-31 14:49         ` Eric Blake
2013-10-31 15:07           ` Michael S. Tsirkin
2013-11-04  9:25     ` Christian Borntraeger

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=52166E68.5070609@redhat.com \
    --to=eblake@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=lersek@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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).