[Fedora-xen] Testing report for xen against RHEL5 Beta2 M5

Zhao, Yunfeng yunfeng.zhao at intel.com
Mon Oct 23 14:37:11 UTC 2006


Hi.
We have finished a full test for xen IA32p/IA32e/IA64 against RHEL5
Beta2 M5.
The full test includes guest installation test,smp Linux/Windows guest
test,device model test,control panel test, hvm guest stress test and
manual testing for Virtual Machine Manager.
In the testing we found 20 issues totally. (10 are RHEL5 specific
issues,and 10 are common issues.)

Following are the issues:
 
RHEL5 specific issues:
1. 'Could not initialize SDL - exiting' error
The error happens when I try to create vmx guest on RHEL5.
A workround for this issue is: execute "xend stop" and "xend start"
before creating vmx guests.
https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&t
id=104369

2. 'Failed vm entry' error when install RHEL5 IA32e into VMX
The guest crashed for vm entry failure.
(XEN) Failed vm entry (exit reason 0x80000021) caused by invalid guest
state (0).
https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&t
id=104283

3. Cannot boot RHEL5 Beta2 M5 SMP VMX guest
The guest always stops booting after printing "input: ImExPS/2 Logitech
Explorer Mouse as /class/input/input1".
https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&t
id=104292

4. Virtual Machine Manager cannot detect correct total memory size on
host machine
On my test box the total memory is 1GB, but the tool shows it is 2GB.
https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&t
id=104367

5. Fails to install fully virtualized guests from ISO with using Virutal
Machine Manager
Virutal Machine Manager is slow to bring up the qemu window, that cause
user hasn't chance to choose boot from CDROM.
https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&t
id=104368

6. The network speed between xen0 and hvm guest is slow.
https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&t
id=104855

7. Xen crashed after xen0 rebooted
https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&t
id=104856
8. On IA64 xen, xenu would crash Xen0 if insmod xennet.ko
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208062

9. On IA64 xen, xen0 could be rebooted. (This issue has been fixed in
latest Rawhide.)

10. On IA64 xen, xenU can not boot up with 256M
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207241

Common issues that also exist on xen unstable:
11. Failed to install Vista Beta2 IA32
12. Installing win2k with acpi=1 failed with blue screen error.
13. Can not input number from speail number keys (when Open Num Lock)
14. SMP Windows 2003 HVM guest is not stable. After running for a while
the guest hanged.
15. Full virtualization and Para virtualization networks cannot coexist
on HVM guest. PV network module cannot be loaded when FV network driver
running on HVM guest.
16. Xen0 ia32-pae may hang after running some heavy workload on hvm
guest for several hours.
We met xen0 ia32-pae hang several times in the full functional testing
and stress testing.
In the full functional testing, the test system was continuing creating
and destroying lots of hvm guests.
In the stress testing, two hvm guests were running some heavy stress
test suites synchronously.
17. On IA64 xen, LTP test causes SMP VTI to hang.
18. On IA64 xen, VTI guest can not boot 3 NICs at the same time.
19. On IA64 xen, "Shut down" in VTI win2k3 will cause VTI reboot
20. On IA64 xen, SMP (8 vcpus) VTI failed to pass 5 hours helltest.
(Helltest is an Intel internal stress test for linux )

When RHEL5 beta2 M6 server version is available, we will do a regression
test for xen.


Thanks
Yunfeng




More information about the Fedora-xen mailing list