On Sun, 2015-03-29 at 16:26 +0100, xen.org wrote:
> branch xen-unstable
> xen branch xen-unstable
> job test-amd64-amd64-xl-credit2
> test guest-localmigrate
> 
> Tree: linux git://xenbits.xen.org/linux-pvops.git
> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
> Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.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:  d639e6a05a0f8ee0e61c6cc4eebba78934ef3648
>   Bug not present: 88a2372c6ba44dd42b915a95a823cf9d4d260e25
> 
> 
>   commit d639e6a05a0f8ee0e61c6cc4eebba78934ef3648
>   Author: Jan Beulich <jbeul...@suse.com>
>   Date:   Mon Mar 23 16:51:14 2015 +0100
>   
>       x86: allow 64-bit PV guest kernels to suppress user mode exposure of M2P

As predicted by Jan and already reverted by Tim.

The bisector is now working on another instance of this in a different
job. We could put a stop to it, since it is never going to see the
updated xen-unstable result which will happen in the new facility, but
OTOH those machines aren't doing much else...

Ian.



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

Reply via email to