From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Tovpeko Subject: Re: [xl] a fault happens on pv domain reboot Date: Wed, 02 Jun 2010 14:52:36 +0400 Message-ID: <4C0637F4.2050407@gmail.com> References: <4C051C43.20806@gmail.com> <19461.15405.296603.750199@mariner.uk.xensource.com> <4C061FE8.8000501@gmail.com> <19462.11839.842090.695485@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19462.11839.842090.695485@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org Yes, the error message is the same. And i haven't noticed a message from the new xl_lock_page function. Waiting for domain debian-pv (domid 29) to die [pid 19628] Domain 29 is dead Domain 29 needs to be clean: destroying the domain Done. Rebooting now libxl: error: libxl_dom.c:389:userdata_path unable to find domain info for domain 30: Resource temporarily unavailable cannot save config file: Resource temporarily unavailable libxl: error: libxl.c:747:libxl_domain_destroy xc_domain_pause failed for 30 > Sergey Tovpeko writes ("Re: [Xen-devel] [xl] a fault happens on pv domain reboot"): > >> The mlock issue isn't my case. I mean the patch didn't solve the problem. >> The mentioned mlock returned success with the first iteration. >> > > So, just to be clear, with that 700-line patch it still failed with an > identical error message ? > > Ian. >