WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-devel] VMX status report changset 8979:5541ea99106a

from [Shi, Alex] [Permanent Link][Original]
To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] VMX status report changset 8979:5541ea99106a
From: "Shi, Alex" <alex.shi@xxxxxxxxx>
Date: Mon, 27 Feb 2006 14:55:41 +0800
Delivery-date: Mon, 27 Feb 2006 06:56:14 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcY7atLx8hiDPhy9T2qA714684m9Xw==
Thread-topic: VMX status report changset 8979:5541ea99106a 


We have tested latest xen on VT platform with Intel 915/E8500 chipset and here 
is the test summary:
 

issues:

        -  Create VMX may make service OS hang(issue log 1 as below)
        - destroy 4G memory vmx may make xend hang in IA-32e platform. (isse 
log 2 as below)

IA-32: 
    Build&Boot SMP xen0 without problem
    Can bootup unmodified 2.4/2.6 linux on VMX domain
    Can bootup unmodified Window XP 
    Can bootup VMX & Xen with different configuration
    A selected subset of LTP runs well in VMX domain(2.6)


 
IA-32_PAE: 
    Build&Boot SMP xen0 without problem
    Can bootup unmodified 2.6 linux on VMX domain
    Can bootup unmodified Window XP 
    Can bootup VMX & Xen with different configuration
    A selected subset of LTP runs well in VMX domain(2.6)


IA-32e: 
    Build&Boot SMP xen0 without problem
    Can bootup unmodified IA-32/IA-32e linux on VMX domain 
    Can bootup unmodified Window XP
    Can bootup VMX & xenU with different configuration
    A selected subset of LTP runs well in VMX domain(2.6)



for details
------------------------------------------------------------

Platform: IA-32
Service OS: IA-32, SMP
Default guest OS: IA-32, 2.6 kernel 

1, one vmx with memory 128M       PASS
2, one vmx with memory 256M       PASS
3, one vmx with memory 512M       PASS
4, one xenU create                PASS
5, 2 vmx and 2 xenU coexist       PASS
6, four vmx coexist               PASS
7, network in VMX domain          PASS
8, network in XenU domain         PASS
9, one window domain              PASS
10, IDE test in VMX domain        PASS
11,subset LTP test in VMX domain  PASS
 

Platform: IA-32_PAE
Service OS: IA-32_PAE, SMP
Default guest OS: IA-32, 2.6 kernel 


1, one vmx with memory 256M       PASS
2, one vmx with memory 512M       PASS
3, one vmx with memory 1500MB     PASS
4, one xenU create                PASS
5, network in VMX domain          PASS
6, network in XenU domain         PASS
7, one window domain              PASS
8, subset LTP test in VMX domain  PASS


Platform: IA-32e
Service OS:  IA-32e, SMP 
Default guest OS: IA-32e, 2.6 kernel
 
 
1, one vmx with memory 128M       PASS
2, one vmx with memory 256M       PASS
3, one vmx with memory 512M       PASS
4, one xenU create                PASS
5, 2 vmx and 2 xenU coexist       PASS
6, four vmx coexist               PASS
7, network in VMX domain          PASS
8, network in XenU domain         PASS
9, one 2.4 IA32 VMX domain        PASS
10, one 2.6 IA32 VMX domain       PASS
11, IA-32 2.4 and 2.6 VMX coexist PASS
12, IA-32 and IA-32e VMX coexist  PASS
13,subset LTP test in VMX domain  PASS
14, one window domain             PASS

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Create VMX may make service OS hang, issue log:

1, Environment:
------------
Service OS (ia32/ia32e/IA64):pae
Guest OS (ia32/ia32e/IA64):pae
Change Set:8979
Hardware:Grandstale



Bug detailed description:
--------------------------
Sometimes it happens, sometimes not. But it always happens when several vmx 
have already been created and destroyed. I 
never meet this problem when creating the first vmx after reboot. The problem 
blocked our nightly test on PAE host for 
three days.

In today's nightly test, the machine hung at creating LTP domain(the last case 
in nightly test).

Serial output is as below:

