From: Gerd Hoffmann <kraxel@redhat.com>
To: Paolo Bonzini <pbonzini@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, 08 Dec 2009 17:34:03 +0100 [thread overview]
Message-ID: <4B1E7FFB.1000104@redhat.com> (raw)
In-Reply-To: <1862782368.1376061260288689974.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
On 12/08/09 17:11, Paolo Bonzini wrote:
>>>> Add global command line option to disable default devices.
>>>
>>> Should -readconfig imply this?
>>
>> Hmm, not sure. Why do you think this would be useful?
>
> 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. So I tend to thing -readconfig should not automagically
turn on -nodefaults to avoid unpleasent surprises for users.
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.
cheers,
Gerd
next prev parent reply other threads:[~2009-12-08 16:34 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 [this message]
2009-12-08 16:39 ` Paolo Bonzini
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=4B1E7FFB.1000104@redhat.com \
--to=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 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).