Xen project Mailing List

Re: [Xen-devel] [PATCH] blktap/blktap2: Fix for incorrect parse disk configuration (xen-unstable)

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>

Date: Sun, 11 Jul 2010 06:06:07 -0700 (PDT)

Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>

Delivery-date: Sun, 11 Jul 2010 06:07:13 -0700

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=EJVGvXS/tt7duImKnaIPTVNDiBHuvrxXdxe+r8b7hpr6FxjAvydif0DMK+8f8lzR1LP2Fk/1pQt1Dw11lFtgJkT2tDwvKYr5tqX7RtbYMHH0gYUWOlIaMYyLqUelXlIWo5YndAAsAGjIU3RB2UcSeLcsjxsDqYZbmYgzA0/kej8=;

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Patching :-

diff -r c514d69c71d8 tools/python/xen/xend/XendBootloader.py
--- a/tools/python/xen/xend/XendBootloader.py    Fri Jun 04 11:39:06 2010 +0100
+++ b/tools/python/xen/xend/XendBootloader.py    Sun Jun 06 23:44:20 2010 +0400
@@ -38,10 +38,15 @@
         msg = "Bootloader isn't executable"
         log.error(msg)
         raise VmError(msg)
-    if not os.access(disk, os.R_OK):
-        msg = "Disk isn't accessible"
-        log.error(msg)
-        raise VmError(msg)
+    attempt = 0
+    while True:
+        if not os.access(disk, os.R_OK) and attempt > 3:
+            msg = "Disk isn't accessible"
+            log.error(msg)
+            raise VmError(msg)
+        else:
+            break
+        attempt = attempt + 1

doesn't help any longer under xen-unstable vs 4.0.1.

Boris.

--- On Sun, 7/11/10, eXeC001er <execooler@xxxxxxxxx> wrote:

From: eXeC001er <execooler@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] blktap/blktap2: Fix for incorrect parse disk configuration (xen-unstable)
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Sunday, July 11, 2010, 5:16 AM

2010/7/11 Boris Derzhavets <bderzhavets@xxxxxxxxx>

After patching xen-unstable (changeset: 21769:a672af698bc3)
Rebuilt and reinstalled xen&tools.
Changed "tap2:tapdisk:vhd" to "tap:vhd"

you can use: "tap:vhd" or "tap:tapdisk:vhd"

root@ServerLSX:~/NexentaStor-Community-3.0.2# xm create -c nexentastor-3.0.2-xen.cfg
Using config file "./nexentastor-3.0.2-xen.cfg".
root@ServerLSX:~/NexentaStor-Community-3.0.2# Error: Device 51952 not connected

root@ServerLSX:/usr/local/NexentaStor-Community-3.0.2# xm create -c nexentastor-3.0.2-xen.cfg
Using config file "./nexentastor-3.0.2-xen.cfg".
Error: Device /dev/xvdp (51952, tap2) is already connected.

Yes, for fix these issues need to use other patch (I will send it during 30 min.)

Boris.

--- On Sun, 7/11/10, eXeC001er <execooler@xxxxxxxxx> wrote:

From: eXeC001er <execooler@xxxxxxxxx>
Subject: [Xen-devel] [PATCH] blktap/blktap2: Fix for incorrect parse disk configuration (xen-unstable)
To: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Sunday, July 11, 2010, 4:16 AM

Current source-code work if use following configuration:
config example: disk=['tap:vhd:/path/../disk.img,xvda,w']

but not work if use:
config example: disk=['tap:tapdisk:vhd:/path/../disk.img,xvda,w']

Error during start DomU: File 'vhd:/path/.../disk.img' doesn't exist.

this patch fix this bug.

Signed-off-by: eXeC001er <execooler@xxxxxxxxx>

Thanks.

-----Inline Attachment Follows-----

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

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