Re: [Xen-users] Suspicious URL:Re: Problem using PoD on Xen 4.2.1 (win domU crash)

[James Harper <james.harper@xxxxxxxxxxxxxxxx>]

> Hi,
> 
> I just tried on my win2008R2/64 and it is still the same with the new driver.
> Started with 1/8GB; no sign of a "balloon"; did some alloc/dealloc until it
> crashed.
> Tried both regular & debug. Log and xl dmesg attached.
> 
> (To make sure, I just also tried with 1/4GB - the same)
> 

Your one says:

13005008825593: XenPCI --> XenPci_InitialBalloonDown
13005008825593: XenPCI     base = 0x40000000, Xen Signature = Microsoft Hv, EAX 
= 0x40000006
13005008825593: XenPCI     base = 0x40000100, Xen Signature = XenVMMXenVMM, EAX 
= 0x40000102
13005008825593: XenPCI     Xen Version 4.2
13005008825593: XenPCI     Hypercall area at FFFFFA80063A4000
13005008825593: XenPCI     XENMEM_maximum_reservation = 262400
13005008825593: XenPCI     XENMEM_current_reservation = 262136
13005008825609: XenPCI     Trying to give 1056 KB (1 MB) to Xen
13005008825624: XenPCI <-- XenPci_InitialBalloonDown

So for some reason gplpv can't determine that you want to be ballooned down 
7GB, it's just giving back the default 1MB (there are/were some problems with 
save/restore when this didn't happen).

I notice you are using 4.2 while I'm using 4.1, which probably accounts for the 
difference.

I'll post on xen-devel to ask what the correct way of determining this is under 
4.2...

I suspect that giving your VM 8G but ballooning down to 1G might be pushing 
things a bit. There are overheads with higher amounts of memory, and Windows 
will make some assumptions about how large to allocate internal tables etc 
based on the amount of memory.

James

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users