Hi, I''m using SLES11 sp2 both on Dom0 and DomU. The kernel is > 3.0 and Xen 4.1 is installed. Online resizing has become a feature not too long ago with XEN. It allows one to expand the disk''s capacity without having to restart DomU. I tried to use that feature, but when I append memory to my virtual block device in Dom0, it is not registered by DomU. I have to either reboot or live migrate in order to achieve a disk resize. I tried to load some modules with modprobe, but it didn''t work. Has anyone been able to achieve an online resize? I should mention that modprobe in DomU doesn''t "see" the additional capacity. Thanks, Stefan
On Thu, Jun 28, 2012 at 3:31 AM, sstan <sstanisi@cbnco.com> wrote:> Hi, > > > I''m using SLES11 sp2 both on Dom0 and DomU. The kernel is > 3.0 and Xen 4.1 > is installed. > > Online resizing has become a feature not too long ago with XEN. It allows > one to expand the disk''s capacity without having to restart DomU. > > I tried to use that feature, but when I append memory to my virtual block > device in Dom0, it is not registered by DomU.You can''t "append memory to my virtual block device". Memory is not a block device.> I tried to load some modules > with modprobe, but it didn''t work."try some stuff at random even if it''s completely unrelated and pray that it works"?> Has anyone been able to achieve an online > resize?Yes.> I should mention that modprobe in DomU doesn''t "see" the additional > capacity.Again, "try some stuff at random even if it''s completely unrelated and pray that it works"? Simply put, just look at domU''s console and syslog. If it shows a block device size change, then your system supports it. If not, then one of the components (either hypervisor or kernel) doesn''t support it. -- Fajar
Hello, "You can''t "append memory to my virtual block device". Memory is not a block device" I''m clearly speaking of disk space / capacity. "try some stuff at random even if it''s completely unrelated and pray that it works"? At random? You should rather read "some RELEVANT modules" ...>> Has anyone been able to achieve an online >> resize? >> Yes. >>Well, may whoever did tell us more about it please? I''m>> I should mention that modprobe in DomU doesn''t "see" the additional >> capacity.I should have wrote "partprobe" ... I realize that the sentence doesn''t make sense, sorry.>> Simply put, just look at domU''s console and syslog. If it shows a >> block device size change, then your system supports it. If not, then >> one of the components (either hypervisor or kernel) doesn''t support >> it.Well that''s why I''m sending this email! According to the documentation, I''m using the right Xen version, SLES version, kernel, etc. This very question keeps coming back on forums... If someone more knowledgeable can address it, please do because no solution is available yet.
On Thu, Jun 28, 2012 at 10:41 PM, sstan <sstanisi@cbnco.com> wrote:>>> Simply put, just look at domU''s console and syslog. If it shows a >>> block device size change, then your system supports it. If not, then >>> one of the components (either hypervisor or kernel) doesn''t support >>> it. > > Well that''s why I''m sending this email! According to the documentation, I''m > using the right Xen version, SLES version, kernel, etc. This very question > keeps coming back on forums... If someone more knowledgeable can address it, > please do because no solution is available yet.There''s nothing much to do, really. Last time I test I was using RHEL5 with gitco''s xen 4.x, and self-compiled kernel based on RHEL''s config. The size change just works. However since my implementation now uses partition table on the block device, the online resize feature is not much use for me (since I''d also have to resize the partition, which must be done offline). Since you say you''re using SLES, perhaps you''ll find more help on their list/forum/support. -- Fajar