All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org, vpalatin@chromium.org, blauwirbel@gmail.com
Subject: [Qemu-devel] -net interface association behavior change in current -git.
Date: Wed, 11 May 2011 21:39:43 -0500	[thread overview]
Message-ID: <4DCB486F.70509@landley.net> (raw)

In 1.14.0, if I did this:

  qemu -net nic,blah -net user -net nic,blah -net tun,blah

Then the first nic would be -net user, and the second nic would be -net
tun.    In current -git, -net user attaches to the second interface and
-net tun attaches to the first, I.E. the order is reversed.

Either way the first -nic becomes eth0 in Linux and the second becomes
eth1 (I can manually assign mac addresses in order to confirm which is
which), but eth0 used to be the -net user interface and now eth1 is the
-net user interface.

I bisected this to commit 60c07d933c66c4b30a83b but I don't know why it
changed the behavior, and I can't find _documentation_ on having
multiple interfaces transports hooked up to the same qemu instance
anyway.  (It used to work, but possibly that was an accident?)

Any ideas?

Rob

             reply	other threads:[~2011-05-12  2:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  2:39 Rob Landley [this message]
2011-05-12 13:20 ` [Qemu-devel] -net interface association behavior change in current -git Vincent Palatin
2011-05-13  1:10   ` Rob Landley
2011-05-13  1:19     ` Vincent Palatin
2011-05-13  1:49       ` Rob Landley
2011-05-13  6:39         ` Jan Kiszka
2011-05-13 10:31           ` Rob Landley
2011-05-13 10:57             ` Jan Kiszka
2011-05-13  6:15       ` Brad Hards
2011-05-12 14:10 ` Markus Armbruster
2011-05-13  1:48   ` Rob Landley
2011-05-13  6:54     ` Markus Armbruster
2011-05-13 10:34       ` Rob Landley
2011-05-13 12:19         ` Markus Armbruster
2011-05-13 21:45           ` Rob Landley
2011-05-16 14:12             ` Markus Armbruster

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=4DCB486F.70509@landley.net \
    --to=rob@landley.net \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vpalatin@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.