Bug 180375 - VMX guest auto-balloon doesn't take into account video memory
Summary: VMX guest auto-balloon doesn't take into account video memory
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 179629
TreeView+ depends on / blocked
 
Reported: 2006-02-07 18:43 UTC by Jeremy Katz
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-05 17:48:51 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jeremy Katz 2006-02-07 18:43:03 UTC 
VMX guests don't cause dom0 to auto-balloon as paravirt guests do.  Probably
just needs some logic brought over to the vmx builder
Comment 1 Jeremy Katz 2006-02-07 20:31:20 UTC 
Hrmm, it's all common code. 
tools/python/xen/xend/XendDomainInfo.py:initDomain() is where the balloon call
occurs and then it's followed almost directly by the memory_increase_reservation.
Comment 2 Jeremy Katz 2006-02-07 22:56:42 UTC 
Urk, this is caused by the device model requesting more memory to store the
video RAM in.  Bad hack committed to CVS so that we account for that when
ballooning at domain creation, but it needs a better solution for
upstream/long-term.  Filed upstream as
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=521
Comment 5 Jeremy Katz 2006-09-05 17:48:51 UTC 
A nice fix for this went upstream earlier today
Note You need to log in before you can comment on or make changes to this bug.