From: Vasiliy Tolstov <v.tolstov@selfip.ru>
To: Konrad Rzeszutek Wilk <konrad@darnok.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: shutdown/migration stop working on paravirt domU
Date: Mon, 23 Jan 2012 18:46:02 +0400 [thread overview]
Message-ID: <CACaajQtYyGpOZQsqeKUb4ewt04Wm7_yueK7miadwgx3DAj1smw@mail.gmail.com> (raw)
In-Reply-To: <CACaajQtqbqFDj2kHSp-2P1MqYWe_PLdcv_Q5UL7sxOWSCwModQ@mail.gmail.com>
2012/1/20 Vasiliy Tolstov <v.tolstov@selfip.ru>:
> 2012/1/20 Vasiliy Tolstov <v.tolstov@selfip.ru>:
>> 2012/1/19 Konrad Rzeszutek Wilk <konrad@darnok.org>:
>>>> >
>>>> > 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.
>>>>
I'm finally find the problem. If domU write to xenstore some
incomplete command by writin binary data to /proc/xen/xenbus
(for example "\2\0\0\0\0\0\0\0\0\0\0\0\21\0\0\0") and exists, watches
stop working and second attemp to read/write some from domU to
xenstore failed with process lock that tries to write message...
Can this be solved (or solved already in some version of xenbus driver code?).
--
Vasiliy Tolstov,
Clodo.ru
e-mail: v.tolstov@selfip.ru
jabber: vase@selfip.ru
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2012-01-23 14:46 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
2012-01-20 7:41 ` Vasiliy Tolstov
2012-01-20 11:02 ` Vasiliy Tolstov
2012-01-23 14:46 ` Vasiliy Tolstov [this message]
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=CACaajQtYyGpOZQsqeKUb4ewt04Wm7_yueK7miadwgx3DAj1smw@mail.gmail.com \
--to=v.tolstov@selfip.ru \
--cc=konrad@darnok.org \
--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).