From: Ian Campbell <ian.campbell@citrix.com>
To: "Pang, LongtaoX" <longtaox.pang@intel.com>, Ian.Jackson@eu.citrix.com
Cc: "Hu, Robert" <robert.hu@intel.com>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [OSSTEST Nested PATCH v7 4/6] Add new script to custmize nested test configuration
Date: Wed, 1 Apr 2015 09:58:33 +0100 [thread overview]
Message-ID: <1427878713.2115.233.camel@citrix.com> (raw)
In-Reply-To: <86C3224E41A7434B904EC364302132D80E487DED@SHSMSX101.ccr.corp.intel.com>
On Wed, 2015-04-01 at 08:45 +0000, Pang, LongtaoX wrote:
> > As it happens I was rebasing that series this morning but due to other issues
> > I've not managed to run it yet. Once I've managed to at least smoke test I'll CC
> > you on the repost.
> >
> OK. What's more, for the below codes which is used for starting
> 'osstest-confirm-booted' script to confirm whether L1 is fully booted
> after reboot it. I think it's necessary here.
> +target_cmd_root($l1, <<END);
> + wget -O overlay.tar $url
> + tar -xf overlay.tar -C /
> + rm overlay.tar -f
> + update-rc.d osstest-confirm-booted start 99 2 .
> +END
In my distro series I also have some patches refactoring the overlay
stuff, which would mean you could reuse that.
http://article.gmane.org/gmane.comp.emulators.xen.devel/224433
I'll CC you on that one too.
I don't think there would be any harm in adding those overlays for all
guests and enabling the initscript, but Ian may disagree or know
something which I don't.
> > > +my $l2_disk_mb = 20000;
> > > +my $l2_lv_name = 'nestedl2';
> > > +my $vgname = $l0->{Name};
> > > +$vgname .= ".$c{TestHostDomain}" if ($l0->{Suite} =~ m/lenny/);
> > > +target_cmd_root($l0, <<END);
> > > + lvremove -f /dev/${vgname}/${l2_lv_name} ||:
> > > + lvcreate -L ${l2_disk_mb}M -n $l2_lv_name $vgname
> > > + dd if=/dev/zero of=/dev/${vgname}/${l2_lv_name} count=10
> > > + xl block-attach $l1->{Name}
> > > +/dev/${vgname}/${l2_lv_name},raw,sdb,rw
> >
> > This attach won't be persistent over domain destroy, is that expected?
> >
> We need create a logical volume in L0 and attach it to L1 for L2 VM
> installing. Before creating, it will remove the logical volume with
> the same "$l2_lv_name" that has already existed.
> Yes, after destroyed L1 VM, the logical volume will still exist inside
> L0, but there is no harm, I think.
OK.
Ian./
next prev parent reply other threads:[~2015-04-01 8:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 23:06 [OSSTEST Nested PATCH v7 0/6] Introduction of netsted HVM test job longtao.pang
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 1/6] parsing grub which has 'submenu' primitive longtao.pang
2015-03-31 13:44 ` Ian Campbell
2015-04-01 1:42 ` Hu, Robert
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 2/6] Edit some testsupport APIs for nested test longtao.pang
2015-03-31 13:49 ` Ian Campbell
2015-04-01 5:56 ` Pang, LongtaoX
2015-04-01 8:50 ` Ian Campbell
2015-03-31 14:20 ` Ian Campbell
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 3/6] Changes on test step of debain hvm guest install longtao.pang
2015-03-31 13:55 ` Ian Campbell
2015-04-01 8:19 ` Pang, LongtaoX
2015-04-01 8:53 ` Ian Campbell
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 4/6] Add new script to custmize nested test configuration longtao.pang
2015-03-31 14:13 ` Ian Campbell
2015-04-01 8:45 ` Pang, LongtaoX
2015-04-01 8:58 ` Ian Campbell [this message]
2015-04-09 7:12 ` Pang, LongtaoX
2015-04-15 9:31 ` Ian Campbell
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 5/6] Add test job for nest test case longtao.pang
2015-03-31 14:23 ` Ian Campbell
2015-04-01 8:27 ` Pang, LongtaoX
2015-04-01 9:06 ` Ian Campbell
2015-04-02 8:16 ` Pang, LongtaoX
2015-04-02 9:15 ` Ian Campbell
2015-03-27 23:06 ` [OSSTEST Nested PATCH v7 6/6] Compose the main recipe of nested test job longtao.pang
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=1427878713.2115.233.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.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.