Hi,
Really weird...
So, you created a clone and obviously you have a full independent VM with the same specs as the original.
Why do you have to use vCCS to "move" it to another ESXi?
Anyway, verify that you're using the correct VM when using vCCS, never see that error and I made many P2V and V2V.
Another thing to check is the .vmx file of the clone and see which are the vmdk files that are using (maybe something wrong is there, who knows...)
Hope this helps.
Hi,
yes, this is really weird...
I tried to unregister the "Template Machine"... Then the Standalone Converter is choosing "randomly" another VMs harddisk for cloning...
I don't know, what the Converter is doing there...
Cloning the harddisk with CLI tools and copying to Destination ESXi via Scp is working as expected... I guess scp'ing the original VMDK files might also work...
The reason for "moving" or cloning them to other ESXi is to have a "backup" before upgrading to the newest ESXi version... I don't have any time to setup all machines from scratch again, if upgrade fails...
Best regards...
Hi
Copying files via scp is not the same thing as converting. There are subtle yet important differences. It is also not the same thing as cloning a VM or doing a VM backup. I also would have a hard time guessing what has gone wrong. My suggestion is to use the tools as intended. In unsupported scenarios you are basically on your own.
Regards,
Plamen
Hey brother,
your step-by-step worked for me . Thanks a lot!
I was facing the same problem (vCenter converter 6.2.0) and the solution was as explained before, pls check image.
Hey, I'm pretty new to the VM world.
I have a lab that I'm trying to take multiple Redhat and Windows computers and convert them to run on an ESXi. The problem is that I can't have access that ESXi in that lab. I wanted to use vCenter Converter to do a remote capture, and then save them as a file on my laptop. Then later on when I can get access to the ESXi, I can upload them to the ESXi. I know that i can take an image of my own local PC and create those files for upload, but when I tried doing a remote linux conversion, my only option was to send it straight up to the ESXi.
So how do people typically create VMs if they can't have access to their ESXi?
I can't get 6.2 to work on XP. It looks like the link has changed/moved for older versions. Is there another place I can get something that will work for XP?
Did you ever find a solution to this? I think I'm encountering the same problem.
I am trying to Virtualize a Windows server 2003 SP1 Server it is running a older version of a Xray software for a medical office.
I have had nothing but issues. I think it's directly related to the old version of Windows
I have the following
1. Windows 2003 32 Bit Sp1 (Non R2)
2. Dell Poweredge R420 server with 1.7 TB of space in a Raid one Mirror
The ESXI server was running a Version custom Dell ISO of ESXI V7
I have did other ESXI server P2V's with no issues. This one how ever is not playing nice at all.
Vmware converter 6.2 won't install on the 2003 box, I was able to install V6.0 but that will not connect to the ESI box when i go to start the P2V
What Version of ESXI on the Server and what Version of the Vmware converter do i need.
I am not sure I can install R2 on this server. It's not supported by the Vendor anymore. and I can't risk breaking anything by installing R2?
Any help would be appreciated.
Thanks
Convert to VMware Workstation format: Select a Hosted Destination
Then later you can convert from that format to ESXi.
Moderator: Thread moved to the Converter Standalone area, this issue has nothing to do with vCenter.
Hi
In the 1st step, convert your physical machines to the VMware Workstation virtual machines (P2V operation) and save their related files (like *.vmdk & *.vmx) on your laptop.
In the 2nd step, bring your laptop on the ESXi connected network and then run the convert operation again (V2V) to create a ESXi compatible VM.
Unfortunately what I'm being asked to do is NOT an option on the menu.
"convert your physical machines to the VMware Workstation virtual machines (P2V operation) and save their related files (like *.vmdk & *.vmx) on your laptop."
It's not an option when I convert remotely, it's only an option on the combobox if I backup my local machine. When I do a remote conversion of my Linux box, when I get to the destination options it doesn't allow me to select "VMware Workstation virtual machines" like it does if I try to convert my local machine. It's just not there. I was hoping I could do that, but its let not letting me which is the problem.
Could I have screwed up some settings or something?
Hi,
Please check the following link in the community, I think it will give the answer you seek ...
Welcome to the Community,
I faced a similar challenge some time ago, and solved it by doing a two step conversion.
The first step was to convert the source system to a "VMware Workstation" format using the older converter version, and then converting the Workstation VM to ESXi using the new converter version.
André
Hi
You cannot do Linux P2V (conversion of powered on Linux machine) to hosted (e.g. Workstation) format. You can do that for Windows, though.
What you could do for the Linux machines is to install a converter in a VM on the target ESxi and do the conversion form there. You need to ensure SSl access from the ESXi VM network to the source machine. Have a look at Remote Hot Cloning of Powered On Source Machines That Are Running Linux, it will give you the idea.
HTH,
Plamen
Moderator: Thread moved to the Converter Standalone area.
Ok that helps explain why I couldn't get the option that I was expecting and was very helpful. Unfortunately I feel like I still have the same original problem. I can't reach the ESXi on the network, and to disconnect the ESXi and physically move it over to the source isn't ideal if an option at all.
I wasn't part of the ESXi setup but it makes me wonder if I could somehow make my laptop act as an ESXi temporarily to use during a conversion and then send it to the real ESXi later on when I have access to it again.
This error is occurd while performing v2v conversion "Unable to query live linux source machine."
Ubuntu Os 16.04 is supported and vcenter converter version is 6.2
In worker logs i am finding this error vmware-converter-worker[00532] [Originator@6876 sub=Default] No disks for volume with id '/dev/sda1' and label ''
I am able to do ssh from converter standalone machine.
No firewall in between
DNS entries are made properly.
can anyone help me with resolving this issue?
when i try to do conversion in power off state it gives me error as "a file i/o error has occurred while accessing "
Please help on above issue. your inputs will mattr
Final Answer on what I need to do