'VDI resize failed' errors on nova-compute (XenServer)

Bug #862653 reported by Dan Prince on 2011-09-29
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)

Bug Description

Starting with Git revision bf181c2 (according to smokestack) I'm now getting 'VDI resize failed' errors on nova-compute XenServer:

2011-09-29 14:35:49,665 ERROR nova.compute.manager [-] Instance '1' failed to spawn. Is virtualization enabled in the BIOS? Details: ['SR_BACKEND_FAILURE_110', '', "VDI resize failed [opterr=Command ['/usr/sbin/vhd-util', 'revert', '--debug', '-n', '/var/run/sr-mount/934ab597-ff32-94f6-c1da-9213c7f02a65/366c6ed4-5030-4f7b-b8d9-3f14e51a5743.vhd', '-j', '.journal-366c6ed4-5030-4f7b-b8d9-3f14e51a5743'] failed (2): ]", '']
(nova.compute.manager): TRACE: Traceback (most recent call last):
(nova.compute.manager): TRACE: File "/usr/lib/python2.6/dist-packages/nova/compute/manager.py", line 426, in _run_instance
(nova.compute.manager): TRACE: network_info, block_device_info)
(nova.compute.manager): TRACE: File "/usr/lib/python2.6/dist-packages/nova/virt/xenapi_conn.py", line 190, in spawn
(nova.compute.manager): TRACE: self._vmops.spawn(context, instance, network_info)
(nova.compute.manager): TRACE: File "/usr/lib/python2.6/dist-packages/nova/virt/xenapi/vmops.py", line 213, in spawn
(nova.compute.manager): TRACE: raise spawn_error
(nova.compute.manager): TRACE: Failure: ['SR_BACKEND_FAILURE_110', '', "VDI resize failed [opterr=Command ['/usr/sbin/vhd-util', 'revert', '--debug', '-n', '/var/run/sr-mount/934ab597-ff32-94f6-c1da-9213c7f02a65/366c6ed4-5030-4f7b-b8d9-3f14e51a5743.vhd', '-j', '.journal-366c6ed4-5030-4f7b-b8d9-3f14e51a5743'] failed (2): ]", '']


This is causing instances to fail to boot.

Dan Prince (dan-prince) on 2011-09-29
Changed in nova:
status: New → Confirmed
importance: Undecided → Critical
Dan Prince (dan-prince) on 2011-09-30
Changed in nova:
assignee: nobody → Dan Prince (dan-prince)
Dan Prince (dan-prince) wrote :

Okay. Spent a good bit of time tinkering w/ this issue this afternoon. The VDI resize code added in bf181c2 is absolutely the problem. If I comment it out I'm able to boot instances fine.

I'm using XenServer 5.6 SP2:

[root@xen1 ~]# cat /etc/*release
XenServer release 5.6.100-46766p (xenenterprise)

This isn't an out of space issue for my SR. The same thing appears to happen on multiple Xen Servers. The SR's are pretty big and I can boot an instance normally. Furthermore I'm also able to do instances resizes and just about anything else on these machines which are all Dell R710's.

When the instance fails to boot I can go to the machine and reproduce this manually with the following command:

[root@xen1 ~]# xe vdi-resize uuid=b8714fde-9741-4ea0-b460-15c4e8b444df disk-size=20GiB
Error code: SR_BACKEND_FAILURE_110
Error parameters: , VDI resize failed [opterr=Command ['/usr/sbin/vhd-util', 'revert', '--debug', '-n', '/var/run/sr-mount/934ab597-ff32-94f6-c1da-9213c7f02a65/b8714fde-9741-4ea0-b460-15c4e8b444df.vhd', '-j', '.journal-b8714fde-9741-4ea0-b460-15c4e8b444df'] failed (2): ],


Also. If I comment out this code I can boot instances fine:

- for vdi in vdis:
- if vdi["vdi_type"] == "os":
- self.resize_instance(instance, vdi["vdi_uuid"])

Furthermore. I've verified that I can resize VDI's just fine for an instance once I've started and stopped the instance. So for example if I:

1) boot an instance
2) shut it down
3) I can then resize the VDI on the command line just fine with 'xe vdi-resize' to sizes much large than 20 Gigs.

So what I'm saying is that VDI resizes appear to fail before we've spawned the instance at least once. Once we've spawned it we can shut it down and perform whatever resize we want.


