This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 1729] Fail to create HVM after creating large memory gue

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1729] Fail to create HVM after creating large memory guest
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 31 Jan 2011 18:58:17 -0800
Delivery-date: Mon, 31 Jan 2011 18:58:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1729-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

shaohui.zheng@xxxxxxxxx changed:

           What    |Removed                     |Added
            Summary|xl does not check the memory|Fail to create HVM after
                   |size of guest               |creating large memory guest

------- Comment #1 from shaohui.zheng@xxxxxxxxx  2011-01-31 18:58 -------
Try to create a guest OS with the memory size which is more than the physical
memory size, the creation will fail obviously, but after that, xen print a lot
of memory allocation error, and we can not create any HVM guest anymore.

xl should be responsible to check whether the system free memory is enough to
create the guest, it should forbid such illegal action. 

it is a serious issue since it may cause all the HVM creation fail after this
action action.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>