Migration of servers to Proxmox VE: Difference between revisions

From Proxmox VE
Jump to navigation Jump to search
(Apapted KVM part (new beta2 format))
m (Redirected page to Migrate to Proxmox VE)
Tag: New redirect
 
(169 intermediate revisions by 25 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 [http://www.proxmox.com/cms_proxmox/cms/upload/misc/mergeide.reg 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") - open a cmd and go to the directory where your vmdk disk files are.
<pre>"C:\Program Files\VMware\VMware Server\vmware-vdiskmanager" -r win2003.vmdk -t 0 win2003-pve.vmdk</pre>
* 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 [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>
 
==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 stable)
* 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]]
* 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)=
XEN also uses qemu disk format, so it should work in the same manner as described under "VMware to Proxmox VE (KVM)".
 
=Move OpenVZ containers to Proxmox VE=
You can move existing OpenVZ containers (container=VE=VPS) with vzmigrate or vzdump:
* Use vzmigrate offline migration to move your container to Proxmox VE
* Use vzdump to restore from a backup
 
After you moved your container you need to add the following line to the corresponding config file (see /etc/vz/conf/xyz.conf):
<pre>nano /etc/vz/conf/xyz.conf</pre>
 
Add the following line:
<pre>ORIGIN_SAMPLE="pve.auto"</pre>
 
Now you can manage resource settings on the Proxmox VE management interface.
 
=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"