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 13762
Date: Thu, 01 Feb 2007 10:28:53 -0500 [thread overview]
Message-ID: <45C20735.6030305@virtualiron.com> (raw)
Summary:
Changeset 13762
- 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)
- 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 |
|----------|------|-------|------|-------|------|-------|------|-------|
| 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) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 13330 | 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 |
|----------|------|---------|------|---------|
| 13762 | Fail | | Pass | Pass |
| | (3) | | (2) | |
|----------|------|---------|------|---------|
| 13650 | Fail | | Pass | Pass |
| | (3) | | (2) | |
|----------|------|---------|------|---------|
| 13553 | Fail | | Pass | Pass |
| | (3) | | (2) | |
|----------|------|---------|------|---------|
| 13377 | Fail | | Pass | Pass |
| | (3) | | (2) | |
|----------|------|---------|------|---------|
| 13330 | 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
reply other threads:[~2007-02-01 15:28 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=45C20735.6030305@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.