VMware converter standalone.
Problem:
First the client was unable to connect to the server (both in the same
machine)
Solution:
Reinstall the whole vmware-converter
Problem:
Unable to select localhost or 127.0.0.1 as machine to convert.
Error: Unable to contact host
Solution:
Apparently I was unable to ping localhost.
# Added this line to /etc/sysctl.conf
net.ipv4.icmp_echo_ignore_all=0
Then ensure that lo is up. If not:
sudo ifconfig lo 127.0.0.1
Problem:
Unable to connect to host
Solution:
Start ssh server
/etc/init.d/ssh start (also ensure that root access is allowed)
Problem:
Unable to get details from the host
Same problem than here
http://communities.vmware.com/thread/195371;jsessionid=D5EFBAB5EE4F7027F518AE6797C06D27
Solution:
Also very similar
I did a backup of /root/.bashrc and then cleaned it up almost completely.
Now it completes retrieving the information.
Problem:
NOTE For Linux P2V conversion tasks, the only supported destination is a
VMware Infrastructure virtualization product.
I can't convert my Linux sending it to an external disk.
Solution:
Run ESX on a VM in workstation and send it there. (I haven't completed this
part yet).
Then I will have to convert it again to Workstation format.
Es mejor volver atrás que perderse en el camino.
-- Sentencia rusa.
posted by Ruben }:o) at 00:03
Radboud.HU 
Dylan.HU .0.jpg)
Dylan.UK 
Daniel.ES 
1 Comments:
== Problems encountered converting the Linux physical machine to a VM inside ESX running inside a VM in workstation:
- Better if you use workstation 7 as it supports nicely to run ESX on a VM
- Better ESX4i than ESX4 (smaller VM)
- IMPORTANT: run Workstation as ROOT, as the ESX VM needs to access the physical NIC in promiscuous mode to determine what traffic is for the ESX and what is for the VM inside the ESX (your converted VM)
- You will need to add a specific line to the ESX4 .vmx file to allow VM in a VM (look for xvirt pdf file).
- While you are doing the conversion, have a vSphere Client connected to your ESX host. It will allow you to see what is going on and even errors that Converter won't tell you. It is critical that the VM target inside the ESX can reach the physical Linux. Unless you have a dns on the network, use IPs only.
- Don't use a wireless connection, at some stage it will fail.
Linux hostA ----------> Linux HostB // Workstation 7 // ESX4i // VM (Linux hostA converted)
When the conversion is completed, you will have to convert it back to a hosted VM version.
The fastest way I found is NOT to use Converter again, NOT to copy the vmdk throught "scp". It is to attach a external usb disk DIRECTLY to the ESX (with Workstation 7 you can do it), and then clone "vmkfstools -i source.vmdk destination.vmdk" the virtual disk of the destination VM into the USB disk. It will be SEVERAL times faster than any other method.
Warning:
- You may destroy the content on the USB disk if you don't know what you are doing.
- The filesystem on the usb must be ext2 or ext3 for the ESX to write on it.
When the clone is completed, you can unmount the USB disk, stop ESX and attach the USB to your LinuxB host.
Then you create a VM in workstation with the specifics of your guest and attach "an existing virtual disk".
The whole thing took me 2 weekends, with a network on my own room (to avoid having to use wireless). A nightmare, but finally I did it, and I learned a lot. Now I understand much better how every step works.
Post a Comment
<< Home