Summary:
Changeset 13205
- FIXED: RHEL4U2-64bit uniprocessor kernel guest panics on boot:
Kernel panic from APIC_init_uniprocessor+133 (failure.4)
- 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 |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13205 | Pass | | Pass | 851/1 | Pass | | Pass | 851/1 |
| | | | | (1) | | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13078 | Pass | | Pass | 852/0 | Fail | | Pass | 851/1 |
| | | | | (1) | (4) | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 12895 | Pass | | Pass | 851/1 | Fail | | Pass | 852/0 |
| | | | | (1) | (4) | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 12756 | Pass | | Pass | 851/1 | Fail | | Pass | 851/1 |
| | | | | (1) | (4) | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 12731 | Pass | | Pass | 850/2 | Fail | | Pass | 852/0 |
| | | | | (1) | (4) | | | (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 |
|----------|------|---------|------|---------|
| 13205 | Pass | Pass | Pass | Pass |
| | (2) | | (2) | |
|----------|------|---------|------|---------|
| 13078 | Fail | | Pass | Pass |
| | (4) | | (2) | |
|----------|------|---------|------|---------|
| 12895 | Fail | | Pass | Pass |
| | (4) | | (2) | |
|----------|------|---------|------|---------|
| 12756 | Fail | | Pass | Pass |
| | (4) | | (2) | |
|----------|------|---------|------|---------|
| 12731 | Fail | | Pass | Pass |
| | (4) | | (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')
4. FIXED: 64bit uni-processor guest doesn't boot:
Kernel panic from APIC_init_uniprocessor+133
Call Trace:<ffffffff80541e28>{APIC_init_uniprocessor+133}
<ffffffff8010c35f>{init+214}
<ffffffff8010c289>{init+0}
<ffffffff8011138b>{child_rip+8}
<ffffffff8010c289>{init+0}
<ffffffff80111383>{child_rip+0}
Code: 0f 0b 77 9f 36 80 ff ff ff ff 31 01 48 8b 05 fa 24 ee ff ff
RIP <ffffffff805418e3>{setup_local_APIC+27} RSP <00000100014b1ef8>
<0>Kernel panic - not syncing: Oops
File: failure.1
[root@tst079 ~]# xm info
host : tst079
release : 2.6.16.33-xen
version : #1 SMP Wed Jan 3 01:49:59 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 hvm-3.0-x86_32 hvm-3.0-x86_32p
hvm-3.0-x86_64
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Tue Jan 02 14:19:47 2007 +0000 13205:886f7312257e
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 : Wed Jan 3 01:10:52 EST 2007
xend_config_format : 3
[root@tst079 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 725 2 r----- 4486.2
vs161 1 264 2 r----- 14059.5
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 1167858562.738284 vs
new 1167858562.738283!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1167858564.772759 vs
new 1167858564.772674!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1167858566.804445 vs
new 1167858566.804368!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1167858568.838943 vs
new 1167858568.838904!
[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 FAIL : Child execution not suspended for 2 seconds.
(Wanted 2000 ms, got 2566 ms)
nanosleep01 1 FAIL : Failures reported above
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
[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 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 PASS : Functionality of nanosleep() is correct
nanosleep02 1 PASS : Functionality of nanosleep() is correct
nanosleep02 1 FAIL : Remaining sleep time 3998 msec doesn't match with
the expected 3741 msec time
nanosleep02 1 FAIL : child process exited abnormally
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 3999 msec doesn't match with
the expected 3746 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.16.33-xen
version : #1 SMP Wed Jan 3 01:49:59 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 hvm-3.0-x86_32 hvm-3.0-x86_32p
hvm-3.0-x86_64
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Tue Jan 02 14:19:47 2007 +0000 13205:886f7312257e
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 : Wed Jan 3 01:10:52 EST 2007
xend_config_format : 3
[root@tst078 ~]# cat /proc/meminfo
MemTotal: 1778688 kB
MemFree: 12800 kB
Buffers: 1596312 kB
Cached: 16728 kB
SwapCached: 0 kB
Active: 597904 kB
Inactive: 1045868 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 1778688 kB
LowFree: 12800 kB
SwapTotal: 6450056 kB
SwapFree: 6449768 kB
Dirty: 4 kB
Writeback: 0 kB
Mapped: 40136 kB
Slab: 60704 kB
CommitLimit: 7339400 kB
Committed_AS: 125748 kB
PageTables: 2556 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 85604 kB
VmallocChunk: 34359651751 kB
[root@tst078 ~]# cat /proc/xen/balloon
Current allocation: 1778688 kB
Requested target: 1778688 kB
Low-mem balloon: 149088 kB
High-mem balloon: 0 kB
Driver pages: 1024 kB
Xen hard limit: ??? kB
[root@tst078 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1737 2 r----- 4047.1
vs170 1 264 2 -b---- 12896.4
[root@tst078 ~]# xm create /boot/vs160_sdl.hvm
Using config file "/boot/vs160_sdl.hvm".
Error: (12, 'Cannot allocate memory')
[root@tst078 ~]#
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|