From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: xl list -l doesn't work for incoming domain
Date: Wed, 12 Nov 2014 14:52:56 +0000
Message-ID: <1415803976.1155.14.camel@citrix.com>
References: <20141110123525.GD28360@zion.uk.xensource.com>
	<5460D342.9090308@oracle.com>
	<20141110152535.GA6110@zion.uk.xensource.com>
	<5460F102.9000100@oracle.com>
	<20141110172408.GA6588@zion.uk.xensource.com>
	<5460FBCA.5060302@oracle.com>
	<20141111110156.GA12465@zion.uk.xensource.com>
	<5462201C.302@oracle.com>
	<20141111152011.GA21312@zion.uk.xensource.com>
	<54623C5C.6010504@oracle.com>
	<20141112113156.GA28075@zion.uk.xensource.com>
	<54637076.7060708@oracle.com> <1415803209.1155.10.camel@citrix.com>
	<54637326.6090908@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>) id 1XoZI9-00066P-4F
	for xen-devel@lists.xenproject.org; Wed, 12 Nov 2014 14:53:05 +0000
In-Reply-To: <54637326.6090908@oracle.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Zhigang Wang <zhigang.x.wang@oracle.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Wei Liu <wei.liu2@citrix.com>
List-Id: xen-devel@lists.xenproject.org

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.