| 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
| ||
|
Message-ID: <87a9yprc4v.fsf@rustcorp.com.au> Date: Tue, 24 Jul 2012 14:25:44 +0930 From: Rusty Russell <rusty@...tcorp.com.au> To: Sasha Levin <levinsasha928@...il.com>, mst@...hat.com, penberg@...nel.org, asias.hejun@...il.com Cc: virtualization@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, kvm@...r.kernel.org, avi@...hat.com, anthony@...emonkey.ws, wency@...fujitsu.com, Sasha Levin <levinsasha928@...il.com> Subject: Re: [RFC 0/2] virtio: provide a way for host to monitor critical events in the device On Mon, 23 Jul 2012 22:32:39 +0200, Sasha Levin <levinsasha928@...il.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. -- 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