xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: xen-devel@lists.xensource.com
Subject: Re: shutdown/migration stop working on paravirt domU
Date: Thu, 19 Jan 2012 14:50:49 -0500	[thread overview]
Message-ID: <20120119195046.GA3890@konrad-lan> (raw)
In-Reply-To: <CACaajQt=xO3aRKM2HvdXTcHmToED-DmnWa62EQwMTLgnrJVd8A@mail.gmail.com>

On Wed, Jan 18, 2012 at 01:16:10AM +0400, Vasiliy Tolstov wrote:
> 2012/1/18 Konrad Rzeszutek Wilk <konrad@darnok.org>:
> > On Tue, Jan 17, 2012 at 12:58:14PM +0400, Vasiliy Tolstov wrote:
> >> Hello. Today i'm try to research, why most of our vm (pvm) not
> >> shutdown correctly (we use shutdown with timeout, then it arrives we
> >> destroy vm), and write simple test case to check that domU watches
> >
> > Which kernel version of DomU?
> 
> 2.6.32.26 from xen git tree and  2.6.18-194.26.1.el5xen

First order is to upgrade your kernel and see if the problem exists
with a newer 2.6.32.X tree. then also try 3.0 or 3.1 kernel.
> 
> 
> >
> > Play a bit with xenctx to get an idea where the guest is stuck at.
> >
> 
> Ok, nice. When i need to run xenctx and what i need to see in its output?

<sigh> Google for it. There should be tons of examples of how to use it
to figure out where the guest is stuck at.

  reply	other threads:[~2012-01-19 19:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17  8:58 shutdown/migration stop working on paravirt domU Vasiliy Tolstov
2012-01-17 20:15 ` Konrad Rzeszutek Wilk
2012-01-17 21:16   ` Vasiliy Tolstov
2012-01-19 19:50     ` Konrad Rzeszutek Wilk [this message]
2012-01-20  7:41       ` Vasiliy Tolstov
2012-01-20 11:02         ` Vasiliy Tolstov
2012-01-23 14:46           ` Vasiliy Tolstov

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=20120119195046.GA3890@konrad-lan \
    --to=konrad@darnok.org \
    --cc=v.tolstov@selfip.ru \
    --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).