From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwpoZ-0005sN-Ox for qemu-devel@nongnu.org; Fri, 26 Aug 2011 02:22:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QwpoY-0003pN-Ds for qemu-devel@nongnu.org; Fri, 26 Aug 2011 02:22:51 -0400 Received: from mail-wy0-f173.google.com ([74.125.82.173]:43288) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwpoY-0003pH-2J for qemu-devel@nongnu.org; Fri, 26 Aug 2011 02:22:50 -0400 Received: by wyf22 with SMTP id 22so2383038wyf.4 for ; Thu, 25 Aug 2011 23:22:49 -0700 (PDT) From: Sasha Levin In-Reply-To: <559DD0FA4608774CA06F6DFA0F16FE830C96C30D@ex2k.bankofamerica.com> References: <1314249688.3459.23.camel@lappy> <4E55DE90.2020503@redhat.com> <20110825073212.GD3905@amd.home.annexia.org> <1314258034.3692.7.camel@lappy> <20110825074825.GA1106@amd.home.annexia.org> <20110825100124.GA3197@amd.home.annexia.org> <559DD0FA4608774CA06F6DFA0F16FE830C96C30D@ex2k.bankofamerica.com> Content-Type: text/plain; charset="us-ascii" Date: Fri, 26 Aug 2011 09:22:45 +0300 Message-ID: <1314339765.3647.22.camel@lappy> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Guest kernel device compatability auto-detection List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Decker, Schorschi" Cc: Avi Kivity , "Richard W.M. Jones" , kvm , "qemu-devel@nongnu.org" On Thu, 2011-08-25 at 16:25 +0000, Decker, Schorschi wrote: > I would ask two things be done in the design if it goes forward, 1) > have an explicit way to disable this feature, where the hypervisor > cannot interact with the guest OS directly in any way if disablement > is selected. I doubt that this (or anything similar) introduced will even be set to on by default. It has the potential of breaking stuff that would work otherwise (thats why the default boot is with the safest configuration possible). On Thu, 2011-08-25 at 16:25 +0000, Decker, Schorschi wrote: > 2) implement the feature as an agent in the guest OS where the > hypervisor can only query the guest OS agent, using a standard TCP/IP > methodology. I was planning to implementing it by probing the image before actually booting it. This process is completely offline and doesn't require interaction with the guest. The guest isn't even running at that point. -- Sasha.