From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: Error restoring DomU when using GPLPV Date: Wed, 16 Sep 2009 13:50:22 -0700 Message-ID: <4AB14F8E.2050804@oracle.com> References: <363bf0d0-3856-4c20-87c0-fa834deb6a9f@default> Reply-To: mukesh.rathor@oracle.com Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <363bf0d0-3856-4c20-87c0-fa834deb6a9f@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: Joshua West , xen-devel , kurt.hackel@oracle.com, annie.li@oracle.com, James Harper , Keir Fraser , wayne.gong@oracle.com List-Id: xen-devel@lists.xenproject.org just in case someone missed the thread earlier, 3 = 1 shinfo + 2 gnt frames default. so, tot_pages + shinfo + num gnt frames. Mukesh Dan Magenheimer wrote: > Before we close down this thread, I have a concern: > > According to Mukesh, the fix to this bug is dependent > on the pv drivers tracking tot_pages for a domain > and ballooning to ensure tot_pages+3 does not exceed > max_pages for the domain. > > Well, tmem can affect tot_pages for a domain inside > the hypervisor without any notification to pv drivers > or the balloon driver. And I'd imagine that PoD and > future memory optimization mechanisms such as > swapping and page-sharing may do the same. > > So this solution seems very fragile. > > Dan > >> -----Original Message----- >> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] >> Sent: Wednesday, September 16, 2009 6:28 AM >> To: Annie Li >> Cc: Joshua West; Dan Magenheimer; xen-devel; Kurt Hackel; >> James Harper; >> Wayne Gong >> Subject: Re: [Xen-devel] Error restoring DomU when using GPLPV >> >> >> On 16/09/2009 12:10, "ANNIE LI" wrote: >> >>>> I will do more test to make sure it and update here. >>> I tried to map 256 grant frames during initialization and >> balloon down >>> 256+1(shinfo+gnttab) pages driver first >>> load. Then i did save/restore for 50 times, and live >> migration for 10 >>> times. No error occurs. >> Okay, well I still can't explain why that fixes it, but >> clearly it does. So >> that's good. :-) >> >> -- Keir >> >> >> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel