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

To: "MaoXiaoyun" <tinnycloud@xxxxxxxxxxx>, "xen devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: RE: blue screen in windows balloon driver
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sun, 27 Feb 2011 22:25:28 +1100
Cc: george.dunlap@xxxxxxxxxxxxx
Delivery-date: Sun, 27 Feb 2011 03:26:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BLU157-w6407B20CA375D42DAB1348DADC0@xxxxxxx>
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: <BLU157-w6407B20CA375D42DAB1348DADC0@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcvVtWRhwqYwhbw2TUSiOfXTFulf5wAul59w
Thread-topic: RE: blue screen in windows balloon driver
> Thanks James.
> I think it is GPLPV. The driver is from
> pvdrivers.hg
> But, I have done some other things
> 1) Add pod support
> 2) enable a meminfo thread, periodically write VM meminfo into
>     We use info of Current Memory, Free memory, and Committed memory,
> through NativeAPI
> 3) our code is based from changeset 823, attached is the diff of my
> code with changset of 853.
> Maybe I need add my code to 853, and test again.
> Thanks.

As per other post, I have just committed some patches and PoD should now
be working properly. I can start a DomU with 4GB of maxmem but only
128MB of populated memory without any problems. This now works because I
do the initial balloon down in DriverEntry, way before xenpci does
anything else. Before it would blow up in DriverEntry. I think I
determine the amount to initially balloon down a little differently from
you too.

It takes a while to balloon down the memory though... I think Windows
tends to delay large allocations or something, because ballooning up
again is pretty much instant.

How often are you writing meminfo stuff into xenstore? Could you do that
in userspace (the interface to xenstore exists and seems to work well
although it's a little tedious)? You would then be able to just run it
as a service and not need to patch GPLPV.


Xen-devel mailing list