From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Joey Connelly <joeyconnelly@u.boisestate.edu>,
qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] QEMU - Security Research Questions
Date: Fri, 7 Oct 2016 10:57:26 +0200 [thread overview]
Message-ID: <20161007085726.GC4589@noname.redhat.com> (raw)
In-Reply-To: <87y421hogo.fsf@dusky.pond.sub.org>
Am 06.10.2016 um 10:27 hat Markus Armbruster geschrieben:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
> > On 06/10/2016 02:10, Joey Connelly wrote:
> >> Hey QEMU dev group,
> >> I'm a graduate student at Boise State University working on my thesis
> >> involving Virtualization/Cloud Computing Security and I wanted to ask a few
> >> questions:
> >>
> >> *[QUESTION#1.]* From within a guest KVM/QEMU process (qemu-system-x86_64
> >> -enable-kvm) can the VM invoke commands on its host - either through QEMU
> >> Monitor Console commands, or by some other means I'm unaware of?
> >>
> >> *[QUESTION#**2.]* Can a host administrator running a guest KVM/QEMU process
> >> have QEMU Monitor Console commands invoked on that guest VM if *no*
> >> "-monitor" option was used?
> >>
> >> *[QUESTION#**3.]* If a host admin creates a KVM/QEMU process with the
> >> "qemu-system-x86_64 -enable-kvm -netdev tap,<...>" options is there a
> >> KVM/QEMU specific way to query the "tap,<...>" information later after the
> >> process has been created? (assuming your admin account maintains ring 0
> >> permissions)
> >
> > No to all three.
>
> The pedantically correct answer to #2 would be "not easily": you'd have
> to play games with a debugger.
I think it's rather "it depends". If you don't actively disable it, the
default (i.e. running qemu-system-x86_64 without any parameters) gives
you an HMP monitor. You can use things like '-monitor none' or
'-nodefaults' to get rid of it.
By the way, Gerd, just 'qemu-system-x86_64 -nodefaults' gives me a GTK
window that contains only the menu bar and almost all options in the
"View" menu make it segfault.
Kevin
prev parent reply other threads:[~2016-10-07 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 0:10 [Qemu-devel] QEMU - Security Research Questions Joey Connelly
2016-10-06 7:15 ` Paolo Bonzini
2016-10-06 8:27 ` Markus Armbruster
2016-10-06 16:07 ` Eric Blake
2016-10-07 8:57 ` Kevin Wolf [this message]
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=20161007085726.GC4589@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=joeyconnelly@u.boisestate.edu \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.