From: Vincent Palatin <vpalatin@chromium.org>
To: Rob Landley <rob@landley.net>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -net interface association behavior change in current -git.
Date: Thu, 12 May 2011 21:19:42 -0400 [thread overview]
Message-ID: <BANLkTim2nLrE8f5CACouyyXAO=aOSXTyuw@mail.gmail.com> (raw)
In-Reply-To: <4DCC8523.2000501@landley.net>
>> First of all, as you have 2 totally separated subnets in your setup, I
>> think your command-line should use "vlan=" parameter to isolate them,
>> else you will end up with some random routing/broadcasting (and random
>> tends to change over time).
>
> Does the kernel need some sort of vlan support compiled into it for this
> to work, or can the kernel not care?
You don't need anything in your kernel, this is for Qemu network layer
configuration.
>> I'm not using setup with multiple NICs but I would have written something like :
>> qemu -net nic,vlan=1,blah -net user,vlan=1 -net nic,vlan=2,blah -net
>> tun,vlan=2,blah
>>
>> In addition to this, which type of NIC are you using ?
>
> The actual command line is various permutations of:
>
> ~/qemu/qemu/x86_64-softmmu/qemu-system-x86_64 -m 512 -kernel
> ~/linux/linux/arch/x86/boot/bzImage -no-reboot -hda squeeze.ext3 -append
> "root=/dev/hda rw" -net nic,model=e1000,macaddr=52:54:00:11:11:11 -net
> user -redir tcp:9876::22 -net nic,model=e1000,macaddr=52:54:00:22:22:22
> -net tap,ifname=kvm0,script=no,downscript=no
>
> With the parameters reordered to try to beat some controllable behavior
> out of it. (It had a deterministic behavior before the above commit,
> going back at least 2 years. The behavior was changed by the commit.)
>
>> In my understanding, the Linux kernel might assign interface number
>> depending on the order the interfaces are appearing.
>
> It's going in PCI bus order. And the _interfaces_ are still happily in
> PCI bus order both before and after this commit. What's changing is the
> association between interface and -net user or -net tap.
>
> The first one, with macaddr 11:11:11, is always eth0. But before the
> patch, eth0 is -net user, and after the patch eth0 is -net tap.
So, did you try the vlan parameter which is supposed to associate each
interface with the proper thing (IMO the command line order should not
have anything to do with it) ?
--
Vincent
next prev parent reply other threads:[~2011-05-13 1:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 2:39 [Qemu-devel] -net interface association behavior change in current -git Rob Landley
2011-05-12 13:20 ` Vincent Palatin
2011-05-13 1:10 ` Rob Landley
2011-05-13 1:19 ` Vincent Palatin [this message]
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='BANLkTim2nLrE8f5CACouyyXAO=aOSXTyuw@mail.gmail.com' \
--to=vpalatin@chromium.org \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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).