Migration of servers to Proxmox VE: Difference between revisions

From Proxmox VE
Jump to navigation Jump to search
mNo edit summary
m (Redirected page to Migrate to Proxmox VE)
Tag: New redirect
 
(173 intermediate revisions by 26 users not shown)
Line 1: Line 1:
=Introduction=
#REDIRECT [[Migrate to Proxmox VE]]
You can migrate existing servers to Proxmox VE.
 
=Physical server to Proxmox VE (KVM)=
There are free tools (like [http://www.vmware.com/products/converter/ VMware Converter]) available to migrate a physical host to VMware. So the first step is to migrate the physical server to a VMware image. The second step is to follow the howto "VMware to Proxmox VE (KVM)".
 
=VMware to Proxmox VE (KVM)=
This howto describes the migration of a Windows 2003 Server (or Windows XP) from VMware to Proxmox VE (KVM).
 
==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 in the registry===
* Start the Windows virtual machine on VMware and execute the mergeide.reg (see [http://support.microsoft.com/kb/314082/en-us Microsoft KB article] for details). Now the registry is changed that your Windows can boot from IDE, necessary for KVM.
* 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")
<pre>vmware-vdiskmanager -r win2003.vmdk -t 0 win2003-pve.vmdk</pre>
* Copy the win2003-pve.vmdk to your Proxmox VE server into the following dir: /var/lib/vz/images (I used [http://winscp.net WinSCP] as I worked on a Windows desktop)
* Change the win2003-pve.vmdk file to qemu format
<pre>qemu-img convert -f vmdk win2003-pve.vmdk -O qcow2 win2003-pve.qcow2</pre>
 
==Create a new KVM Virtual Machine==
* Create a new KVM Virtual Machine via the Proxmox VE management interface - do not start.
* Edit the corresponding config file on the console to replace/add the created win2003-pve.qcow2 as hda:
 
<pre>nano /etc/qemu-server/123.conf
 
OLD:
 
ostype: w2k3
network: model=virtio,tap
memory: 512
onboot: 0
cdrom: kvm-driver-disc-20080318.iso
name: win2003-migrate
hda: /var/lib/vz/images/vm-123-default.qcow2
 
NEW:
 
ostype: w2k3
network: model=virtio,tap
memory: 512
onboot: 0
cdrom: kvm-driver-disc-20080318.iso
name: win2003-migrate
hda: /var/lib/vz/images/win2003-pve.qcow2</pre>
 
* 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]]
* If you need to add more disk, just proceed in the same way and add the disk file as hdb, hdc, ... to the /etc/qemu-server/123.conf config file.
* Finished!
 
For comments or problems please post to the [http://www.proxmox.com/forum/forumdisplay.php?f=12 Proxmox VE forum] or to the [http://pve.proxmox.com/wiki/Mailing_Lists mailing list]
 
=XEN to Proxmox VE (KVM)=
tbd.
 
=Physical server (or XEN or VMware or other) to Proxmox VE (Container)=
tbd.
see [http://wiki.openvz.org/Physical_to_container Physical_to_container]
[[Category: HOWTO]]

Latest revision as of 15:47, 13 February 2024

Redirect to:

Retrieved from "https://pve.proxmox.com/mediawiki/index.php?title=Migration_of_servers_to_Proxmox_VE&oldid=11937"