So as far as I can tell booting instances on stock XenServer 5.6 SP2 breaks w/ this commit. Is this a XenServer issue that I need a patch to fix or something?

Dan Prince (dan-prince) wrote :

When this happens I'm also seeing the following output in /var/log/messages on my XenServer box:

Oct 3 09:08:48 dev3 vhd-util: libvhd::vhd_read: /var/run/sr-mount/934ab597-ff32-94f6-c1da-9213c7f02a65/49a735c9-00f9-437e-ba9c-2700b5e7ea63.vhd: read of 512 returned 0, errno: -22
Oct 3 09:08:48 dev3 vhd-util: libvhd::vhd_validate_footer: invalid footer cookie:
Oct 3 09:08:48 dev3 vhd-util: libvhd::vhd_read_short_footer: /var/run/sr-mount/934ab597-ff32-94f6-c1da-9213c7f02a65/49a735c9-00f9-437e-ba9c-2700b5e7ea63.vhd: failed reading short footer: -22
Oct 3 09:08:48 dev3 vhd-util: libvhd::vhd_validate_footer: invalid footer cookie:
Oct 3 09:08:48 dev3 vhd-util: libvhd::vhd_read_footer_at: /var/run/sr-mount/934ab597-ff32-94f6-c1da-9213c7f02a65/49a735c9-00f9-437e-ba9c-2700b5e7ea63.vhd: reading footer at 0x54aa7e00 failed: -22
Oct 3 09:08:48 dev3 fe: 4535 (/opt/xensource/sm/EXTSR <methodCall><methodName>vdi_resize_online</methodName...) exitted with code 0

Dan Prince (dan-prince) wrote :

Still looking for information on this one. As far as I can tell OpenStack Essex will not work out of the box with a stock XenServer 5.6 SP2 installation (w/ thin provisioning). By stock I mean I install XenServer 5.6 SP2 from the ISO's, select thin provisioning in the installer and let it run through a default installation.

I'd be interested to see if anyone who has a working XenServer 5.6 installation (using kickstarts or whatever) could add to this thread.

For now I have to do this to work around the issue:

+++ b/nova/virt/xenapi/vmops.py
@@ -166,9 +166,9 @@ class VMOps(object):
                 instance.user_id, instance.project_id,

- for vdi in vdis:
- if vdi["vdi_type"] == "os":
- self.resize_instance(instance, vdi["vdi_uuid"])
+ #for vdi in vdis:
+ #if vdi["vdi_type"] == "os":
+ #self.resize_instance(instance, vdi["vdi_uuid"])

Glen Campbell (glen-campbell) wrote :

Any speculation on a time for a fix for this?

Dan Prince (dan-prince) wrote :

Hi Glen,

It appears that the vhd_util resize operation doesn't like to work with some OVA images (ones not created on XenServer?).


In my case I think I was using a small Debian Squeeze image that I converted to OVA format using xenconvert (months ago). The image was fine and it booted w/ nova before this commit. Additionally my initial image was also resizable after it booted fully.


The work around for me was to manually create a new OVA image by hand using the VHD of the booted instance on XenServer. Creating a tar of that VHD with an empty manifest.ovf makes this issue go away.

My guess is that others might hit this same issue when using nova w/ XenServer. Specifically anyone booting an OVA image which wasn't created directly from a XenServer dom0.

Hope that helps. I didn't have time to track it any further.


Thierry Carrez (ttx) on 2011-12-13
Changed in nova:
importance: Critical → High
Vish Ishaya (vishvananda) wrote :

Dan: status?

Ken Pepple (ken-pepple) wrote :

This is a vhd-util issue -- it checks the VHD image header for a specific creator code ... which may or may not be there depending on how you created the image. This is especially problematic if you created the image with XenConvert ... We should file this as a bug for XCP (also present there), although I don't know if there are specific reason they are checking for it.

We should mark this bug as invalid and redline the documentation.

Vish Ishaya (vishvananda) wrote :

marking this as invalid for nova and marked it for xcp

Changed in nova:
status: Confirmed → Invalid
Dan Prince (dan-prince) on 2012-02-03
Changed in nova:
assignee: Dan Prince (dan-prince) → nobody
tags: added: xenserver
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers