xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Tovpeko <tsv.devel@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [xl] a fault happens on pv domain reboot
Date: Wed, 02 Jun 2010 14:52:36 +0400	[thread overview]
Message-ID: <4C0637F4.2050407@gmail.com> (raw)
In-Reply-To: <19462.11839.842090.695485@mariner.uk.xensource.com>

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.
>   

  reply	other threads:[~2010-06-02 10:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 14:42 [xl] a fault happens on pv domain reboot Sergey Tovpeko
2010-06-01 14:53 ` Gihan Munasinghe
2010-06-01 16:05 ` Stefano Stabellini
2010-06-01 16:58   ` Ian Jackson
2010-06-02  9:10     ` Sergey Tovpeko
2010-06-02  9:27       ` Keir Fraser
2010-06-02 10:11       ` Ian Jackson
2010-06-02 10:52         ` Sergey Tovpeko [this message]
2010-06-02 16:05           ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C0637F4.2050407@gmail.com \
    --to=tsv.devel@gmail.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).