XenServer VM start failed due to lack of memory
Bug #962311 reported by
John Garbutt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
It looks like XenServer is not quite reporting the correct memory usage.
On a test machine I had XenCenter reporting:
16374MB total
12224MB used
4151MB available
But the nova db read:
16374MB total
12200MB used
4174MB available
Although this was only out a small amount, I had errors where the scheduler decided to launch an instance on that server, but that spawn failed because there was not enough memory. Possibly because XenServer decided their was not enough memory despite the figures showing that there is enough memory.
In this particular case the scheduler thought a 4GB instance could be launched, but when it attempted it, it failed.
| description: | updated |
| tags: | added: xen |
| tags: |
added: xenserver removed: xen |
Revision history for this message
| Mark McLoughlin (markmc) wrote | #1 |
| Changed in nova: | |
| status: | New → Incomplete |
| status: | Incomplete → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| Mark McLoughlin (markmc) wrote | #2 |
Revision history for this message
| Mark McLoughlin (markmc) wrote | #3 |
| Changed in nova: | |
| status: | Confirmed → Incomplete |
Revision history for this message
| John Garbutt (johngarbutt) wrote | #4 |
| Changed in nova: | |
| status: | Incomplete → Invalid |
To post a comment you must log in.
Doesn't look like much has changed in xenapi's update_status() since John filed the bug, so marking as Confirmed