From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [FOR 0.12 PATCH v3 10/21] default devices: add global cmd line option.
Date: Tue, 8 Dec 2009 11:39:43 -0500 (EST) [thread overview]
Message-ID: <1530577928.1378661260290383458.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <4B1E7FFB.1000104@redhat.com>
> > Here is my thinking: if you used -writeconfig, your machine description
> > is (at least in theory) entirely included in the config file including
> > (again in theory) the default devices.
>
> The default devices are *not* included by in the file created by
> -writeconfig.
Yes, that's why I wrote "at least in theory". It doesn't now but that
would be a bug, because it makes -nodefaults another legacy option that
has to be remembered and passed again upon -readconfig.
> Devices created via -readconfig are treated like devices created via
> [device] sections in the config file. So it doesn't matter whenever you
> configure your isa-serial device via command line or config file, in any
> case it will make qemu not create the default serial port.
I was thinking about the case when you don't want at all a particular
default device.
Paolo
next prev parent reply other threads:[~2009-12-08 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1236361906.1375741260288537008.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2009-12-08 16:11 ` [Qemu-devel] Re: [FOR 0.12 PATCH v3 10/21] default devices: add global cmd line option Paolo Bonzini
2009-12-08 16:32 ` Daniel P. Berrange
2009-12-08 16:34 ` Gerd Hoffmann
2009-12-08 16:39 ` Paolo Bonzini [this message]
2009-12-07 12:42 [Qemu-devel] [FOR 0.12 PATCH v3 00/21] default devices: qdev integration Gerd Hoffmann
2009-12-07 12:42 ` [Qemu-devel] [FOR 0.12 PATCH v3 10/21] default devices: add global cmd line option Gerd Hoffmann
2009-12-08 12:46 ` [Qemu-devel] " Paolo Bonzini
2009-12-08 15:58 ` Gerd Hoffmann
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=1530577928.1378661260290383458.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com \
--to=pbonzini@redhat.com \
--cc=kraxel@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).