Created attachment 468539 [details] v7 virtualization job Description of problem: fv_tests fail in virtualization job, except fv_network: "Error: memory run on guest Failed" run "virsh console v7x86_64", error in guest as follow: <output> Running ./memory.py: <output name="Limits" description="Get test parameters based on hardware"> System Memory: 498 MB Free Memory: 397 MB Swap Memory: 0 MB <summary>PASS</summary> </output> <output name="Single-process" description="None"> Starting Threaded Memory Test Error: this test requires non-zero swap memory. <summary>FAIL</summary> </output> ...finished running ./memory.py, exit code=1 </output> run "/usr/libexec/qemu-kvm -hda /var/lib/libvirt/images/v7x86_64.img -nographic" to start the guest. [root@dhcp-65-79 ~]# free total used free shared buffers cached Mem: 122948 112140 10808 0 5252 33824 -/+ buffers/cache: 73064 49884 Swap: 0 0 0 [root@dhcp-65-79 ~]# cat /etc/fstab /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 [root@dhcp-65-79 ~]# swapon /dev/VolGroup00/LogVol01 Unable to find swap-space signature swapon: /dev/VolGroup00/LogVol01: Invalid argument At this point, run command: [root@dhcp-65-79 ~]# mkswap /dev/VolGroup00/LogVol01 Setting up swapspace version 1, size = 1073737 kB [root@dhcp-65-79 ~]# swapon /dev/VolGroup00/LogVol01 and then rerun all fv_tests, and all pass. Version-Release number of selected component (if applicable): RHEL5.6, RHEL6.0 How reproducible: 100% Steps to Reproduce: 1. submit a v7 virtualization job 2. 3. Actual results: all FAIL except fv_network Expected results: all PASS Additional info: The swap failure won't happen if provisioning RHEL5.6 or RHEL6 manually.
Created attachment 468540 [details] fv_memory testing log in v7 virtualization job
Created attachment 468541 [details] virsh console log of fv_memory testing
Created attachment 468542 [details] log of starting v7x86_64.img manually
A related bug on ia64: https://bugzilla.redhat.com/show_bug.cgi?id=649673
Is this something unique to and/or caused by beaker? ..as of yet I'm not seeing the outcry from the vendors who use this everyday.
*** This bug has been marked as a duplicate of bug 663901 ***