Bug 478812 - Size of Maximum allocation for memory should not exceed the total memory on host
Summary: Size of Maximum allocation for memory should not exceed the total memory on host
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-05 08:18 UTC by Yolkfull Chow
Modified: 2010-03-16 17:17 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-16 19:11:27 UTC
Embargoed:


Attachments (Terms of Use)
screen shot of this problem (52.77 KB, image/png)
2009-01-05 08:18 UTC, Yolkfull Chow
no flags Details

Description Yolkfull Chow 2009-01-05 08:18:33 UTC
Created attachment 328177 [details]
screen shot of this problem

Description of problem:
In virt-manager->hardware->Memory, user could allocate a size of Maximum exceed that total memory on host which should not be I think. 

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

How reproducible:
Everytime

Steps to Reproduce:
1. launch virt-manager
2. go to "Hardware"->Memory, try to increase the size of Maximum allocation exceed the total memory below
3.
  
Actual results:
The size could be increased without a stop.

Expected results:
The size should be only allocated by the size of total memory on host.

Additional info:

Comment 1 Daniel Berrangé 2009-01-05 11:06:56 UTC
This is not so clear-cut. KVM allows  overcommit of memory, and only pages in RAM when it is actually accessed by a guest. So you can trivially boot a guest with more RAM than is available in the host. It is wise to make sure there is enough SWAP space in the host to cope with this overcommit, but we shouldn't deny overcommit in virt-manager IMHO.

Comment 2 Cole Robinson 2009-11-16 19:11:27 UTC
Closing as NOTABUG as per comment #1.


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