qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Glines <mark@glines.org>
To: Paul Brook <paul@codesourcery.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] emulated lance device crashes in debian-sparc32
Date: Sun, 20 May 2007 06:15:02 -0700	[thread overview]
Message-ID: <20070520061502.2e76772f@chirp> (raw)
In-Reply-To: <200705201125.26929.paul@codesourcery.com>

On Sun, 20 May 2007 11:25:25 +0100
Paul Brook <paul@codesourcery.com> wrote:
> > In my past experience, -net user implies -net nic. 
> 
> You are mistaken. -net user does not imply -net nic.

I just tested this.  You are absolutely right, I was wrong about the
behavior on x86.


> > Hmm.  -net performs 2 separate functions.  First, it sets up the
> > network card in the guest machine (nic, model, and macaddr).
> > Second, it specifies how that card behaves on the host side of
> > things (vlan, user, tap, or socket).
> 
> -net creates devices and attaches them to the virtual network,
> whether they be emulated devices on the host, or devices for
> communication with the "real" world.

Thanks for explaining.

So the issue on sparc was that the device is relied on by the
SS-5 platform code (it sounds like sun4m has this device on-board at
a fixed offset, non-pci), but not initialized properly due to the lack
of -net nic?  Should sun4m imply -net nic,model=lance then?  It doesn't
make much sense to me to ever turn the lance port off, if its
integrated into the platform itself (not a daughter card).

I apologize for the additional confusion; I guess I was confused by the
fact that "-net nic -net user" is the default when no -net options are
provided, and passing "-net user" on the cmdline disabled the implicit
-net nic.

Mark

  reply	other threads:[~2007-05-20 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19 14:16 [Qemu-devel] emulated lance device crashes in debian-sparc32 Mark Glines
2007-05-19 17:03 ` Blue Swirl
2007-05-19 19:08   ` Blue Swirl
2007-05-19 22:08     ` Mark Glines
2007-05-20  7:10       ` Blue Swirl
2007-05-20  9:11         ` Mark Glines
2007-05-20 10:25           ` Paul Brook
2007-05-20 13:15             ` Mark Glines [this message]
2007-05-20 13:51               ` Paul Brook
2007-05-20 15:45             ` Blue Swirl
2007-05-20 19:45               ` Blue Swirl

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=20070520061502.2e76772f@chirp \
    --to=mark@glines.org \
    --cc=blauwirbel@gmail.com \
    --cc=paul@codesourcery.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).