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-devel

[Xen-devel] blue screen in windows balloon driver

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] blue screen in windows balloon driver
From: "xiaoyun.maoxy" <xiaoyun.maoxy@xxxxxxxxxxxxxx>
Date: Sat, 26 Feb 2011 19:20:33 +0800
Cc: george.dunlap@xxxxxxxxxxxxx, 'James Harper' <james.harper@xxxxxxxxxxxxxxxx>
Delivery-date: Sat, 26 Feb 2011 13:32:23 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <SNT0-MC4-F15TlpsWqi0002f5ac@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <BLU157-ds1AEAC80753959EC959A12DA160@xxxxxxx> <291EDFCB1E9E224A99088639C47620228CF938AAE0@xxxxxxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01BB8BA7@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcudjQT/1ru6fBA9Q+y8rx823coE9AACJPTwAAxzPMAAAQPzAA25IzBgAD0vYoA=
Hi:

        We've confronted the windows 2003 Blue screen when using balloon
driver.
        
        The blue screen has the information of "NO_PAGES_AVAILABLE", and 
        Technical information:
        ***STOP: 0x0000004D (0x0002A8FB,0x0002A8FB,0x00000000,0x00000000)

        In fact we are doing the stress test on 24 windows2003 HVM on a 24G,
16core host.
        In dom0, there is a daemon process (balloond) will give memory back
to the VM who acclaim memory.
        The balloond will ensure every VM at least has 512M memory.
        
        Each VM is started with memory=512 maxmem=2048
        Inside each of the VM, there is two processes eat memory, each of
which will eat 1G memory.
        And the page file size configured on C:\ is init size 1536M, max
size 3072M, which I think even
        If balloond process not give back the memory back to VM, the VM can
has 512M+3072M = 3.5G virtual
        memory.

        Am I right?, if so , since our eat memory process only consume 2G
memory, h
        how could "NO_PAGES_AVAILABLE" happen?

        Also, since we enable VM writes its memory status into xenstore, and
when blue screen, it has only has 972KB memory.

        Any comments? Many thanks.




        

 
        
        
        


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

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