From mboxrd@z Thu Jan 1 00:00:00 1970 From: ANNIE LI Subject: Re: Error restoring DomU when using GPLPV Date: Fri, 21 Aug 2009 12:11:49 +0800 Message-ID: <4A8E1E85.6020902@oracle.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1920724150==" 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: Joshua West , James Harper , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============1920724150== Content-Type: multipart/alternative; boundary="------------090701070002030209080006" This is a multi-part message in MIME format. --------------090701070002030209080006 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi >> It seems that a >> restored vm lost those pages ballooned down. For migration, destination >> does not have those pages which ballooned down on source. >> > > Right, that's the correct behaviour isn't it? Pages freed on source VM do > not magically reappear on destination VM? > > Yes, so this method can not fix this problem. >> But if i balloon down those pages every time(not driver first load), i >> tested save/restore/migration for several times, and all work fine. But >> the domu will waste lots of memory in this situation. >> > > Yes, that's weird. Do you know what condition causes guest memory allocation > failure on xc_domain_restore? Is it due to hitting the guest maxmem limit in > Xen? If so, is maxmem the same value across multiple iterations of > save/restore or migration? > Sorry, i have no idea about it. Maybe I need to print more log in for(;;) in xc_domain_restore to see what is the difference between without and with balooning down pages. Thanks Annie. --------------090701070002030209080006 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi

It seems that a 
restored vm lost those pages ballooned down. For migration, destination
does not have those pages which ballooned down on source.
    

Right, that's the correct behaviour isn't it? Pages freed on source VM do
not magically reappear on destination VM?
Yes,  so this method can not fix this problem.

  

    
But if i balloon down those pages every time(not driver first load),  i
tested save/restore/migration for several times, and all work fine.  But
the domu will waste lots of memory in this situation.
    

  

  

Yes, that's weird. Do you know what condition causes guest memory allocation
failure on xc_domain_restore? Is it due to hitting the guest maxmem limit in
Xen? If so, is maxmem the same value across multiple iterations of
save/restore or migration?
  



Sorry, i have no idea about it. Maybe I need to print more log in
for(;;) in xc_domain_restore to see what is the difference between
without and with balooning down pages.



Thanks

Annie.






--------------090701070002030209080006--


--===============1920724150==
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

--===============1920724150==--