On Tuesday 13 April 2010 16:27:44 Nick Couchman wrote:
> Unfortunately functionality like this requires end-to-end supports for this
> change. Not only do you need to be able to extend the backend device
> (lvextend, like you did), you need Xen to see it (probably the feature you
> mentioned), you need the guest kernel to see it, and you need the
> filesystem to be able to expand. Getting the guest kernel to see the
> change has always been the tricky piece, as the kernel usually locks this
> information in and you have to reboot for it to reread the information.
> However, I saw some patches recently for the Linux kernel that allow for
> on-the-fly resizing of disks, and I think I actually tried it with some
> amount of success. I wish I still had the links - I would point you in
> the direction of them.
The patches for the Linux Kernel have been included in the latest Suse patch-
set.
One thing with these is, though, that the new size isn't noticed by the guest
untill you actually access the disk.
A "ls" on the mount is sufficient for this.
> Other guest operating systems will vary on whether they support this or
> not. Windows is usually pretty good about detecting size changes for
> disks and allowing you to expand the filesystem. Other O/Ss will vary.
I doubt MS Windows will notice this change as it requires Driver-support in
the guest-OS for this to work.
--
Joost
>
> >>> On 2010年04月12日 at 21:39, Chao-Rui Chang <ppc52776@xxxxxxxxx> wrote:
> >
> > Hello all,
> >
> > I just notice the new feature in the latest version 4 release.
> >
> > Any one know how to do this ?
> >
> > I have tried lvextend the partition size in dom0,
> > but domU doesn't see the change.
> > I also need to reboot to make domU reread the block size.
> >
> > Any idea?
> >
> > Best regards,
> > Chao-Rui
>
> --------
> This e-mail may contain confidential and privileged material for the sole
> use of the intended recipient. If this email is not intended for you, or
> you are not responsible for the delivery of this message to the intended
> recipient, please note that this message may contain SEAKR Engineering
> (SEAKR) Privileged/Proprietary Information. In such a case, you are
> strictly prohibited from downloading, photocopying, distributing or
> otherwise using this message, its contents or attachments in any way. If
> you have received this message in error, please notify us immediately by
> replying to this e-mail and delete the message from your mailbox.
> Information contained in this message that does not relate to the business
> of SEAKR is neither endorsed by nor attributable to SEAKR.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users