On Fri, 2007-10-19 at 13:34 -0400, Dustin Henning wrote:
> >-----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: [Fedora-xen] 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,
> Could you tell me if you passed any arguments to the installer during
> your initial install? Also, can you show me the appropriate portion of your
> grub.conf? I would like to see if maybe it is different than mine even
> though they are both pre-packaged installs. I had a machine with
> 2.6.20-2931.fc7xen, so I copied that to the machine in question, and it also
> only shows 3.1GiB for me. I compared the config files for that kernel and
> the one I was using, and they are identical (minus version and date comment
> lines), so that was as I expected, but it makes it less likely that my
> problem is a version problem and more likely that something else is haywire.
> Thanks,
> Dustin
My install command line was:
ksdevice=eth0 console=tty0 console=ttyS0,9600 load_ramdisk=1
initrd=f7/x86_64/initrd.img network ks=http://ks/ks-f7-v40z.cfg
kssendmac BOOT_IMAGE=f7/x86_64/vmlinuz
My grub entry for the currently running kernel is:
title Fedora (2.6.20-2931.fc7xen)
root (hd0,0)
kernel /xen.gz-2.6.20-2931.fc7 com1=9600
module /vmlinuz-2.6.20-2931.fc7xen ro root=/dev/VGRAID/LVRoot
console=ttyS0,9600
module /initrd-2.6.20-2931.fc7xen.img
My messy KS and KS post script is attached.
During install, I did hit a bug
https://bugzilla.redhat.com/show_bug.cgi?id=242107 that I had to work
around by running mkinitrd before I rebooted. If I didn't I would be
missing the RAID1 module and fail to boot, but that's not related to the
memory issue.
--
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
install-ks.cfg
Description: Text document
ks-post-config.sh
Description: application/shellscript
|
