From mboxrd@z Thu Jan 1 00:00:00 1970 From: Teck Choon Giam Subject: Re: [patch] xen udev rule interfering with openvpn Date: Fri, 20 Apr 2012 23:26:15 +0800 Message-ID: References: <1334658395.23948.6.camel@zakaz.uk.xensource.com> <1334817587.11493.44.camel@dagon.hellion.org.uk> <1334912603.28331.2.camel@zakaz.uk.xensource.com> <20369.15528.270106.567037@mariner.uk.xensource.com> <1334918900.28331.47.camel@zakaz.uk.xensource.com> <20369.16555.46229.798603@mariner.uk.xensource.com> <1334919613.28331.53.camel@zakaz.uk.xensource.com> <20369.17085.330843.561841@mariner.uk.xensource.com> <1334928115.28331.81.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1334928115.28331.81.camel@zakaz.uk.xensource.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 Cc: M A Young , Roger Pau Monne , Ian Jackson , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Fri, Apr 20, 2012 at 9:21 PM, Ian Campbell wro= te: > On Fri, 2012-04-20 at 12:04 +0100, Ian Jackson wrote: >> Ian Campbell writes ("Re: [Xen-devel] [patch] xen udev rule interfering = with openvpn"): >> > On Fri, 2012-04-20 at 11:55 +0100, Ian Jackson wrote: >> > > I'm not quite up to speed with all the context here but is the reason >> > > that you're not suggesting "xen-" is that that's already used for >> > > something else ? >> > >> > This is to distinguish the vif device from the associated tap device, >> > which would otherwise both be called whatever the user gave as "vifnam= e" >> > in their config, so for vifname=3Dfoo you would get foo (the PV one) a= nd >> > xen-foo (the EMU one) which does the job but doesn't really distinguish >> > them. >> >> Ah, I see. =A0This sounds like more a job for a suffix than a prefix so >> if we can spare 4 chars I would suggest foo-emu. So what is the final prefix/suffix here? Is it "emu-"? Sorry, need to counter check :p Question... vifname is limited to 16 characters? If so, does the configuration for xm/xl check for its allowable length? I mean if a user set vifname more than its allowable length in the domU configuration, would xm/xl show error? Sorry for asking as it isn't clear in manual... ... http://xenbits.xen.org/docs/unstable/misc/xl-network-configuration.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D vifname This keyword is valid for HVM guest devices with type=3Dioemu only. Specifies the backend device name for an emulated device. The default is tapDOMID.DEVID where DOMID is the guest domain ID and DEVID is the device number. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D > > I agree. > > This patch interacts a bit with Roger's hotplug series, I'll rebase on > top of his with this change when he reposts it. Looking forward for your reports ;) > > Ian. > Thanks. Kindest regards, Giam Teck Choon