RE: 64-Bit RAM Detection >4GB?

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

 



>-----Original Message-----
>From: fedora-xen-bounces@xxxxxxxxxx [mailto:fedora-xen-bounces@xxxxxxxxxx] On Behalf Of Dale Bewley
>Sent: Friday, October 19, 2007 11:46
>To: fedora-xen
>Subject: Re:  64-Bit RAM Detection >4GB?
>
>I have 4 procs with 16G RAM and no mem paramters in grub at all, and it looks like this:
>
>Linux h 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
>
># grep 'model name' /proc/cpuinfo
>model name      : AMD Opteron(tm) Processor 852
>model name      : AMD Opteron(tm) Processor 852
>model name      : AMD Opteron(tm) Processor 852
>model name      : AMD Opteron(tm) Processor 852
>
># grep Total /proc/meminfo
>MemTotal:     13335552 kB
>SwapTotal:     5261240 kB
>VmallocTotal: 34359738367 kB
>
># xm info |grep total
>total_memory           : 16319
>
>I have 3 domU's running with each allocated 1G, so 16-3=13 which I suppose explains the MemTotal line above from the perspective of dom0.
>
>
>On an identical server running RHEL with no xen and I see something a bit different:
>
>Red Hat Enterprise Linux AS release 4 (Nahant Update 5)
>Linux z 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:58:20 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
>
># grep Total /proc/meminfo
>MemTotal:     16359284 kB
>HighTotal:           0 kB
>LowTotal:     16359284 kB
>SwapTotal:     5261240 kB
>VmallocTotal: 536870911 kB
>HugePages_Total:     0
>
>Not sure if that was helpful.
>--
>Dale Bewley - Unix Administrator - Shields Library - UC Davis
>GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD  1753 064D 2583 B098 A0F3

Dale,
	That could be very helpful, or it might just get someone to blame Intel.  Either way, thanks, now I at least know that it should work and I can try to determine why it isn't.  As for the MemTotal, you are correct on why it is 13 instead of 16.  However, if you shut down one of those domU's, the memory wouldn't necessarily be automatically re-assigned to dom0, and /proc/meminfo is based on what is assigned to dom0.  I think "xm info" would be the correct way to see the detected memory in the system once domU's are created or if dom0 isn't assigned all memory.  There may be other ways.  Thanks,
	Dustin



--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen

[Index of Archives]     [Fedora General]     [Fedora Music]     [Linux Kernel]     [Fedora Desktop]     [Fedora Directory]     [PAM]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux