From: Rob Landley <rob@landley.net>
To: Vincent Palatin <vpalatin@chromium.org>
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 20:49:21 -0500 [thread overview]
Message-ID: <4DCC8E21.3030405@landley.net> (raw)
In-Reply-To: <BANLkTim2nLrE8f5CACouyyXAO=aOSXTyuw@mail.gmail.com>
On 05/12/2011 08:19 PM, Vincent Palatin wrote:
>>> 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.
Oh good. (The kernel has a couple different VLAN config options, plus
cisco has vlan stuff in its routers... I've been trying not to get any
of this complexity on me.)
>>> 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) ?
Apparently you cannot stick a vlan on -redir, and if you do the error
message is a bit funky (cannot initialize -net user). Good to know...
Yup, that fixed it. Thanks.
By the way, does -redir only apply to -net user? Actually, reading qemu
--help it looks like I should be using hostfwd= but the documentation on
that is REALLY WEIRD:
This option can not be given multiple times, but multiple rules may
be combined.
...
To combine two or more hostfwd rules, simply use a comma as a
delimiter. For example, to combine the two rules mentioned in
the examples above, use the following:
#on the host
qemu -net user,hostfwd=tcp:127.0.0.1:6001-:6000,hostfwd=tcp:5555-::23
Define "may not be given multiple times"...? Oh well, specifying one of
'em seems to work.
Thanks. As you can tell, confusion is sort of my ground state,
Rob
next prev parent reply other threads:[~2011-05-13 1:49 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
2011-05-13 1:49 ` Rob Landley [this message]
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=4DCC8E21.3030405@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 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).