From: erin.balid@inoutbox.com
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: After switching from "xm" to "xl" toolstack, can't get Guest networking to work.
Date: Tue, 24 Jan 2012 10:05:29 -0800 [thread overview]
Message-ID: <1327428329.24310.140661027473797@webmail.messagingengine.com> (raw)
In-Reply-To: <1327425015.8709.140661027442201@webmail.messagingengine.com>
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).
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."
exit 0
fi
+ ## TEST ##
+ echo "made it to 003"
...
Then
xl destroy test
xl create /etc/xen/vm/test.cfg
tail -f /tmp/vif-bridge.log
Tue Jan 24 09:59:29 PST 2012: Running /etc/xen/scripts/vif-bridge
online type_if=vif
made it to 001
made it to 002
Tue Jan 24 09:59:29 PST 2012: Running /etc/xen/scripts/vif-bridge
online
made it to 001
made it to 002
Never makes it to "003".
Erin
next prev parent reply other threads:[~2012-01-24 18:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 20:06 After switching from "xm" to "xl" toolstack, can't get Guest networking to work erin.balid
2012-01-21 22:57 ` Roger Pau Monné
2012-01-21 23:04 ` erin.balid
2012-01-22 0:54 ` erin.balid
2012-01-22 11:08 ` Roger Pau Monné
2012-01-22 17:11 ` erin.balid
2012-01-22 17:28 ` Roger Pau Monné
2012-01-22 17:54 ` erin.balid
2012-01-24 23:13 ` Jim Fehlig
2012-01-25 2:01 ` erin.balid
2012-01-25 15:55 ` Jim Fehlig
2012-01-25 16:27 ` erin.balid
2012-01-25 16:47 ` Jim Fehlig
2012-01-22 15:49 ` djmagee
2012-01-23 11:27 ` Ian Campbell
2012-01-23 15:28 ` erin.balid
2012-01-24 14:26 ` Ian Campbell
2012-01-24 15:56 ` erin.balid
2012-01-24 16:41 ` Ian Campbell
2012-01-24 17:10 ` erin.balid
2012-01-24 18:05 ` erin.balid [this message]
2012-01-24 18:19 ` erin.balid
2012-01-24 21:20 ` Ian Campbell
2012-01-24 21:20 ` Ian Campbell
2012-01-24 21:44 ` erin.balid
2012-01-25 3:59 ` erin.balid
2012-01-25 9:35 ` Ian Campbell
2012-01-25 16:19 ` Jim Fehlig
2012-01-25 16:32 ` Ian Campbell
[not found] <mailman.1527.1327510060.1471.xen-devel@lists.xensource.com>
2012-01-25 17:06 ` John McDermott CIV
2012-01-25 17:16 ` Ian Campbell
2012-01-25 17:22 ` John McDermott CIV
2012-01-25 17:33 ` Jim Fehlig
2012-01-25 17:39 ` John McDermott CIV
2012-01-25 18:02 ` Jim Fehlig
2012-01-25 19:20 ` John McDermott CIV
2012-01-25 21:16 ` Jim Fehlig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1327428329.24310.140661027473797@webmail.messagingengine.com \
--to=erin.balid@inoutbox.com \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).