Re: [Xen-devel] [OSSTEST PATCH 0/4] Introduction of the patches.

["Hu, Robert" <robert.hu@xxxxxxxxx>]

> -----Original Message-----
> From: Ian Jackson [mailto:Ian.Jackson@xxxxxxxxxxxxx]
> Sent: Friday, November 28, 2014 8:26 PM
> To: Pang, LongtaoX
> Cc: xen-devel@xxxxxxxxxxxxx; Ian.Campbell@xxxxxxxxxx; wei.liu2@xxxxxxxxxx;
> Hu, Robert; Zheng, Di
> Subject: Re: [OSSTEST PATCH 0/4] Introduction of the patches.
> 
> longtao.pang writes ("[OSSTEST PATCH 0/4] Introduction of the patches."):
> > We updated these patchs about adding Nested test job into OSSTest.
> 
> Thanks for your contribution.
> 
> Having some testing of nested HVM would be good.
Hi Ian, thanks for your support and glad getting your attention on this.
We're new to osstest, and didn't find much documentation on its framework. 
So might violate some design and/or convention of it. We will modify as we get 
more conception of it.
> 
> But I'm not convinced that these patches take the right approach to
> achieving that.  There seems to be a great deal of duplication of
> code.  I think we should have a conversation about what moving parts
> are necessary for nested HVM testing.
Agree with you we shall reuse existing ts-* if possible. Actually I had thought 
of this approach but later I 
defeated myself because I thought ts-* shall compromise itself as a whole test 
case and better not to touch them.
Now I see that ts- is more like components to constitute a test case (my 
current understanding is your job == test cases).
If we had some documentation illustrating the your hierarchy of design, we 
should have less misunderstanding.
> 
> I would guess that you could reuse ts-debian-hvm-install for the
> initial install of the L1 guest, and then ts-xen-install to install
> Xen on it.  Finally, you could run some other ts-* scripts to install
> your L2 guests.  I think you would probably find that there are only
> some small changes needed to make those existing scripts flexible
> enough.
OK, we're going to do this, try to use ts-debian-hvm-install to fulfill the 
step of L1 dom0; 
use ts-xen-install to fulfil next step of constructing the normal guest to a L1 
Xen environment.
We will probably changes some of ts-debian-hvm-install and ts-xen-install to 
fulfill our test case. 
e.g., we may use some different configuration for L1, we will parameterize some 
configurations which now is hard-coded.
> 
> And I don't understand why you need to rebuild anything.  Surely the
> already-built hypervisor and tools ought to work just as well in the
> L1 guest ?
We'll refine these parts to re-use existing things as much as possible. 
> 
> Thanks,
> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel