From: Martin Kletzander <mkletzan@redhat.com>
To: qemu-devel@nongnu.org
Cc: Jason Baron <jbaron@redhat.com>
Subject: [Qemu-devel] Bug in option parsing
Date: Wed, 22 Aug 2012 17:05:51 +0200 [thread overview]
Message-ID: <5034F54F.30302@redhat.com> (raw)
Hi everybody,
while coding the support for Jason's dump-guest-core option I realized
there is (probably) a problem with the way QEMU parses additional
machine options ('dump-guest-core', 'kvm_shadow_mem' etc.). Running QEMU
with option to -machine works ok, but using '-M' (as libvirt does) works
only w/o additional options, otherwise it ends in an error (the whole
string is probably parsed as a machine name).
Is '-M' so obsolete it shouldn't be used at all or is it just an bug? We
still use '-M' everywhere I know and '-machine' isn't compatible with
older versions and different builds of QEMU.
Should I file a bug or do we have to drop '-M' for this situations?
Have a nice day,
Martin
next reply other threads:[~2012-08-22 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 15:05 Martin Kletzander [this message]
2012-08-22 15:15 ` [Qemu-devel] Bug in option parsing Jan Kiszka
2012-08-22 15:58 ` Martin Kletzander
2012-08-22 16:10 ` Jan Kiszka
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=5034F54F.30302@redhat.com \
--to=mkletzan@redhat.com \
--cc=jbaron@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 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).