This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: stubdom questions

To: "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>
Subject: [Xen-devel] Re: stubdom questions
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Date: Mon, 25 Feb 2008 12:56:35 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 25 Feb 2008 03:57:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080219113941.GF21201@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>, Keir <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
References: <20080219113941.GF21201@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14

Zhai, Edwin, le Tue 19 Feb 2008 19:39:41 +0800, a écrit :
> I have a try with HVM stubdomain on r17062, but failed to make on 32b 
> platform.
> Attached patch can fix it, but don't know if okay.

That is how such issues have usually been solved so I guess in principle
it is.  Is your code coming from freebsd too?

> After installation, I failed to start stubdom. So I created it manually

See the commented "xm create" line in the stubdom-dm script, to enable

> 1. I use default vnclisten. Does it matter?


> #----------------------------------------------------------------------------
> # address that should be listened on for the VNC server if vnc is set.
> # default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp
> #vnclisten="localhost"

So if your vnc-listen setting is e.g. localhost, the VNC server of the
stubdom will be restricted to the stub domain itself, and you won't be
able to connect.

> 2. Seems qemu in stubdom has some issue and couldn't update the 'vnc-port' in 
> xenstore.

Actually mini-os has no name resolving support so that it won't be able
to understand the default "localhost" for vnclisten and hence not start

> Or the stubdom didn't run at all.

It did: messages like

******************* BLKFRONT for /local/domain/45/device/vbd/5632 **********

come from Mini-OS and mean that qemu is currently connecting to the
block backend.

> 3. "Create /etc/xen/stubdom-hvmconfig" in readme -- seems "hvmconfig" should 
> match the domain name rather than config file.

Oh indeed, here is a patch to fix that and other documentation/debugging

- Document that for vnclisten names and should not be used.
- Documentation cosmetic fixes
- Dump qemu output to the usual logs

Signed-off-by: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>

diff -r e85399173769 stubdom/README
--- a/stubdom/README    Tue Feb 12 16:59:08 2008 +0000
+++ b/stubdom/README    Mon Feb 25 11:51:48 2008 +0000
@@ -16,10 +16,12 @@
 In your HVM config "hvmconfig",
-- use VNC, set vnclisten to "" for instance:
+- use VNC, set vnclisten to "" for instance.  Do not use a host 
+as Mini-OS does not have a name resolver.  Do not use since then you
+will not be able to connect to it.
+vnc = 1
+vnclisten = ""
 - use /usr/lib/xen/bin/stubdom-dm as dm script
@@ -28,14 +30,15 @@
 - comment the disk statement:
 #disk = [  'file:/tmp/install.iso,hdc:cdrom,r', 'phy:/dev/sda6,hda,w', 
'file:/tmp/test,hdb,r' ]
-Create /etc/xen/stubdom-hvmconfig ("hvmconfig" must match your main config 
+Create /etc/xen/stubdom-hvmconfig (where "hvmconfig" is your HVM guest domain
+name) with
-vif=[ 'ip=', 'ip=,mac=aa:00:00:12:23:34']
+kernel = "/usr/lib/xen/boot/stubdom.gz"
+vif = [ 'ip=', 'ip=,mac=aa:00:00:12:23:34']
 disk = [  'file:/tmp/install.iso,hdc:cdrom,r', 'phy:/dev/sda6,hda,w', 
'file:/tmp/test,hdb,r' ]
 - is the IP for vnc,
-- 'ip=,mac=' is the same net configuration as in the hvmconfig script,
+- 'ip=,mac= etc...' is the same net configuration as in the hvmconfig
 - and disk = is the same block configuration as in the hvmconfig script.
--- a/stubdom/stubdom-dm        Tue Feb 12 16:59:08 2008 +0000
+++ b/stubdom/stubdom-dm        Mon Feb 25 11:51:48 2008 +0000
@@ -62,11 +62,12 @@
 creation="xm create -c stubdom-$domname target=$domid memory=32"
-(while true ; do sleep 60 ; done) | $creation &
+(while true ; do sleep 60 ; done) | $creation > 
/var/log/xen/qemu-dm-$domid.log &
 #xterm -geometry +0+0 -e /bin/sh -c "$creation ; echo ; echo press ENTER to 
shut down ; read" &
+# Wait for vnc server to appear
 while ! vnc_port=`xenstore-read /local/domain/$domid/console/vnc-port`
         # Check that the stubdom job is still alive

Xen-devel mailing list