Re: [Xen-devel] [xen-unstable test] 12876: tolerable FAIL - PUSHED

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2012-05-15 at 08:12 +0100, xen.org wrote:
> flight 12876 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/12876/
> 
> Failures :-/ but no regressions.
> 
> Tests which are failing intermittently (not blocking):

(re-ordered to get the short ones over with first)

>  test-amd64-amd64-xl-sedf-pin 14 guest-localmigrate/x10      fail pass in 
> 12860

Known intermittent bug in non-default scheduler. Don't care for 4.2.

> test-amd64-i386-qemuu-rhel6hvm-amd 7 redhat-install fail in 12860 pass in 
> 12876

qemuu is still a bit flakey. It's not the default qemu for 4.2 but would
still be nice to investigate.

> test-i386-i386-xl-win         7 windows-install             fail pass in 12860

The test harness seems to die ~11 mins after starting the guest. The
timeout was 7000 seconds which is 100+ mins.

2012-05-15 03:22:39 Z executing ssh ... root@xxxxxxxxxxxx xl create 
/etc/xen/win.guest.osstest.cfg
WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" 
instead if you really want a non-default firmware
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019bca4
  TOTAL:         0000000000000000->000000001f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000000fb
  1GB PAGES: 0x0000000000000000
libxl: error: libxl.c:3162:libxl_sched_credit_domain_set: Cpu weight out of 
range, valid values are within range from 1 to 65535
Parsing config file /etc/xen/win.guest.osstest.cfg
Daemon running with PID 2548
2012-05-15 03:22:40 Z guest win.guest.osstest 5a:36:0e:4c:00:1d 8936 
link/ip/tcp: waiting 7000s...
2012-05-15 03:22:40 Z guest win.guest.osstest 5a:36:0e:4c:00:1d 8936 
link/ip/tcp: no active lease (waiting) ...
Died at Osstest.pm line 1833, <GEN1332> line 2553.
...
+ rc=255
+ date -u '+%Y-%m-%d %H:%M:%S Z exit status 255'
2012-05-15 03:33:45 Z exit status 255

The screenshot shows that the guest was in the middle of an XP boot.
 
Hopefully a harness problem but otherwise needs looking at for 4.2?

>  test-amd64-i386-win           7 windows-install             fail pass in 
> 12860

This timed out after ~2 hours. The screenshot shows that the Windows
installer was still at the blue and yellow text mode stage, and a fairly
early looking one at that. It seems rather like the guest has hung, or
at least stalled.

Needs investigation for 4.2?

Towards the end of the host serial log is a stack trace which suggests
that we were at least in the guest context.

