Xen project Mailing List

[Xen-devel] Testing status of HVM (Intel VT) on 64bit XEN unstable c/s 13553

To: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>

From: Ed Smith <esmith@xxxxxxxxxxxxxxx>

Date: Wed, 24 Jan 2007 10:08:52 -0500

Delivery-date: Wed, 24 Jan 2007 07:08:46 -0800

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Summary: Changeset 13553 - gettimeofday02 nanosleep01/02 ltp tests fail (failure.1) - After a 256MB guest has been up and running for some time on a 2GB node, launching another 256MB guest fails with: Error: (12, 'Cannot allocate memory') (failure.2) - 32bit non-pae uniprocessor kernel guest hangs on boot. xm list shows no cpu time consumption (failure.3) Test Configuration: Dell Precision WorkStation 380, Dual Core, 2GB, 3 SATA (Intel VT) 64bit XEN RELEASE Build Hypervisor on a RHEL4U2 64bit root (/dev/sda) 32bit fully virtualized (HVM) guest RHEL4U2 256MB (/dev/sdb) pae=1(smp) pae=0(up), acpi=1, apic=1 64bit fully virtualized (HVM) guest RHEL4U2 256MB (/dev/sdc) pae=1, acpi=1, apic=1 Boot Tests: Boot a fully virtualized (HVM) guest to the login prompt Results are marked Pass|Fail where (n) points to a failure description Regression Tests: 852 tests (851 ltp tests and one 30 minute user load test) Tests are marked #Pass/#Fail where (n) points to a failure description XEN 64bit 2 CPU Hypervisor (booted smp): ---------------------------------------------------------------------- | XEN | Guest Kernel (SMP kernels booted with 2 CPUs) | | Changeset|-----------------------------------------------------------| | | 32bit UP | 32bit SMP | 64bit UP | 64bit SMP | | |--------------|--------------|--------------|--------------| | | Boot | Test | Boot | Test | Boot | Test | Boot | Test | |----------|------|-------|------|-------|------|-------|------|-------| | 13553 | Fail | | Pass | 851/1 | Pass | | Pass | 852/0 | | | (3) | | | (1) | | | | | |----------|------|-------|------|-------|------|-------|------|-------| | 13377 | Fail | | Pass | 851/1 | Pass | | Pass | 851/1 | | | (3) | | | (1) | | | | (1) | |----------|------|-------|------|-------|------|-------|------|-------| | 13330 | Fail | | Pass | 851/1 | Pass | | Pass | 851/1 | | | (3) | | | (1) | | | | (1) | |----------|------|-------|------|-------|------|-------|------|-------| | 13214 | Pass | | Pass | 851/1 | Pass | | Pass | 851/1 | | | | | | (1) | | | | (1) | |----------|------|-------|------|-------|------|-------|------|-------| | 13205 | Pass | | Pass | 851/1 | Pass | | Pass | 851/1 | | | | | | (1) | | | | (1) | ---------------------------------------------------------------------- Multiple Guest Boot Test Test is a 30 minute user load on both Guests XEN 64bit 2 CPU Hypervisor (booted smp): -------------------------------------------- | XEN | Guest Kernel | | Changeset|---------------------------------| | | 32bit 1CPU UP | 32bit 2CPU SMP | | | 64bit 1CPU UP | 64bit 2CPU SMP | | |----------------|----------------| | | Boot | Test | Boot | Test | |----------|------|---------|------|---------| | 13553 | Fail | | Pass | Pass | | | (3) | | (2) | | |----------|------|---------|------|---------| | 13377 | Fail | | Pass | Pass | | | (3) | | (2) | | |----------|------|---------|------|---------| | 13330 | Fail | | Pass | Pass | | | (3) | | (2) | | |----------|------|---------|------|---------| | 13214 | Pass | Pass | Pass | Pass | | | (2) | | (2) | | |----------|------|---------|------|---------| | 13205 | Pass | Pass | Pass | Pass | | | (2) | | (2) | | -------------------------------------------- Failures: 1. BUG 666: 32bit guests fail gettimeofday02, nanosleep01/02 with clock problems 2. After a 256MB guest has been up and running for some time on a 2GB node, launching another 256MB guest fails with: Error: (12, 'Cannot allocate memory') 3. 32bit non-pae uniprocessor kernel guest hangs on boot xm list shows no cpu time consumption

