From: Rusty Russell <rusty@rustcorp.com.au>
To: Sasha Levin <levinsasha928@gmail.com>,
mst@redhat.com, penberg@kernel.org, asias.hejun@gmail.com
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
avi@redhat.com, anthony@codemonkey.ws, wency@cn.fujitsu.com,
Sasha Levin <levinsasha928@gmail.com>
Subject: Re: [RFC 0/2] virtio: provide a way for host to monitor critical events in the device
Date: Tue, 24 Jul 2012 14:25:44 +0930 [thread overview]
Message-ID: <87a9yprc4v.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1343075561-29316-1-git-send-email-levinsasha928@gmail.com>
On Mon, 23 Jul 2012 22:32:39 +0200, Sasha Levin <levinsasha928@gmail.com> wrote:
> As it was discussed recently, there's currently no way for the guest to notify
> the host about panics. Further more, there's no reasonable way to notify the
> host of other critical events such as an OOM kill.
I clearly missed the discussion. Is this actually useful? In practice,
won't you want the log from the guest? What makes a virtual guest
different from a physical guest?
Guest watchdog functionality might be useful, but that's simpler to
implement via a virtio watchdog device, and more effective to implement
via a host facility that actually pings guest functionality (rather than
the kernel).
Cheers,
Rusty.
next prev parent reply other threads:[~2012-07-24 5:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 20:32 [RFC 0/2] virtio: provide a way for host to monitor critical events in the device Sasha Levin
2012-07-23 20:32 ` [RFC 1/2] virtio: Introduce virtio-notifier Sasha Levin
2012-07-23 20:32 ` [RFC 2/2] kvm tools: support virtio-notifier Sasha Levin
2012-07-24 4:55 ` Rusty Russell [this message]
2012-07-24 8:26 ` [RFC 0/2] virtio: provide a way for host to monitor critical events in the device Dor Laor
2012-07-24 12:30 ` Sasha Levin
2012-07-24 12:46 ` Dor Laor
2012-07-24 13:01 ` Sasha Levin
2012-07-25 0:36 ` Rusty Russell
2012-07-25 8:46 ` Amit Shah
2012-07-24 12:23 ` Sasha Levin
2012-07-24 7:44 ` Gleb Natapov
2012-07-24 12:26 ` Sasha Levin
2012-07-24 12:28 ` Gleb Natapov
2012-07-24 12:31 ` Sasha Levin
2012-07-24 12:33 ` Gleb Natapov
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=87a9yprc4v.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=anthony@codemonkey.ws \
--cc=asias.hejun@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=penberg@kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wency@cn.fujitsu.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