qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Christoffer Dall <christoffer.dall@linaro.org>,
	"eric.auger@st.com" <eric.auger@st.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Ashok Kumar <ashoks@broadcom.com>,
	Eric Auger <eric.auger@linaro.org>
Subject: Re: [Qemu-devel] [PULL 5/5] hw/arm/virt: Support legacy -nic command line syntax
Date: Mon, 18 Jan 2016 09:32:21 -0700	[thread overview]
Message-ID: <1453134741.32741.85.camel@redhat.com> (raw)
In-Reply-To: <CAFEAcA-__iZNVY2PUhouuraAQfu4obu5oqMbGABcNXiz1zMtyg@mail.gmail.com>

On Mon, 2016-01-18 at 16:00 +0000, Peter Maydell wrote:
> On 18 January 2016 at 15:55, Alex Williamson <alex.williamson@redhat.
> com> wrote:
> > On Mon, 2016-01-18 at 15:54 +0100, Eric Auger wrote:
> > > On 01/18/2016 03:14 PM, Peter Maydell wrote:
> > > > ...but presumably the x86 folks have been here before us
> > > > and know how this should work :-)
> > 
> > No, we haven't.  vfio-pci devices are opaque on x86, we don't
> > know or care that they're NICs or HBAs or GPUs or whatever.
> >  If you don't want the default NIC, turn it off with -net none.
> >  Don't want graphics, -nographics.  Default QEMU devices may be
> > useful for the commandline, but do they really matter in
> > practical use?
> 
> "User is expected to use -net none" is a fine answer to "how
> this should work"...
> 
> (I was thrown off track because http://wiki.qemu.org/Documentation/Ne
> tworking
> doesn't document '-net none', and also -net is the legacy
> syntax -- is there a -netdev equivalent?)

My guess would be that -netdev is often used in conjunction with
-nodefaults and therefore it becomes unnecessary to explicitly disable
it.  Thanks,

Alex

  parent reply	other threads:[~2016-01-18 16:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 14:34 [Qemu-devel] [PULL 0/5] target-arm queue Peter Maydell
2016-01-11 14:34 ` [Qemu-devel] [PULL 1/5] i.MX: move i.MX31 CCM object to register array Peter Maydell
2016-01-11 14:34 ` [Qemu-devel] [PULL 2/5] hw/dma/xilinx_axidma: remove dead code Peter Maydell
2016-01-11 14:34 ` [Qemu-devel] [PULL 3/5] xlnx-zynqmp: Add support for high DDR memory regions Peter Maydell
2016-01-11 14:34 ` [Qemu-devel] [PULL 5/5] hw/arm/virt: Support legacy -nic command line syntax Peter Maydell
2016-01-18 13:29   ` Eric Auger
2016-01-18 13:34     ` Peter Maydell
2016-01-18 13:57       ` Eric Auger
2016-01-18 14:14         ` Peter Maydell
2016-01-18 14:54           ` Eric Auger
2016-01-18 15:55             ` Alex Williamson
2016-01-18 15:57               ` Eric Auger
2016-01-18 16:00               ` Peter Maydell
2016-01-18 16:29                 ` Markus Armbruster
2016-01-18 16:32                 ` Alex Williamson [this message]
2016-01-11 16:11 ` [Qemu-devel] [PULL 0/5] target-arm queue Peter Maydell

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=1453134741.32741.85.camel@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=ashoks@broadcom.com \
    --cc=christoffer.dall@linaro.org \
    --cc=eric.auger@linaro.org \
    --cc=eric.auger@st.com \
    --cc=peter.maydell@linaro.org \
    --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).