Mailing List Archive

Testing status of HVM (Intel VT) on 64bit XEN unstable c/s 12731
Summary:
Changeset 12731
- 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 |
|----------|------|-------|------|-------|------|-------|------|-------|
| 12731 | Pass | | Pass | 850/2 | Fail | | Pass | 852/0 |
| | | | | (1) | (4) | | | (1) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 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) | |
----------------------------------------------------------------------

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

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