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] Resizing VDI with Local Caching enabled

To: xen-api <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] Resizing VDI with Local Caching enabled
From: Marco Sinhoreli <msinhore@xxxxxxxxx>
Date: Wed, 23 Mar 2011 12:03:07 -0300
Delivery-date: Wed, 23 Mar 2011 08:04:36 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=sPzp8y/LWa1XjBfWg9AvZjAeqYVGQIrX3HPwnK5NbZ0=; b=FN8Zx4MMuPxkdlkEsP716Ej6HsKXcN2cx3ZkYhm32Y64Mr0l21lq8FhjW+/FQZPku2 K0DuF1fg48/wjqjr57pCM+YtlwQDy+9WoTLd3vYGH1J/Eu1QwSHkk4hnmoMTfmL7XWvM o9zPZkolCqUxDszMb/swHj/7JJ816uKbPUtj4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=AhytX7KJph0rQFeXc9vNjMVqJ6SNltlj73NQrWo9Lin6vPEIHxVte6rI6KYbeMdBF2 UmvwYVJVsCnCBxRGYioJYPWMNlFP0uhHDTOYY3gryM1ul6BftPyqdC4LA4p7Yx/Eswt2 7mNV2hi3t6C3QIEy+bfzDaDWF22UOFALZBZcM=
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
Hello all:

I'm trying resize a VDI cloned from a gold-image. I'm using storage
local caching in my tests. After resize, the virtual machine isn't
booting. Bellow the exception:


<output>
[root@server ~]# vdi=$(xe vbd-list
vm-uuid=fa537d17-1b07-b472-74c7-67b2a2f5561f device=xvda
params=vdi-uuid --minimal)
[root@server ~]# xe vdi-resize uuid=$vdi disk-size=40GiB
[root@server ~]# echo $?
0
[root@server ~]# xe vm-start  uuid=fa537d17-1b07-b472-74c7-67b2a2f5561f
There was an SR backend failure.
status: non-zero exit
stdout:
stderr: Traceback (most recent call last):
  File "/opt/xensource/sm/NFSSR", line 253, in ?
    SRCommand.run(NFSSR, DRIVER_INFO)
  File "/opt/xensource/sm/SRCommand.py", line 246, in run
    ret = cmd.run(sr)
  File "/opt/xensource/sm/SRCommand.py", line 94, in run
    return self._run_locked(sr)
  File "/opt/xensource/sm/SRCommand.py", line 131, in _run_locked
    return self._run(sr, target)
  File "/opt/xensource/sm/SRCommand.py", line 183, in _run
    caching_params)
  File "/opt/xensource/sm/blktap2.py", line 1280, 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 1312, in _activate_locked
    dev_path = self._activate(sr_uuid, vdi_uuid, caching_params)
  File "/opt/xensource/sm/blktap2.py", line 1326, in _activate
    dev_path = self.setup_cache(sr_uuid, vdi_uuid, caching_params)
  File "/opt/xensource/sm/blktap2.py", line 1468, in setup_cache
    local_sr_uuid, scratch_mode)
  File "/opt/xensource/sm/blktap2.py", line 1550, in _setup_cache
    standby=scratch_mode)
  File "/opt/xensource/sm/blktap2.py", line 711, in launch_on_tap
    raise TapdiskFailed(cls.Arg(_type, path), ctl)
blktap2.TapdiskFailed:
Tapdisk(vhd:/var/run/sr-mount/01cbd019-bd89-1296-a4bf-fd9d412f64f4/05732396-9466-4828-9926-2217a10a18c9.vhdcache):
['/usr/sbin/tap-ctl', 'open', '-p', '21483', '-m', '3', '-a',
'vhd:/var/run/sr-mount/01cbd019-bd89-1296-a4bf-fd9d412f64f4/05732396-9466-4828-9926-2217a10a18c9.vhdcache',
'-e', '0', '-2',
'vhd:/var/run/sr-mount/b5631d2b-7931-c93c-39da-5a20978e823b/05732396-9466-4828-9926-2217a10a18c9.vhd']
failed: status=22, pid=21485, errmsg=
</output>

Is it a bug or could I have done something not permitted?

Thoughts?


Cheers!

-- 
Marco Sinhoreli

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