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] re:RE: blue screen in windows balloon driver

To: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] re:RE: blue screen in windows balloon driver
From: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>
Date: Sat, 26 Feb 2011 21:01:38 +0800
Cc: george.dunlap@xxxxxxxxxxxxx, james.harper@xxxxxxxxxxxxxxxx
Delivery-date: Sat, 26 Feb 2011 05:03:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanks James.
 
I think it is GPLPV. The driver is from http://xenbits.xen.org/ext/win-pvdrivers.hg
But, I have done some other things
 
1) Add pod support
2) enable a meminfo thread, periodically write VM meminfo into xenstore
    We use info of Current Memory, Free memory, and Committed memory, retrived through NativeAPI
3) our code is based from changeset 823, attached is the diff of my current code with changset of 853.
 
Maybe I need add my code to 853, and test again.
Thanks.
 
>From: James Harper [mailto:james.harper@xxxxxxxxxxxxxxxx]
>To: xiaoyun.maoxy; xen-devel@xxxxxxxxxxxxxxxxxxx
>cc: george.dunlap@xxxxxxxxxxxxx
>Subject: RE: blue screen in windows balloon driver
>
>> 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, how could "NO_PAGES_AVAILABLE" happen?
>>      Also, since we enable VM writes its memory status into xenstore,
>>      when blue screen, it has only has 972KB memory.
>>      Any comments? Many thanks.
>>
>
>
>You've put myself (I wrote GPLPV) and George Dunlap (from Citrix) in the
>CC list but you don't say if you are using GPLPV drivers or Citrix PV
>drivers. If you are using GPLPV drivers let me know and I'll get some
>more i nformation about the problem from you. If you aren't using GPLPV
>drivers then I don't think I can be of much assistance...
>
>Thanks
>
>James
>

Attachment: changset823.diff
Description: Binary data

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