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 13835
Date: Fri, 09 Feb 2007 12:48:12 -0500 [thread overview]
Message-ID: <45CCB3DC.4060003@virtualiron.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4046 bytes --]
Summary:
Changeset 13835
- gettimeofday02 nanosleep01/02 ltp tests fail (failure.1)
- 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 |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13835 | Fail | | Pass | 851/1 | Pass | | Pass | 851/1 |
| | (3) | | | (1) | | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13762 | Fail | | Pass | 851/1 | Pass | | Pass | 851/1 |
| | (3) | | | (1) | | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13650 | Fail | | Pass | 851/1 | Pass | | Pass | 851/1 |
| | (3) | | | (1) | | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13553 | Fail | | Pass | 851/1 | Pass | | Pass | 852/0 |
| | (3) | | | (1) | | | | |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13377 | 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 |
|----------|------|---------|------|---------|
| 13835 | Fail | | Pass | Pass |
| | (3) | | | |
|----------|------|---------|------|---------|
| 13762 | Fail | | Pass | Pass |
| | (3) | | (2) | |
|----------|------|---------|------|---------|
| 13650 | Fail | | Pass | Pass |
| | (3) | | (2) | |
|----------|------|---------|------|---------|
| 13553 | Fail | | Pass | Pass |
| | (3) | | (2) | |
|----------|------|---------|------|---------|
| 13377 | Fail | | Pass | Pass |
| | (3) | | (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
[-- Attachment #2: failure.1 --]
[-- Type: text/plain, Size: 7749 bytes --]
File: failure.1
[root@tst079 ~]# xm info
host : tst079
release : 2.6.18-xen
version : #1 SMP Fri Feb 9 01:50:17 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 : Thu Feb 08 16:52:05 2007 +0000 13835:d609929f1408
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 Feb 9 01:06:26 EST 2007
xend_config_format : 3
[root@tst079 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 723 2 r----- 4388.6
vs161 1 264 2 -b---- 13381.9
[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 1171041541.200658 vs new 1171041541.200642!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1171041546.981654 vs new 1171041546.981606!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1171041549.13913 vs new 1171041549.13828!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1171041551.46904 vs new 1171041551.46869!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1171041553.79354 vs new 1171041553.79320!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1171041555.111918 vs new 1171041555.111821!
gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
gettimeofday02 1 FAIL : Time is going backwards (old 1171041557.142100 vs new 1171041557.141994!
[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 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 2256 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 PASS : Functionality of nanosleep() is correct
nanosleep02 1 FAIL : Remaining sleep time 4660 msec doesn't match with the expected 4071 msec time
nanosleep02 1 FAIL : child process exited abnormally
nanosleep02 1 PASS : Functionality of nanosleep() is correct
nanosleep02 1 FAIL : Remaining sleep time 4685 msec doesn't match with the expected 4261 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
[-- Attachment #3: failure.2 --]
[-- Type: text/plain, Size: 2492 bytes --]
File: failure.2
[root@tst078 ~]# xm info
host : tst078
release : 2.6.18-xen
version : #1 SMP Thu Feb 1 01:50:14 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 : Wed Jan 31 19:37:44 2007 +0000 13762:588dd80b56b5
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 : Thu Feb 1 01:06:08 EST 2007
xend_config_format : 3
[root@tst078 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1735 2 r----- 3353.2
vs170 1 264 2 -b---- 12344.8
[root@tst078 ~]# cat /proc/meminfo
MemTotal: 1776640 kB
MemFree: 14244 kB
Buffers: 1575780 kB
Cached: 18008 kB
SwapCached: 0 kB
Active: 589632 kB
Inactive: 1036096 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 1776640 kB
LowFree: 14244 kB
SwapTotal: 6450056 kB
SwapFree: 6449768 kB
Dirty: 1108 kB
Writeback: 0 kB
AnonPages: 32032 kB
Mapped: 9648 kB
Slab: 72040 kB
PageTables: 2516 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 7338376 kB
Committed_AS: 135716 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 ~]#
[-- Attachment #4: failure.3 --]
[-- Type: text/plain, Size: 2203 bytes --]
File: failure.3
[root@tst078 ~]# xm info
host : tst078
release : 2.6.18-xen
version : #1 SMP Fri Feb 9 01:50:17 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 : 270
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 : Thu Feb 08 16:52:05 2007 +0000 13835:d609929f1408
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 Feb 9 01:06:26 EST 2007
xend_config_format : 3
[root@tst078 ~]# xm create /boot/vs160_vnc_nopae.hvm
** GUEST HANGS **
[root@tst078 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1467 2 r----- 3478.5
vs160 13 264 1 -b---- 9.8
[root@tst078 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1467 2 r----- 3478.8
vs160 13 264 1 -b---- 9.8
[root@tst078 ~]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1467 2 r----- 3479.0
vs160 13 264 1 -b---- 9.8
[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
[-- 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:[~2007-02-09 17:48 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=45CCB3DC.4060003@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.