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

[Xen-devel] Not able to boot domU (root VBD not visible at domU)


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
  • Date: Mon, 31 Oct 2005 17:33:56 -0800
  • Delivery-date: Tue, 01 Nov 2005 01:31:34 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXehFNS6tY5mwTuR2iOu1VXF/1SUA==
  • Thread-topic: 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

Attachment: dom1_output
Description: dom1_output

Attachment: dom1
Description: dom1

Attachment: xend.log
Description: xend.log

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

 


Rackspace

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