Re: [Xen-devel] [OSSTEST PATCH v14 PART 2 10-26/26] Nested HVM testing

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Mon, 2015-10-12 at 08:04 +0000, Hu, Robert wrote:
> > -----Original Message-----
> > From: Hu, Robert
> > Sent: Monday, October 12, 2015 11:36 AM
> > To: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>;
> > xen-devel@xxxxxxxxxxxxxxxxxxxx
> > Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
> > Subject: RE: [OSSTEST PATCH v14 PART 2 10-26/26] Nested HVM testing
> > 
> > > -----Original Message-----
> > > From: Ian Jackson [mailto:ian.jackson@xxxxxxxxxxxxx]
> > > Sent: Saturday, September 26, 2015 3:15 AM
> > > To: xen-devel@xxxxxxxxxxxxxxxxxxxx
> > > Cc: Hu, Robert <robert.hu@xxxxxxxxx>; Ian Campbell
> > > <ian.campbell@xxxxxxxxxx>; Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
> > > Subject: [OSSTEST PATCH v14 PART 2 10-26/26] Nested HVM testing
> > > 
> > > This is the second part of v14 Robert Ho's osstest patch series to
> > > support nested HVM tests.
> > > 
> > > It is also available here:
> > >   git://xenbits.xen.org/people/iwj/xen.git
> > >   http://xenbits.xen.org/git-http/people/iwj/xen.git
> > > in wip.nested-hvm.v14.part1..wip.nested-hvm.v14
> > > 
> > > Compared to Robert's v13, which was passed to me by private email,
> > >  * I have rebased onto current osstest pretest;
> > >  * I have changed how selecthost() is told it's dealing with
> > >    a nested host (in practice, L1 guest);
> > >  * There are a large number of minor cleanups;
> > >  * There are some new preparatory cleanup and admin patches;
> > >  * I have rewritten almost all of the commit messages.
> > > 
> > > However, I have done only VERY LIMITED testing.  Much of the code
> > > here
> > > is UNTESTED since my changes.  My testing was confined to:
> > >  * Verifying that my changes to cs-adjust-flight worked
> > >  * Checking that ad-hoc runs of ts-host-reboot and ts-host-powercycle
> > >    seemed to work when a guest was specified on the command line.
> > > 
> > > Robert, you kindly volunteered to test a revised version of this
> > > series.  I would appreciate if you would check that all of this still
> > > works as you expect.  I expect there will be some bugs, perhaps even
> > > very silly bugs, introduced by me.
> > Sure.
> > Am I supposed to test Part 1 together with this Part 2? or each
> > individually?
> > How's Part 1's status now? pass pretest and in production branch? or
> > still
> > need test?
> Seems Part 1 already in production tree. So I directly merged Part 2 on
> latest production master branch.
> 
> However, when I run 'standalone-reset', I get these errors
> [root@robert-ivt osstest]# ./standalone-reset 
> ** need to generate d-i with firmware for armhf
> fetching initrd.gz
> http://linux-ftp.sh.intel.com/pub/mirrors/debian//dists/wheezy/main/insta
> ller-armhf/current/images/vexpress/netboot/initrd.gz => initrd.gz.new
> collecting firmware-bnx2
> collecting backports initramfs-tools
> collecting backports kernel
> dpkg-deb: error: `backports.deb' is not a debian format archive

Can you look at the file backports.deb and see what it is? e.g.
    $ file backports.deb
might give a clue. For me it says "Debian binary package (format 2.0)".

My guess is that it will tern out to be some HTML explaining that this file
is not available via your proxy for some reason.



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