All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Zhigang Wang <zhigang.x.wang@oracle.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: xl list -l doesn't work for incoming domain
Date: Wed, 12 Nov 2014 14:52:56 +0000	[thread overview]
Message-ID: <1415803976.1155.14.camel@citrix.com> (raw)
In-Reply-To: <54637326.6090908@oracle.com>

On Wed, 2014-11-12 at 09:48 -0500, Zhigang Wang wrote:
> On 11/12/2014 09:40 AM, Ian Campbell wrote:
> > On Wed, 2014-11-12 at 09:36 -0500, Zhigang Wang wrote:
> >> Also I want clarify one thing: the @introduceDomain watch is triggered at the same
> >> time for xm/xend and xl: when VM fully migrated.
> >>
> >> The different between xm/xend and xl is: xend will populate destination side VM 
> >> xenstore entries at the beginning of migration.
> > 
> > Do you mean *before* @introduceDomain has triggered?
> 
> Yes, from my test. I didn't check the code logic yet.

I think anything which is trying to inspect the state of a domain before
the corresponding @introduceDomain and expecting anything more complex
than the fact of that domain's existence is broken.

IOW the json associated with such a domain should be:
    {
        "domid": 123,
        "config": {}
    }
Or even
    {
        "domid": 123,
    }

No more or less.

> I designed a test: set eth0 to low speed:
> 
>     $ ethtool -s eth0 speed 10 duplex half
> 
> and then migrate the VM. I can see the watch been triggered very late (couple minutes later after migration).

A couple of minutes after *starting* the migration (i.e. the couple of
minutes is just the time taken to migrate) or a couple of minutes after
*finishing* the migration (which would be unfortunate and should be
investigated).

Ian.

  reply	other threads:[~2014-11-12 14:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 19:14 xl list -l doesn't work for incoming domain Zhigang Wang
2014-11-07 10:47 ` Wei Liu
2014-11-07 16:34   ` Zhigang Wang
2014-11-10 12:35     ` Wei Liu
2014-11-10 12:38       ` Ian Campbell
2014-11-10 13:54         ` Wei Liu
2014-11-10 14:05           ` Ian Campbell
2014-11-10 14:16             ` Wei Liu
2014-11-10 15:01       ` Zhigang Wang
2014-11-10 15:25         ` Wei Liu
2014-11-10 17:08           ` Zhigang Wang
2014-11-10 17:24             ` Wei Liu
2014-11-10 17:54               ` Zhigang Wang
2014-11-11 11:01                 ` Wei Liu
2014-11-11 14:41                   ` Zhigang Wang
2014-11-11 15:20                     ` Wei Liu
2014-11-11 16:42                       ` Zhigang Wang
2014-11-12 11:31                         ` Wei Liu
2014-11-12 14:36                           ` Zhigang Wang
2014-11-12 14:40                             ` Ian Campbell
2014-11-12 14:48                               ` Zhigang Wang
2014-11-12 14:52                                 ` Ian Campbell [this message]
2014-11-12 15:04                                   ` Zhigang Wang
2014-11-12 15:40                                     ` Wei Liu
2014-11-13 11:44                                     ` Ian Campbell

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=1415803976.1155.14.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=zhigang.x.wang@oracle.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 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.