From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=55407 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PnTKm-0001pK-ID for qemu-devel@nongnu.org; Thu, 10 Feb 2011 05:01:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PnTKg-0007SN-Dk for qemu-devel@nongnu.org; Thu, 10 Feb 2011 05:01:03 -0500 Received: from mail-fx0-f45.google.com ([209.85.161.45]:41447) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PnTKg-0007SB-9M for qemu-devel@nongnu.org; Thu, 10 Feb 2011 05:01:02 -0500 Received: by fxm12 with SMTP id 12so1295658fxm.4 for ; Thu, 10 Feb 2011 02:01:01 -0800 (PST) Message-ID: <4D53B752.1080804@codemonkey.ws> Date: Thu, 10 Feb 2011 11:00:50 +0100 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] KVM call minutes for Feb 8 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> In-Reply-To: <20110210090748.GD673@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: Blue Swirl , Chris Wright , Markus Armbruster , kvm@vger.kernel.org, qemu-devel@nongnu.org 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