From: Andrea Bolognani <abologna@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, marcel@redhat.com, drjones@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] q35: Improve sample configuration files
Date: Thu, 02 Feb 2017 11:39:35 +0100 [thread overview]
Message-ID: <1486031975.3484.17.camel@redhat.com> (raw)
In-Reply-To: <1486021764.20628.29.camel@redhat.com>
On Thu, 2017-02-02 at 08:49 +0100, Gerd Hoffmann wrote:
> Oh yes, the wonderful confusing world of default devices ;)
>
> So, if you run qemu with "-nodefaults" it will not add those two
> devices.
And I wouldn't have it any other way ;)
> If you add a video card manually (via -device or config file entry) qemu
> will not add the default video card.
>
> Likewise, if you add a NIC manually, qemu will not add the default
> ethernet device (and IIRC creating the default netdev will be skipped
> too).
This has the potential to give you some unexpected results
but I'd say it's still entirely reasonable.
So what do you think, should q35-emulated.cfg recommend the
use of -nodefaults the same way q35-virtio-*.cfg do and add
the video card (cirrus-vga?) and Ethernet adapter explicitly?
The advantage in doing so would be that we would provide
maybe slightly more documentation, and we would be able to
plug the Ethernet adapter at 19.0 instead of 02.0, which as
I understand it matches real hardware better.
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2017-02-02 10:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 17:20 [Qemu-devel] [PATCH v2] q35: Improve sample configuration files Andrea Bolognani
2017-02-02 7:49 ` Gerd Hoffmann
2017-02-02 10:39 ` Andrea Bolognani [this message]
2017-02-02 11:49 ` Gerd Hoffmann
2017-02-02 14:42 ` Marcel Apfelbaum
2017-02-02 15:20 ` Andrea Bolognani
2017-02-02 20:38 ` Marcel Apfelbaum
2017-02-02 22:13 ` Gerd Hoffmann
2017-02-02 22:21 ` Marcel Apfelbaum
2017-02-03 8:39 ` Andrea Bolognani
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=1486031975.3484.17.camel@redhat.com \
--to=abologna@redhat.com \
--cc=drjones@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcel@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).