-----Original Message-----
From: Jim Fehlig
Sent: Sunday, June 24, 2007 11:46 PM
To: Szymanski, Lukasz K
Subject: Re: Code dump
Szymanski, Lukasz K wrote:
Jim -
So like I said, I cleared this hurdle, and found another problem. I
know where it is, but am not sure how to fix it. In XendDomuloader
there is a fifo from which data is supposed to arrive. In my case,
that never happens. I am sending you the various logs and my version
of XendDomuloader so you can tell where the debug statements came
from. If you have any insights on this, I would appreciate it.
Try running domUloader by hand, e.g.
usr/lib/xen/boot/domUloader.py, --verbose
--entry=xvda2:/boot/vmlinuz-2.6-xen,/boot/initrd-xen
/tmp/images/sles10gm-x64-clean.img
Verbose should tell us where domUloader is bailing. The image name
suggests sles10 and not sles10sp1. Perhaps the partition is hda2
instead of xvda2?
1 message in com.xensource.lists.xen-cim[Xen-cim] Python script problems, part 4