From mboxrd@z Thu Jan 1 00:00:00 1970 From: ANNIE LI Subject: Re: Balloon down memory failed in x86 PAE mode when memory size>4G Date: Mon, 21 Sep 2009 18:14:07 +0800 Message-ID: <4AB751EF.4070108@oracle.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0394607324==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============0394607324== Content-Type: multipart/alternative; boundary="------------050809090603000604070502" This is a multi-part message in MIME format. --------------050809090603000604070502 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit >> My xen version is Xen3.4.0, and i use el5u2 pvhvm to have test. >> The memory size is 6114. "xm info" dose not show any change on free_memory >> after command "xm mem-set domid 4096". It seems free_memory will change after >> i set memory size less than 3083M, such as: free memory will increase 1 after >> command "xm mem-set domid 3082". >> > > And this is the exact same behaviour you see in a PAE Linux HVM guest with > PV drivers also? It's weird, seems like maybe for some reason the balloon > driver thinks the guest has 3083M and therefore doesn't balloon down until > it sees a target lower than that, and even then only by the difference > between 3083M and the target. > > I suggest you add tracing to your PV drivers and see what the balloon driver > thinks is going on. This configuration really should work, so hopefully only > something simple and stupid is going wroing. Sorry the false alarm. The linux template el5u2 i use can not manage memory larger than 4G even if i set the 6G memory and PAE mode in vm configure file, because CONFIG_HIGHMEM4G is set when compiling the OS kernel. I did more test on el4u8 with CONFIG_HIGHMEM64G enabled, balloon works correctly. I will check the windows pv driver again. Thanks Annie. --------------050809090603000604070502 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 
My xen version is Xen3.4.0, and i use el5u2 pvhvm to have test.
The memory size is 6114.  "xm info" dose not show any change on free_memory
after command "xm mem-set domid 4096". It seems free_memory will change after
i set memory size less than 3083M,  such as: free memory will increase 1 after
command "xm mem-set domid 3082".
    

And this is the exact same behaviour you see in a PAE Linux HVM guest with
PV drivers also? It's weird, seems like maybe for some reason the balloon
driver thinks the guest has 3083M and therefore doesn't balloon down until
it sees a target lower than that, and even then only by the difference
between 3083M and the target.

I suggest you add tracing to your PV drivers and see what the balloon driver
thinks is going on. This configuration really should work, so hopefully only
something simple and stupid is going wroing.
Sorry the false alarm.
The linux template el5u2 i use can not manage memory larger than 4G even if i set the
6G memory and PAE mode in vm configure file, because CONFIG_HIGHMEM4G is set
when compiling the OS kernel.

I did more test on el4u8 with CONFIG_HIGHMEM64G enabled, balloon works correctly.

I will check the windows pv driver again.

Thanks
Annie.
--------------050809090603000604070502-- --===============0394607324== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0394607324==--