From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Pang, LongtaoX" <longtaox.pang@intel.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>,
"Ian.Jackson@eu.citrix.com" <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"Hu, Robert" <robert.hu@intel.com>,
"Zheng, Di" <di.zheng@intel.com>
Subject: Re: [OSSTEST PATCH 3/4] Add nested testcase of installing L2 guest VM
Date: Thu, 8 Jan 2015 18:20:00 +0100 [thread overview]
Message-ID: <1420737600.28459.43.camel@Abyss.station> (raw)
In-Reply-To: <86C3224E41A7434B904EC364302132D80E421EE7@SHSMSX101.ccr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 798 bytes --]
On Tue, 2015-01-06 at 03:28 +0000, Pang, LongtaoX wrote:
> [Pang, LongtaoX]
> [Pang, LongtaoX] Thanks for checking. We used ts-debian-hvm-install for installing L1 HVM guest via ISO Image,
> because we will build XEN, XEN-Tools and dom0 kernel inside it, and then we will install L2 guest inside L1.
>
This has been asked already, and so far, I haven't seen an answer: why
do you want to rebuild Xen, the toolstack, and even Dom0 kernel inside
the L1 guest, instead than just installing them (with ts-xen-install)?
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-01-08 17:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 8:07 [OSSTEST PATCH 0/4] Introduction of the patches longtao.pang
2014-12-10 8:07 ` [OSSTEST PATCH 1/4] Add nested testcase of preparing and installing L1 guest VM longtao.pang
2014-12-11 11:06 ` Wei Liu
2014-12-26 5:13 ` Robert Hu
2015-01-02 9:51 ` Dario Faggioli
2014-12-10 8:07 ` [OSSTEST PATCH 2/4] Build XEN and HVM Dom0 kernel for " longtao.pang
2014-12-11 11:25 ` Wei Liu
2015-01-27 8:33 ` Hu, Robert
2015-01-27 11:01 ` Ian Campbell
2015-01-29 6:05 ` Hu, Robert
2014-12-10 8:07 ` [OSSTEST PATCH 3/4] Add nested testcase of installing L2 " longtao.pang
2014-12-11 11:43 ` Wei Liu
2015-01-06 3:28 ` Pang, LongtaoX
2015-01-06 16:52 ` Wei Liu
2015-01-07 3:52 ` Pang, LongtaoX
2015-01-08 7:34 ` Pang, LongtaoX
2015-01-08 10:48 ` Wei Liu
2015-01-08 11:12 ` Ian Campbell
2015-01-08 11:16 ` Ian Jackson
2015-01-08 11:22 ` Robert Hu
2015-01-08 11:26 ` Ian Campbell
2015-01-08 17:20 ` Dario Faggioli [this message]
2015-01-08 17:25 ` Ian Campbell
2015-01-09 2:46 ` Pang, LongtaoX
2014-12-10 8:07 ` [OSSTEST PATCH 4/4] Insert nested test job name and runvars into longtao.pang
2014-12-11 11:46 ` Wei Liu
2015-01-06 3:31 ` Pang, LongtaoX
2015-01-29 9:57 ` Hu, Robert
2015-01-29 10:42 ` Wei Liu
2015-01-29 10:52 ` Ian Campbell
2015-01-29 10:55 ` Ian Campbell
2014-12-11 10:38 ` [OSSTEST PATCH 0/4] Introduction of the patches Wei Liu
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=1420737600.28459.43.camel@Abyss.station \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=di.zheng@intel.com \
--cc=longtaox.pang@intel.com \
--cc=robert.hu@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.