Re: After switching from "xm" to "xl" toolstack, can't get Guest networking to work.

[Ian Campbell <Ian.Campbell@citrix.com>]

On Tue, 2012-01-24 at 18:05 +0000, erin.balid@inoutbox.com wrote:
> Hi Ian.
> 
> On Tue, Jan 24, 2012, at 09:10 AM, erin.balid@inoutbox.com wrote:
> > > At this point I'm afraid my only suggesting is to drop "echo made it to
> > > XXX" breadcrumbs throughout the script and try to narrow down to the
> > > line which exits.
> > 
> > I'll give that a try and report.
> 
> I can't figure out how to get xl to output to a xend-debug.log (xm does,
> as expected).

They should be going to /var/log/xen/xen-hotplug.

> Using the same log redirection you mentioned before
> 
> edit /etc/xen/scripts/vif-bridge
> 	#!/bin/bash
> +       exec 1>>/tmp/vif-bridge.log
> +       exec 2>&1
> +       echo "`date`: Running $0 $*"
> ...
> +       ## TEST ##
> +       echo "made it to 001"
> 
> 	dir=$(dirname "$0")
> 	. "$dir/vif-common.sh"
> 
> +       ## TEST ##
> +       echo "made it to 002"
> 
> 
> 	domu=$(xenstore_read_default "$XENBUS_PATH/domain" "")
> 	if [ -z "$domu" ]
> 	then
> 	    log debug "No device details in $XENBUS_PATH, exiting."

So, presumably either the xenstore_read_default is failing or domu is
zero length and the script is explicitly bailing here.

However I do not see anything like this anywhere in the hotplug script
shipped with Xen. Either this is a local modification or something done
by your distribution, in which case you should contact them.

What does this node contain under xend?

What does your script go on to do with this domu value?

Perhaps given that xend writes this domain node so perhaps xl should
too. In a few cases (vkb, vfb, console) it does seem to add it but in
others (disk, nic, etc) etc does not. To be honest I don't really see
what purpose it serves to put the domain's name in each device's backend
subdirectory.

Ian.