WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Bugs with block devices to domU - let's find solution
From: Guryanov Dmitry <dimak@xxxxxxxxxxxx>
Date: Tue, 18 Oct 2005 21:06:51 +0400
Delivery-date: Tue, 18 Oct 2005 17:03:57 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
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 ?


P.S.
To start domU i comment out block in backend driver, where this parameter must be obtained and give explicitly value for that variable:

file -    linux-.../drivers/xen/blkback/xenbus.c
function - backend_changed

replace
---------------------
   err = xenbus_scanf(NULL, dev->nodename,
              "physical-device", "%li", &pdev);
if (XENBUS_EXIST_ERR(err))
       return;
---------------------

with, for example:
---------------------
pdev=0x307;   //hda7 - physical device
err=1;
---------------------


--
Guryanov Dmitry

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

<Prev in Thread] Current Thread [Next in Thread>