I''ve got a strange memory problem...
I installed debian testing with the debian testing version of xen (4.1)
and am using the xm/xend toolstack.
I have 16G RAM installed in the machine, but the dom0 dmesg command
produces the following:
free
total used free shared buffers cached
Mem: 3485856 1026140 2459716 0 87408 751056
-/+ buffers/cache: 187676 3298180
Swap: 1632252 0 1632252
ie, only 3.5G total RAM, which seems to come from this line in the dom0
dmesg:
[ 0.000000] Memory: 15498248k/17268736k available (3418k kernel code,
525336k absent, 1245152k reserved, 3319k data, 576k init)
I realise there is the dom0_mem xen kernel option, but that doesn''t
seem
to be used:
xm dmesg shows:
(XEN) Command line: placeholder dom0_max_vcpus=1 dom0_vcpus_pin=1
also, dmesg shows:
[ 0.000000] Command line: placeholder
root=UUID=8a8dd516-0d4d-4080-af43-d2efffb738a2 ro quiet
which matches /proc/cmdline.
So, I just can''t find where or why the dom0 has less than the full
amount of memory.
xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 3751 1 r-----
5143.2
There are no domU''s currently running, xm info shows:
total_memory : 16351
free_memory : 12417
I have a Windows 2003 domU that I want to run, and I''d like to create a
4G ramdisk, allocate that to the domU, and then get windows to use the
ramdisk for the pagefile (which should provide windows an effective 8G
RAM, and reduce IO to the physical disks).
Of course, the downside I''ve seen to this is that I won''t be
able to do
a live migration anymore (since the pagefile won''t exist on the
destination host), but I can deal with that by simply shutdown on old
machine, and startup on new machine. Also, I will need to pre-populate
the NTFS and pagefile on the ramdisk before windows bootup each time I
reboot the dom0.
Any suggestions on how to get more RAM allocated to the dom0?
Thanks,
Adam
--
Adam Goryachev
Website Managers
www.websitemanagers.com.au
> I installed debian testing with the debian testing version of xen (4.1) > and am using the xm/xend toolstack. >Do you have 32bit or 64bit system? "uname -a" command should print this info.
povder <povder@gmail.com> wrote:>> I installed debian testing with the debian testing version of xen >(4.1) >> and am using the xm/xend toolstack. >> > >Do you have 32bit or 64bit system? "uname -a" command should print this >info.Should be 64bit I think: Linux pm01 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux Anywhere else I might look ? Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au
On 15/01/13 01:03, Adam Goryachev wrote:> povder <povder@gmail.com> wrote: > >>> I installed debian testing with the debian testing version of xen >> (4.1) >>> and am using the xm/xend toolstack. >>> >> Do you have 32bit or 64bit system? "uname -a" command should print this >> info. > Should be 64bit I think: > Linux pm01 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux > > Anywhere else I might look ?I finally solved my "problem"... I realised I only had this problem on two dom0 out of eight, so I compared all files in /etc and then /boot, and started to panic since I couldn''t find any difference. I also compared the output of xm dmesg, dmesg, xm info, etc... all returned basically identical information. Finally, I compared the output of xm list, and suddenly, the light came on :) I had started a couple of domU''s on the dom0 with the problem, hence it had shrunk dom0 dynamically to release memory for the domU''s. When I shutdown (migrated the domU to a different dom0), the dom0 never grew it''s memory back up. I suppose there may be a manual method to tell the dom0 to reclaim the memory, but in my case, a reboot solved the issue. Sorry for wasting everyone''s time, but hopefully this will help someone else looking for some missing memory. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au