linux-kernel - Re: [PATCH v11] kvm: notify host when the guest is panicked

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121113021908.GA8176@amt.cnet>
Date:	Tue, 13 Nov 2012 00:19:08 -0200
From:	Marcelo Tosatti <mtosatti@...hat.com>
To:	Sasha Levin <levinsasha928@...il.com>
Cc:	Hu Tao <hutao@...fujitsu.com>, Wen Congyang <wency@...fujitsu.com>,
	kvm list <kvm@...r.kernel.org>,
	qemu-devel <qemu-devel@...gnu.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Avi Kivity <avi@...hat.com>,
	"Daniel P. Berrange" <berrange@...hat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Jan Kiszka <jan.kiszka@...mens.com>,
	Gleb Natapov <gleb@...hat.com>,
	Blue Swirl <blauwirbel@...il.com>,
	Eric Blake <eblake@...hat.com>,
	Andrew Jones <drjones@...hat.com>,
	Luiz Capitulino <lcapitulino@...hat.com>
Subject: Re: [PATCH v11] kvm: notify host when the guest is panicked

On Fri, Nov 09, 2012 at 03:17:39PM -0500, Sasha Levin wrote:
> On Mon, Nov 5, 2012 at 8:58 PM, Hu Tao <hutao@...fujitsu.com> wrote:
> > But in the case of panic notification, more dependency means more
> > chances of failure of panic notification. Say, if we use a virtio device
> > to do panic notification, then we will fail if: virtio itself has
> > problems, virtio for some reason can't be deployed(neither built-in or
> > as a module), or guest doesn't support virtio, etc.
> 
> Add polling to your virtio device. If it didn't notify of a panic but
> taking more than 20 sec to answer your poll request you can assume
> it's dead.
> 
> Actually, just use virtio-serial and something in userspace on the guest.

They want the guest to stop, so a memory dump can be taken by management
interface.

Hu Tao, lets assume port I/O is the preferred method for communication.
Now, the following comments have still not been addressed:

1) Lifecycle of the stopped guest and interaction with other stopped
states in QEMU.

2) Format of the interface for other architectures (you can choose
a different KVM supported architecture and write an example).

3) Clear/documented management interface for the feature.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/