Bug 592806
| Summary: | rhel4 PV guest installations busted on rhel 5.5 i386 intel boxboro dom0 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | yanfu,wang <yanwang> | ||||
| Component: | kernel-xen | Assignee: | Xen Maintainance List <xen-maint> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.7.z | CC: | drjones, xen-maint | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-05-17 10:11:17 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
yanfu,wang
2010-05-17 02:48:57 UTC
Install a rhel5.5 GA treeļ¼ hadn't upgraded to the lastest 5.5.z kernel, and same problem occur on yet, pls refer to the below job: http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=157517 4.7.z does not support Boxboro (Nehalem-EX), pls refer to bz491338. (In reply to comment #2) > 4.7.z does not support Boxboro (Nehalem-EX), pls refer to bz491338. The bz referenced here is for a deadlock, but the backtrace in this bug is in paging code, and looks unrelated. Does this machine have >= 64G of memory? If so, then this bug is likely a dup of bug 504988. (In reply to comment #3) > (In reply to comment #2) > > 4.7.z does not support Boxboro (Nehalem-EX), pls refer to bz491338. > > The bz referenced here is for a deadlock, but the backtrace in this bug is in > paging code, and looks unrelated. Does this machine have >= 64G of memory? If > so, then this bug is likely a dup of bug 504988. I check the machine intel-s3e36-01.lab.bos.redhat.com which my job run on it, seems not. [root@intel-s3e36-01 ~]# cat /proc/meminfo MemTotal: 14042112 kB MemFree: 13552432 kB Buffers: 31072 kB Cached: 144136 kB SwapCached: 0 kB Active: 76292 kB Inactive: 140100 kB HighTotal: 13303304 kB HighFree: 13096432 kB LowTotal: 738808 kB LowFree: 456000 kB SwapTotal: 3899384 kB SwapFree: 3899384 kB Dirty: 28 kB Writeback: 84 kB AnonPages: 41164 kB Mapped: 12196 kB Slab: 39600 kB PageTables: 2076 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 10920440 kB Committed_AS: 276988 kB VmallocTotal: 114680 kB VmallocUsed: 9796 kB VmallocChunk: 104784 kB [root@intel-s3e36-01 ~]# uname -a
Linux intel-s3e36-01.lab.bos.redhat.com 2.6.32-19.el6.x86_64 #1 SMP Tue Mar 9 17:48:46 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@intel-s3e36-01 ~]# free -m
total used free shared buffers cached
Mem: 64439 2429 62009 0 75 752
-/+ buffers/cache: 1602 62837
Swap: 66495 0 66495
Looks like it has 64G.
(In reply to comment #5) > [root@intel-s3e36-01 ~]# uname -a > Linux intel-s3e36-01.lab.bos.redhat.com 2.6.32-19.el6.x86_64 #1 SMP Tue Mar 9 > 17:48:46 EST 2010 x86_64 x86_64 x86_64 GNU/Linux > [root@intel-s3e36-01 ~]# free -m > total used free shared buffers cached > Mem: 64439 2429 62009 0 75 752 > -/+ buffers/cache: 1602 62837 > Swap: 66495 0 66495 > > Looks like it has 64G. hi Andrew, Thanks your reminder, I checked my failed jobs about the mem size again, seems there is limit with the available memory in kernel-xen on host, the info is below: ********** System Information ********** Hostname = intel-s3e36-01.lab.bos.redhat.com Kernel Version = 2.6.18-194.el5xen Machine Hardware Name = i686 Processor Type = i686 uname -a output = Linux intel-s3e36-01.lab.bos.redhat.com 2.6.18-194.el5xen #1 SMP Tue Mar 16 22:08:06 EDT 2010 i686 i686 i386 GNU/Linux Swap Size = 3807 MB Mem Size = 13713 MB pls refer to these below links, sorry I can't reserve the machine to double check since there's problem on inventory today. http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=14084523 http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=14058503 http://rhts.redhat.com/testlogs/2010/05/156034/400833/3242361/sys.log (In reply to comment #6) > hi Andrew, > Thanks your reminder, I checked my failed jobs about the mem size again, seems > there is limit with the available memory in kernel-xen on host, the info is Right, there are limits. 32G is the limit for a 64b dom0, and 16G for a 32b. There's a warning in the third log file you linked to. <4>RAM exceeds maximum supported memory for x86, Truncating to 64GB <4>Warning only 4GB will be used. <4>Use a PAE enabled kernel. When I hopped on the machine it was booted to a bare-metal kernel, so I just did 'free -m'. If you want to check system memory on a dom0 (kernel-xen) machine then you should do 'xm info | grep total_mem'. Since I saw 64G on the system, and also the warning I've copied above in the log, then I'm pretty sure this bug is a dup of bug 504988. I guess leaving it closed as NOTABUG is fine as well though. |