Hi Paras,
I've done p2v migrations another way, that we've found a little
easier to manage:
-
stop all services but networking on the host to migrate (httpd,
mysql, etc.)
-
create a target volume on our virtualization SAN with the
desired size
-
mke2fs the target volume, and mount it somewhere
-
"rsync –a" the entire filesystem from the host
we are migrating to the target volume (probably easier if you umount /proc)
-
Edit /etc/fstab on the target volume, changing from physical
devices to Xen block devices
-
unmount the target volume and stop the physical host
-
create a Xen configuration to go with the target volume, and
appropriate kernel/ramdisk
-
"xm create" the new host
A few extra steps may be necessary, such as adjusting ifconfig-eth0
for the new MAC address, adding xvc0 to /etc/securetty, etc.
This plan lets us partition storage for the virtualization environment
however we like. To keep it simple we often use a single large root
partition—Xen does not require a /boot filesystem on a paravirtualized domU
unless you use pygrub.
Jeff
From:
xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Paras
pradhan
Sent: Friday, May 14, 2010 12:53 PM
To: Xen Users
Subject: [Xen-users] Manual p2v
Hi,
I am converting few physical machines to xen virtual
machines. The virt-p2v requires my physical machines to shut
down. These servers are centos / redhat 5.x. I will be using tap:aio. How
do I create an img file from my partitions? some has 1 HDD and some has 2 or
more.
