From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Fehlig Subject: Re: vif-bridge: ip link set failed, "name" too long Date: Fri, 26 Jun 2015 00:28:52 -0600 Message-ID: <558CF124.6010504@suse.com> References: <20150625113648.GK3393@perard.uk.xensource.com> <1435233219.32500.53.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1435233219.32500.53.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Anthony PERARD Cc: Xen Devel List-Id: xen-devel@lists.xenproject.org On 06/25/2015 05:53 AM, Ian Campbell wrote: > On Thu, 2015-06-25 at 12:36 +0100, Anthony PERARD wrote: >> Error: argument "tap695cf459-b0-emu" is wrong: "name" too long > Under Linux IFNAMSIZ is 16, whereas this is 18 characters. > > Since our suffix is "-emu" we are adding 4 to the original 14, so we > could/should pick a 2 character suffix to distinguish PV from emulated > interfaces. "-e" perhaps? I'm not familiar with Neutron, but might this break some rules or filters it creates based on the name? Appending stuff to a user-provided name doesn't seem right. One way to avoid the emulated interface is to set libxl_device_nic->nictype = LIBXL_NIC_TYPE_VIF, so only the pv interface is created. In xl.cfg, I suppose that would be vif = [ '...,model=netfront' ] In libvirt domXML ... I realize that doesn't help much if the guest has no pv network driver. I wonder how this is handled in KVM? In the libvirt qemu driver, the default interface model is rtl8139 if is not specified. Does nova add to interfaces for KVM instances? Is it expected that the guest OS has a virtio network driver? Regards, Jim