Using Converter Standalone 6 client and attempting to convert a CentOS 6.5 physical box, the process goes to 97% and then gives this error: "Partition number must be set for the boot volume". The result was a virtual machine with disks that appeared to be of correct size, but would not boot. The target destination was vCenter 5.5 U2. In the converter worker log, I see a number of interesting items regarding disks, but am not sure what they might mean. What can I look for to troubleshoot this specific issue? Thanks.
↧
Converter 6 - Partition number must be set for the boot volume
↧
Re: Converter 6 - Partition number must be set for the boot volume
The error seems to be like incompatible scsi drive..
I would suggest to add a disk and point to the existing vmdk so that the VM adjust it self to the compatible version..
As well the VMM should know it OS detail .. Try this and let me know in case any help needed.
↧
↧
Re: Converter 6 - Partition number must be set for the boot volume
Most probably your boot volume is placed on disk without partition, this is not supported by converter currently,
You can run the VM with rescue CD and reconfig manually your GRUB.
HTH
↧
Problema para Convertir un servidor Debian - login de root
Hola a todos:
Tengo un problema para loguearme en la conexión para convertir un servidor Debian dentro de la LAN.
En el primer intento me apareció un error que el servidor no permitía login de root.
En la configuración de SSH del servidor habilité el login de root, pero el vCenter Converter Standalone Client no me permite loguearme con "root" y el password de root, me dice que el usuario o password son incorrectos. Probé con otro usuario y me acepta el nombre y pass, aunque me dice que debe ser un usuario con permisos de root.
Con el nombre root y la password correspondiente me da error.
Alguien tiene alguna sugerencia? Hay que habilitar otra cosa en la configuración del servicio SSH de Debian?
Gracias!
Daniel
↧
How to convert Ubuntu 8.10 to a vSphere 5.5U2 VM?
I have a fully visualized Ubuntu 8.10 server running as a Xen DomU on SLES11 SP3. I need to move it to VMware. I haven't yet played with VMware Converter Standalone but I've read the release notes for several versions and it seems the newer versions don't support Ubuntu 8.10 while the older versions don't support vSphere 5.5U2.
Is there a workaround?
Are there other conversion options?
↧
↧
Re: Converter 6 - Partition number must be set for the boot volume
Since you got up to 97% this means the data cloning has completed and the failed part is the reconfiguration of the resulting machine in order to make it bootable. This is done by the helper service. You can export a log bundle of the failed task and then dig into the archive until you get to vmware-converter-helper.log. There you can find more information about what Converter was doing at the time of failure and possibly more detailed error info.
Since the data is there you can try to repair your destination VM manually. Converter includes four steps in this process
1. Repair GRUB boot loader (incl. patching the menu.lst file)
2. Repair /ets/fstab paths
3. Rebuild initrd image
4. Fix network files
There are detailed steps in other posts for fixing any of these.
↧
Re: Problema para Convertir un servidor Debian - login de root
Hello
You need to enable both PermitRootLogin and PasswordAuthentication (and don't forget to restart sshd).
You also need to use Converter 6.0 for Debian.
HTH
Plamen
↧
Re: How to convert Ubuntu 8.10 to a vSphere 5.5U2 VM?
Try with 5.0.1 (not 5.0 because it will crash when you point to vSphere 5.5!). 5.1 might also work.
Longer answer: There is no explicit disabling of older GOS version in the code and they usually can be converted albeit not supported. However Ubuntu 8 is known not to work (don't remember which version since). Also Converter is usually able to point to a newer vSphere version as a destination (after fixing the bug in 5.0). Keep in mind neither of these 'usuals' is supported but with some luck you may succeed. If not, the workaround is to convert to some older ESX and then to the real destination.
HTH
Plamen
↧
Re: Problema para Convertir un servidor Debian - login de root
Hola.
Hice todo como indicaban, pero no me podía conectar.
Al fin agregué 'root' a la línea "AllowUsers xxx", de modo que quedó como:
AllowUsers xxx root
De este modo pude conectarme sin problemas.
Muchas gracias.
Daniel
↧
↧
Re: Error when trying to virtualize a Windows 2008 R2
I installed an English Windows with Converter standalone, I've run a Convert Machine Job with Final synchro, Guest OS customization and reconfiguration.
It failed with the same error at 97 %.
Then I've run a Configure Machine job, and no error occured.
With this task, there is no agent (and no problem with french unicode...)
Thanks for your useful help, but I don't understand why the agent is not programmed to use the same temp path for all OS languages (C:\Windows\TEMP\vmware-temp\vmware-SYSTEM\deploypkgxxxxxxxx\deployPkg.cab)
↧
I try to convert rhel 5.4 to vmware 6 Esxi but cannot success
I try to convert rhel 5.4 to vmware 6 Esxi but cannot success ,
in task process to alert "FAILED: An error occurred during the conversion: '/usr/lib/vmware-converter/bin/ssh -z -F /usr/lib/vmware-converter/ssh.conf root@192.168.10.6 -p 22 " tar --one-file-system --sparse -C /home -cf - ." | /bin/tar_1.20 --numeric-owner --delay-directory-restore -C /mnt/p2v-src-root/home -y -xf - Read from remote host 192.168.10.6: Connection timed out /bin/tar_1.20: Unexpected EOF in archive /bin/tar_1.20: Unexpected EOF in archive /bin/tar_1.20: Error is not recoverable:
exiting now (return code 2)'"
I don't know how to solve it .
Help me please.
↧
Re: I try to convert rhel 5.4 to vmware 6 Esxi but cannot success
Try with Converter 6.0
↧
The destination does not support EFI firmware - Converter 6.0.0 - ESXi 5.5
Hello there,
I'm trying to run a live P2V using vmware converter standalone 6.0.0 running on the actually physical machine to be converted and after selecting the ESXi 5.5 destination I get "The destination does not support EFI firmware". The physical machine is running Windows 2008 R2 standard x64 and is a System x3550 M2. Ive searched the internet but cant seem to find anyone with the same issue.
Does anyone know if there is a workaround for this issue?
Many thanks
↧
↧
Re: The destination does not support EFI firmware - Converter 6.0.0 - ESXi 5.5
Upgrade or change your destination (i.e. ESX) with one that supports EFI.
HTH
↧
Re: The destination does not support EFI firmware - Converter 6.0.0 - ESXi 5.5
Hi
See the VMware KB article.
↧
Acronis 11.5 - error on coverting an image
I was given a USB drive with several Acronis 11.5 image (.tib) files.
Converter does not work - I get an error ,,,,The source parameters are invalid
So, I was going to try a restore of an image to a VM by booting up the Acronis Universal Restore and selecting the image.
However, the image disk is 298 gb but only about 30gb is used
Since I can't use converter to down size, what is the best way to get the image over to a VM?
↧
Re: The destination does not support EFI firmware - Converter 6.0.0 - ESXi 5.5
Are you saying that ESXi 5.5 doesn't support efi guests?
↧
↧
Re: The destination does not support EFI firmware - Converter 6.0.0 - ESXi 5.5
Well the problem was that EVC mode was enabled on the cluster and there were some 4.1 esxi hosts in the cluster. once i removed the 4.1 host out of the cluster the converter offered 8,9 and 10 virtual machine versions which support efi. This resolved the prob.
↧
Re: Acronis 11.5 - error on coverting an image
Look at User's Manual for supported Acronis versions.
HTH
↧
Re: Acronis 11.5 - error on coverting an image
The manual says
Acronis True Image Echo 9.1 and 9.5, and Acronis True Image Home 10 and 11 (.tib)
Also
VMware vCenter Converter Standalone 6.0 is the last release of the product to support third-party backup images and virtual machines as sources for conversion.
This capability will be discontinued in the next release. If you use this capability, you should start planning your transition.
I am trying to load an image into a new VM by using Universal Restore but it is taking way to long.,..now on 16hrs,,
Something is not right and there should be a way to restore the image and downsize the drive
↧