Bug 591749
| Summary: | v7-1.1-23 fails to setup virtual machine tests and fails to test virtual machines using Xeon RHEL 5.4 or 5.5 kernels | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Bob Sanders <rsanders> | ||||||
| Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 1.1 | CC: | Rainer.Koenig, rlandry, ykun | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-11-18 20:20:31 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Please attach the results of "v7 clean" followed by "v7 plan". It would be helpful to know if v7 detects that the system is capable of virtualization. Also, attach the results "cat /proc/cpuinfo | fgrep flags". Thanks! Created attachment 413814 [details]
Sgi Origin 400 eunning RHEL 5.4 Xen
Created attachment 413817 [details]
SGI XE210 running RHEL 5.5 Xen
Hi Greg, I stumbled over the same issue on my system, testing both X3450 and X3470 CPUs. I managed to perform a successful fv_* test with v7-1.0-18 as you can see here: https://hardware.redhat.com/attachment.cgi?id=413097&action=view The problem seems to be that evey virtualization site says there should be a "vmx" flag in the output of /proc/cpuinfo, but with those processors there is no such flag. From the INFO protocol: (8) Intel(R) Xeon(R) CPU X3470 @ 2.93GHz Arch: i386 L2 Cache: 8192 KB Vendor: GenuineIntel Stepping: 5 Family: 6 CPU Flags: fpu tsc msr pae cx8 apic mtrr cmov pat clflush acpi mmx fxsr sse sse2 ss ht nx constant_tsc ida nonstop_tsc pni est ssse3 sse4_1 sse4_2 popcnt [8] Ok, according to this http://www.gossamer-threads.com/lists/xen/users/168172 it is a normal behaviour of the Xen kernel not to show the vmx flag. # cat /sys/hypervisor/properties/capabilities 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 So the question is why v7 1.1-23 is not scheduling and running the tests. Meanwhile I'm back to 1.0-18 for continuing with my tests. This issue should be addressed as of v7-1.1-24 with the fix included in the v7-1.2 stream. https://rhn.redhat.com/errata/RHBA-2010-0463.html I'm going to go ahead and close this bug as fixed/current release. Please re-open or open a new bug if needed. |
Description of problem: fv_* fail to register, and under manual add, fail to execute Version-Release number of selected component (if applicable): v7-1.1-23.el5.noarch.rpm How reproducible: Each time v7 plan is run or v7 plan --add --test=fv_network Steps to Reproduce: 1. Install v7-1.1-23.el5.noarch.rpm on any RHEL x86_64 system running RHEL 5.4 or 5.5 Xen kernel. 2. execute v7 plan or v7 plan --add --test=fv_network (or fv_core, fv_memory,etc.) 3. v7 certify Actual results: Running ./fv_network.py: Using test server 10.1.1.2 Warning: Guest v7x86_64 is already running Attempting shutdown: Domain v7x86_64 destroyed Verified that guest v7x86_64 is not running Traceback (most recent call last): File "./fv_network.py", line 43, in ? returnValue = test.do(sys.argv) File "/usr/share/v7/lib/v7/test.py", line 255, in do return self.run() File "./fv_network.py", line 39, in run return FvTest.run(self) File "/usr/share/v7/lib/v7/fvtest.py", line 435, in run if not self.verifyGuest(): File "/usr/share/v7/lib/v7/fvtest.py", line 142, in verifyGuest return self.verifyGuestFiles() File "/usr/share/v7/lib/v7/fvtest.py", line 146, in verifyGuestFiles if not self.verifyFile(self.guestImageDirectory, self.dataImageFile): AttributeError: FvNetworkTest instance has no attribute 'guestImageDirectory' ...finished running ./fv_network.py, exit code=1 </output> recovered exit code=1 v7-report-result /V7/v7/fv_network FAIL /var/log/v7/runs/2/fv_network/output.log Expected results: Additional info: