From mboxrd@z Thu Jan  1 00:00:00 1970
From: Robert Hu <robert.hu@vmm.sh.intel.com>
Subject: Re: [OSSTEST Nested PATCH v11 6/7] Compose the main
 recipe of nested test job
Date: Sun, 14 Jun 2015 20:52:45 +0800
Message-ID: <1434286365.25577.8.camel@localhost>
References: <1432631304-27347-1-git-send-email-longtaox.pang@intel.com>
	<1432631304-27347-7-git-send-email-longtaox.pang@intel.com>
	<21880.23264.813171.606123@mariner.uk.xensource.com>
	<86C3224E41A7434B904EC364302132D80E4BFEC4@SHSMSX101.ccr.corp.intel.com>
	<21881.42757.84361.654532@mariner.uk.xensource.com>
	<86C3224E41A7434B904EC364302132D80E4C0A6B@SHSMSX101.ccr.corp.intel.com>
	<21882.64076.306554.733060@mariner.uk.xensource.com>
	<21882.64129.355645.21123@mariner.uk.xensource.com>
Reply-To: robert.hu@intel.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <21882.64129.355645.21123@mariner.uk.xensource.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: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Hu, Robert" <robert.hu@intel.com>, "Pang,
	LongtaoX" <longtaox.pang@intel.com>, "wei.liu2@citrix.com" <wei.liu2@citrix.com>, "Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

On Fri, 2015-06-12 at 16:28 +0100, Ian Jackson wrote:
> Ian Jackson writes ("RE: [OSSTEST Nested PATCH v11 6/7] Compose the main recipe of nested test job"):
> > Thinking about this leads me to ask another question.  Suppose that a
> > bug causes the l1 to lock up completely.  ts-logs-capture will attempt
> > to hard reboot a locked-up host.  If it can't fetch any logs, it calls
> >     target_reboot_hard($ho);
> > 
> > What will that do if $ho refers to the l1 ?  It relies on the power
> > method.  Does your nested l1 "host" have a power method ?
> 
> Oh, and (sorry) another thought: in principle it would be possible for
> the l0 and l1 toolstacks to be different.
> 
> AFAICT your current series doesn't support this ?
No it doesn't. Actually we support only xl tool stack.
> 
> Ian.