From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [patch] xen udev rule interfering with openvpn Date: Mon, 21 May 2012 14:04:18 +0100 Message-ID: <1337605458.24660.122.camel@zakaz.uk.xensource.com> 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> <1335347949.28015.19.camel@zakaz.uk.xensource.com> <20375.52677.287182.934829@mariner.uk.xensource.com> <1335348880.28015.24.camel@zakaz.uk.xensource.com> <1335358736.28015.41.camel@zakaz.uk.xensource.com> <20397.10224.96552.711065@mariner.uk.xensource.com> <1336861837.3891.29.camel@dagon.hellion.org.uk> <1337603519.24660.116.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Teck Choon Giam Cc: "xen-devel@lists.xen.org" , Roger Pau Monne , Ian Jackson , M A Young List-Id: xen-devel@lists.xenproject.org On Mon, 2012-05-21 at 13:51 +0100, Teck Choon Giam wrote: > > How does case #7 fail? Do you get both devices created but not placed on > > the bridge or something else? > > I am not sure just in #7 fail to create. The error as below: > > # xm create hvmdomaintest-vifname.cfg > Using config file "./hvmdomaintest-vifname.cfg". > Error: Device 0 (vif) could not be connected. ip link set vif1.0-emu > name b1-emu failed So am I correct that you use vifname="b1"? I wonder if there was any output from this command. Did anything appear in var/log/xen/xen-hotplug.log ? > > > > What names do the devices end up with? ("ifconfig -a", while guest is > > running, "brctl show" also useful) > > Can't even create the hvmdomain with vifname set. > If you mean trying > to capture the ifconfig -a output while xm create hvmdomain with > vifname set... the interval for xm create hvmdomain with vifname set > is too short for me to issue ifconfig -a and brctl show output in > another terminal :( Yes, that's something of a problem. One approach you could try is to add the commands to the vif-bridge script and re-direct to a file. One useful place to do that might be in vif-common.sh just before the do_or_die ip link set "$dev" name "$vifname" calls. e.g. add ( ifconfig -a ; brctl show ) >> /tmp/hotplug.dbg.log or something. You might also want to add ">> /tmp/hotplug.dbg.log" to the door_die so that it's output can also be logged. > Just to confirm... are we going to "throw away" xm in 4.2 and use only xl? Not yet, they will both existing in 4.2 but xl will now be considered the default. We hope to be able to get rid of xm in the 4.3 time frame, but that depends on a variety of factors. > > Thanks. > > Kindest regards, > Giam Teck Choon > > > > > > Ian. > >