All of lore.kernel.org
 help / color / mirror / Atom feed
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 14043
Date: Thu, 22 Feb 2007 17:25:02 -0500	[thread overview]
Message-ID: <45DE183E.4030109@virtualiron.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4437 bytes --]

Summary:
Changeset 14043
- 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)
- FIXED: 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  |
|----------|------|-------|------|-------|------|-------|------|-------|
| 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)   |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13650    | 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    |
|----------|------|---------|------|---------|
| 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)  |         |
|----------|------|---------|------|---------|
| 13650    | 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. 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.

[-- Attachment #2: failure.1 --]
[-- Type: text/plain, Size: 3468 bytes --]

File: failure.1
[root@tst079 ~]# xm info
host                   : tst079
release                : 2.6.18-xen
version                : #1 SMP Thu Feb 22 05:51:04 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          : Wed Feb 21 20:30:37 2007 +0000 14043:eb190b1faa52
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 22 05:06:32 EST 2007
xend_config_format     : 3
[root@tst079 ~]# xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0   723     2     r-----   3367.9
vs161                                      1   264     2     -b----  11989.2
[root@tst079 ~]#                                                                            

Guest:
[root@vs161 ~]# cd /qa/conductor/tests/ltp/testcases/bin/
[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 1172181546.462811 vs new 1172181546.462757!
gettimeofday02    0  INFO  :  checking if gettimeofday is monotonous, takes 30s
gettimeofday02    1  FAIL  :  Time is going backwards (old 1172181548.520513 vs new 1172181548.520458!
gettimeofday02    0  INFO  :  checking if gettimeofday is monotonous, takes 30s
gettimeofday02    1  FAIL  :  Time is going backwards (old 1172181550.551863 vs new 1172181550.551808!

[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  FAIL  :  Child execution not suspended for 2 seconds.  (Wanted 2000 ms, got 2305 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  :  Child execution not suspended for 5 seconds
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

[-- Attachment #3: failure.2 --]
[-- Type: text/plain, Size: 2667 bytes --]

File: failure.2

[root@tst078 ~]# xm info
host                   : tst078
release                : 2.6.18-xen
version                : #1 SMP Thu Feb 22 05:51:04 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 Feb 21 20:30:37 2007 +0000 14043:eb190b1faa52
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 22 05:06:32 EST 2007
xend_config_format     : 3
[root@tst078 ~]# xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0  1735     2     r-----   4109.9
vs170                                      1   264     2     -b----  12997.3
[root@tst078 ~]# cat /proc/meminfo
MemTotal:      1776640 kB
MemFree:         13428 kB
Buffers:       1588092 kB
Cached:          16344 kB
SwapCached:          0 kB
Active:         588124 kB
Inactive:      1048992 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      1776640 kB
LowFree:         13428 kB
SwapTotal:     6450056 kB
SwapFree:      6449784 kB
Dirty:             988 kB
Writeback:           0 kB
AnonPages:       32604 kB
Mapped:           9788 kB
Slab:            61472 kB
PageTables:       2664 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   7338376 kB
Committed_AS:   136856 kB
VmallocTotal: 34359738367 kB
VmallocUsed:     85616 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_vnc.hvm
Using config file "/boot/vs160_vnc.hvm".
Error: (12, 'Cannot allocate memory')
[root@tst078 ~]# xm destroy vs170
[root@tst078 ~]# xm create /boot/vs160_vnc.hvm
Using config file "/boot/vs160_vnc.hvm".
Started domain vs160
[root@tst078 ~]#                                                         

[-- Attachment #4: 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-22 22:25 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=45DE183E.4030109@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.