From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Smith Subject: Re: [Xen-users] xl and vifname Date: Wed, 28 Dec 2011 15:10:54 +0000 Message-ID: <20111228151054.GC4221@bitfolk.com> References: <20111217135342.DDB9E3806B9@mx1.internecto.net> <20111228111918.GN12984@reaktio.net> <20111228143123.GB4221@bitfolk.com> <1325084532.24422.8.camel@liuw-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1325084532.24422.8.camel@liuw-desktop> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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