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/
Home Products Support Community News


Re: [Xen-devel] reports of xend not starting

To: Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: Re: [Xen-devel] reports of xend not starting
From: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Date: Fri, 05 Mar 2010 15:05:34 +0900
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 04 Mar 2010 22:06:17 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B9003F5.5080601@xxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4B9003F5.5080601@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thu, 04 Mar 2010 12:03:17 -0700, Jim Fehlig wrote:

>Hi Kan,
>I've received several reports of xend not starting with the following
>[2010-03-04 13:24:10 9096] ERROR (SrvDaemon:349) Exception starting xend (
>Traceback (most recent call last):
>  File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py", 
>line 341, in run
>    servers = SrvServer.create()
>  File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvServer.py", 
>line 261, in create
>    root.putChild('xend', SrvRoot())
>  File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvRoot.py", 
>line 40, in __init__
>    self.get(name)
>  File "/usr/lib64/python2.6/site-packages/xen/web/SrvDir.py", line 84, in 
>    val = val.getobj()
>  File "/usr/lib64/python2.6/site-packages/xen/web/SrvDir.py", line 52, in 
>    self.obj = klassobj()
>  File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvNode.py", 
>line 30, in __init__
>    self.xn = XendNode.instance()
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendNode.py", line 1187
>, in instance
>    inst = XendNode()
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendNode.py", line 161,
> in __init__
>    self._init_PSCSIs()
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendNode.py", line 339,
> in _init_PSCSIs
>    saved_HBA_uuid = saved_pscsis[pscsi_uuid].get('HBA', None)
>KeyError: '044dde78-2896-cb88-2ada-3c03a73c35c1'
>All reported cases involve fresh installs of dom0, so
>/var/lib/xend/state/ is empty.  I wasn't able to reproduce the issue
>myself but a reporter was kind enough to try a debug patch. I found that
>vscsi_util.get_all_scsi_devices() returns several records containing
>same scsi_id.  With /var/lib/xend/state/pscsi.xml non-existent and
>identical scsi_id, we access an element of saved_pscsis that does not
>exist.  In fact, the list is empty.
>The attached patch catches the exception and allows xend to start but
>I'm not sure if this breaks other parts of the code.  It looks safe to
>me but would like your review.

Hi Jim,

Thanks for your report and patch.

Are your SCSI devices multi-path configuration?
If so, the configuration isn't supported by pvSCSI of XenAPI yet.

I added a small fix to your patch.  Could you send your Signed-off-by 

Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>

Best regards,

Attachment: multi_path_scsi.patch
Description: Binary data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>