All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
	Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: xen-devel@lists.xenproject.org, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: broken live migration in xen 4.3 (release)
Date: Tue, 18 Mar 2014 10:49:06 +0100	[thread overview]
Message-ID: <53281692.7070100@citrix.com> (raw)
In-Reply-To: <1395135419.12847.4.camel@kazak.uk.xensource.com>

On 18/03/14 10:36, Ian Campbell wrote:
> On Tue, 2014-03-18 at 03:25 +0400, Vasiliy Tolstov wrote:
>> I'm solve my issue. /etc/xen/scripts/vif-ospf (my own network script)
>> have which ethtool not redirected to /dev/null.
>> When domain started i don't have errors, but when migration appeared
>> last message has been /sbin/ethtool. Thanks Ian Campbell and Ian
>> Jackson!
> 
> Great.
> 
> Did you by any chance produce a debug patch to help you track this down
> (e.g. to log the unexpected message)? If so then that might be something
> which is useful to others diagnosing the same issue -- would you mind
> submitting it? See http://wiki.xen.org/wiki/Submitting_Xen_Patches for
> guidance. (Even if it is unsuitable for applying it would perhaps be
> helpful to have in the list archives to point at)
> 
> Roger, where should the hotplug scripts be logging to? Should we
> consider slurping up stdout/stderr of the script to somewhere other than
> xl's std*?

IMHO I like hotplug messages to be printed on screen while using xl
create/destroy... But for migration it should be redirected to /dev/null
or some suitable logfile I guess.

Or maybe a more canonical way to deal with this would be to always
redirect the output of hotplug scripts to a temp file, and in case of
not doing a migration print the contents of the file after executing the
hotplug script.

Roger.

  reply	other threads:[~2014-03-18  9:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 12:28 broken live migration in xen 4.3 (release) Vasiliy Tolstov
2014-03-17 12:58 ` Ian Campbell
2014-03-17 15:45   ` Ian Jackson
2014-03-17 22:06     ` Vasiliy Tolstov
2014-03-17 22:07   ` Vasiliy Tolstov
2014-03-17 23:09     ` Vasiliy Tolstov
2014-03-17 23:25       ` Vasiliy Tolstov
2014-03-18  9:36         ` Ian Campbell
2014-03-18  9:49           ` Roger Pau Monné [this message]
2014-03-18  9:54             ` Ian Campbell
2014-03-18 16:13               ` Ian Jackson
2014-03-18 16:15                 ` Ian Campbell
2014-03-18 17:08                 ` [PATCH 1/3] libxl: Make libxl_exec tolerate foofd<=2 Ian Jackson
2014-03-18 17:08                   ` [PATCH 2/3] libxl: hotplug scripts: stdout >& stderr Ian Jackson
2014-03-18 17:44                     ` Ian Campbell
2014-03-18 17:47                       ` Andrew Cooper
2014-03-18 18:12                       ` Ian Jackson
2014-03-19  9:55                         ` Ian Campbell
2014-03-19 13:41                           ` Ian Jackson
2014-03-19 14:00                             ` Vasiliy Tolstov
2014-03-18 17:08                   ` [PATCH 3/3] libxl: hotplug scripts: stdin < /dev/null Ian Jackson
2014-03-18 17:46                     ` Ian Campbell
2014-03-18 18:12                       ` Ian Jackson
2014-03-18 17:43                   ` [PATCH 1/3] libxl: Make libxl_exec tolerate foofd<=2 Ian Campbell
2014-03-18 18:14                     ` Ian Jackson
2014-03-19  9:56                       ` Ian Campbell
2014-03-18  9:53           ` broken live migration in xen 4.3 (release) 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=53281692.7070100@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=v.tolstov@selfip.ru \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.