I have this kernel option in grub.conf: dom0_mem=512m After boot, dom0 allocates all memory instead of 512M. It used to work in rhel-5.2. As a workaround, I have to call: $ xm mem-set Domain-0 512
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
Can you please attach the full output of the grub.conf entry that you think should work, but doesn't? Thanks, Chris Lalancette
FYI: on my system, the following does indeed do the right thing: title Red Hat Enterprise Linux Server (2.6.18-134.el5virttest12xen) root (hd0,0) kernel /xen.gz-2.6.18-134.el5virttest12 dom0_mem=512M module /vmlinuz-2.6.18-134.el5virttest12xen ro root=/dev/VolGroup02/LogVol00 module /initrd-2.6.18-134.el5virttest12xen.img # xm list (right after boot) Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 512 4 r----- 27.8 Chris Lalancette
Chris, sorry for confusion, I had the dom0_mem as a kernel (not xen) option in grub.conf. Now everything works fine. Since I didn't have xen dom0 ballooning problems for a long time so I thought that the "not enough memory" problems during `xm create` were caused by a kernel upgrade and therefore a regression. Looks like I was just lucky and didn't hit this problem since 5.2 was released until now. thanks, - daniel