Re: [Xen-devel] [xen-unstable test] 5352: regressions - FAIL

[George Dunlap <dunlapg@xxxxxxxxx>]

On Thu, Jan 27, 2011 at 5:49 AM, xen.org <ian.jackson@xxxxxxxxxxxxx> wrote:
> flight 5352 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/5352/
...
> Tests which did not succeed and are blocking:
>  test-amd64-i386-xl-multivcpu  9 guest-start                fail REGR. vs. 
> 5237
>  test-amd64-i386-xl            9 guest-start                fail REGR. vs. 
> 5237
>  test-amd64-xcpkern-i386-pv    9 guest-start                fail REGR. vs. 
> 5237
>  test-amd64-xcpkern-i386-xl-credit2  9 guest-start          fail REGR. vs. 
> 5237
>  test-amd64-xcpkern-i386-xl    9 guest-start                fail REGR. vs. 
> 5237
>  test-i386-xcpkern-i386-pair  16 guest-start                fail REGR. vs. 
> 5237

All of these seem to be failing because it can't find the dhcp address
after boot:

011-01-27 03:50:58 Z FAILURE: guest debian.guest.osstest
5a:36:0e:e8:00:15 22 link/ip/tcp: wait timed out:
/var/lib/dhcp3/dhcpd.leases:755: lease without `hardware ethernet'.
failure: guest debian.guest.osstest 5a:36:0e:e8:00:15 22 link/ip/tcp:
wait timed out: /var/lib/dhcp3/dhcpd.leases:755: lease without
`hardware ethernet'.

However, the guest console log indicates that it has actually booted,
and received an IP address:

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 10.80.248.4
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.80.248.4
bound to 10.80.249.225 -- renewal in 758 seconds.
done.

Not sure why this only failed for the 32-on-64-bit cases, but it seems
like some (perhaps temporary) flakiness in the code trying to find the
dhcp address.

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel