1 files changed, 104 insertions, 0 deletions
diff --git a/results/classifier/118/all/545089 b/results/classifier/118/all/545089
new file mode 100644
index 000000000..99008f1e9
--- /dev/null
+++ b/results/classifier/118/all/545089
@@ -0,0 +1,104 @@
+peripherals: 0.971
+graphic: 0.963
+architecture: 0.962
+semantic: 0.962
+kernel: 0.960
+network: 0.959
+device: 0.958
+permissions: 0.955
+register: 0.955
+virtual: 0.955
+assembly: 0.954
+debug: 0.952
+user-level: 0.950
+socket: 0.949
+arm: 0.948
+risc-v: 0.947
+PID: 0.946
+vnc: 0.946
+TCG: 0.944
+boot: 0.941
+hypervisor: 0.934
+VMM: 0.932
+performance: 0.932
+files: 0.928
+ppc: 0.928
+KVM: 0.926
+i386: 0.900
+mistranslation: 0.898
+x86: 0.874
+
+qemu-img should be able to create scsi based vmdk images
+
+qemu-img can create vmdk disk images. These are always created as "ide" disks; that is, the paramter ddb.adapterType is set to "ide" in the .vmdk file.
+
+I needed to create a scsi style vmdk image, in which ddb.adapterType is set to "lsilogic".
+
+The attached patch (against qemu-0.12.3) allows me to convert a raw image into a scsi vmdk image:
+
+ qemu-img convert -O vmdk -o scsi rootfs.raw rootfs.vmdk
+
+The "scsi" option works also for the "create" command.
+
+I hope very much that this change can be rolled into qemu.
+
+best,
+
+Seb James
+
+
+
+This has been presented on qemu-devel before.  We didn't feel this was appropriate for qemu because 1) it's an invasive change 2) these images are not useful when using qemu--only useful for creating images for use with VMware.
+
+I'll leave this as wishlist, but at this time, we're not interested in supporting this feature.
+
+So it has - by Soren Hansen: http://<email address hidden>/msg15054.html
+
+In what sense is the change invasive, in your opinion? It seems like a fairly minor addition of a command line option to me.
+
+I, at least, find this patch very useful. My company builds network print appliances and our build scripts use qemu-img to create both qcow2 images for Linux KVM/qemu platforms and also vmdk disk images for those of our customers who insist on using vmware ;)
+
+Thanks for your reply.
+
+Block flags are a limited space.  We should have never taken the COMPAT6 support for the same reason.
+
+If the change could be entirely contained to the vmdk driver, it would be more palatable.
+
+Thanks for the explanation. There's an int for the block flags, so I guess there are nominally 32 flags available and 3 in use (including the compat6 flag)... unless qemu-img needs to be compilable on 16 or 8 bit machines?
+
+It looks like a fair amount of work to make this change entirely contained in the vmdk driver. I'll continue to maintain the patch against qemu.
+
+Those of us who have vmdk images bestowed upon us and would prefer to run them under qemu would very like to have a way to convert the images in both directions.
+
+On Wed, Nov 9, 2011 at 1:09 AM, Rob White <email address hidden> wrote:
+>  The attached patch (against qemu-0.12.3) allows me to convert a raw
+>  image into a scsi vmdk image:
+>
+>   qemu-img convert -O vmdk -o scsi rootfs.raw rootfs.vmdk
+
+Please rebase onto qemu.git/master.
+
+Please see this wiki page on how to submit patches to QEMU:
+http://wiki.qemu.org/Contribute/SubmitAPatch
+
+Stefan
+
+
+Modern qemu has this and more:
+qemu-img convert -O vmdk -o ? source dest.vmdk
+Supported options:
+size             Virtual disk size
+adapter_type     Virtual adapter type, can be one of ide (default), lsilogic, buslogic or legacyESX
+backing_file     File name of a base image
+compat6          VMDK version 6 image
+subformat        VMDK flat extent format, can be one of {monolithicSparse (default) | monolithicFlat | twoGbMaxExtentSparse | twoGbMaxExtentFlat | streamOptimized} 
+zeroed_grain     Enable efficient zero writes using the zeroed-grain GTE feature
+
+So perhaps this patch went mainstream after all?
+
+This seems to be fixed by this commit here:
+http://git.qemu.org/?p=qemu.git;a=commitdiff;h=7f2039f61113f11be9211
+==> Setting status to "Fix released"
+
+Great news!
+