From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35953) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPYzA-0002ms-Ta for qemu-devel@nongnu.org; Mon, 17 Mar 2014 10:57:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPYz6-0000Y6-24 for qemu-devel@nongnu.org; Mon, 17 Mar 2014 10:57:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:13109) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPYz5-0000Y1-Qw for qemu-devel@nongnu.org; Mon, 17 Mar 2014 10:57:47 -0400 Date: Mon, 17 Mar 2014 14:57:41 +0000 From: "Richard W.M. Jones" Message-ID: <20140317145741.GA24641@redhat.com> References: <53270678.8090901@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] virtio device error reporting best practice? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Dave Airlie , Laszlo Ersek , "qemu-devel@nongnu.org" , Seiji Aguchi On Mon, Mar 17, 2014 at 02:40:09PM +0000, Peter Maydell wrote: > On 17 March 2014 14:28, Laszlo Ersek wrote: > > On 03/17/14 07:02, Dave Airlie wrote: > >> The main reason I'm considering this stuff is for security reasons if > >> the guest asks for something really illegal or crazy what should the > >> expected behaviour of the host be? (at least secure I know that). > > > > exit(1). > > No thanks -- the guest should never be able to cause QEMU > to exit (in an ideal world). Use > qemu_log_mask(LOG_GUEST_ERROR, ...) > and continue. Don't look too closely at the spice backend ... https://bugzilla.redhat.com/buglist.cgi?component=spice&list_id=2320267 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org