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

Re: [Xen-devel] Bugs with block devices to domU - let's find solution

  • To: "Guryanov Dmitry" <dimak@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Stephan Boni" <boeni@xxxxxx>
  • Date: Tue, 18 Oct 2005 19:23:23 +0200
  • Delivery-date: Tue, 18 Oct 2005 17:20:49 +0000
  • Importance: high
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Priority: Urgent
  • Thread-index: AcXUBmTBOUzdwuBbSI6YGiH8j65x3AAAbd7Q
  • Thread-topic: [Xen-devel] Bugs with block devices to domU - let's find solution

> Hello
> I have the same bug, that've been disscussed before - domU can't find 
> any block devices and crashes with "Unable to mount root fs". 
> I've spend 
> a week under heavy debugging and find, that this bug take 
> place because 
> dom0 backend driver can't read parameter physical-device from 
> xenstore. 
> For example 
> /local/domain/0/backend/vbd/1/776/physical_device, where  1- 
> domU id, 776=0x308 - major and minor numbers of block device, 
> which will 
> used by domU.
> This parameter must be written by script 
> /etc/xen/scripts/block, which 
> must start like /etc/xen/scripts/vif-bridge any time as domU 
> starts, but 
> it doesn't.
> So, there is a question to xen developers: when and how must 
> this script 
> must been started ?

I have this problem too! Can anyone of the xen developers solve this problem? 
It seams, it's the last very critical bug we have.

Thanks a lot.


Xen-devel mailing list



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