I suggest the virt-clone method since I use it for cloning windows and
linux. It is a perfect tool. I created a template windows and linux
setup. First, shut the main copy, after virt-clone, change the temp
name and IP and use it.
- vserver01 template copy to vserver0X example,
- virt-clone
- (file path)? /var/lib/xen/images/xserver0X.img
- the name of the original virtual machine? xserver01
- the name for the cloned virtual machine? xserver0X
- Cloning from /var/lib/xen/images/xserver01.img to
/var/lib/xen/images/xserver0X.img
- Change IP address
- Change name if Windows as xserver0X
Jeff Williams wrote:
On
08/06/09 23:02, Olivier B. wrote:
Javier Guerra a Ãcrit :
On Mon, Jun 8, 2009 at 9:42 AM, Olivier
B.<xen.list@xxxxxxxxx> wrote:
Â
about LVM : one the big advantages of LVM
is the resize... "lvresize" on
Dom0, then (for ext3/ext4) resize2fs in DomU.
ÂÂÂ
add a partition resize step. even so, this only works if the
filesystem you want to resize is the last partition in the virtual
device
Â
I never partition LVM "virtual device", I used different LV. So there
is no problem to resize any of this partitions.
About the additionnal step, I don't really see where it is a problem.
So to confirm, rather than making /dev/xenvg/domudisk and doing:
disk = ['phy:/dev/xenvg/domudisk,xvda,w']
and partitioning /dev/xenvg/domudisk in the guest, you'd make (for
example):
/dev/xenvg/domudisk-root
/dev/xenvg/domudisk-home
/dev/xenvg/domudisk-swap
and configure it like:
disk = [
ÂÂ 'phy:/dev/xenvg/domudisk-root,xvda1,w',
ÂÂ 'phy:/dev/xenvg/domudisk-home,xvda2,w',
ÂÂ 'phy:/dev/xenvg/domudisk-swap,xvda3,w'
]
Is that right? The idea had crossed my mind, but all the tools seemed
to want to do it the other way.
Regards,
Jeff
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
--
Umut Arus
SabancÄ Ãniversitesi - Bilgi Teknolojisi
http://www.sabanciuniv.edu
Tel: (+90 216) 483 9172
|
