[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-cim] Python script problems, part 4


  • To: <xen-cim@xxxxxxxxxxxxxxxxxxx>
  • From: "Szymanski, Lukasz K" <Lukasz.Szymanski@xxxxxxxxxx>
  • Date: Tue, 3 Jul 2007 11:18:58 -0400
  • Delivery-date: Tue, 03 Jul 2007 08:16:50 -0700
  • List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
  • Thread-index: Ace221ZPyVL8T3NoRFuj/7igmSymXgGqF3bw
  • Thread-topic: Python script problems, part 4

 

-----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?

Jim


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.