From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] stubdom: fix mini-os messages log and SDL termination
Date: Thu, 28 Feb 2008 11:30:30 +0000 [thread overview]
Message-ID: <20080228113030.GA5538@implementation.uk.xensource.com> (raw)
stubdom: fix mini-os messages log and SDL termination
We can now let the stubdom-dm script output mini-os messages to
stdout/err so that it gets output to the new
/var/log/xen/qemu-dm-$domname.log
In the SDL case, we must not wait for the VNC server port to appear, as
it won't ever.
Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com>
diff -r af3301aedb3e stubdom/stubdom-dm
--- a/stubdom/stubdom-dm Thu Feb 28 11:11:12 2008 +0000
+++ b/stubdom/stubdom-dm Thu Feb 28 11:26:16 2008 +0000
@@ -62,32 +62,23 @@ done
creation="xm create -c stubdom-$domname target=$domid memory=32"
-(while true ; do sleep 60 ; done) | $creation > /var/log/xen/qemu-dm-$domid.log &
+(while true ; do sleep 60 ; done) | $creation &
#xterm -geometry +0+0 -e /bin/sh -c "$creation ; echo ; echo press ENTER to shut down ; read" &
consolepid=$!
-
-# Wait for vnc server to appear
-while ! vnc_port=`xenstore-read /local/domain/$domid/console/vnc-port`
-do
- # Check that the stubdom job is still alive
- kill -0 $consolepid || term
- sleep 1
-done
-
-################
-# DEBUG: tcpdump
-#while ! stubdomid=`xm domid stubdom-$domname`
-#do
-# sleep 1
-#done
-#xterm -geometry 160x25+0+$height -e /bin/sh -c "tcpdump -n -i vif$stubdomid.0" &
-#xterm -geometry 160x25+0+$((2 * $height)) -e /bin/sh -c "tcpdump -n -i vif$stubdomid.1" &
###########
# vncviewer
if [ "$vncviewer" = 1 ]
then
+ # Wait for vnc server to appear
+ while ! vnc_port=`xenstore-read /local/domain/$domid/console/vnc-port`
+ do
+ # Check that the stubdom job is still alive
+ kill -0 $consolepid || term
+ sleep 1
+ done
+
vncviewer $ip:$vnc_port &
vncpid=$!
fi
reply other threads:[~2008-02-28 11:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080228113030.GA5538@implementation.uk.xensource.com \
--to=samuel.thibault@eu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.