WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] resize xen disk file

To: "Rudi Ahlers" <Rudi@xxxxxxxxxxx>
Subject: Re: [Xen-users] resize xen disk file
From: "Brian Stempin" <brian.stempin@xxxxxxxxx>
Date: Thu, 6 Mar 2008 23:40:31 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 06 Mar 2008 20:41:03 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=hHQuo9RutcaYAVfvoEHfLFhQrZWtcfhhEBKGSZAZd5A=; b=K+AJMmJSjRQxObM9sT6OhvyBjMHQKHUlDDyFrQNJUmvy0UiJjvuTeGiPHmjpOJksitSMiif/RiEgtn5HZ8o4VnvZN8aB8mPif3nCsh/9e2gkMbzNrr8a3Fx+Q4Cy73qvT++zDQxZWi6oYuE3GvJJjJT/Ti2e7DUBNKLlayTwr9Q=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=KQMUP2lT/+JsEJLA5YySvw48CUimW+5oexwbELHuGQyn6+4R+1vExb2m7lBgVopCbJ/f19SJUtkAYCJihZj49Xi4DePiz1cU/R6fxSlwc1n/CkqsyY+glfdHfRlVcvgoOHEIfJmsBHsFbC/cT23/8uzOwDSzT+qdWbTmXpF5ZQs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47D0C3C0.2070300@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <d35cd2560803060807u58b132dfo9e003b4783ff479@xxxxxxxxxxxxxx> <351785350803061011s1f89f392vd66b8eeff02ce1c6@xxxxxxxxxxxxxx> <d35cd2560803061018y595154d6hb583e64b15cf577b@xxxxxxxxxxxxxx> <47D05F47.1060301@xxxxxxxxxxx> <90eb1dc70803061354o6ca90dc7h4f417602151e942@xxxxxxxxxxxxxx> <47D06D11.2030700@xxxxxxxxxxx> <351785350803061733u34080122t5b354c0b26732788@xxxxxxxxxxxxxx> <351785350803061740l51b00ed4qd12c611b6740e5f3@xxxxxxxxxxxxxx> <47D0C3C0.2070300@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Rudi,

Great, so existing data should still stay the same then
 
Yes, your data will remain untouched if you use conv=notrunc

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

That's not quite what I meant.  Some people prefer to install their VMs directly to disk.  Instead of having a disk stanza that contains "file:/media/storage/domainxx/disk0.img", you could use "phy:/dev/sda1".  In cases where you want to use direct access, it's generally a common practice to use LVM on dom0 to make managing these physical partitions easier.  The domU doesn't ever need to know that it's disk is really a LV, and thus does not need any LVM utilities installed.



On Thu, Mar 6, 2008 at 11:25 PM, Rudi Ahlers <Rudi@xxxxxxxxxxx> 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
>
> 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
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

I'm learning a lot today :)

--

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web:   http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stugg


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>