En el sitio de Proxmox dan una solución, esta en ingles: VMware to Proxmox VE (KVM)
This howto describes the migration of a Windows 2003 Server (or Windows XP) from VMware to Proxmox VE (KVM). This procedure can be applied to *VMware Linux guests* as well, just skip the Windows specific steps. Prepare the Windows operating system Before you begin make a copy of the VMware image. Remove VMware tools Start the Windows virtual machine on VMware and remove the VMware tools via the Windows control panel. Reboot. Enable IDE - Start the Windows virtual machine on VMware and execute the mergeide.reg<http://www.proxmox.com/downloads/proxmox-ve/misc/59-mergeide>. Now the registry is changed that your Windows can boot from IDE, necessary for KVM. - Make sure Atapi.sys, Intelide.sys, Pciide.sys, and Pciidex.sys are in the %SystemRoot%\System32\Drivers folder. If any are missing they can be extracted from %SystemRoot%\Driver Cache\I386\Driver.cab which can be opened in Windows file Exlorer like a directory and then the missing files can be copied out. - see Microsoft KB article <http://support.microsoft.com/kb/314082/en-us>for details. - Shutdown Windows. Prepare the disk file My disk file used for this howto: win2003.vmdk - Change your VMDK disk file with vmware-vdiskmanager.exe to a single growable file (vmware-vdiskmanager.exe is located in your VMware installation path, e.g. "C:\Program Files\VMware\VMware Server") - open a cmd and go to the directory where your vmdk disk files are. "C:\Program Files\VMware\VMware Server\vmware-vdiskmanager" -r win2003.vmdk -t 0 win2003-pve.vmdk - Create a new KVM VM on Proxmox VE web interface and - do not start - take a look on the VMID (e.g. 102) - Copy the win2003-pve.vmdk to your Proxmox VE server into the following dir: /var/lib/vz/images/VMID (I used WinSCP <http://winscp.net> as I worked on a Windows desktop) - Change the win2003-pve.vmdk file to qemu format: qemu-img convert -f vmdk win2003-pve.vmdk -O qcow2 win2003-pve.qcow2 - Or, copy the vmdk to an LVM based disk of the same size or larger dd if=win2003-pve.vmdk of=/dev/VG_iscsi/vm-102-disk-1 *Alternatively*, your .vmdk file might be in a flat format, so running "qemu-img convert *-f vmdk*" will abort with "Operation not permitted". You can check your .vmdk file actual format with the *nix command "file". If it is a flat file instead of native format, your output would look like: # file myVMwFlatImage-pre.vmdk myVMwFlatImage-pre.vmdk: x86 boot sector; partition 1: ID=0x83, active, starthead 1, startsector 63, 208782 sectors; partition 2: ID=0x8e, starthead 0, startsector 208845, 16563015 sectors, code offset 0x48 So simply convert .vmdk into .qcow2 omitting the "-f vmdk" from the command above, and let qemu-img auto-detect the source format: qemu-img convert myVMwFlatImage-pve.vmdk -O qcow2 myVMwFlatImage-pve.qcow2 (This was experienced with a VMware ESXi 3.5 clone of a RHEL guest.) *If your kvm starts but does not boot* (vnc console reporting something like "booting from hard disk...boot failed: not a bootable disk"), try instead of "single growable file", a "preallocated virtual disk", to know how: launch "vmware-vdiskmanager" without parameters, you will see all the instructions. You can specify "single growable file" using parameter "-t <disk type>", where Disk types: 0 : single growable virtual disk 1 : growable virtual disk split in 2GB files 2 : preallocated virtual disk 3 : preallocated virtual disk split in 2GB files 4 : preallocated ESX-type virtual disk 5 : compressed disk optimized for streaming so, you have to use type 2 vmware-vdiskmanager -r whatever.vmdk -t 2 whatever-pve.vmdk Be aware that vmware-vdiskmanager could now create 2 files: - one whatever-pve.vmdk really small: it is really a text file, which you can read and see that it refers to - another vmdk, like whatever-pve-flat.vmdk, which has the full size of your disk, and this is what you want to convert to kvm after. - please note that the second file has the real size of the hard disk as seen from inside the guest vm, so if you are copying this to LVM with dd, you have to make room enough for this file size, or more. - This happened converting a ubuntu.vmdk from a linux vmware server 2 to pve using LVM storage, and the solution proposed worked. Alternative migration using a rescue CD disk image As an alternative to copying the .vmdk file, you can also boot the VMware guest using a rescue CD image, I use http://www.sysresccd.org/ There was no (obvious) method in (my) VMware Server 2.0 to specify that the VMware guest should boot from a CD image, and trying to intercept the VMware boot process in time to press F2 proved futile so many times I gave up. Instead, I changed the disk order, some VMware guests by adding a new little disk, others just by swapping the existing disks. And then it booted from the rescue CD image. Once inside the rescue CD image, could use SSH from the ProxMox VE server into the VMware guest running the rescue CD image. After that I simply ran this command: - ssh root@vmware_guest dd if=/dev/sdb | dd of=/dev/VG/vm-103-disk-1 REMEMBER! that you swapped the disks in VMware to be able to boot from the rescue CD image. You can also dd of=/to/a/file/if/you/want/that. Remember to also dd all the other disks from the VMware guest. It is possible to use gzip to transfer less data over the network, but I was on a local network in the same switch so it didnt matter. I did not see any higher speeds using gzip, and my speeds was from 4 MB/s to 12MB/s. Adapt the new KVM Virtual Machine - Go to the hardware tab on the web interface and remove the default harddisk file - Add the migrated harddisk as IDE for windows (only IDE works for windows) or SCSI for Linux - 2012-09-24: virtio now also works for windows, but it can not boot from it the first time. So boot as IDE, then shutdown, add or change a 2. harddisk as virtio, then boot up. Then shut down. Then change the ide0 to virtio0, I do that using vi in the console. Then you can boot up windows again, and it will change to the virtio driver, and say that the driver is from RedHat. - Start the new Virtual Machine via the management interface - First boot takes some time as some drives has to be loaded - Do not forget to install Paravirtualized_Network_Drivers_for_Windows<http://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows> - Finished! PD: Personalmente confio en las soluciones de VMware que en el resto de la competencia. En cuanto a recuperación de desastres, alta disponibilidad y balanceo de recursos. El 6 de septiembre de 2013 19:10, Pablo M. Drake <adminen...@infomed.sld.cu>escribió: > El 06/09/2013 18:38, Jesús Miguel Iriarte Oñoz escribió: > >> disculpen por incluir aquí a Vmware pero es que tengo la necesidad de >> pasar a Promox (NEW SERVER OF VIRTUALITATION) una máquina que está en >> VMware. >> >> necesito saber vías posibles para hacer esto, claro si se puede hacer >> >> migración a software libre, jaja >> >> saludos >> >> >> >> >> >> >> ______________________________**______________________________** >> __________ >> Lista de correos del Grupo de Usuarios de Tecnologías Libres de Cuba. >> Gutl-l@jovenclub.cu >> https://listas.jovenclub.cu/**cgi-bin/mailman/listinfo/gutl-**l<https://listas.jovenclub.cu/cgi-bin/mailman/listinfo/gutl-l> >> > Yo recientemente pase de VMWare Server a Proxmox. > Es muy sencillo el procedimiento.... La próxima semana envió a la lista > los pasos pues están mas allá de los mares y ahora no tengo acceso.... > Aunque si la imagen de la MV esta en un solo fichero Proxmox la asimila > bien. Pues Proxmox a partir de la versión 2.1 soporta imágenes de VMWare > > -- > Grupo de Usuarios de Tecnologías Libres Cuba > http://gutl.jovenclub.cu/ > > > > -- > > Este mensaje le ha llegado mediante el servicio de correo electronico que > ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema > Nacional de Salud. La persona que envia este correo asume el compromiso de > usar el servicio a tales fines y cumplir con las regulaciones establecidas > > Infomed: http://www.sld.cu/ > > > -- > Este mensaje ha sido analizado por MailScanner > en busca de virus y otros contenidos peligrosos, > y se considera que está limpio. > > ------------ próxima parte ------------ > Se ha borrado un adjunto en formato HTML... > URL: <http://listas.jovenclub.cu/**pipermail/gutl-l/attachments/** > 20130906/8af81b64/attachment.**html<http://listas.jovenclub.cu/pipermail/gutl-l/attachments/20130906/8af81b64/attachment.html> > > > ______________________________**______________________________**__________ > Lista de correos del Grupo de Usuarios de Tecnologías Libres de Cuba. > Gutl-l@jovenclub.cu > https://listas.jovenclub.cu/**cgi-bin/mailman/listinfo/gutl-**l<https://listas.jovenclub.cu/cgi-bin/mailman/listinfo/gutl-l> > -- Este mensaje ha sido analizado por MailScanner en busca de virus y otros contenidos peligrosos, y se considera que está limpio. ------------ próxima parte ------------ Se ha borrado un adjunto en formato HTML... URL: <http://listas.jovenclub.cu/pipermail/gutl-l/attachments/20130909/3a3f8d30/attachment.html> ______________________________________________________________________ Lista de correos del Grupo de Usuarios de Tecnologías Libres de Cuba. Gutl-l@jovenclub.cu https://listas.jovenclub.cu/cgi-bin/mailman/listinfo/gutl-l
