Re: [Xen-devel] [PATCH OSSTEST v2 0/2] Test booting hvm guest with empty cdrom drive

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, Jun 07, 2016 at 05:29:14PM +0100, Wei Liu wrote:
> On Tue, Jun 07, 2016 at 02:58:05PM +0100, Ian Jackson wrote:
> > Wei Liu writes ("[PATCH OSSTEST v2 0/2] Test booting hvm guest with empty 
> > cdrom drive"):
> > > This can only go in after the bug is fixed and possibly backported to all 
> > > the
> > > trees we care about. It won't pass osstest self pushgate otherwise.
> > 
> > I pushed these but they broke, but only with XSM.  See, for example:
> > 
> >   From: osstest service owner <osstest-admin@xxxxxxxxxxxxxx>
> >   To: <osstest-admin@xxxxxxxxxxxxxx>
> >   Subject: [osstest test] 95322: regressions - FAIL
> >   Date: Mon, 6 Jun 2016 19:29:51 +0000
> > 
> >   flight 95322 osstest real [real]
> >   http://logs.test-lab.xenproject.org/osstest/logs/95322/
> > 
> >   Regressions :-(
> > 
> >   Tests which did not succeed and are blocking,
> >   including tests which could not be run:
> >    test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 9 
> > debian-hvm-install fail REGR. vs. 93413
> >    test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 
> > debian-hvm-install fail REGR. vs. 93413
> > 
> > I haven't had a chance to look at why, yet.  For now, I have dropped
> > these patches from the osstest push gate.
> > 
> 
> I would say it is more related to stubdom.
> 
> libxl: error: libxl_dm.c:1967:stubdom_xswait_cb: Stubdom 4 for 3 startup: 
> startup timed out
> libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch 
> w=0x219b2d8: deregister unregistered
> libxl: error: libxl_create.c:1422:domcreate_devmodel_started: device model 
> did not start: -9
> 
> I've put this on my list and will investigate further.

I know why.

The backend for empty CDROM is always in state 1. Mini-OS blkfront
refuses to move forward unless the backend status turns 4. See
mini-os.git blkfront.c:init_blkfront.

I'm not entirely sure how to fix it though.

Wei.

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