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


Fwd: [Xen-API] Host Down VDI Locked

To: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: Fwd: [Xen-API] Host Down VDI Locked
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Thu, 24 Feb 2011 00:35:55 +0300
Delivery-date: Wed, 23 Feb 2011 13:34:23 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:content-type; bh=++mjr7vrZSrKBC8RWya7f+QYhodnmW4+YXHssyaBGNg=; b=UYHRySI4eHHNQZb8nkazjFuc5pa5Mz2nkqMSi3pmEBskZbG4XsM68TlJAvvvVzd0FP r+++VXakRkVej4gWDq6n68OyzZdLkocsaH68t5Tfy7I5mqPtIWPE5I1IH4l9iwGXs2iO 9c/TijR3Fj7Ctj6ig7Fm57Bi33hKhXy018pVE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; b=DQ33zTAquWQdzrlOqxVr0ybpBQoIn+OOvC903GvEP8c4EGVNsZLfjdGIFa6on41JFD nmv5+zfweLWMaaVOYFGnO0bKi2o9yq+XoTHXBdC5sWdFE/6S2YjYPfF5Z3zsLSyFpWto yFity00uVydTKDy+h6hdWLplo8g7o+WpJhPZA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101226 Icedove/3.0.11

1. XCP main part (xapi) is written not in Python, but OCaml.
2. You just met a well known bug of b1, was fixed in newer versions.

-------- Original Message --------
Subject: [Xen-API] Host Down VDI Locked
Date: Thu, 24 Feb 2011 02:39:42 +0530
From: Rushikesh <rushikesh.jadhav@xxxxxxxxxx>
To: xen-api@xxxxxxxxxxxxxxxxxxx

Hello all,

I am using and studying XCP from past 2 month and have got my self a
little acquainted with its architectural working.

My setup: 3 XCP 1beta hosts and shared iSCSI storage.  ( not the rc3 )

I have just started getting my hands dirty on code. (Python is very new
for me)

I had a case when my host was hard rebooted while VM on it were running.
And now all are refusing to start with Exception "VDI is unavailable".

So, when I started reading the traceback more closely I found that the
exception is generating at

File "/opt/xensource/sm/blktap2.py", line 1230, in _add_tag
if sm_config.get("writable") == "true":
    raise util.SMException("VDI %s already attached RW" % vdi_uuid)

I compared a crashed VDI and non crashed and saw that the crashed VDI
still has  a writable : true in sm-config.

# xe vdi-param-list uuid=03dfd013-bdd0-4c76-b099-4ad30d4018b6   (
Crashed VDI )

sm-config (MRO): writable: true; vhd-parent:
host_OpaqueRef:205c3920-6b6d-c96b-a963-d16cdc21496f: active

# xe vdi-param-list uuid=f701575e-b399-4c02-a930-e3d0dee87b6e    (
Normal VDI )

sm-config (MRO): vhd-parent: 545b2f45-552a-474c-8b4f-f6079907fd21;
vdi_type: vhd

Then I started reading the code but Im getting little lost and I dont
want to make xe database corrupt. Recreating SR is a solution with a
risk of getting all VM rebooted.

So, I tried same scene with XCP1 and all VM were able to get
successfully boot. Nice work guys :)

I really want to understand how you did it and was I on correct path...
I really want to get into some development of XCP but my first problem
is already solved ;)

Thanks for patience and expecting a positive reply.


xen-api mailing list
xen-api mailing list
<Prev in Thread] Current Thread [Next in Thread>