Xen devel - Nov 2005 - Not able to boot domU (root VBD not visible at domU)

Hi,

  I am not being able to boot domU using the current version of
xen-unstable. DomU is not finding its root disk. For some reason the VBD
is not becoming visible. I am not sure but I suspect this may have
something to do with the fact that I am using a machine with an HP smart
array. The array has 2 disks, but is configured to be accessed as two
independent disks (/dev/cciss/c0d0 and /dev/cciss/c0d1). Note that with
old versions of xen-unstable (changeset 6651, September 7) I used to be
able to create domU without ay problem, but not after I moved to the
latest xen-unstable version (changeset 7572, October 31). I believe
there were several changes on the vbd code during this time, but I
don''t
know exactly what changed and how these can be causing this problem.
  I am attaching the output of the domU console after a "xm create",
the
domU config file and the xend log.
  I hope these may give you some hint of why vbd is not working properly
with my machine. Any help is greatly appreciated

  Thanks

  Renato




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

Thanks Ian

  Yes, I was able to boot dom0 on RHEL4 using an initrd.
  I could also boot domU on RHEL4 successfully. The problem
  was indeed redhat 9 which seems to not work well with
  the new way of setting VBD.
  
  Everything was fine when using RHEL4 and a xen-unstable version
  of October 31 (I have to check the exact changeset number when
  I am back at work, Monday). But then I decided to update to the
  newest xen-unstable version (I believe this was on November 3)
  and then was unable to boot domU again (although the behavior
  is somewhat different now: an error message is printed after
  running command xm create).
  I reversed back to the version of October 31 and I have a 
  working version for now. Not sure if others are seing the
  same problem, but some changeset introduced between Oct 31 and 
  Nov 3 is causing a problem with VBD setting for me (i.e. not 
  setting VBD properly when creating domU preventing domU to boot).

  Renato 
   

-----Original Message-----
From: Ian Pratt [mailto:m+Ian.Pratt@cl.cam.ac.uk] 
Sent: Sunday, November 06, 2005 11:53 AM
To: Santos, Jose Renato G
Cc: ian.pratt@cl.cam.ac.uk; ian.pratt@cl.cam.ac.uk
Subject: RE: [Xen-devel] Not able to boot domU (root VBD not visible at
domU)

 
I haven''t booted on an RH9 dom0 for a while, but its possible it
doesn''t
have a new enough hotplug script.

We test Xen under a wide range of different distros including FC2/3/4,
RHEL3/4, SLES9, SuSE Pro 9.3/10 and Debian 
>   Do you think the problem might be related to the fact that I am 
> using an old distro (redhat 9)? I tried using redhat enterprise WS 4, 
> but with this distro I could not even get dom0 to boot (it complained 
> about not being able to open console).
RHEL4 requires an initrd for udev otherwise you won''t have a /dev.

Ian

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