Details
Description
1. Post-installation, dom0_mem was set to default 752M in /boot/grub.cfg
2. Changed value to 2048M:
menuentry 'XenServer' {
search --label --set root root-oejmirfv
multiboot2 /boot/xen.gz dom0_mem=2048M ....
3. Post reboot and unlike XenServer 6.5, I found that /etc/xensource-inventory states dom0_mem as:
cat /etc/xensource-inventory | grep "^DOM"
...
DOM0_MEM='752'
4. Checked free -m for control domain mem:
[root@CHAMP boot]# free -m
total used free shared buffers cached
Mem: 1455 1183 272 1 76 243
-/+ buffers/cache: 863 592
Swap: 511 0 511
5. Check xl dmesg for Command Line (boot) entry:
(XEN) [ 0.000000] Bootloader: GRUB 2.02~beta2
(XEN) [ 0.000000] Command line: dom0_mem=2048M watchdog dom0_max_vcpus=2 crashkernel=128M@32M cpuid_mask_xsave_eax=0 console=vga vga=mode-0x0311
5. Completed another reboot for sanity and /etc/xensource-inventory does not reflect dom0_mem value of 2048M
With 6.5, changes in DOM0_MEM settings were reflected (after reboot) in /etc/xensource-inventory as well as XAPI, etc. Since this file is used in troubleshooting live and offline, I present this minor item for consideration/review.
I cannot track down what init-level bit is responsible for updating this in 6.5 nor Dundee – wish I could be of more help there.
Thanks!