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
| ||
|
Date: Wed, 29 Feb 2012 12:00:41 +0200 From: Avi Kivity <avi@...hat.com> To: Gleb Natapov <gleb@...hat.com> CC: Wen Congyang <wency@...fujitsu.com>, kvm list <kvm@...r.kernel.org>, KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>, "Daniel P. Berrange" <berrange@...hat.com>, linux-kernel@...r.kernel.org, qemu-devel <qemu-devel@...gnu.org> Subject: Re: [PATCH] kvm: notify host when guest paniced On 02/29/2012 11:55 AM, Gleb Natapov wrote: > > > > > > > How about using a virtio-serial channel for this? You can transfer any > > amount of information (including the dump itself). > > > Isn't it unreliable after the guest panicked? So is calling hypercalls, or dumping, or writing to the screen. Of course calling a hypercall is simpler and so is more reliable. > Having special kdump > kernel that transfers dump to a host via virtio-serial channel though > sounds interesting. May be that's what you mean. Yes. The "panic, starting dump" signal should be initiated by the panicking kernel though, in case the dump fails. -- error compiling committee.c: too many arguments to function -- 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/
Powered by blists - more mailing lists