[Xen-users] domUloader problem

To:	xen-users@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-users] domUloader problem
From:	"Remigiusz Stachura" <remigiusz.stachura@xxxxxxxxx>
Date:	Mon, 20 Aug 2007 17:22:47 +0200
Delivery-date:	Thu, 30 Aug 2007 02:22:48 -0700
Dkim-signature:	a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Ql0sZv1X/LKJ50AtJDC0DQHUBbiau7zprhMNZa3ujaVcOd1FY3fPrU2sG334PiY5vFPUngS+I8otsxha9Ilk1JMXTRsu606ztdjqSlvKsHrJpz3vhoIwl7TNXNYxgL14kPtEDKNn8Ib/6uNSP4Bp7G0lOBMqBs5W7pfh4X1mVxA=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=eImOVNmUKnewJa2ZTbsE4YyMP0YwHKjETxws+1ccX7ea986H/mlAlA2WTdNzy2bOwFpi68AjQEVig67TWoOwg+E5ul8wPWer4cK7cVCIuGK7bXzMclSwbSDFhgulDKlhDBktubniINraGiqgmcuY0XnuX80h4i8fSKPL8XOxlGc=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-users-request@lists.xensource.com?subject=help>
List-id:	Xen user discussion <xen-users.lists.xensource.com>
List-post:	<mailto:xen-users@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Hi,
I've got debian 64-bit etch0 as DomU working on SLES10SP1 as a Dom0 in
paravirtualized mode. My config is:

ostype="debian"
name="tr2-1"
memory=2048
cpus="5,4"
vcpus=2
uuid=""
on_crash="restart"
on_poweroff="restart"
on_reboot="restart"
localtime=1
builder="linux"
kernel = "/boot/xen/vmlinuz-xen"
ramdisk = "/boot/xen/initrd-xen"
root = "/dev/xvda1 ro"
extra="TERM=xterm 2"
disk=[ 'phy:/dev/cciss/c0d0p9,xvda1,w', 'phy:/dev/cciss/c0d0p10,xvdb1,w' ]
vif = [ 'mac=00:16:3e:35:96:5b, bridge=xenbr0', ]
acpi=0

Kernel vmlinuz-xen is taken from DomU (vmlinuz-2.6.18-5-xen-amd64) and
putted into directory /boot/xen on Dom0.

I have created new config based on the same  DomU filesystem located
at /dev/cciss/c0d0p9 - xvda1 and /dev/cciss/c0d0p10 - swap, but I get
error:

Using config file "./tr2-2".
domUloader error: Partition 'xvda1' does not exist
No handlers could be found for logger "xend"
Error: Boot loader didn't return any data!

tr2-2 config:
builder='linux'
memory = 2048
name = "tr2-2"
cpus = "5,4"
vcpus = 2
vif = [ 'mac=00:16:3e:35:36:5b, bridge=xenbr0' ]
disk = [ 'phy:/dev/c0d0p9,xvda1,w', 'phy:/dev/c0d0p10,xvdb1,w' ]
bootloader = "/usr/lib/xen/boot/domUloader.py"
bootargs = "--entry=xvda1:/vmlinuz,/initrd.img"
root = "/dev/xvda1 ro"
extra = "TERM=xterm 2"
on_poweroff = 'restart'
on_reboot   = 'restart'
on_crash    = 'restart'

/dev/cciss/c0d0p9 is reiserfs partition and is not mounted during
start and working DomU. (tr2-1 was destroyed before creating tr2-2)
I think that creating DomU using domUloader solve my problems with DomU console
(there is no access during boot process to files located in xvda1
partition needed by console:
problem when loading /etc/console/boottime.kmap.gz.
I think it should be located into initrd image.

Thanks for any advice ...
R.S.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users