WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-devel] Testing status of HVM (Intel VT) on 64bit XEN unstable c/s 1

from [Ed Smith] [Permanent Link][Original]
To: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XEN unstable c/s 12673
From: Ed Smith <esmith@xxxxxxxxxxxxxxx>
Date: Mon, 04 Dec 2006 16:17:03 -0500
Delivery-date: Mon, 04 Dec 2006 13:17:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.2 (X11/20060420) 
Summary:
Changeset 12673
- gettimeofday02 ltp clock test failed again today.
  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  |
|----------|------|-------|------|-------|------|-------|------|-------|
| 12673    | Pass |       | Pass | 852/0 | Fail |       | Pass | 851/1 |
|          |      |       |      | (1)   | (4)  |       |      | (1)   |
|----------|------|-------|------|-------|------|-------|------|-------|
| 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)   |
 ----------------------------------------------------------------------

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    |
|----------|------|---------|------|---------|
| 12673    | Fail |         | Pass | Pass    |
|          | (4)  |         | (2)  |         |
|----------|------|---------|------|---------|
| 12663    | Fail |         | Pass | Pass    |
|          | (4)  |         | (2)  |         |
|----------|------|---------|------|---------|
| 12621    | Fail |         | Pass | Pass    |
|          | (4)  |         | (2)  |         |
|----------|------|---------|------|---------|
| 12603    | Fail |         | Fail |         |
|          | (3)  |         | (3)  |         |
|----------|------|---------|------|---------|
| 12502    | Pass | Pass    | Pass | Pass    |
|          | (2)  |         | (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. 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


File: failure.1

[root@tst078 ~]# xm info
host                   : tst078
release                : 2.6.16.33-xen
version                : #1 SMP Sat Dec 2 05:41:15 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            : 2
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          : Fri Dec 01 11:54:53 2006 +0000 12673:bec95280b565
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 Dec  2 05:02:12 EST 2006
xend_config_format     : 3


Guest:

[root@vs170 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 1165264991.546494 vs 
new 1165264991.546123!
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 1165265036.755950 vs 
new 1165265036.755911!
gettimeofday02    0  INFO  :  checking if gettimeofday is monotonous, takes 30s
gettimeofday02    1  FAIL  :  Time is going backwards (old 1165265038.985504 vs 
new 1165265038.980139!

[root@vs170 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  FAIL  :  Child execution not suspended for 2 seconds.  
(Wanted 2000 ms, got 2316 ms)
nanosleep01    1  FAIL  :  Failures reported above
nanosleep01    1  PASS  :  nanosleep functionality is correct

[root@vs170 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  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 3786 msec doesn't match with 
the expected 3795 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  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
nanosleep02    1  PASS  :  Functionality of nanosleep() is correct
nanosleep02    1  FAIL  :  Remaining sleep time 4662 msec doesn't match with 
the expected 3729 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 4111 msec doesn't match with 
the expected 3833 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 Sat Dec 2 05:41:15 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          : Fri Dec 01 11:54:53 2006 +0000 12673:bec95280b565
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 Dec  2 05:02:12 EST 2006
xend_config_format     : 3
[root@tst078 ~]# xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0  1737     2     r-----   4681.0
vs170                                      1   264     2     ------  14062.2
[root@tst078 ~]# cat /proc/meminfo
MemTotal:      1778688 kB
MemFree:         10764 kB
Buffers:       1600764 kB
Cached:          16436 kB
SwapCached:          0 kB
Active:         596300 kB
Inactive:      1048104 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      1778688 kB
LowFree:         10764 kB
SwapTotal:     6450056 kB
SwapFree:      6449768 kB
Dirty:             420 kB
Writeback:           0 kB
Mapped:          36884 kB
Slab:            61652 kB
CommitLimit:   7339400 kB
Committed_AS:   122432 kB
PageTables:       2532 kB
VmallocTotal: 34359738367 kB
VmallocUsed:     85708 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 ~]#                                    

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 Sat Dec 2 05:41:15 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            : 2
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          : Fri Dec 01 11:54:53 2006 +0000 12673:bec95280b565
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 Dec  2 05:02:12 EST 2006
xend_config_format     : 3

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Testing status of HVM (Intel VT) on 64bit XEN unstable c/s 12673, Ed Smith <=
Previous by Date:  Re: [Xen-devel] [PATCH] PV framebuffer, Ewan Mellor
Next by Date:  [Xen-devel] [PATCH] Safely finish closing protocol when guest fails in blkfront, Glauber de Oliveira Costa
Previous by Thread:  [Xen-devel] XENBUS: Timeout connecting to device errors, Graham, Simon
Next by Thread:  [Xen-devel] [PATCH] Safely finish closing protocol when guest fails in blkfront, Glauber de Oliveira Costa
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy