[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] RE: RE: blue screen in windows balloon driver
> 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. > 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. James _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |