[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Expanding a virtual block device


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Fajar A. Nugraha" <list@xxxxxxxxx>
  • Date: Mon, 2 May 2011 19:10:38 +0700
  • Delivery-date: Mon, 02 May 2011 05:12:23 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Mon, May 2, 2011 at 6:58 PM, Andy Smith <andy@xxxxxxxxxxxxxx> wrote:
> Hi Mark,
>
> On Mon, May 02, 2011 at 12:44:09PM +0200, Mark Dokter wrote:
>> On 05/02/2011 10:07 AM, Vivien Bernet-Rollande wrote:
>> > I want to resize my disk, and have Xen and the domU notice it, without
>> > having to reboot the domU.
>> >
>> > Is this actually possible with Xen ?
>>
>> I tried this and it's actually not a Xen issue. A resized volume in dom0
>> (even on DRBD :) ) is noticed by the domU.
>
> Are you sure about that? It's never worked for me, but I've not yet
> tried it in Xen 4.x. It's always needed a shut down and boot of the
> domU for me, for it to see a larger block device.

It used to be like that for Xen 3.x

In 4.x, online resize is possible but ONLY if the domU kernel also
support it. I'm using 2.6.32.28 pv_ops from Jeremy's git tree, and it
can recognize the size change just fine once I run partprobe on both
dom0 and domU (the dom0 part might not be necessary though).

Of course, if you have partitions/LV on top of domU's block device,
then it becomes a lot more complicated since you have to deal with
manual partition change or pvresize as well.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.