Hyper-V to vCenter 7.0-Invalid configuration for device '1'.

[JamesEdmondsAspall]

Hi,

I am trying to migrate a powered off Hyper-V VM running Windows Server 2016 from a clustered Hyper-V host, to a vCenter cluster running VC/ESXi 7.0
When starting the conversion, the job fails. Looking at the vCenter task list, it fails with this error:
Invalid configuration for device '1'.

As I don't get much ability to configure VM settings before creation in the converter, I am not sure how to go about diagnosing and resolving this issue.
Has anyone come across this and know how to work around this error?

Many thanks
James

[yaroslav (staff)]

Greetings,

While shutting down the VM please do not specify any reason for shut-down.

[JamesEdmondsAspall]

Hi,

I don't think the OS was given a reason for the shutdown when it was powered off.
I'm not clear on why this would cause a device error in Vmware when creating a new VM though?

Many thanks
James

[JamesEdmondsAspall]

I have just tested with a running virtual machine, and have the same error.
Assume this is an issue on the Vmware side, but not sure how to approach diagnosis?

Cheers
James

[yaroslav (staff)]

As a workaround, try converting individual disks for that VM and setting up a new VM afterwards.

[JamesEdmondsAspall]

Yes it appears that converting the disk only from within the VM, then attaching to a new VM works as expected.

I've opened a ticket with Vmware to see if they can see what the VM creation issue is from the vCenter/host logs, but suspect the converter is not fully compatible with vCenter/ESXi 7.0?

Cheers
James

[yaroslav (staff)]

No, the Converter is compatible with ESXi 7.0. I think there can be a problem with non-ASCII symbols in the name.

[tr360]

+1 for this issue running the starwindconverterVersion 9 (build 268) withVMware ESXi, 7.0.2+.

Coming from Hyper-V to ESXi
Things I tried:
- Tried the vCenter and ESXi directly as targets, and I get 'Invalid configuration for device '1'' which according to VMware, its related to CD-ROM and Floppy.
- Removed CD-ROM. no floppy, and same conversion error.
- Tried Building a new VM on vSphere then converting the Disk only to attach to my vSphere VM, but this fails to convert.

It looks like StarWind is not getting disk information correctly rather than VMware being the problem
---------------- snipet start ---------
[root@server:/var/log] tail -f hostd.log
2022-05-23T23:35:54.845Z verbose hostd[2262225] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/<notshownID>/TestVM6 - DO NOT POWER ON/TestVM6 - DO NOT
POWER ON.vmx opID=91713c4f user=root] CreateDisk: Specified disk size is 0 KB
2022-05-23T23:35:54.845Z info hostd[2262225] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/<notshownID>/TestVM6 - DO NOT POWER ON/TestVM6 - DO NOT POW
ER ON.vmx opID=91713c4f user=root] SetHostDiskProperties: disk capacity less than 0: (vim.vm.device.VirtualDisk) {
--> fileName = "[DATASTORE_NAME] TestVM6 - DO NOT POWER ON/Empty.vmdk",
2022-05-23T23:35:54.845Z info hostd[2262225] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=91713c4f user=root] Event 3780 : Cannot create virtual disk [DATASTORE_NAME] TestVM6 - DO NOT POWER ON/Empty.vmdk
2022-05-23T23:35:54.845Z info hostd[2262225] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/<notshownID>/TestVM6 - DO NOT POWER ON/TestVM6 - DO NOT POW
ER ON.vmx opID=91713c4f user=root] Reconfigure failed: N3Vim5Fault17InvalidDeviceSpec9ExceptionE(Fault cause: vim.fault.InvalidDeviceSpec
2022-05-23T23:35:54.847Z info hostd[2262225] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/<notshownID>/TestVM6 - DO NOT POWER ON/TestVM6 - DO NOT POW
ER ON.vmx opID=91713c4f user=root] Create failed with given spec: /vmfs/volumes/<notshownID>/TestVM6 - DO NOT POWER ON/TestVM6 - DO NOT POWER ON.vmx
--> name = "TestVM6 - DO NOT POWER ON",
--> fileName = "[DATASTORE_NAME] TestVM6 - DO NOT POWER ON/Empty.vmdk",
-------------------------- snipet end ----------------------

Another observation is in the StarWind 9.0.1.258 wizard "Select a virtual machine or image file to convert" it shows all Hyper-V VMs but all disks are worded as "Empty".

Hope this helps narrow things down.

I am going to try using the Local Administrator on the Hyper-V as the credentials and report back if it's a permission issue.

[yaroslav (staff)]

Welcome to StarWind Forum! Thank you for your update. Can we have the conversion logs, please?
Please keep us posted on the conversion results.

[tr360]

Logs as requested from

C:\Program Files\StarWind Software\StarWind V2V Converter\logs\V2V_Log-20220530-170518.log

[yaroslav (staff)]

I'd like to draw your attention to these events

Code: Select all

5/30 17:05:58.225 ccc Facility ???INFO: WrapperHyperV::connect: Host - \\Hyper-vHostname.some.domain\root\virtualization\v2
5/30 17:05:58.240 ccc Facility ???ERROR: WrapperHyperV::connect: pLoc->ConnectServer \\Hyper-vHostname.some.domain\root\virtualization\v2 - 0x80070005
5/30 17:05:58.240 ccc Facility ???ERROR: WrapperHyperV::failResultToStr: Last Error - Access is denied.
 (0x80070005)
5/30 17:05:58.240 ccc Facility ???ERROR: VMConverter::HyperVConverter::Connection: connect fail - 0x80070005
5/30 17:05:59.801 ccc Facility ???WARNING: CPPHYPERVConnection::onNext: connect Access is denied.

They point to constrained access to the file. Please try running V2V converter as an administrator or while logged in as an domain administrator.

[tr360]

hi Yaroslav,
thanks for that. I am also getting permissions issues using VMware converter directly to Hyper-V as a source.

Both issues are related to permissions.
I use the local Hyper-V administrator and a Full Domain Admin account, and still permission issues.
The source File system, where the source VMs live, are accessible by the domain admin account, but still there is a permission issue.

Thanks for your help. I will post back if I get permission issues sorted.

[yaroslav (staff)]

Hi,

It looks strange to me now but still thank you for your update. Please try the following test.
Create a small, 5-10 GB, VHDX that is not used by any VM on the Hyper-V server. Run conversion as a local file to VMDK. Let me know if this works.