Re: [Users] Bad volume specification

I have a couple ESXi Win 7 images on VMDKs that I converted to raw using qemu-img convert. Under ovirt 3.3.1 I then used a procedure posted here previously where you create a VM, add a disk, then copy over the converted image onto the oVirt created image and away you go. I did this twice under oVirt 3.3.1 and it worked great. Now I have built a new oVirt 3.3.2 system and tried the same thing, and I get the error: VM win7-01 is down. Exit message: Bad volume specification {'index': 0, 'iface': 'virtio', 'reqsize': '0', 'format': 'raw', 'bootOrder': '1', 'volumeID': 'd750e9e0-a906-4369-8bbb-a3b676121321', 'apparentsize': '107374182400', 'imageID': 'f674cb27-c28b-4373-ad75-9ed8a765ca31', 'specParams': {}, 'readonly': 'false', 'domainID': 'f14f471e-0cce-414d-af57-779eeb88c97a', 'optional': 'false', 'deviceId': 'f674cb27-c28b-4373-ad75-9ed8a765ca31', 'truesize': '107374194688', 'poolID': '18f6234c-a9de-4fdf-bd9a-2bd90b9f33f9', 'device': 'disk', 'shared': 'false', 'propagateErrors': 'off', 'type': 'disk'}. The original oVirt 3.3.1 system that has now been upgraded to 3.3.2 still boots this same disk image just fine. I'm guessing it's upset because apparentsize and truesize are different? Why did 3.3.1 seem not to care but 3.3.2 does now?

Any way I can true these up? I've tried a few things with qemu-img but haven't gotten the magic right yet.