[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [qemu-upstream-unstable test] 33842: regressions - FAIL



On Thu, 29 Jan 2015, Ian Campbell wrote:
> On Thu, 2015-01-29 at 01:26 +0000, xen.org wrote:
> > flight 33842 qemu-upstream-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/33842/
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-i386-freebsd10-i386 11 guest-localmigrate      fail REGR. vs. 
> > 33488
> >  test-amd64-i386-freebsd10-amd64 11 guest-localmigrate     fail REGR. vs. 
> > 33488
> >  test-amd64-i386-xl-win7-amd64 10 guest-localmigrate       fail REGR. vs. 
> > 33488
> >  test-amd64-amd64-xl-winxpsp3 10 guest-localmigrate        fail REGR. vs. 
> > 33488
> >  test-amd64-amd64-xl-win7-amd64 10 guest-localmigrate      fail REGR. vs. 
> > 33488
> >  test-amd64-i386-xl-winxpsp3-vcpus1 10 guest-localmigrate  fail REGR. vs. 
> > 33488
> >  test-amd64-i386-xl-winxpsp3  10 guest-localmigrate        fail REGR. vs. 
> > 33488
> 
> These all appear the same, picking one at random
> http://www.chiark.greenend.org.uk/~xensrcts/logs/33842/test-amd64-amd64-xl-win7-amd64/info.html
> 
> I see in
> http://www.chiark.greenend.org.uk/~xensrcts/logs/33842/test-amd64-amd64-xl-win7-amd64/10.ts-guest-localmigrate.log
>  :
> 
>         2015-01-28 15:14:57 Z executing ssh ... root@xxxxxxxxxxxx xl migrate 
> win.guest.osstest localhost
>         migration target: Ready to receive domain.
>         Saving to migration stream new xl format (info 0x1/0x0/1677)
>         Loading new save file <incoming migration stream> (new xl fmt info 
> 0x1/0x0/1677)
>          Savefile contains xl domain config in JSON format
>         Parsing config from <saved>
>         xc: progress: Reloading memory pages: 53248/1044481    5%
>         xc: progress: Reloading memory pages: 105472/1044481   10%
>         xc: progress: Reloading memory pages: 157316/1044481   15%
>         libxl: error: libxl_dm.c:1482:device_model_spawn_outcome: domain 6 
> device model: spawn failed (rc=-3)
>         libxl: error: libxl_create.c:1330:domcreate_devmodel_started: device 
> model did not start: -3
>         libxl: error: libxl_dm.c:1586:kill_device_model: Device Model already 
> exited
>         migration target: Domain creation failed (code -3).
>         libxl: error: libxl_utils.c:430:libxl_read_exactly: file/stream 
> truncated reading ready message from migration receiver stream
>         libxl: info: libxl_exec.c:118:libxl_report_child_exitstatus: 
> migration transport process [6163] exited with error status 3
>         Migration failed, resuming at sender.
> 
> http://www.chiark.greenend.org.uk/~xensrcts/logs/33842/test-amd64-amd64-xl-win7-amd64/lake-frog---var-log-xen-qemu-dm-win.guest.osstest.log
>  has:
> 
>         xen_ram_alloc: do not alloc 1f800000 bytes of ram at 0 when runstate 
> is INMIGRATE
>         xen_ram_alloc: do not alloc 800000 bytes of ram at 1f800000 when 
> runstate is INMIGRATE
>         xen_ram_alloc: do not alloc 10000 bytes of ram at 20000000 when 
> runstate is INMIGRATE
>         xen_ram_alloc: do not alloc 40000 bytes of ram at 20010000 when 
> runstate is INMIGRATE
> 
> http://www.chiark.greenend.org.uk/~xensrcts/logs/33842/test-amd64-amd64-xl-win7-amd64/lake-frog---var-log-xen-qemu-dm-win.guest.osstest--incoming.log
>  has:
> 
>         xen: ioreq server create: Invalid argument
>         xen hardware virtual machine initialisation failed
>         
> The log of the commits under test is below.

Thanks for the analysis!
I can confirm that the issue has been introduced by

"Xen: Use the ioreq-server API when available"

that is 7665d6ba98e20fb05c420de947c1750fd47e5c07 on the qemu-xen tree.

Paul, are you going to take a look at that?


> 
> > 
> > ------------------------------------------------------------
> > commit be11dc1e9172f91e798a8f831b30c14b479e08e8
> > Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> > Date:   Fri Jan 23 12:09:47 2015 +0000
> > 
> >     fix QEMU build on Xen/ARM
> >     
> >     xen_get_vmport_regs_pfn should take a xen_pfn_t argument, not an
> >     unsigned long argument (in fact xen_pfn_t is defined as uint64_t on
> >     ARM).
> >     
> >     Also use xc_hvm_param_get instead of the deprecated xc_get_hvm_param.
> >     
> >     upstream-commit-id: d01a5a3fe19645f3cdea1566f0e518ea2152a029
> >     
> >     Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> >     Reviewed-by: Don Slutz <dslutz@xxxxxxxxxxx>
> > 
> > commit 7665d6ba98e20fb05c420de947c1750fd47e5c07
> > Author: Paul Durrant <paul.durrant@xxxxxxxxxx>
> > Date:   Tue Jan 20 11:06:19 2015 +0000
> > 
> >     Xen: Use the ioreq-server API when available
> >     
> >     The ioreq-server API added to Xen 4.5 offers better security than
> >     the existing Xen/QEMU interface because the shared pages that are
> >     used to pass emulation request/results back and forth are removed
> >     from the guest's memory space before any requests are serviced.
> >     This prevents the guest from mapping these pages (they are in a
> >     well known location) and attempting to attack QEMU by synthesizing
> >     its own request structures. Hence, this patch modifies configure
> >     to detect whether the API is available, and adds the necessary
> >     code to use the API if it is.
> >     
> >     upstream-commit-id: 3996e85c1822e05c50250f8d2d1e57b6bea1229d
> >     
> >     Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx>
> >     Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> >     Acked-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> > 
> > commit 9026dca821a61b72983778e3dcd92cfc34b02e8b
> > Author: Paul Durrant <paul.durrant@xxxxxxxxxx>
> > Date:   Tue Jan 20 11:05:07 2015 +0000
> > 
> >     Add device listener interface
> >     
> >     The Xen ioreq-server API, introduced in Xen 4.5, requires that PCI 
> > device
> >     models explicitly register with Xen for config space accesses. This 
> > patch
> >     adds a listener interface into qdev-core which can be used by the Xen
> >     interface code to monitor for arrival and departure of PCI devices.
> >     
> >     upstream-commit-id: 707ff80021ccd7a68f4b3d2c44eebf87efbb41c4
> >     
> >     Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx>
> >     Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> >     Reviewed-by: Paolo Bonzini <pbonzini@xxxxxxxxxx>
> >     
> >     Conflicts:
> >         include/qemu/typedefs.h
> > 
> > commit 901230fd8ce053cc21312a2eca2f3ba9f1d103f2
> > Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> > Date:   Wed Dec 3 08:15:19 2014 -0500
> > 
> >     xen-hvm: increase maxmem before calling xc_domain_populate_physmap
> >     
> >     Increase maxmem before calling xc_domain_populate_physmap_exact to
> >     avoid the risk of running out of guest memory. This way we can also
> >     avoid complex memory calculations in libxl at domain construction
> >     time.
> >     
> >     This patch fixes an abort() when assigning more than 4 NICs to a VM.
> >     
> >     upstream-commit-id: c1d322e6048796296555dd36fdd102d7fa2f50bf
> >     
> >     Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> >     Signed-off-by: Don Slutz <dslutz@xxxxxxxxxxx>
> 

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.