<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Thanks for your answers, but I still don't know how to do it. Ben, yes I used an lvg with xenguest-install. Then, with anaconda, I created a single partition in it to mount "/" (size=full disk=size of lvg). domU sees one disk (/dev/xvda) with one partition (/dev/xvda1) and yes, after that, I successfully expanded the size of the lvg from dom0. After that I'm stucked: - I cant expand the filesystem for "/" from domU: "fdisk" gives the correct (new) size for "/dev/xvda", but I can't use parted or rezise2fs on "/dev/xvda1" as it is mounted... - I could create another lvg, clone its content ("dd if=lvg of=clonevg"), then start my domU from the clonevg and pass the original one to the domU in the config file, then use "parted" on "resize2fs" from domU on teh unmounted partition, then stop domU and start it again with the original expanded lvg with teh expanded filesystem on it . But it's a real pain.. - Maybe, from dom0, a combination of "lomount" and "parted" or "resize2fs" or other tools could do the job but I don't know how to do it. Thanks for your help. (I realize after re-reading that maybe this is not a xen specific question..) Ben wrote: <blockquote cite="midPine.LNX.4.64.0604241109560.15001@localhost.localdomain" type="cite">Sorry, I should have been more clear. When you create the domU, you need to give it an LVM logical volume. As far as the domU is concerned, it's just a disk. But from the dom0 side, it's an easily expandible partition. After you grow it, use tools on the domU side to expand the filesystem. There's really no point in trying to expand a swap partition because you can just make another one. On Mon, 24 Apr 2006, Chris Hirsch wrote: <blockquote type="cite">Ben wrote: <blockquote type="cite">Yeah, you use LVM and grow you logical volume size, then expand it in the guest domain. I'm not sure, but I suspect you'd have to restart your guest before you can expand it. </blockquote> But isn't the xvda just a file containing partitions and the like? I've actually been wanting to do this myself WITH LVM. I'd LOVE to have lvm extend the file itself. I did find the trick extending an image: dd if=/dev/zero bs=1024 count=3500000 >> fedora.fc5.img resize2fs -f fedora.fc5.img and thats works great...The way I understand the xvda file is that you'd have to copy out anything that is after the main image resize the image (like above) and then append the old stuff back to the end of the disk. I'd assume "stuff" here to mean something like swap. Chris </blockquote> -- Fedora-xen mailing list <a class="moz-txt-link-abbreviated" href="mailto:Fedora-xen@redhat.com">Fedora-xen@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/fedora-xen">https://www.redhat.com/mailman/listinfo/fedora-xen</a> </blockquote> </body> </html>