Hi
Welcome to the communities.
Please let us know if you have taken below steps & you are trying to convert local system or remote system?
"a journey of a thousand miles starts with a single step."![]()
Re: Error: Unable to clone volume 'D'
↧
↧
Re: Converter - Warning The destination guest OS cannot be reconfigured. It may not boot properly.
Hi
Welcome to the communities.
We can ignore this warning ,
Please convert & try to boot if dose not post error message.
"You must not lose faith in humanity".![]()
↧
Re: P2V windows 2000 fails
Can you give me more details on the os you are using and version of software and some hardware info as well to help you out more ? Best regards
Your Oscar
↧
Re: Cannot start virtual machine
After installing vSphere Client and connection to the host it worked....
Problem was a question about the vmdk file, if it's was copied or moved. But in vim-cmd there was no way to get noticed about this message. Also hunting in all possible log files gave no hint to this reason.
↧
Re: Property vim.UserSession,ipAddress not found
Its probably a DNS issue , the machine you are trying to convert got its own DNS and DC server ? check that and once the connection is back i think everything will be ok , check the Workers log
Best regards and hope that helped
Yours, Oscar
↧
↧
Re: Best Practice to convert Physical to virtual
Hi Ashrafali79,
You might want to look into these resources for more information.
http://www.vmware.com/products/converter/
Regards, Harold
↧
Unable to obtain hardware information for the selected machine with vmware converter 5.5 (Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32))
Hello
I'm trying to do a P2V with vmware converter standalone 5.5
The source is the same machine that hosts vmware converter 5.5
The operating system is W2003 which acts as domain controller
Vmware-converter is launched by the administrator account.
The error I can see from the vmware-converter.worker logs is:
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive1: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive1'
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{0395a0a1-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{18297536-8c0b-11da-8528-0014852d7e43}\"
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{caf5e9f8-4e6c-11dd-b440-0014852d7e43}\"
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{2958b89a-b562-11dc-a508-806e6f6e6963}\"
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{0395a09f-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{0395a09e-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive1: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive1'
2014-02-13T17:36:41.155+01:00 [04344 warning 'Default'] Warning: no attached disks were detected.
2014-02-13T17:36:41.155+01:00 [04344 error 'Default'] [LiveWindowsComputer] Unable to find any disks attached to the computer.
2014-02-13T17:36:41.170+01:00 [04344 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds
2014-02-13T17:36:41.170+01:00 [04344 error 'Default'] Unknown exception while invoking VMOMI method queryComputerInfo
2014-02-13T17:36:50.358+01:00 [05648 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:50.358+01:00 [05648 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:50.358+01:00 [05648 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive1: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:50.358+01:00 [05648 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive1'
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{0395a0a1-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{18297536-8c0b-11da-8528-0014852d7e43}\"
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{caf5e9f8-4e6c-11dd-b440-0014852d7e43}\"
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{2958b89a-b562-11dc-a508-806e6f6e6963}\"
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{0395a09f-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{0395a09e-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:50.421+01:00 [05648 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:50.421+01:00 [05648 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:50.452+01:00 [05648 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:50.452+01:00 [05648 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:50.499+01:00 [05648 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive1: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:50.499+01:00 [05648 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive1'
2014-02-13T17:36:56.155+01:00 [05648 warning 'Default'] Warning: no attached disks were detected.
2014-02-13T17:36:56.155+01:00 [05648 error 'Default'] [LiveWindowsComputer] Unable to find any disks attached to the computer.
2014-02-13T17:36:56.155+01:00 [05648 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds
This had happened before with another server (also W2003 DC) but which hardware was completely different; unfortunately I wasn't able to solve that time.
Any help or hints would be appreciated, thanks in advance
↧
Re: Unable to obtain hardware information for the selected machine with vmware converter 5.5 (Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32))
The message for error 32 is "The process cannot access the file because it is being used by another process.". It looks to me as a permission error. Are you using the *local* administrator account, but not the domain admin account?
↧
Re: Unable to obtain hardware information for the selected machine with vmware converter 5.5 (Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32))
Hello
I suppose you are aware that virtualizing domain controllers is a tricky thing. If not, you may want to have a look at VMware KB: Virtualizing existing domain controllers in VMware vCenter Converter , and probably other articles about that. Some people even recommend not converting, but rather installing a new DC and syncing it with the old one.
HTH
Plamen
↧
↧
Re: Unable to obtain hardware information for the selected machine with vmware converter 5.5 (Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32))
Thank Plamen you for your hint, however I believe that it is not the case.
I've already converted many DC before (either 2003 and 2008) w/o major issues.
The problem here is that the converter is unable to detect its own hardrives; the hard drives of the source machine, so the converter is not able even to create the converting task. The issue is not related to problems with the resulting VM.
↧
Re: Unable to obtain hardware information for the selected machine with vmware converter 5.5 (Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32))
Thanks ivivanov for your answer.
I'll take a look to see if I find if there is a process blocking the disk access of the converter
Answering your question I'm using the domain administrator to launch the converter. Not sure If I can use the local administrator since lusrmgr.msc won't open in this DC
↧
Re: Unable to obtain hardware information for the selected machine with vmware converter 5.5 (Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32))
Said that I can confirm that the domain user "administrator" is member of the localgroup "administrators"
↧
Re: Unable to obtain hardware information for the selected machine with vmware converter 5.5 (Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32))
Yes, I know this is not the case. Just wanted to draw your attention to that.
For the specific error - check for antivirus, backup software, or anything else that could open and use the whole disk.
↧
↧
FAILED: An error occured while opening a virtual disk. Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts.
Hello,
I am trying to convert 3 very large physical fileservers into 3 virtual servers. I am using VMware Converter 5.5 and have installed it locally on each server. I am converting directly into an ESXi 5.5 host without vCenter.
Each server is about 15 TB total disk space ( >10TB consumed), but they have different disk setup.
- Server 1 has 1 C: drive, and 2 large volumes on 7,5 TB each.
- Server 2 has 1 C: drive and 8x1,9TB volumes
- Server 3 has 1 C: drive and 1 large volume on 7,5TB and 4x1,9TB
If I choose to run this with default setting (block size level copy, maintain disk size, all volumes on the same datastore) it creates the virtual machine on the ESX server and Converter reports the following task: "Task: Convert physical machnie". After a couple of minutes the newly created virtual machine on the ESX is deleted and after a few more minutes VMware Converter times out and reports the following error message:
- FAILED: An error occured while opening a virtual disk. Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts.
You would think that this is network related, but as it turns out, everything on the network/DNS side is OK:
If I choose to run the same job, but change the volume size and shrink it below 10 TB, the job runs fine! (Are there any limitations to this in Converter?) The only problem is that by doing this, it changes the copy type from "block level" to "file level". With file level copy you are not able to run synchronization afterwards, which we really need to do since this conversion will take several days and there will be a lot of changes left out if we don't synchronize in the end.
Does anyone have an idea how I could work around this?
↧
Re: FAILED: An error occured while opening a virtual disk. Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts.
Could you upload log-bundle?
↧
Re: FAILED: An error occured while opening a virtual disk. Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts.
You should attach converter-worker/converter-agent logs, GUI logs are useless in this case.
↧
Re: Unable to obtain hardware information for the selected machine with vmware converter 5.5 (Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32))
Thanks all for your help
I've finally found the guilty service.
It was pcmonitor a remote monitor/control software. Once I've stopped it's service vmware converter could get the capacity of the physical drives.
It's rather curious because I've done several P2V conversions of servers using this software (so far the last one was two weeks ago - the difference between that server and this one was that the former wasn't a DC).
Hope this thread will help others in the future.
↧
↧
Re: FAILED: An error occured while opening a virtual disk. Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts.
Ok, thank you. I've attached the latest logs.
↧
Re: FAILED: An error occured while opening a virtual disk. Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts.
Hmmm... no obvious problem, seems you hit some limitation in ESX because of bug number of disks... Also do not use this ESX as destination of other conversion(s), use for this conversion one only.
As first probe you can turn off SSL and then try to convert again... (converter-worker.xml: <nfc><useSsl>false</useSsl>; then restart converter-worker)
Please share the result.
↧
Re: FAILED: An error occured while opening a virtual disk. Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts.
It looks like that might have helped a little. One of the three servers are converting now, Server 2 with 8x2TB disks. The other two fails like before.
I've attached the worker log from one of the failed servers (Server1) and from the one that is working (Server2).
↧
More Pages to Explore .....
