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] vbd devices stuck in Initialising/InitWait

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] vbd devices stuck in Initialising/InitWait
From: "Christopher S. Aker" <caker@xxxxxxxxxxxx>
Date: Tue, 28 Mar 2006 17:34:25 -0600
Delivery-date: Tue, 28 Mar 2006 23:36:11 +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: Thunderbird 1.5 (Windows/20051201)
Sorry for the cross-post. I'm looking for advice on where next to debug my problem outlined here:

http://lists.xensource.com/archives/html/xen-users/2006-03/msg00850.html

Not all vbds are coming up in my domU. This happens randomly, so rebooting a time or two will bring them back, but it's unpredictable. Normally it's only the even numbered devices, but I have seen an odd one missing.

This can happen regardless of if I specify the devices in a conf file, or start a domU paused and add them with block-attach.

Xen-unstable, changeset Sun Mar 26 11:50:39 2006 +0100 9441:30ae67d6e5f0

For a missing device:
dom0:~# xenstore-read /local/domain/0/backend/vbd/77/770/state
2
dom0:~# xenstore-read /local/domain/77/device/vbd/770/state
1

Normally:
dom0:~# xenstore-read /local/domain/0/backend/vbd/77/769/state
4
dom0:~# xenstore-read /local/domain/77/device/vbd/769/state
4

According to the xenbusState values, the frontend is Initialising, and the backend is in InitWait. From my (very basic) understanding of the code in the frontend and backend drivers, it looks to me like the backend is waiting for the frontend driver to finish initialising and switch to XenbusStateInitialised, but that's never happening...

Any help you could offer debugging this issue would be appreciated.

Thanks,
-Chris

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