From: Paolo Bonzini <pbonzini@redhat.com>
To: Michal Privoznik <mprivozn@redhat.com>,
zhenwei pi <pizhenwei@bytedance.com>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>,
Greg KH <gregkh@linuxfoundation.org>,
qemu-devel@nongnu.org, linux-kernel@vger.kernel.org,
"yelu@bytedance.com" <yelu@bytedance.com>
Subject: Re: discuss about pvpanic
Date: Wed, 8 Jan 2020 11:05:02 +0100 [thread overview]
Message-ID: <05c5fcc0-24bd-ae6e-6bb8-23970ab0b56c@redhat.com> (raw)
In-Reply-To: <d0c57f84-a25c-9984-560b-2419807444e1@redhat.com>
On 08/01/20 10:58, Michal Privoznik wrote:
>> the kernel-side patch certainly makes sense. I assume that you want the
>> event to propagate up from QEMU to Libvirt and so on? The QEMU patch
>> would need to declare a new event (qapi/misc.json) and send it in
>> handle_event (hw/misc/pvpanic.c). For Libvirt I'm not familiar, so I'm
>> adding the respective list.
>
> Adding an event is fairly easy, if everything you want libvirt to do is
> report the event to upper layers. I volunteer to do it. Question is, how
> qemu is going to report this, whether some attributes to GUEST_PANICKED
> event or some new event.
I think it should be a new event, using GUEST_PANICKED could cause upper
layers to react by shutting down or rebooting the guest.
Thanks,
Paolo
next prev parent reply other threads:[~2020-01-08 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 8:25 discuss about pvpanic zhenwei pi
2020-01-08 9:36 ` Paolo Bonzini
2020-01-08 9:58 ` Michal Privoznik
2020-01-08 10:05 ` Paolo Bonzini [this message]
2020-01-08 10:33 ` [External] " zhenwei pi
2020-01-08 12:14 ` 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=05c5fcc0-24bd-ae6e-6bb8-23970ab0b56c@redhat.com \
--to=pbonzini@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=libvir-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mprivozn@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=qemu-devel@nongnu.org \
--cc=yelu@bytedance.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).