[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [rhelv6-list] qemu-img has no scsi support anymore?


Am 18.10.2011 20:52, schrieb Robin Price II:
On 10/18/2011 11:32 AM, Rainer Traut wrote:

I'm trying to conevrt an old Vmware Server 2.0 vm with W2k Server to kvm.
I converted from vmdk to raw, changed controller to scsi and hit this:

Virtualized SCSI devices
SCSI emulation is not supported with KVM in Red Hat Enterprise Linux.
Virtualized IDE devices
KVM is limited to a maximum of four virtualized (emulated) IDE devices
per guest.

Will this be supported in the future? Not sure. SCSI emulation, at the
moment, is not looking to be supported and is very buggy upstream as well.

However, I don't think qemu-img can convert any vmdk image to a KVM
image. I ran into something very similar recently. I had to use the
'vmware-vdiskmanager' tool provided from VMware.

The <vm_name>-flat.vmdk files store the content of the virtual machines
actual hard disk drives. Earlier versions of ESX used the extension .dsk
for the virtual disk files. The <vm_name>.vmdk files are the disk
descriptor files. This file contains all the information about the
associated flat file. The files tell you the CID of the file, the parent
CID of the file, and the type and size of the file amongst other things.

Thx Robin for your detailed answer.
I managed to solve it though in a very unusual way I guess.
Converting the image with qemu-img was no problem but as I said this resulted in a blue screen within w2k.

A windows admin told me how to import the vmware2 image in hyperv described here (2nd answer, so that it uses IDE):

After this it ran fine in Hyperv, then I converted the vhd with qemu-img to raw format. This image boots fine now with KVM and IDE controller. :)

Note: I was not able to run the image without having started it under Hyperv, but your results may vary.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]