WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 901] PANIC ON CPU X - Fatal page fault at Domu creation

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 901] PANIC ON CPU X - Fatal page fault at Domu creation - WORKAROUND FOUND
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 19 Feb 2007 12:42:24 -0800
Delivery-date: Mon, 19 Feb 2007 12:43:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-901-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/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=901


mister.binda@xxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
            Summary|PANIC ON CPU X -  Fatal page|PANIC ON CPU X -  Fatal page
                   |fault at Domu creation      |fault at Domu creation -
                   |                            |WORKAROUND FOUND




------- Comment #1 from mister.binda@xxxxxxxxxx  2007-02-19 12:42 -------
Gotcha!
The error raises because the hypervisor seem not to be able to shrink enough
Dom0 memory in presence of on or more HVM guest (and Dom0 normally takes as
much ram as he can). For some reason the error 'Cannot allocate memory' is
given only if the paravirt. machines have no eth interface configured,
otherwise che cpu panic happens making the error hard to individuate (that
sound very strange but any of my tries have always brought to that conclusion).
The workaround to solve that issue is to force Dom-0 memory manually *BEFORE*
starting domUs ("xm mem-set Domain-0 xyzM" where xyz is the maximum MB that
dom-0 should use). Eventually you can raise again Dom-0 ram *AFTER* the
creation of domUs
Oh yes! for those who uses lvm backend do not force 256 MB or less for dom0 or
it will may hang during lvm operations (lvcreate etc...)


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

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