May 15 01:56:45.470932 (XEN) *** Dumping CPU1 host state: ***
May 15 01:56:45.470966 (XEN) ----[ Xen-4.2-unstable  x86_64  debug=y  Not 
tainted ]----
May 15 01:56:45.478913 (XEN) CPU:    1
May 15 01:56:45.478937 (XEN) RIP:    e008:[<ffff82c4801cd933>] 
vmx_vmcs_enter+0xc5/0xc6
May 15 01:56:45.478977 (XEN) RFLAGS: 0000000000000246   CONTEXT: hypervisor
May 15 01:56:45.490925 (XEN) rax: ffff8301281bff18   rbx: ffff8300cfd19000   
rcx: 0000000000010093
May 15 01:56:45.498909 (XEN) rdx: 0000000000000093   rsi: 0000000000000000   
rdi: ffff8300cfd19000
May 15 01:56:45.498947 (XEN) rbp: ffff8301281bf5f8   rsp: ffff8301281bf5b0   
r8:  ffff82f602289d68
May 15 01:56:45.510917 (XEN) r9:  0000000000000000   r10: 0000000000000000   
r11: 0000000000000000
May 15 01:56:45.518908 (XEN) r12: 0000000000000005   r13: 000000000000ffff   
r14: 0000000000000000
May 15 01:56:45.518945 (XEN) r15: 0000000000000000   cr0: 0000000080050033   
cr4: 00000000000426f0
May 15 01:56:45.530913 (XEN) cr3: 000000010ce45000   cr2: 0000000000000000
May 15 01:56:45.530947 (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 
0000   cs: e008
May 15 01:56:45.538921 (XEN) Xen stack trace from rsp=ffff8301281bf5b0:
May 15 01:56:45.538954 (XEN)    ffff82c4801d0405 ffff8301281bf688 
00000093cfd19000 ffff8301281bf5f8
May 15 01:56:45.550915 (XEN)    ffff8300cfd19000 0000000000000005 
0000000000000005 0000000080010021
May 15 01:56:45.558914 (XEN)    ffff8301281bf628 ffff8301281bf6d8 
ffff82c4801d227c 00000000000244e2
May 15 01:56:45.566906 (XEN)    0000000000000024 ffff8301281bf688 
00000000801e0cc8 0000ffff009b2000
May 15 01:56:45.566945 (XEN)    0000000000020000 0000ffff009322f3 
0000000000022f30 0000ffff009322f3
May 15 01:56:45.578924 (XEN)    0000000000022f30 0000ffff00930000 
0000000000000000 0000ffff00930030
May 15 01:56:45.586968 (XEN)    0000000000000300 0000ffff00930000 
0000000000000000 00000077008b0028
May 15 01:56:45.587027 (XEN)    0000000000024460 ffff8301281bf708 
ffff8301281bf700 ffff8301281bfdd8
May 15 01:56:45.598935 (XEN)    0000000080000011 ffff8300cfd19000 
0000000000000010 00000000001144eb
May 15 01:56:45.607211 (XEN)    0000000000000039 ffff8301281bf738 
ffff82c4801b0b76 ffff830100000001
May 15 01:56:45.607248 (XEN)    ffff8300cfd19000 ffff8301281bf728 
0000000000000007 ffff8301281bfdd8
May 15 01:56:45.618930 (XEN)    0000000000000000 0000000080000011 
0000000000000000 0000000000000000
May 15 01:56:45.626921 (XEN)    ffff82c480265500 ffff8301281bf778 
ffff82c4801ab15a ffff8301281bf778
May 15 01:56:45.626960 (XEN)    ffff8301281bfdd8 ffff8301281bf778 
ffff82c480189e69 ffff8301281bfdd8
May 15 01:56:45.638934 (XEN)    0000000000000022 ffff8301281bfcd8 
ffff82c480198204 0000000100000008
May 15 01:56:45.646931 (XEN)    0000000000000000 01ff82f6025a14c0 
0000000000000000 ffff8301281bff00
May 15 01:56:45.646969 (XEN)    ffff8301281bff18 ffff8301281bf800 
ffff82c4801a5182 01ff8300cfe6b000
May 15 01:56:45.658921 (XEN)    0000000800000000 ffff8301281bffc0 
000000008016fec4 0000000100000008
May 15 01:56:45.666915 (XEN)    0001000000000000 0100000000000000 
0000000000000002 ffff8301281b0000
May 15 01:56:45.666951 (XEN)    0000000000000001 0000000000000048 
00000000001144d5 0000000000000002
May 15 01:56:45.678914 (XEN) Xen call trace:
May 15 01:56:45.678940 (XEN)    [<ffff82c4801cd933>] vmx_vmcs_enter+0xc5/0xc6
May 15 01:56:45.686917 (XEN)    [<ffff82c4801d227c>] 
vmx_update_guest_cr+0x252/0x663
May 15 01:56:45.686954 (XEN)    [<ffff82c4801b0b76>] hvm_set_cr0+0x562/0x5e8
May 15 01:56:45.698910 (XEN)    [<ffff82c4801ab15a>] hvmemul_write_cr+0x91/0xd4
May 15 01:56:45.698945 (XEN)    [<ffff82c480198204>] x86_emulate+0xdba9/0xfc89
May 15 01:56:45.706917 (XEN)    [<ffff82c4801aad74>] hvm_emulate_one+0x120/0x1af
May 15 01:56:45.706953 (XEN)    [<ffff82c4801cc796>] 
realmode_emulate_one+0x3b/0x21a
May 15 01:56:45.718907 (XEN)    [<ffff82c4801cca75>] vmx_realmode+0x100/0x25b
May 15 01:56:45.718942 (XEN)    
May 15 01:56:45.718968 (XEN) *** Dumping CPU1 guest state (d1:v0): ***
May 15 01:56:45.726921 (XEN) ----[ Xen-4.2-unstable  x86_64  debug=y  Not 
tainted ]----
May 15 01:56:45.726959 (XEN) CPU:    1
May 15 01:56:45.738920 (XEN) RIP:    2000:[<0000000000000252>]
May 15 01:56:45.738950 (XEN) RFLAGS: 0000000000010086   CONTEXT: hvm guest
May 15 01:56:45.738987 (XEN) rax: 0000000080000011   rbx: 0000000000067ff2   
rcx: 00000000000000b6
May 15 01:56:45.746923 (XEN) rdx: 0000000000000001   rsi: 0000000000011d68   
rdi: 0000000006000000
May 15 01:56:45.758908 (XEN) rbp: 0000000000060b88   rsp: 0000000000067ff2   
r8:  0000000000000000
May 15 01:56:45.758945 (XEN) r9:  0000000000000000   r10: 0000000000000000   
r11: 0000000000000000
May 15 01:56:45.766919 (XEN) r12: 0000000000000000   r13: 0000000000000000   
r14: 0000000000000000
May 15 01:56:45.778914 (XEN) r15: 0000000000000000   cr0: 0000000080000011   
cr4: 0000000000000000
May 15 01:56:45.778951 (XEN) cr3: 0000000000039000   cr2: 0000000000000000
May 15 01:56:45.786916 (XEN) ds: 0060   es: 0000   fs: 0030   gs: 0000   ss: 
22f3   cs: 2000
May 15 01:56:45.786952 (XEN) 



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