A VM failed to start and reported a "Bad volume specification" error.

Solution Verified - Updated -

Issue

  • A VM failed to start, reporting "Bad volume specification" error.

  • The vdsm logs on the host that the VM tried to start on contained;

VolumeError: Bad volume specification {'index': 0, 'iface': 'virtio', 'reqsize': '0', 'format': 'cow', 'bootOrder': '1', 'poolID': '1fd21961-5fcb-4845-b1ab-d543544e1430', 'volumeID': '3c3f8c7c-d3b8-4771-bb58-a47e54069591', 'apparentsize': '3221225472', 'imageID': '516b36fc-0367-4ee1-8cb7-8aafe1434653', 'specParams': {}, 'readonly': 'false', 'domainID': '573548e3-6846-4380-98f7-6440ae1f036d', 'optional': 'false', 'deviceId': '516b36fc-0367-4ee1-8cb7-8aafe1434653', 'truesize': '3221225472', 'address': {'bus': '0x00', ' slot': '0x06', ' domain': '0x0000', ' type': 'pci', ' function': '0x0'}, 'device': 'disk', 'shared': 'false', 'propagateErrors': 'off', 'type': 'disk'}
  • Live Storage Migration had been used to move the disk images of this VM from one storage domain to another.

Environment

  • Red Hat Enterprise Virtualization (RHEV) 3.1
  • Live Storage Migration (Tech Preview in RHEV 3.1)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content