RE: [Xen-ia64-devel] xm-test status report changset 8602:cfa3b96b056d

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

Hi Matsumoto-san --

Xen/ia64 does not fully support domain destroy
as memory resources are not recovered.  So if
the test creates and destroys domains many times,
Xen/ia64 will run out of memory.

Also, I do not think that Linux/ia64 is supported
with 64MB of memory, so this might not be a good
test for Xen/ia64 and Xenlinux/ia64.

Thanks,
Dan

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Matsumoto
> Sent: Thursday, January 19, 2006 11:38 PM
> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-ia64-devel] xm-test status report changset 
> 8602:cfa3b96b056d
> 
> Hi, all
> 
> I've run xm-test in latest xen. However, I do not carry out 
> some tests.
> Because there is the problem.
> 
> ãDom0 is downed when xm-test repeats create and destroy of DomU.
> ãDom0 is downed when xm-test start DomU of memory 64.
> 
> test which I did not carry out:
>   06_create_mem_neg
>   07_create_mem64_pos
>   10_create_fastdestroy
>   11_create_concurrent_pos
>   12_create_concurrent_stress_pos
>   15_create_smallmem_pos
>   07_destroy_stale_pos
> 
> TEST ENVIRONMENT
>   Machine          : Tiger4
>   Release          : 2.6.12.6-xen0
>   Changeset        : 8602:cfa3b96b056d
>   Dom0 OS          : RHEL4 U2 (no SMP)
>   DomU memory      : 96MB
> 
> Xm-test execution summary:
>   PASS:  64
>   FAIL:  28
>   XPASS: 0
>   XFAIL: 3
> 
> 
> Details:
> 
>  FAIL: 01_block_attach_device_pos 
>        Device is not actually connected to the domU
> 
>  FAIL: 02_block_attach_file_device_pos 
>        Device is not actually connected to the domU
> 
>  FAIL: 04_block_attach_device_repeatedly_pos 
>        xm block attach returned invalid 256 != 0
> 
>  FAIL: 05_block_attach_and_dettach_device_repeatedly_pos 
>        Failed to attach block device /proc/partitions does 
> not show that!
> 
>  FAIL: 09_block_attach_and_dettach_device_check_data_pos 
>        File created was lost or not updated!
> 
>  FAIL: 11_block_attach_shared_dom0 
>        Bug #331 Started a DomU with write access to a rw 
> mounted block device
> 
>  FAIL: 12_block_attach_shared_domU 
>        Bug #331 Started a DomU with write access to an in-use 
> block device
> 
>  FAIL: 01_block-list_pos 
>        Fail to list block device
> 
>  FAIL: 05_block-destroy_byname_pos 
>        block device isn't attached; can't detach!
> 
>  FAIL: 04_create_conflictname_neg 
>        xm create let me create a duplicate-named domain!
> 
>  FAIL: 13_create_multinic_pos 
>        (1 nics) Console didn't respond probably crashed!
> 
>  FAIL: 14_create_blockroot_pos 
>        Timed out waiting for console
> 
>  FAIL: 01_memset_basic_pos 
>        The DomU command 'cat /proc/xen/balloon' failed.
> 
>  FAIL: 03_memset_random_pos 
>        Invalid domU meminfo line
> 
> XFAIL: 02_network_local_ping_pos 
>        Timed out waiting for console
> 
> XFAIL: 05_network_dom0_ping_pos 
>        Timed out waiting for console
> 
> XFAIL: 11_network_domU_ping_pos 
>        Timed out waiting for console
> 
>  FAIL: 01_network_attach_pos 
>        xm network-attach returned invalid 256 != 0
> 
>  FAIL: 02_network_attach_detach_pos 
>        xm network-attach returned invalid 256 != 0
> 
>  FAIL: 03_network_attach_detach_multiple_pos 
>        xm network-attach returned invalid 256 != 0
> 
>  FAIL: 01_sedf_multi_pos 
>        [0] xm sedf returned invalid 256 != 0
> 
>  FAIL: 01_shutdown_basic_pos 
>        Guest domain failed to shutdown
> 
>  FAIL: 02_sysrq_sync_pos 
>        Sync SysRq not delivered
> 
>  FAIL: 03_sysrq_withreboot_pos 
>        [Errno 5] Input/output error
> 
>  FAIL: 01_save_basic_pos 
>        save command exited 256 != 0
> 
>  FAIL: 01_restore_basic_pos 
>        save command exited 256 != 0
> 
>  FAIL: 04_restore_withdevices_pos 
>        Timed out waiting for console
> 
>  FAIL: 01_migrate_localhost_pos 
>        xm migrate returned invalid 256 != 0
> 
> Best Regards,
> 
> Matsumoto
> 
> 
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

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