1 files changed, 62 insertions, 0 deletions
diff --git a/results/classifier/deepseek-1/output/files/1253465 b/results/classifier/deepseek-1/output/files/1253465
new file mode 100644
index 00000000..9c502b2b
--- /dev/null
+++ b/results/classifier/deepseek-1/output/files/1253465
@@ -0,0 +1,62 @@
+
+qemu-img: 'image' uses a vmdk feature which is not supported by this qemu version: VMDK version 3
+
+qemu-img convert in.vmdk  -O RAW out.img
+
+Fails with:
+qemu-img: 'image' uses a vmdk feature which is not supported by this qemu version: VMDK version 3
+
+qemu-img version 1.6.1
+
+On Wed, Nov 20, 2013 at 11:00:14PM -0000, adrelanos wrote:
+> qemu-img convert in.vmdk  -O RAW out.img
+> 
+> Fails with:
+> qemu-img: 'image' uses a vmdk feature which is not supported by this qemu version: VMDK version 3
+> 
+> qemu-img version 1.6.1
+
+This is a known issue.  VMware has not released the file format
+specification for VMDK version 3.  At this point the information needed
+to implement version 3 support is not publicly available.
+
+If you are aware of open source software which already supports version
+3, please let us know!
+
+Fam: Do you have instructions for exporting version 2 images from
+VMware?
+
+Stefan
+
+
+> If you are aware of open source software which already supports version 3, please let us know!
+
+VirtualBox can.
+
+- VirtualBox uses VMDK version 3 disks.
+- When you export a VM with VirtualBox (creating an .ova), it will include VMDK version 3 disks.
+- VirtualBox can convert from vmkd to vdi. ('VBoxManage clonehd --format VDI "vmdk_file" "vdi_file"')
+
+Does that help?
+
+
+On Sat, 01/07 21:36, Patrick Schleizer wrote:
+> > If you are aware of open source software which already supports
+> version 3, please let us know!
+> 
+> VirtualBox can.
+> 
+> - VirtualBox uses VMDK version 3 disks.
+> - When you export a VM with VirtualBox (creating an .ova), it will include VMDK version 3 disks.
+> - VirtualBox can convert from vmkd to vdi. ('VBoxManage clonehd --format VDI "vmdk_file" "vdi_file"')
+> 
+> Does that help?
+
+Can you try again with QEMU 2.8? Recent versions of QEMU should be able to
+handle version 3 VMDK disks.
+
+Fam
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+