Re: [Xen-users] resize xen disk file

[Nico Kadel-Garcia <nkadel@xxxxxxxxx>]

Rudi Ahlers wrote:
> Brian Stempin wrote:
> > Rudi,
> >
> > conv=notrunc prevents dd from truncating the file.  Normally, dd 
> > would just overwrite the file.  When using conv=notrunc, dd will 
> > leave the existing data alone and stop taking on 0s when the desired 
> > file size is reached.
> Great, so existing data should still stay the same then?
> > Setting up LVM inside of a VM is the most useful in cases where you 
> > give the VM direct disk access.  Since you have a file (or a series 
> > of files), most of the advantages that LVM affords you are redundant.
> Ok, so you're saying that when I setup the VM's / dum_U's, and I get 
> to the partitioning part, that I should use LVM? Even thoug h LVM is 
> already being used on dom0 / the main server's hard drives? That 
> sounds odd to me, but I'll give it a shot on my next VM deployment
Use LVM to create partitions, on Dom0, to act like block devices on 
DomU. Use them as raw block block devices, not LVM, inside the DomU: you 
can add a pretty arbitrary number of such block devices in DomU, and do 
your resizing on Dom0 with the DomU shut down. This works well for 
everything except the boot loader, which is its own adventure in Xen.
> > Since you're using LVM, you'll have to expand your LVM partitions 
> > before you can expand the underlying EXT2 file system.  As indicated 
> > earlier in this email chain, you can expand your LVM group via 
> > pvresize and lvextend.
> My main system still has plenty space on the HDD's, and I use image 
> files for the VM's, not seperate LV's / PV's - The only reason I use 
> LVM is to make it easier to upgrade the HDD's
Hmm. Can you keep snapshotting that way? And don't you suffer a 
performance penalty?
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users