Re: [Xen-devel] [linux-linus bisection] complete test-amd64-amd64-qemuu-nested-intel

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

> From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
> Sent: Saturday, March 14, 2020 12:03 AM
> 
> On 12/03/2020 23:56, osstest service owner wrote:
> > branch xen-unstable
> > xenbranch xen-unstable
> > job test-amd64-amd64-qemuu-nested-intel
> > testid debian-hvm-install/l1/l2
> >
> > Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-
> 2.6.git
> > Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> > Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
> > Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
> > Tree: qemuu git://xenbits.xen.org/qemu-xen.git
> > Tree: seabios git://xenbits.xen.org/osstest/seabios.git
> > Tree: xen git://xenbits.xen.org/xen.git
> >
> > *** Found and reproduced problem changeset ***
> >
> >   Bug is in tree:  xen git://xenbits.xen.org/xen.git
> >   Bug introduced:  f96e1469ad06b61796c60193daaeb9f8a96d7458
> >   Bug not present: 0729830cc425a8ff27a3137e87b93768ae3c853c
> >   Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/148496/
> >
> >
> >   commit f96e1469ad06b61796c60193daaeb9f8a96d7458
> >   Author: Roger Pau Monné <roger.pau@xxxxxxxxxx>
> >   Date:   Wed Feb 5 13:49:09 2020 +0100
> >
> >       x86/vvmx: fix virtual interrupt injection when Ack on exit control is 
> > used
> >
> >       When doing a virtual vmexit (ie: a vmexit handled by the L1 VMM)
> >       interrupts shouldn't be injected using the virtual interrupt delivery
> >       mechanism unless the Ack on exit vmexit control bit isn't set in the
> >       nested vmcs.
> >
> >       Gate the call to nvmx_update_apicv helper on whether the nested vmcs
> >       has the Ack on exit bit set in the vmexit control field.
> >
> >       Note that this fixes the usage of x2APIC by the L1 VMM, at least when
> >       the L1 VMM is Xen.
> >
> >       Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
> >       Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>
> 
> Looks like there are further problems here.  I'm afraid I haven't
> investigated further, but this also might be the source of the
> intermittent problems in staging.
> 

any error message or stack dump for this failure?

Thanks
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel