From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Hu, Robert" <robert.hu@intel.com>
Cc: "Ian.Jackson@eu.citrix.com" <Ian.Jackson@eu.citrix.com>,
"Pang, LongtaoX" <longtaox.pang@intel.com>,
Wei Liu <wei.liu2@citrix.com>, "Zheng, Di" <di.zheng@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [OSSTEST PATCH 2/4] Build XEN and HVM Dom0 kernel for L1 guest VM
Date: Tue, 27 Jan 2015 11:01:09 +0000 [thread overview]
Message-ID: <1422356469.25294.8.camel@citrix.com> (raw)
In-Reply-To: <9E79D1C9A97CFD4097BCE431828FDD31AD6008@SHSMSX103.ccr.corp.intel.com>
On Tue, 2015-01-27 at 08:33 +0000, Hu, Robert wrote:
[...] please trim quotes.
> >
> > FWIW, OSSTest has a bunch of overlay files (look at overlay directory),
> > which includes an init script called xenbridge. In theory if you're
> > reusing this script (ts-xen-install) then you don't need to worry about
> > setting up bridge?
> I tried this approach, using xenbridge init scripts, it can work.
> However, in original xen install, it seems not used. I don't see 'xenbridge'
> in /etc/rc2.d/
xenbridge is only enabled if OldSeparateBridgeInitd is set, which it is
not for a modern Xen install so I think this is a red-herring.
> Shall I know the xenbr0 is created? I think not by xenbridge init service.
The host networking is configured by the function nodhcp in
ts-xen-install.
Per our previous conversations once the L1 guest is installed you can
mostly treat it as a if it were an L0 host wrt configuring it. In other
words there should be no need for a separate setup_l1_bridge function,
just some minor modifications to ts-xen-install.
Ian.
next prev parent reply other threads:[~2015-01-27 11:01 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 [this message]
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
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=1422356469.25294.8.camel@citrix.com \
--to=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.