Re: [Xen-devel] [OSSTest Nested v12 03/21] Allow runvars to specify guest disk and ram size (turning previous values into defaults)

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

> -----Original Message-----
> From: Ian Jackson [mailto:Ian.Jackson@xxxxxxxxxxxxx]
> Sent: Friday, September 25, 2015 6:35 PM
> To: Hu, Robert <robert.hu@xxxxxxxxx>; xen-devel@xxxxxxxxxxxxx;
> ian.campbell@xxxxxxxxxx; wei.liu2@xxxxxxxxxx; Jin, Gordon
> <gordon.jin@xxxxxxxxx>; Zheng, Di <di.zheng@xxxxxxxxx>
> Subject: Re: [OSSTest Nested v12 03/21] Allow runvars to specify guest disk
> and ram size (turning previous values into defaults)
> 
> Ian Jackson writes ("Re: [OSSTest Nested v12 03/21] Allow runvars to specify
> guest disk and ram size (turning      previous values into defaults)"):
> > Robert Ho writes ("[OSSTest Nested v12 03/21] Allow runvars to specify
> guest disk and ram size (turning      previous values into defaults)"):
> > >     1. The default disk size for guest is '10000M' which is not sufficient
> > >         for nested HVM guest, using larger disk size for nested guest
> > >         to accommodate to nested test requirement, the specific
> disk_size is
> > >         defined by make-flight.
> > >     2. Also, also allow ram size to be defined by runvar. It takes
> precedence
> > >         over the calculation formula.
> > >     3. Add comment at the interface code.
> > >
> > > Signed-off-by: Robert Ho <robert.hu@xxxxxxxxx>
> >
> > Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
> 
> Robert, I see that the v13 of this series you passed me under the
> table does not include this ack.
> 
> It is conventional to transcribe an ack when preparing a new version
> of a series.  That helps reviewers and other contributors see which
> parts of a series still need attention.
> 
Sure. I will remember this in following series.
> I will record the ack in my own git tree.
Thanks.

And sorry I haven't got a chance to read your replies/patches until now.
So many test tasks almost crushed me.
I'm going to read your mails in the coming week.
> 
> Thanks,
> Ian.

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