All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: xen-devel@lists.xensource.com
Subject: Re: [Xen-users] xl and vifname
Date: Wed, 28 Dec 2011 15:10:54 +0000	[thread overview]
Message-ID: <20111228151054.GC4221@bitfolk.com> (raw)
In-Reply-To: <1325084532.24422.8.camel@liuw-desktop>

Hi Wei,

On Wed, Dec 28, 2011 at 03:02:12PM +0000, Wei Liu wrote:
> On Wed, 2011-12-28 at 14:31 +0000, Andy Smith wrote:
> > Ditto here, being able to give a vif a specific name is required.
> 
> I'm a bit confused. xl parses 'vif' names for both HVM and PV guest. I
> think you're using QEMU as network backend when you run HVM guest?
> 
> Well if backend is netback, the vif name is hardcoded as "vif%d.%d" --
> see $KERNEL/drivers/net/xen-netback/interface.c:xenvif_alloc. xl has
> nothing to do with this because the creation of vif is automatically
> done when FE connects to BE.

I haven't followed the thread; I just saw it here on xen-devel that:

"You might want to communicate to xen-devel that you rely on
[vifname support]"

Currently we use xm and xend, specify vifname in the PV guest's
config in order to get a dom0 network interface of a given name.
That functionality is required for us.

If I misunderstood then I apologise; it seemed that it was being
indicated that this functionality didn't exist with xm and there
were no plans to provide it.

Cheers,
Andy

  reply	other threads:[~2011-12-28 15:10 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 [this message]
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
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=20111228151054.GC4221@bitfolk.com \
    --to=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 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.