File: failure.1 [root@tst079 ~]# xm info host : tst079 release : 2.6.18-xen version : #1 SMP Tue Jan 23 05:55:51 EST 2007 machine : x86_64 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2793 hw_caps : bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001 total_memory : 1022 free_memory : 1 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Mon Jan 22 16:27:03 2007 +0000 13553:200a9c6deeb3 cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) cc_compile_by : build cc_compile_domain : virtualiron.com cc_compile_date : Tue Jan 23 05:12:12 EST 2007 xend_config_format : 3 [root@tst079 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 723 2 r----- 3527.7 vs161 1 264 2 -b---- 14713.8 [root@tst079 ~]# Guest: [root@vs161 bin]# while [ 1 ]; do gettimeofday02; sleep 2; done gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s gettimeofday02 1 FAIL : Time is going backwards (old 1169648439.560203 vs new 1169648439.560102! gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s gettimeofday02 1 FAIL : Time is going backwards (old 1169648441.626595 vs new 1169648441.626561! gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s gettimeofday02 1 FAIL : Time is going backwards (old 1169648443.659636 vs new 1169648443.659602! gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s gettimeofday02 1 FAIL : Time is going backwards (old 1169648445.760869 vs new 1169648445.760833! gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s gettimeofday02 1 FAIL : Time is going backwards (old 1169648447.791462 vs new 1169648447.791408! gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s gettimeofday02 1 FAIL : Time is going backwards (old 1169648449.851587 vs new 1169648449.851047! gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s gettimeofday02 1 FAIL : Time is going backwards (old 1169648451.913218 vs new 1169648451.913168! gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s gettimeofday02 1 FAIL : Time is going backwards (old 1169648453.947117 vs new 1169648453.947082! [root@vs161 bin]# while [ 1 ]; do nanosleep01; sleep 2; done nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 FAIL : Child execution not suspended for 2 seconds. (Wanted 2000 ms, got 2295 ms) nanosleep01 1 FAIL : Failures reported above nanosleep01 1 PASS : nanosleep functionality is correct nanosleep01 1 FAIL : Child execution not suspended for 2 seconds. (Wanted 2000 ms, got 2275 ms) nanosleep01 1 FAIL : Failures reported above nanosleep01 1 PASS : nanosleep functionality is correct [root@vs161 bin]# while [ 1 ]; do nanosleep02; sleep 2; done nanosleep02 1 PASS : Functionality of nanosleep() is correct nanosleep02 1 PASS : Functionality of nanosleep() is correct nanosleep02 1 PASS : Functionality of nanosleep() is correct nanosleep02 1 PASS : Functionality of nanosleep() is correct nanosleep02 1 PASS : Functionality of nanosleep() is correct nanosleep02 1 FAIL : Remaining sleep time 4231 msec doesn't match with the expected 3805 msec time nanosleep02 1 FAIL : child process exited abnormally nanosleep02 1 PASS : Functionality of nanosleep() is correct

File: failure.2 [root@tst078 ~]# xm info host : tst078 release : 2.6.18-xen version : #1 SMP Tue Jan 23 05:55:51 EST 2007 machine : x86_64 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2793 hw_caps : bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001 total_memory : 2046 free_memory : 1 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Mon Jan 22 16:27:03 2007 +0000 13553:200a9c6deeb3 cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) cc_compile_by : build cc_compile_domain : virtualiron.com cc_compile_date : Tue Jan 23 05:12:12 EST 2007 xend_config_format : 3 [root@tst078 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1735 2 r----- 4239.6 vs170 1 264 2 -b---- 15311.5 [root@tst078 ~]# cat /proc/meminfo MemTotal: 1776640 kB MemFree: 13924 kB Buffers: 1529820 kB Cached: 60776 kB SwapCached: 0 kB Active: 561900 kB Inactive: 1059136 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 1776640 kB LowFree: 13924 kB SwapTotal: 6450056 kB SwapFree: 6449768 kB Dirty: 296 kB Writeback: 0 kB AnonPages: 30512 kB Mapped: 9620 kB Slab: 77524 kB PageTables: 2532 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 7338376 kB Committed_AS: 125592 kB VmallocTotal: 34359738367 kB VmallocUsed: 85600 kB VmallocChunk: 34359651751 kB [root@tst078 ~]# cat /proc/xen/balloon Current allocation: 1776640 kB Requested target: 1776640 kB Low-mem balloon: 149208 kB High-mem balloon: 0 kB Driver pages: 1024 kB Xen hard limit: ??? kB [root@tst078 ~]# xm create /boot/vs160_sdl.hvm Using config file "/boot/vs160_sdl.hvm". Error: (12, 'Cannot allocate memory') [root@tst078 ~]#

File: failure.3 [root@tst078 ~]# xm info host : tst078 release : 2.6.18-xen version : #1 SMP Tue Jan 23 05:55:51 EST 2007 machine : x86_64 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2793 hw_caps : bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001 total_memory : 2046 free_memory : 1 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Mon Jan 22 16:27:03 2007 +0000 13553:200a9c6deeb3 cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) cc_compile_by : build cc_compile_domain : virtualiron.com cc_compile_date : Tue Jan 23 05:12:12 EST 2007 xend_config_format : 3 [root@tst078 ~]# xm create /boot/vs160_sdl_nopae.hvm Using config file "/boot/vs160_sdl_nopae.hvm". Started domain vs160 ** GUEST HANGS ** [root@tst078 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1467 2 r----- 4266.8 vs160 4 264 1 -b---- 2.9 [root@tst078 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1467 2 r----- 4267.0 vs160 4 264 1 -b---- 2.9 [root@tst078 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1467 2 r----- 4267.2 vs160 4 264 1 -b---- 2.9 [root@tst078 ~]# Guest hangs after: Mounting root filesystem kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Switching to new root

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

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.