From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] KVM call minutes for Feb 8 Date: Thu, 10 Feb 2011 11:00:50 +0100 Message-ID: <4D53B752.1080804@codemonkey.ws> References: <4D51B1C9.3080507@codemonkey.ws> <4D526D0D.9020507@codemonkey.ws> <4D52A86A.1030407@codemonkey.ws> <4D52F20A.7070009@codemonkey.ws> <4D539800.3070802@codemonkey.ws> <20110210090748.GD673@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Blue Swirl , Chris Wright , Markus Armbruster , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Gleb Natapov Return-path: Received: from mail-fx0-f46.google.com ([209.85.161.46]:59354 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753958Ab1BJKBC (ORCPT ); Thu, 10 Feb 2011 05:01:02 -0500 Received: by fxm20 with SMTP id 20so1267319fxm.19 for ; Thu, 10 Feb 2011 02:01:01 -0800 (PST) In-Reply-To: <20110210090748.GD673@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 02/10/2011 10:07 AM, Gleb Natapov wrote: > So what if it is easier, it doesn't mean it is correct thing to do. If we spend the next 10 years trying to do the "correct thing" for some arbitrary definition of correct, that's not terribly useful. It's really simple actually. Let's do the least clever thing and model how hardware actual works. Once we have that, we can try to be better than real hardware (if it's possible). > >> If all composition is done through a factory interface, it doesn't. >> But my main argument here is that we shouldn't try to make all >> composition done through a factory interface--only where it makes >> sense. >> >> So very concretely, I'm suggesting we do the following to target-i386: >> >> 1) make the i440fx device have an embedded ide controller, piix3, >> and usb controller that get initialized automatically. The piix3 >> embeds the PCI-to-ISA bridge along with all of the default ISA >> devices (rtc, serial, etc.). >> > This may be a problem even from security point of view. What if usb code > (ide, serial, parallel) has guest exploitable bug? Currently I can happily > continue running guests if they do not need affected subsystem. If we'll > get it your way I will no longer be able to do so. > qemu -device i440fx,ide=off If you really care to do this. But this desire to remove devices is silly IMHO. Concerns about security are misplaced. If you have to change the way a guest is invoked in order to eliminate security problems, then there's something seriously wrong. Regards, Anthony Liguori