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-api

[Xen-API] XCP 1.0-beta: SM backend driver

To: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] XCP 1.0-beta: SM backend driver
From: Tomoe Sugihara <sugihara@xxxxxxxxxxxxx>
Date: Mon, 29 Nov 2010 16:49:35 +0900
Delivery-date: Sun, 28 Nov 2010 23:51:17 -0800
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 i686; en-US; rv:1.9.1.15) Gecko/20101027 Lightning/1.0b1 Thunderbird/3.0.10
Hi,

I got the following error while testing XCP 1.0 beta with VastSky SM backend:

----------------------
[4779] 2010-11-26 10:22:50.311777       blktap2.activate
[4779] 2010-11-26 10:22:50.311844       lock: acquired 
/var/lock/sm/b9c2db94-bb72-5fae-9848-02c06de4e24d/vdi
[4779] 2010-11-26 10:22:50.319652       ***** BLKTAP2:<function _activate_locked at 
0xb706433c>: EXCEPTION blktap2.UnexpectedVDIType, Target <class '__main__.VASVDI'> 
has unexpected VDI type 'disk'
  File "/opt/xensource/sm/blktap2.py", line 29, in wrapper
    ret = op(self, *args)
  File "/opt/xensource/sm/blktap2.py", line 1299, in _activate_locked
    if self.tap_wanted():
  File "/opt/xensource/sm/blktap2.py", line 922, in tap_wanted
    self.target.vdi)

[4779] 2010-11-26 10:22:50.319711       lock: released 
/var/lock/sm/b9c2db94-bb72-5fae-9848-02c06de4e24d/vdi
[4779] 2010-11-26 10:22:50.322101       ***** vdi_activate: EXCEPTION 
blktap2.UnexpectedVDIType, Target <class '__main__.VASVDI'> has unexpected VDI 
type 'disk'
  File "/opt/xensource/sm/SRCommand.py", line 87, in run
    return self._run_locked(sr)
  File "/opt/xensource/sm/SRCommand.py", line 124, in _run_locked
    return self._run(sr, target)
  File "/opt/xensource/sm/SRCommand.py", line 174, in _run
    caching_params)
  File "/opt/xensource/sm/blktap2.py", line 1286, in activate
    if self._activate_locked(sr_uuid, vdi_uuid, caching_params):
  File "/opt/xensource/sm/blktap2.py", line 29, in wrapper
    ret = op(self, *args)
  File "/opt/xensource/sm/blktap2.py", line 1299, in _activate_locked
    if self.tap_wanted():
  File "/opt/xensource/sm/blktap2.py", line 922, in tap_wanted
    self.target.vdi)
----------------------

This is because blktap2.VDI_PLUG_TYPE doesn't have the key 'disk'.
'disk' for vid_type used be usable in XCP 0.5, but seems like it isn't anymore.

Is there any suggested policies on the value?
I referred to the documentation(http://www.xen.org/files/XenCloud/storage.pdf),
but I couldn't find any.

Incidentally, SHMSR.py also has "disk" as vid_type and should causes an error.

Best,
Tomoe



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-API] XCP 1.0-beta: SM backend driver, Tomoe Sugihara <=