Bug 189085
Summary: | xend seems to mismeasure memory | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michael De La Rue <mvyynqbgerqungqbgpbz.yeuhc> |
Component: | xen | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | bstein, katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | xen-3.0.3-2.fc5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-01-11 21:20:59 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: |
Description
Michael De La Rue
2006-04-15 19:38:57 UTC
Turning of selinux with "setenforce 0" has no effect whatsoever. Booting with "kernel /xen.gz-2.6.16-1.2080_FC5 dom0_mem=512M" in /etc/grub.conf seems to fix this problem. Looking at "xm top" it seems as if memory allocated to domain 0 never falls, even if "xm mem-set 0 512" is used. At this point the installation continues on to crash at a later point. xend is doing a backwards comparison... I remember seeing the patch fly across xen-devel a week or two ago Built a couple systems (one x86_64 one i386) and this problem seemed confined to i386 version for some bizarre reason. The problem of the backwards memory comparison was fixed in the 3.0.3 release of Xen. Since FC5 is now on xen-3.0.3-2.fc5, this ticket is resolved. |