(XEN) (GUEST: 5) HVM Loader
(XEN) (GUEST: 5) Loading ROMBIOS ...
(XEN) (GUEST: 5) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 5) Loading VMXAssist ...
(XEN) (GUEST: 5) VMX go ...
(XEN) (GUEST: 5) VMXAssist (Feb 25 2006)
(XEN) (GUEST: 5) Memory size 256 MB
(XEN) (GUEST: 5) E820 map:
(XEN) (GUEST: 5) 0000000000000000 - 000000000009F800 (RAM)
(XEN) (GUEST: 5) 000000000009F800 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 5) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 5) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 5) 0000000000100000 - 000000000FFFE000 (RAM)
(XEN) (GUEST: 5) 000000000FFFF000 - 0000000010000000 (Type 17)
(XEN) (GUEST: 5) 000000000FFFE000 - 000000000FFFF000 (Type 18)
(XEN) (GUEST: 5) 0000000010000000 - 0000000010003000 (ACPI NVS)
(XEN) (GUEST: 5) 0000000010003000 - 000000001000D000 (ACPI Data)
(XEN) (GUEST: 5) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 5) 
(XEN) (GUEST: 5) Start BIOS ...
(XEN) (GUEST: 5) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 5)  rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) HVM_PIT: guest freq in cycles=189653190
(XEN) (GUEST: 5) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 5) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 5) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp 
$(XEN) (GUEST: 5) HVMAssist BIOS, 1 
cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
(XEN) (GUEST: 5) 
(XEN) (GUEST: 5) ata0-0: PCHS=6243/16/63 translation=lba LCHS=780/128/63
(XEN) (GUEST: 5) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (3073 MBytes)
(XEN) (GUEST: 5) ata0  slave: Unknown device
(XEN) (GUEST: 5) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) (GUEST: 5) ata1  slave: Unknown device
(XEN) (GUEST: 5) 
(XEN) (GUEST: 5) Booting from Hard Disk...
(XEN) ----[ Xen-3.0.0    Not tainted ]----
(XEN) CPU:    1
(XEN) EIP:    e008:[<ff150e2c>] shadow_direct_map_fault+0x1ec/0x490
(XEN) EFLAGS: 00010202   CONTEXT: hypervisor
(XEN) eax: fec00010   ebx: ef3f000e   ecx: 00000001   edx: 00000000
(XEN) esi: f000e000   edi: 00000001   ebp: fec00000   esp: ffbf7ed4
(XEN) cr0: 8005003b   cr3: 6fc14000
(XEN) ds: e010   es: e010   fs: e010   gs: e010   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ffbf7ed4:
(XEN)    ef3f000e 00000000 ff1c9f10 ffffe000 496f59b6 0000017c ff1f0080 
ff13d9f0 
(XEN)    ff1f0080 0004bb69 ffbe4080 ff1f0080 4bb6a067 00000000 6f3cb067 
00000000 
(XEN)    6fbd0001 00000000 ff192090 0046b000 ffbf7fb4 ff1f0080 ffbf7fb4 
ff13e9dd 
(XEN)    0046b000 ffbf7fb4 0000017c 00000080 0046b000 00000010 ff1f0080 
ff14219c 
(XEN)    ff1f0080 ffbe4080 ffbf7fb4 00000002 ff1f0080 0007a120 ff1f0080 
ff1f0080 
(XEN)    ff1f0080 0007a120 00000000 00000080 00000080 00000080 00000080 
ff1f0080 
(XEN)    00051e84 00000000 000014ca 0000162c 000556a0 0046b000 000014ce 
ff142622 
(XEN)    0000162c 000005a7 534d0043 000556a0 0046b000 000014ce 00000000 
000d0002 
(XEN)    00002c0c 00ef2000 00000000 000014d0 00000202 0000b800 000022f2 
0000f000 
(XEN)    0000f000 00000001 ff1f0080 
(XEN) Xen call trace:
(XEN)    [<ff150e2c>] shadow_direct_map_fault+0x1ec/0x490
(XEN)    [<ff13d9f0>] arch_vmx_do_resume+0x100/0x120
(XEN)    [<ff13e9dd>] vmx_do_page_fault+0x3d/0x180
(XEN)    [<ff14219c>] vmx_vmexit_handler+0xbec/0xf20
(XEN)    [<ff142622>] vmx_asm_vmexit_handler+0x22/0x30
(XEN)    
(XEN) Pagetable walk from fec00010:
(XEN) ----[ Xen-3.0.0    Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e008:[<ff1054e5>] send_guest_pirq+0x35/0xd0
(XEN) EFLAGS: 00010006   CONTEXT: hypervisor
(XEN) eax: 000000ff   ebx: 00000012   ecx: ff1de080   edx: ffbf5a00
(XEN) esi: 0007ee2c   edi: 00000001   ebp: ff1a4300   esp: ff187f48
(XEN) cr0: 8005003b   cr3: 0f21c000
(XEN) ds: e010   es: e010   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ff187f48:
(XEN)    000000c9 00000014 ffbe7480 ff11da32 ff1de080 00000014 ff193040 
ff187fb4 
(XEN)    00000000 00000000 00000000 ff11ad01 ff187f7c ff187fb4 00000000 
00000000 
(XEN)    00000000 00000000 00000000 00000000 00c90000 ff119488 0000e008 
00000246 
(XEN)    ff1dd180 00000314 ffbfe080 00000001 00000000 0006c8cc c057c000 
00000001 
(XEN)    c057dfac 00000000 000d0000 c01010c7 00000061 00000246 c057df98 
00000069 
(XEN)    0000007b 0000007b 00000000 00000000 00000000 ffbfe080 
(XEN) Xen call trace:
(XEN)    [<ff1054e5>] send_guest_pirq+0x35/0xd0
(XEN)    [<ff11da32>] do_IRQ+0x72/0x130
(XEN)    [<ff11ad01>] common_interrupt+0x41/0x50
(XEN)    [<ff119488>] idle_loop+0x38/0x80
(XEN)    
(XEN) Faulting linear address: 0007ee38
(XEN) Pagetable walk from 0007ee38:
(XEN)  L3 = 000000000265e001 0000345e
(XEN)   L2 = 0000000000000000 55555555 
(XEN) ************************************
(XEN) CPU0 FATAL TRAP 14 (page fault), ERROR_CODE 0000, IN INTERRUPT CONTEXT.
(XEN) System shutting down -- need manual reset.
(XEN) ************************************



------- Additional Comment #1 From Zhang Xiao 2006-02-27 13:29 [reply] ------- 
Just now I tried once more, the machine hung at creating windows domain.
Serial output is below:

(XEN) (GUEST: 5) HVM Loader
(XEN) (GUEST: 5) Loading ROMBIOS ...
(XEN) (GUEST: 5) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 5) Loading VMXAssist ...
(XEN) (GUEST: 5) VMX go ...
(XEN) (GUEST: 5) VMXAssist (Feb 27 2006)
(XEN) (GUEST: 5) Memory size 256 MB
(XEN) (GUEST: 5) E820 map:
(XEN) (GUEST: 5) 0000000000000000 - 000000000009F800 (RAM)
(XEN) (GUEST: 5) 000000000009F800 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 5) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 5) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 5) 0000000000100000 - 000000000FFFE000 (RAM)
(XEN) (GUEST: 5) 000000000FFFF000 - 0000000010000000 (Type 17)
(XEN) (GUEST: 5) 000000000FFFE000 - 000000000FFFF000 (Type 18)
(XEN) (GUEST: 5) 0000000010000000 - 0000000010003000 (ACPI NVS)
(XEN) (GUEST: 5) 0000000010003000 - 000000001000D000 (ACPI Data)
(XEN) (GUEST: 5) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 5) 
(XEN) (GUEST: 5) Start BIOS ...
(XEN) (GUEST: 5) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 5)  rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) HVM_PIT: guest freq in cycles=189651090
(XEN) (GUEST: 5) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 5) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 5) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert 
Exp $(XEN) (GUEST: 5) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 
2005/05/07 15:55:26 $
(XEN) (GUEST: 5) 
(XEN) (GUEST: 5) ata0-0: PCHS=6243/16/63 translation=lba LCHS=780/128/63
(XEN) (GUEST: 5) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (3073 MBytes)
(XEN) (GUEST: 5) ata0  slave: Unknown device
(XEN) (GUEST: 5) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) (GUEST: 5) ata1  slave: Unknown device
(XEN) (GUEST: 5) 
(XEN) (GUEST: 5) Booting from Hard Disk...
(XEN) ----[ Xen-3.0.0    Not tainted ]----
(XEN) CPU:    1
(XEN) EIP:    e008:[<ff150f6c>] shadow_direct_map_fault+0x1ec/0x490
(XEN) EFLAGS: 00010202   CONTEXT: hypervisor
(XEN) eax: fec00010   ebx: ef3f000e   ecx: 00000001   edx: 00000000
(XEN) esi: f000e000   edi: 00000001   ebp: fec00000   esp: ffbf7ed4
(XEN) cr0: 8005003b   cr3: 4dc1d000
(XEN) ds: e010   es: e010   fs: e010   gs: e010   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ffbf7ed4:
(XEN)    ef3f000e 00000000 ff1c9f90 ffffe000 99d22943 000001ec ff1f0080 
ff13daa0 
(XEN)    ff1f0080 0004afd2 ffbe4080 ff1f0080 4afd3067 00000000 4d3d4067 
00000000 
(XEN)    4dbd9001 00000000 ff192090 0046b000 ffbf7fb4 ff1f0080 ffbf7fb4 
ff13eb1d 
(XEN)    0046b000 ffbf7fb4 000001ec 00000080 0046b000 00000010 ff1f0080 
ff1422dc 
(XEN)    00000000 ffbe5718 ffbe5778 00000002 ff1f0080 ffbf5900 ff192090 
ff1113aa 
(XEN)    99d9ca63 000001ec 00000000 00000080 00000080 00000080 00000080 
00000080 
(XEN)    99d22943 00000000 ff1f0080 0000162c 000556a0 0046b000 000014ce 
ff142762 
(XEN)    0000162c 000005a7 534d0043 000556a0 0046b000 000014ce 00000000 
00000002 
(XEN)    00002c0c 00ef2000 00000000 000014d0 00000202 0000b800 000022f2 
0000f000 
(XEN)    0000f000 00000001 ff1f0080 
(XEN) Xen call trace:
(XEN)    [<ff150f6c>] shadow_direct_map_fault+0x1ec/0x490
(XEN)    [<ff13daa0>] arch_vmx_do_resume+0x100/0x120
(XEN)    [<ff13eb1d>] vmx_do_page_fault+0x3d/0x180
(XEN)    [<ff1422dc>] vmx_vmexit_handler+0xbec/0xf20
(XEN)    [<ff1113aa>] timer_softirq_action+0x10a/0x140
(XEN)    [<ff142762>] vmx_asm_vmexit_handler+0x22/0x30
(XEN)    
(XEN) Pagetable walk from fec00010:
(XEN) ----[ Xen-3.0.0    Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e008:[<ff105655>] send_guest_pirq+0x35/0xd0
(XEN) EFLAGS: 00010006   CONTEXT: hypervisor
(XEN) eax: 000000ff   ebx: 00000012   ecx: ff1de080   edx: ffbf5a00
(XEN) esi: 0007ee2c   edi: 00000001   ebp: ff1a4300   esp: ff187f48
(XEN) cr0: 8005003b   cr3: 4a917000
(XEN) ds: e010   es: e010   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ff187f48:
(XEN)    000000c9 00000014 ffbe7580 ff11d892 ff1de080 00000014 ff187f7c 
ff187fb4 
(XEN)    00000000 00000000 ff1dd180 ff11ab61 ff187f7c ff187fb4 00000000 
00000000 
(XEN)    00000000 00000000 ff1dd180 00000000 00c90000 ff119298 0000e008 
00000246 
(XEN)    00000000 ff1dd180 ffbfe080 00000001 00000000 0008b2b2 c057e000 
00000001 
(XEN)    c057ffac 00000000 000d0000 c01010c7 00000061 00000246 c057ff98 
00000069 
(XEN)    0000007b 0000007b 00000000 00000000 00000000 ffbfe080 
(XEN) Xen call trace:
(XEN)    [<ff105655>] send_guest_pirq+0x35/0xd0
(XEN)    [<ff11d892>] do_IRQ+0x72/0x130
(XEN)    [<ff11ab61>] common_interrupt+0x41/0x50
(XEN)    [<ff119298>] idle_loop+0x38/0x80
(XEN)    
(XEN) Faulting linear address: 0007ee38
(XEN) Pagetable walk from 0007ee38:
(XEN)  L3 = 0000000004202001 00009802
(XEN)   L2 = 0000000000000000 55555555 
(XEN) ************************************
(XEN) CPU0 FATAL TRAP 14 (page fault), ERROR_CODE 0000, IN INTERRUPT CONTEXT.
(XEN) System shutting down -- need manual reset.
(XEN) ************************************

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
 destroy 4G memory vmx may make xend hang in IA-32e platform, serial line 
output:

Kernel BUG at mm/rmap.c:555
invalid opcode: 0000 [1] SMP
CPU 0
Modules linked in: video thermal processor fan button battery ac
Pid: 6207, comm: qemu-dm Not tainted 2.6.16-rc4-xen0 #1
RIP: e030:[<ffffffff80166b57>] <ffffffff80166b57>{page_remove_rmap+135}
RSP: e02b:ffff8800122e5b98  EFLAGS: 00010286
RAX: 00000000ffffffff RBX: ffff880001218210 RCX: 0000000000000000
RDX: ffffffffff578000 RSI: 0000000000000000 RDI: ffffffff80526440
RBP: ffff8800122e5ba8 R08: 000000000000000b R09: 000000000000000a
R10: 00000000000003d5 R11: 000000000000000d R12: 00002aaaaae7f000
R13: ffff880001218210 R14: 0000000000000000 R15: ffff88001e559600
FS:  00002af2c79a2640(0000) GS:ffffffff80651000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process qemu-dm (pid: 6207, threadinfo ffff8800122e4000, task ffff88001d82ee40)
Stack: 0000000000000000 ffff8800098933f8 ffff8800122e5ca8 ffffffff8015d65f
       00002aaaaaeabfff 00002aaaaaeabfff 00002aaaaaeabfff 8000000162e44067
       ffff88001e559670 ffffffff00000000
Call Trace: <ffffffff8015d65f>{unmap_vmas+1791} 
<ffffffff80164001>{exit_mmap+129}
       <ffffffff80128f90>{mmput+48} <ffffffff8012e316>{exit_mm+230}
       <ffffffff8012eaf0>{do_exit+528} <ffffffff80136d72>{recalc_sigpending+18}
       <ffffffff801374e9>{__dequeue_signal+441} 
<ffffffff8012f2df>{do_group_exit+271}
       <ffffffff801396dd>{get_signal_to_deliver+1709} 
<ffffffff801420f0>{autoremove_wake_function+0}
       <ffffffff8010a51d>{do_signal+125} <ffffffff80180cf7>{pipe_readv+663}
       <ffffffff80180d8e>{pipe_read+30} <ffffffff8010b2ef>{sysret_signal+56}
       <ffffffff8010ad00>{do_notify_resume+48} 
<ffffffff8010b5c5>{ptregscall_common+61}

Code: 0f 0b 68 14 bd 4a 80 c2 2b 02 48 c7 c6 ff ff ff ff bf 20 00
RIP <ffffffff80166b57>{page_remove_rmap+135} RSP <ffff8800122e5b98>
 <1>Fixing recursive fault but reboot is needed!
peth0: received packet with  own address as source address
Bad page state in process 'mrtg'
page:ffff880001218210 flags:0x0000000000000014 mapping:0000000000000000 
mapcount:-1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:

Call Trace: <ffffffff80152a4d>{bad_page+93} 
<ffffffff801537ba>{get_page_from_freelist+650}
       <ffffffff8015394a>{__alloc_pages+90} 
<ffffffff8015fe16>{__handle_mm_fault+774}
       <ffffffff80151dd8>{generic_file_aio_read+56} 
<ffffffff80173ce0>{do_sync_read+240}
       <ffffffff80117ae8>{do_page_fault+2232} 
<ffffffff801420f0>{autoremove_wake_function+0}
       <ffffffff80173e52>{vfs_read+306} <ffffffff8010b90f>{error_exit+0}

Thanks and best regards
Alex shi
--- Begin Message ---
To: "CSD-OTC Linux VMM QA" <csd-otc.linux.vmm.qa@xxxxxxxxx>
Subject: xm-test result for changset 8978
From: "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>
Date: Mon, 27 Feb 2006 09:17:48 +0800
Thread-index: AcY7O55x7I3wWLkuR0SLh3xdG2vNKg==
Thread-topic: xm-test result for changset 8978 
Xm-test execution summary:
  PASS:  43
  FAIL:  5
  XPASS: 0
  XFAIL: 2


Details:

XFAIL: 02_network_local_ping_pos
         ping loopback failed for size 32767 65507. ping eth0 failed for
size 32767 65507.

XFAIL: 11_network_domU_ping_pos
         Ping failed for size 32767 65507.

 FAIL: 01_reboot_basic_pos
         [Errno 5] Input/output error

 FAIL: 01_sedf_multi_pos
         [0] xm sedf returned invalid 256 != 0

 FAIL: 01_enforce_dom0_cpus_basic_pos
         /proc/cpuinfo says xend didn't enforce dom0_cpus (2 != 1)

--- End Message ---
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] VMX status report changset 8979:5541ea99106a, Shi, Alex <=
Previous by Date:  Re: [Xen-devel] domU clock over 23s off, Saku Ytti
Next by Date:  Re: [Xen-devel] [Patch] cleanup warning in xen/ia64, Keir Fraser
Previous by Thread:  [Xen-devel] [PATCH] Clean up warning for page_alloc.c, Masaki Kanno
Next by Thread:  [Xen-devel] [PATCH] Fix qemu-dm segfault when multiple HVM domains ---Was: qemu-dm segfault with multiple HVM domains?, Jiang, Yunhong
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy