From: Sasha Levin <levinsasha928@gmail.com>
To: "Decker, Schorschi" <schorschi.decker@bankofamerica.com>
Cc: Avi Kivity <avi@redhat.com>,
"Richard W.M. Jones" <rjones@redhat.com>,
kvm <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Guest kernel device compatability auto-detection
Date: Fri, 26 Aug 2011 09:22:45 +0300 [thread overview]
Message-ID: <1314339765.3647.22.camel@lappy> (raw)
In-Reply-To: <559DD0FA4608774CA06F6DFA0F16FE830C96C30D@ex2k.bankofamerica.com>
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.
next prev parent reply other threads:[~2011-08-26 6:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 5:21 [Qemu-devel] Guest kernel device compatability auto-detection Sasha Levin
2011-08-25 5:33 ` Avi Kivity
2011-08-25 7:32 ` Richard W.M. Jones
2011-08-25 7:40 ` Sasha Levin
2011-08-25 7:48 ` Richard W.M. Jones
2011-08-25 10:01 ` Richard W.M. Jones
2011-08-25 16:25 ` Decker, Schorschi
2011-08-26 6:22 ` Sasha Levin [this message]
2011-08-26 8:04 ` Richard W.M. Jones
2011-08-26 10:18 ` Sasha Levin
2011-08-26 10:28 ` Richard W.M. Jones
2011-08-25 21:48 ` Anthony Liguori
2011-08-26 6:08 ` Sasha Levin
2011-08-26 8:43 ` Richard W.M. Jones
2011-08-26 8:40 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1314339765.3647.22.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=schorschi.decker@bankofamerica.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).