From: Wei Liu <wei.liu2@citrix.com>
To: Andy Smith <andy@strugglers.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
wei.liu2@citrix.com
Subject: Re: [Xen-users] xl and vifname
Date: Wed, 28 Dec 2011 15:56:15 +0000 [thread overview]
Message-ID: <1325087775.24422.25.camel@liuw-desktop> (raw)
In-Reply-To: <20111228153758.GE4221@bitfolk.com>
On Wed, 2011-12-28 at 15:37 +0000, Andy Smith wrote:
> Hi Wei,
>
> On Wed, Dec 28, 2011 at 03:25:57PM +0000, Wei Liu wrote:
> > Does xm serve your purpose -- specifying dom0 network interface of a
> > given name (rather then using vifX.X)?
>
> Yes. We need to statically configure the vif names in order to have
> them be the same every time, and to know which virtual machine
> configuration they belong to. Not have them change every time the VM
> is restarted.
>
> (Yes I am aware that it would be possible to translate the vifX.Y
> string into a domU name and go from there, but that adds a lot of
> complexity)
>
> > If it can serve you purpose, can you verify which network backend you
> > are using by running following command:
> >
> > $ ps aux | egrep '(qemu|net)'
>
> This didn't match anything. These are PV domUs and there isn't a
> process in dom0 for each domU's netback. This is 4.0.1 on Debian
> stable.
>
What's your dom0 kernel version? The newer kernel (2.6.32 3.X) should
have something like netback/0. However, historical kernel doesn't have
that.
Hmm... Maybe I misunderstood something here. I skimmed code from 2.6.18
to 3.0, it all hardcodes vif names. Maybe the toolstack alters interface
name after creation.
I will spend some time on this and get back to you later.
> > If you're running netback and you can use you preferred name for the
> > interface, then a similar fix for xl should be possible.
>
> Something like:
>
> vif = [ "mac=00:16:3e:8e:ac:0a, ip=192.168.82.198, vifname=vm-85" ]
>
> has worked for us for ~5 years through Xen 3.x and 4.x.
>
Alright, got it.
Wei.
> Cheers,
> Andy
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-12-28 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111217135342.DDB9E3806B9@mx1.internecto.net>
[not found] ` <CAFivhP=Uw=e8M_JsE2_fRpT5KtqYuKEf_Jdm2aEQz17iT_vHMw@mail.gmail.com>
2011-12-28 11:19 ` [Xen-users] xl and vifname Pasi Kärkkäinen
2011-12-28 13:59 ` chris
2011-12-28 14:31 ` Andy Smith
2011-12-28 15:02 ` Wei Liu
2011-12-28 15:10 ` Andy Smith
2011-12-28 15:14 ` Andy Smith
2011-12-28 15:25 ` Wei Liu
2011-12-28 15:37 ` Andy Smith
2011-12-28 15:56 ` Wei Liu [this message]
2012-01-05 18:28 ` Stefano Stabellini
2012-01-05 18:47 ` Stefano Stabellini
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=1325087775.24422.25.camel@liuw-desktop \
--to=wei.liu2@citrix.com \
--cc=andy@strugglers.net \
--cc=xen-devel@lists.xensource.com \
/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).