From: Ed Smith <esmith@virtualiron.com>
To: Xen Devel <xen-devel@lists.xensource.com>
Subject: Testing status of HVM (Intel VT) on 64bit XEN unstable c/s 12663
Date: Fri, 01 Dec 2006 16:57:17 -0500 [thread overview]
Message-ID: <4570A53D.8000309@virtualiron.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4790 bytes --]
Summary:
Changeset 12663
- NEW: gettimeofday02 ltp clock test now passes. nanosleep01/02
tests still occasionally fail. (failure.1)
- RHEL4U2-64bit uniprocessor kernel guest panics on boot:
Kernel panic from APIC_init_uniprocessor+133 (failure.4)
- 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 |
|----------|------|-------|------|-------|------|-------|------|-------|
| 12663 | Pass | | Pass | 852/0 | Fail | | Pass | 852/0 |
| | | | | (1) | (4) | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 12621 | Pass | | Pass | 851/1 | Fail | | Pass | 851/1 |
| | | | | (1) | (4) | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 12603 | Fail | | Fail | | Fail | | Fail | |
| | (3) | | (3) | | (3) | | (3) | |
|----------|------|-------|------|-------|------|-------|------|-------|
| 12502 | Pass | | Pass | 851/1 | Pass | | Pass | 851/1 |
| | | | | (1) | | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 12472 | Pass | | Pass | 850/2 | 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 |
|----------|------|---------|------|---------|
| 12663 | Fail | | Pass | Pass |
| | (4) | | (2) | |
|----------|------|---------|------|---------|
| 12621 | Fail | | Pass | Pass |
| | (4) | | (2) | |
|----------|------|---------|------|---------|
| 12603 | Fail | | Fail | |
| | (3) | | (3) | |
|----------|------|---------|------|---------|
| 12502 | Pass | Pass | Pass | Pass |
| | (2) | | (2) | |
|----------|------|---------|------|---------|
| 12472 | Pass | Pass | Pass | Pass |
| | (2) | | (2) | |
--------------------------------------------
Failures:
1. BUG 666: 32bit guests fail 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 and 64bit HVM domains crash on boot
(XEN) a6, This opcode isn't handled yet!
4. 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
[-- Attachment #2: failure.1 --]
[-- Type: text/plain, Size: 3965 bytes --]
File: failure.1
[root@tst079 ~]# xm info
host : tst079
release : 2.6.16.33-xen
version : #1 SMP Fri Dec 1 05:40:50 EST 2006
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 : Thu Nov 30 20:16:54 2006 +0000 12663:952c2cddff0c
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 : Fri Dec 1 05:01:45 EST 2006
xend_config_format : 3
[root@tst079 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 725 2 r----- 6506.5
vs161 1 264 2 ------ 12417.7
[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 PASS : gettimeofday monotonous in 30 seconds
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 PASS : gettimeofday monotonous in 30 seconds
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 PASS : gettimeofday monotonous in 30 seconds
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
[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 FAIL : Child execution not suspended for 2 seconds. (Wanted 2000 ms, got 2265 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
[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 3999 msec doesn't match with the expected 3648 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
[-- Attachment #3: failure.2 --]
[-- Type: text/plain, Size: 2374 bytes --]
File: failure.2
[root@tst078 ~]# xm info
host : tst078
release : 2.6.16.33-xen
version : #1 SMP Fri Dec 1 05:40:50 EST 2006
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 : Thu Nov 30 20:16:54 2006 +0000 12663:952c2cddff0c
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 : Fri Dec 1 05:01:45 EST 2006
xend_config_format : 3
[root@tst078 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1737 2 r----- 5635.3
vs170 1 264 2 ------ 10081.7
[root@tst078 ~]# cat /proc/meminfo
MemTotal: 1778688 kB
MemFree: 11416 kB
Buffers: 1600168 kB
Cached: 16252 kB
SwapCached: 0 kB
Active: 594748 kB
Inactive: 1049820 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 1778688 kB
LowFree: 11416 kB
SwapTotal: 6450056 kB
SwapFree: 6449768 kB
Dirty: 400 kB
Writeback: 0 kB
Mapped: 37684 kB
Slab: 61184 kB
CommitLimit: 7339400 kB
Committed_AS: 123576 kB
PageTables: 2660 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 85700 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 create /boot/vs160_sdl.hvm
Using config file "/boot/vs160_sdl.hvm".
Error: (12, 'Cannot allocate memory')
[root@tst078 ~]#
[-- Attachment #4: failure.4 --]
[-- Type: text/plain, Size: 1557 bytes --]
File: failure.4
RHEL4U2-64bit Guest - uniprocessor kernel
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
XEN:
[root@tst078 ~]# xm info
host : tst078
release : 2.6.16.33-xen
version : #1 SMP Fri Dec 1 05:40:50 EST 2006
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 : Thu Nov 30 20:16:54 2006 +0000 12663:952c2cddff0c
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 : Fri Dec 1 05:01:45 EST 2006
xend_config_format : 3
[-- Attachment #5: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2006-12-01 21:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4570A53D.8000309@virtualiron.com \
--to=esmith@virtualiron.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.