Hi Devansu,
Now that I was sure that is causes no other regression I was trying to recreate
the case to test the fix itself.
I see the upstream fix, so I totally believe in this hitting you and the fix
makes sense.
But I have problems recreating as it just works for me.
The original bug has not the ovf file attached that they used - so I
can't use that.
So I created my own steps, but for me that works fine even without the fix
applied.
Here are my steps and I have to ask you to help me modifying them so that we
can confirm the fix.
Otherwise we can't SRU it (as we can't prove to fix anything).
0. install vmware
1. cd /tmp/
2. dd if=/dev/zero of=qemu-img-bug.img bs=1M count=1
3. qemu-img convert qemu-img-bug.img -O vmdk \
-o adapter_type=lsilogic,subformat=streamOptimized,compat6 \
qemu-img-bug.vmdk
4. create the most basic vm in vmware player
5. export the vm to ovf
ovftool /home/paelzer/vmware/Ubuntu64-bit/Ubuntu\ 64-bit.vmx /tmp/myvm.ovf
6. overwrite the vmdk with the one you created
$ cp qemu-img-bug.vmdk /tmp/myvm-disk1.vmdk
7. adapt the file size
ovf:size="65536"
to match
$ ll /tmp/myvm-disk1.vmdk
-rw-r--r-- 1 paelzer paelzer 65536 Feb 23 11:48 /tmp/myvm-disk1.vmdk
8. replace SHA1 in manifest /tmp/myvm.mf to match the new ones
$ sha1sum /tmp/myvm-disk1.vmdk /tmp/myvm.ovf
6115963a0bcae38daa242babd2b183b5810251f5 /tmp/myvm-disk1.vmdk
3b48e32d80fbe1d3499b6374ea4b48d797ee7c27 /tmp/myvm.ovf
8. delete the VM in vmware (get rid of old name)
9. import the ovf file in vmware
10. when it asked for an OVF syntax check, press retry to parse relaxed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646240
Title:
qemu-image creats broken vmdk file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1646240/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
