All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] How to reliably start a bare QEMU target to query capabilities via QMP
Date: Thu, 23 Aug 2012 09:56:10 +0100	[thread overview]
Message-ID: <20120823085610.GA10833@redhat.com> (raw)
In-Reply-To: <87obm28yil.fsf@codemonkey.ws>

On Wed, Aug 22, 2012 at 03:25:38PM -0500, Anthony Liguori wrote:
> "Daniel P. Berrange" <berrange@redhat.com> writes:
> 
> > I've been adapting libvirt to use to the various new QMP commands to
> > query QEMU's capabilities, instead of the hated -help parsing. Obviously
> > the critical part of this is being able to reliably start a bare QEMU
> > process with no actual guest OS configured (no disks, no kernel, etc)
> > and talk to its monitor. I hadn't anticipated problems since I only
> > tested with x86_64 / i386 most of the time, which work well in this
> > respect. Currently I am doing
> >
> >   # $QEMU_BINARY -S \
> >          -no-user-config \
> >          -nodefconfig \
> >          -nodefaults \
> >          -nographic \
> >          -qmp stdio
> >
> >
> > This works for about 50% of the QEMU targets:


> > Do we have to go down the route of adding some sort of "-no-vm" flag to
> > explicitly say we don't care about any of the VM setup parts ? This would
> > be more like what my old patches did which mapped monitors commands
> > onto '-query-XXXXX' command line args, bypassing VM setup, but still
> > using normal QMP monitor interaction.
> >
> > Any other suggestions on how to reliably get a QMP monitor to a target,
> > without any VM config. ?
> 
> -M none.  See the patch I just sent out.  I think we can include this in
> 1.2 as it poses no real risk.

Great, that's an nice elegant solution to the problem :-)


Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2012-08-23  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 20:03 [Qemu-devel] How to reliably start a bare QEMU target to query capabilities via QMP Daniel P. Berrange
2012-08-22 20:25 ` Anthony Liguori
2012-08-23  8:56   ` Daniel P. Berrange [this message]
2012-08-23  6:35 ` [Qemu-devel] unicore32 fails assertion without -kernel (was: How to reliably start a bare QEMU target to query capabilities via QMP) Markus Armbruster

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=20120823085610.GA10833@redhat.com \
    --to=berrange@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@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.