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

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



On 01.03.2020 12:44, osstest service owner wrote:
> flight 147735 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/147735/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-qemut-rhel6hvm-amd 13 guest-start.2      fail REGR. vs. 
> 147600

Further to my observations on flight 147522, this time I notice

Feb 29 23:02:52.154601 (d13) Booting from Hard Disk...
Feb 29 23:02:52.310570 [ 1466.981195] xenbr0: port 3(vif13.0-emu) entered 
disabled state
Feb 29 23:04:21.302621 [ 1466.981623] device vif13.0-emu left promiscuous mode
Feb 29 23:04:21.314522 [ 1466.981842] xenbr0: port 3(vif13.0-emu) entered 
disabled state
Feb 29 23:04:21.314567 (XEN) Dom13 callback via changed to Direct Vector 0xe9
Feb 29 23:04:21.338781 (XEN) irq.c:374: Dom13 PCI link 0 changed 5 -> 0
Feb 29 23:04:23.430698 (XEN) irq.c:374: Dom13 PCI link 1 changed 10 -> 0
Feb 29 23:04:23.430784 (XEN) irq.c:374: Dom13 PCI link 2 changed 11 -> 0
Feb 29 23:04:23.430836 (XEN) irq.c:374: Dom13 PCI link 3 changed 5 -> 0
Feb 29 23:04:23.442618 [ 1471.392872] xen-blkback: backend/vbd/13/768: using 1 
queues, protocol 1 (x86_32-abi) 
Feb 29 23:04:25.714618 (XEN) grant_table.c:1809:d13v0 Expanding d13 grant table 
from 1 to 2 frames
Feb 29 23:04:28.832859 [ 1474.532195] vif vif-13-0 vif13.0: Guest Rx ready
Feb 29 23:04:28.856971 [ 1474.532659] IPv6: ADDRCONF(NETDEV_CHANGE): vif13.0: 
link becomes ready
Feb 29 23:04:28.857059 [ 1474.533046] xenbr0: port 2(vif13.0) entered blocking 
state
Feb 29 23:04:28.868814 [ 1474.533304] xenbr0: port 2(vif13.0) entered 
forwarding state
Feb 29 23:04:28.868814 (XEN) emul-priv-op.c:1113:d0v3 Domain attempted WRMSR 
c0011020 from 0x0000000000000000 to 0x0040000000000000
Feb 29 23:04:34.710712 (XEN) emul-priv-op.c:1113:d0v3 Domain attempted WRMSR 
c0011020 from 0x0000000000000000 to 0x0040000000000000
...
Feb 29 23:04:35.910720 (XEN) emul-priv-op.c:1113:d0v0 Domain attempted WRMSR 
c0011020 from 0x0000000000000000 to 0x0040000000000000
Feb 29 23:04:35.922674 [ 1481.497029] systemd-logind[2531]: New session 123 of 
user root.
Feb 29 23:04:35.938273 Feb 29 23:04:36.154636 <client 0x55e5fa76f100 connected 
- now 1 clients>
(XEN) *** Serial input to Xen (type 'CTRL-x' three times to switch input)
Feb 29 23:04:36.178701 Feb 29 23:04:36.180558 <client 0x55e5fa76f100 
disconnected - now 0 clients>
Feb 29 23:04:37.151781 <client 0x55e5fa76f0b0 connected - now 1 clients>
(XEN) '0' pressed -> dumping Dom0's registers
Feb 29 23:04:37.170684 (XEN) *** Dumping Dom0 vcpu#0 state: ***

whereas (note the time stamps)

2020-02-29 23:02:51 Z guest redhat.guest.osstest 5a:36:0e:17:00:4e 22 
link/ip/tcp: waiting 100s... 
2020-02-29 23:03:05 Z guest redhat.guest.osstest 5a:36:0e:17:00:4e 22 
link/ip/tcp: ping gave (256): PING 172.16.146.199 (172.16.146.199) 56(84) bytes 
of data. |  | --- 172.16.146.199 ping statistics --- | 5 packets transmitted, 0 
received, 100% packet loss, time XXXms |  |  (waiting) ... 
2020-02-29 23:03:11 Z guest redhat.guest.osstest 5a:36:0e:17:00:4e 22 
link/ip/tcp: ping gave (256): PING 172.16.146.199 (172.16.146.199) 56(84) bytes 
of data. | From 172.16.144.3 icmp_seq=1 Destination Host Unreachable | From 
172.16.144.3 icmp_seq=2 Destination Host Unreachable | From 172.16.144.3 
icmp_seq=3 Destination Host Unreachable | From 172.16.144.3 icmp_seq=4 
Destination Host Unreachable | From 172.16.144.3 icmp_seq=5 Destination Host 
Unreachable |  | --- 172.16.146.199 ping statistics --- | 5 packets 
transmitted, 0 received, +5 errors, 100% packet loss, time XXXms | pipe 4 |  
(waiting) ... 
...
2020-02-29 23:04:33 Z FAILURE: guest redhat.guest.osstest 5a:36:0e:17:00:4e 22 
link/ip/tcp: wait timed out: ping gave (256): PING 172.16.146.199 
(172.16.146.199) 56(84) bytes of data. | From 172.16.144.3 icmp_seq=1 
Destination Host Unreachable | From 172.16.144.3 icmp_seq=2 Destination Host 
Unreachable | From 172.16.144.3 icmp_seq=3 Destination Host Unreachable | From 
172.16.144.3 icmp_seq=4 Destination Host Unreachable | From 172.16.144.3 
icmp_seq=5 Destination Host Unreachable |  | --- 172.16.146.199 ping statistics 
--- | 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 
XXXms | pipe 4 | . 
failure: guest redhat.guest.osstest 5a:36:0e:17:00:4e 22 link/ip/tcp: wait 
timed out: ping gave (256): PING 172.16.146.199 (172.16.146.199) 56(84) bytes 
of data. | From 172.16.144.3 icmp_seq=1 Destination Host Unreachable | From 
172.16.144.3 icmp_seq=2 Destination Host Unreachable | From 172.16.144.3 
icmp_seq=3 Destination Host Unreachable | From 172.16.144.3 icmp_seq=4 
Destination Host Unreachable | From 172.16.144.3 icmp_seq=5 Destination Host 
Unreachable |  | --- 172.16.146.199 ping statistics --- | 5 packets 
transmitted, 0 received, +5 errors, 100% packet loss, time XXXms | pipe 4 | .
+ rc=1
+ date -u +%Y-%m-%d %H:%M:%S Z exit status 1
2020-02-29 23:04:33 Z exit status 1
+ exit 1

The guest looks to be up fine, but it looks to have taken slightly
longer than the 100s. It is entirely unclear to me though why

Feb 29 23:02:52.154601 (d13) Booting from Hard Disk...

and

Feb 29 23:04:21.314567 (XEN) Dom13 callback via changed to Direct Vector 0xe9

are almost one and a half minutes apart - all prior tests (from
the guest-start/redhat.repeat step) took around 15s for this.

Jan

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

 


Rackspace

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