Summary:
Changeset 14201
- 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)
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 |
|----------|------|-------|------|-------|------|-------|------|-------|
| 14201 | Pass | | Pass | 851/1 | Pass | | Pass | 852/0 |
| | | | | (1) | | | | |
|----------|------|-------|------|-------|------|-------|------|-------|
| 14043 | Pass | | Pass | 851/1 | Pass | | Pass | 851/1 |
| | | | | (1) | | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13899 | Fail | | Pass | 851/1 | Pass | | Pass | 851/1 |
| | (3) | | | (1) | | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13835 | Fail | | Pass | 851/1 | Pass | | Pass | 851/1 |
| | (3) | | | (1) | | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13762 | Fail | | Pass | 851/1 | Pass | | Pass | 851/1 |
| | (3) | | | (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 |
|----------|------|---------|------|---------|
| 14201 | Pass | Pass | Pass | Pass |
| | (2) | | (2) | |
|----------|------|---------|------|---------|
| 14043 | Pass | Pass | Pass | Pass |
| | (2) | | (2) | |
|----------|------|---------|------|---------|
| 13899 | Fail | | Pass | Pass |
| | (3) | | (4) | |
|----------|------|---------|------|---------|
| 13835 | Fail | | Pass | Pass |
| | (3) | | (4) | |
|----------|------|---------|------|---------|
| 13762 | Fail | | Pass | Pass |
| | (3) | | (2) | |
--------------------------------------------
Failures:
1. HVM 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. FIXED: 32bit non-pae uniprocessor kernel guest hangs on boot
xm list shows no cpu time consumption
4. FIXED: After a guest has been up overnight, launching a 2nd
guest results in "Error: an integer is required". Destroying
the guest that had been running overnight allows the new
guest to launch fine.
File: failure.1
[root@tst079 ~]# xm info
host : tst079
release : 2.6.18-xen
version : #1 SMP Sat Mar 3 05:44:15 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 : Fri Mar 02 12:11:52 2007 +0000 14201:3ac19fda0bc2
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 : Sat Mar 3 04:59:09 EST 2007
xend_config_format : 3
[root@tst079 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 723 2 r----- 4906.6
vs161 1 264 2 -b---- 13167.6
[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 PASS : gettimeofday monotonous in 30 seconds
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1173475262.239005 vs
new 1173475262.238916!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1173475264.271175 vs
new 1173475264.271096!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1173475266.303211 vs
new 1173475266.303157!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
[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 FAIL : Child execution not suspended for 2 seconds.
(Wanted 2000 ms, got 2407 ms)
nanosleep01 1 FAIL : Failures reported above
nanosleep01 1 PASS : nanosleep functionality is correct
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 PASS : Functionality of nanosleep() is correct
nanosleep02 1 FAIL : Remaining sleep time 0 msec doesn't match with the
expected 4294966484 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 Sat Mar 3 05:44:15 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 : Fri Mar 02 12:11:52 2007 +0000 14201:3ac19fda0bc2
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 : Sat Mar 3 04:59:09 EST 2007
xend_config_format : 3
[root@tst078 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1735 2 r----- 4149.6
vs170 1 264 2 -b---- 11756.5
[root@tst078 ~]# xm create /boot/vs160_vnc.hvm
Using config file "/boot/vs160_vnc.hvm".
Error: (12, 'Cannot allocate memory')
[root@tst078 ~]# cat /proc/meminfo
MemTotal: 1502208 kB
MemFree: 14088 kB
Buffers: 1311436 kB
Cached: 17956 kB
SwapCached: 0 kB
Active: 451224 kB
Inactive: 910384 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 1502208 kB
LowFree: 14088 kB
SwapTotal: 6450056 kB
SwapFree: 6449784 kB
Dirty: 688 kB
Writeback: 32 kB
AnonPages: 32312 kB
Mapped: 9656 kB
Slab: 61868 kB
PageTables: 2552 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 7201160 kB
Committed_AS: 135876 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 85616 kB
VmallocChunk: 34359651751 kB
[root@tst078 ~]# cat /proc/xen/balloon
Current allocation: 1502208 kB
Requested target: 1502208 kB
Low-mem balloon: 423640 kB
High-mem balloon: 0 kB
Driver pages: 1024 kB
Xen hard limit: ??? kB
[root@tst078 ~]# xm create /boot/vs160_vnc.hvm
Using config file "/boot/vs160_vnc.hvm".
Error: (12, 'Cannot allocate memory')
[root@tst078 ~]#
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|