Bug 189085 - xend seems to mismeasure memory
Summary: xend seems to mismeasure memory
Alias: None
Product: Fedora
Classification: Fedora
Component: xen (Show other bugs)
(Show other bugs)
Version: 5
Hardware: i686 Linux
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2006-04-15 19:38 UTC by Michael De La Rue
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version: xen-3.0.3-2.fc5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-11 21:20:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Michael De La Rue 2006-04-15 19:38:57 UTC
Description of problem:
On a recently cleanly installed machine with 2Gb of memory the
xenguest-install.py bombs out with the message 

Error: Error creating domain: I need 257 MiB, but dom0_min_mem is 256 and
shrinking to 256 MiB would leave only 1254 MiB free.

Version-Release number of selected component (if applicable):

How reproducible:
every time 

Steps to Reproduce:
1. install FC5 / add xen rpms and dependencies manually
2. use yum to upgrade any fixes
3. boot into xenU0 / standard kernel options from install
4. run /usr/sbin/xenguest-install.py and answer as follows
What is the name of your virtual machine? test4
 How much RAM should be allocated (in megabytes)? 256
 What would you like to use as the disk (path)? /scratch/systems
 What is the install location?
Actual results:
Starting install...
Using config file "/etc/xen/test4".
Error: Error creating domain: I need 257 MiB, but dom0_min_mem is 256 and
shrinking to 256 MiB would leave only 1254 MiB free.
If your install has exited, you can restart your guest by running
'xm create -c test4'.  Otherwise, you can reconnect to the console
by running 'xm console test4'

no guest system is created in /scratch/systems

Expected results:
working xenU installation created / no error output.  

Additional info:
2GB Thinkpad R51.  This seems to be similar to Bug 184393 but I'm posting it as
a new bug since it's in the new/current software version.  I haven't yet tried
with selinux turned off, but I will reboot just after filing this info.  

xm mem-set 0 xxx  seems to work fine.

Comment 1 Michael De La Rue 2006-04-15 20:34:09 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.  

Comment 2 Jeremy Katz 2006-04-17 22:12:54 UTC
xend is doing a backwards comparison... I remember seeing the patch fly across
xen-devel a week or two ago

Comment 3 rhbugs@greebo.org 2006-05-05 16:23:43 UTC
Built a couple systems (one x86_64 one i386) and this problem seemed confined to
i386 version for some bizarre reason.

Comment 4 Daniel Berrange 2007-01-11 21:20:59 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.