trobbelke
asked on
VMware ESX 4 problem importing existing virtual machine
Hi,
I'm moving our virtual machines from our old servers running VMware Server 2 (on RHEL4) to ESX 4 servers. I have no problem moving Windows VMs but I can't get RHEL5 VMs to run, I always get the same error:
"Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7. Did you forget to import the disk first? Unable to create virtual scsi device for scsi0:0, /vmfs/etc/etc/<server>.vmd k"
The log file has this:
DumpDiskInfo: scsi0:0 createType=7, capacity = 94371840, numLinks = 1, allocationType = 0
Msg_Post: Error
[msg.scsi.esx.unsupportedD iskType] Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7. Did you forget to import the disk first?[msg.scsi.esx.virtua lDevFailed ] Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/<path>/<ser ver>.vmdk
Since I can successfully copy and run the Windows VMs, I don't think it's a permissions error? Anyway, I even tried adding the VM to the ESX inventory from its old location instead of copying but that didn't work either. All I tried always returned the same error message as above.
I tried it with 2 different (RHEL5) VMs. I'd say ESX is not happy with the vmdk format or so.
Also, When I try booting the VM, a new vmdk file appears, exactly the same size as the original vmdk file, but with -s001 added in the name:
original file: <server>.vmdk (size 29GB)
new file: <server>-s001.vmdk (size 29GB)
Can anyone help me?
I'm moving our virtual machines from our old servers running VMware Server 2 (on RHEL4) to ESX 4 servers. I have no problem moving Windows VMs but I can't get RHEL5 VMs to run, I always get the same error:
"Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7. Did you forget to import the disk first? Unable to create virtual scsi device for scsi0:0, /vmfs/etc/etc/<server>.vmd
The log file has this:
DumpDiskInfo: scsi0:0 createType=7, capacity = 94371840, numLinks = 1, allocationType = 0
Msg_Post: Error
[msg.scsi.esx.unsupportedD
Since I can successfully copy and run the Windows VMs, I don't think it's a permissions error? Anyway, I even tried adding the VM to the ESX inventory from its old location instead of copying but that didn't work either. All I tried always returned the same error message as above.
I tried it with 2 different (RHEL5) VMs. I'd say ESX is not happy with the vmdk format or so.
Also, When I try booting the VM, a new vmdk file appears, exactly the same size as the original vmdk file, but with -s001 added in the name:
original file: <server>.vmdk (size 29GB)
new file: <server>-s001.vmdk (size 29GB)
Can anyone help me?
VMWare Server/workstation VMs are in different format than ESX. The easiest way to do this is to download VMWare's vConverter and point it to the windows VM as source and ESX as destination. You will also be able to resize it the volumes in the process if needed. Afterwards upgrade vmware tools and you're set
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for the quick response, I'll try that.