[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] P2V question
--- On Mon, 4/12/10, Donny Brooks <dbrooks@xxxxxxxxxxxxxxxx> wrote: > From: Donny Brooks <dbrooks@xxxxxxxxxxxxxxxx> > Subject: [Xen-users] P2V question > To: xen-users@xxxxxxxxxxxxxxxxxxx > Date: Monday, April 12, 2010, 1:54 PM > I am looking at virtualizing a few > CentOS 5.4 and Fedora 11 servers (all 64-bit) here at work > onto a brand new shiny Xen 3.4.2 CentOS 5.4 machine. To move > the physical machine to a virtual machine should it be as > easy as > 1. Setup the LVM LV to house the disk on the xen server > 2. Boot the physical machine from a live/rescue cd and use > dd to copy the disk over to the LV on the xen machine. > 3. Mount the LV and change the grub.conf, fstab, and update > the kernel to one that will do paravirt > 4. Setup the guest.xml file and boot > The linked file is a dump of the relevant configs you mentioned above. The traced domU guest is C5 x86_64 with a paravirtual kernel-xen. Unlike Ubuntu and Fedora, but like opensuse, Centos uses a xen kernel in domU. The others use a pv_ops kernel. guest.xml implies using libvirt. You can survive without libvirt and use the xen-tools (xm). -Notice that all hypervisor (xen.gz) references are gone from fstab. -Use labels for your /root and /home -xennet and xenblk.ko are the pivotal PV drivers (xennet is in kernel) -your bootloader is pygrub -pygrub can be dryrun in dom0 pointed to your domU LVM (for test) -your PV kernel is kernel-xen (this is worth repeating) My guest config (C564.py) networks to the dom0 manual bridge. So the xend-config.sxp in dom0 has (network-script network-bridge) commented out and only (network-script network-dummy) is uncommented. -- Mark http://www.tlviewer.org/fostats/c564_pv.txt _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |