On Wed, 25 Feb 2015, Paul Durrant wrote: > > -----Original Message----- > > From: Ian Jackson [mailto:ian.jack...@eu.citrix.com] > > Sent: 24 February 2015 18:00 > > To: Paul Durrant > > Cc: Stefano Stabellini; xen-de...@lists.xensource.com; Ian Campbell > > Subject: RE: [qemu-upstream-unstable bisection] complete test-amd64-i386- > > freebsd10-i386 > > > > Paul Durrant writes ("RE: [qemu-upstream-unstable bisection] complete > > test-amd64-i386-freebsd10-i386"): > > > I thought this was fixed. I posted the fix over a week ago and it's > > > applied: > > > > Looking at the most recent tests it appears that there is a > > combination of heisenbugs: > > > > Many recent flights (eg 35087) have: > > > > test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail pass in 34247 > > > > And 34247 has other problems with migration. > > > > Looking at 35087/test-amd64-i386-pair/17.ts-guest-migrate.log I see: > > > > Parsing config from <saved> > > xc: progress: Reloading memory pages: 7168/131072 5% > > xc: progress: Reloading memory pages: 13312/131072 10% > > xc: progress: Reloading memory pages: 20480/131072 15% > > xc: progress: Reloading memory pages: 26624/131072 20% > > xc: progress: Reloading memory pages: 32768/131072 25% > > 2015-02-23 09:37:11 Z command timed out [400]: timeout 430 ssh -o > > StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=100 -o > > ServerAliveInterval=100 -o PasswordAuthentication=no -o > > ChallengeResponseAuthentication=no -o > > UserKnownHostsFile=tmp/t.known_hosts_35087.test-amd64-i386-pair > > root@10.80.249.149 xl migrate debian.guest.osstest itch-mite > > status (timed out) at Osstest/TestSupport.pm line 397. > > > > The same in 34696. > > It appears that 'test-amd64-i386-freebsd10-i386 qemu-upstream-unstable' > passed in 34696, using current Xen master, and that seems to indicate my fix > was good. The host then changed from grain-weevil to leaf-beetle and it has > failed twice on the xen-boot test. So, there appears to be no justification > to revert my QEMU patch.
Sorry, the latest failures on host change and the lack of activity on the original thread made me think that the issue was still open. I confirm that it is fixed. Thanks! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
