Biweekly upstream qemu-kvm test report (using autotest + manual) - Week 28
Folks, Please find the result of upstream testing. This time we got a kernel panic error while compiling mainline kernel (3.5.rc7). Hence we could verify only mainline qemu-kvm. We are analysing the failures and we will raise the bugs with the appropriate community. Host Kernel: Kernel: 3.1.0-7.fc16.x86_64 KVM Version: 1.1.50 (qemu-kvm-devel) Date: Thu Jul 19 17:51:29 2012 Stat: 59 tests executed - 40 have passed 19 Failed Number of Bugs raised: 2 https://bugzilla.kernel.org/show_bug.cgi?id=44901 https://github.com/autotest/autotest/issues/467 Tests Failed: .. Test Name ResultRun time .. kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.ffsb FAIL 29 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.disktest FAIL 24 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.hackbench FAIL 22 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.cpu_hotplug FAIL 57 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.block_stream FAIL 159 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.linux_s3 FAIL 303 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.boot_guest.qemu_boot_cpu_model FAIL 2280 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.boot_guest.qemu_boot_cpu_model_and_flags FAIL 2483 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_boot_guest_and_try_flags_under_load FAIL 2859 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_online_offline_guest_CPUs FAIL 2619 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_migration_with_additional_flags FAIL 2665 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_throttle FAIL2 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_throttle_multi FAIL 344 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.cpu_share FAIL1 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.cpuset_cpus FAIL1 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.freezer FAIL2 - Tests Passed: ... Test Name ResultRun time ... kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.dbench PASS 131 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.ebizzy PASS 22 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.stress PASS 88 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.sleeptest PASS 55 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.iozone PASS 540 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.jumbo PASS 537 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_bandwidth PASS 28 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.cpuset_cpus_switching PASS 95 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.devices_access PASS 15 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.memory_limit PASS
Re: [Autotest] Biweekly upstream qemu-kvm test report (using autotest + manual) - Week 28
Hi seems there is no virtio_console testing.which I have no one pass and why some of the below cases is mannual, and they are not in the defalut tests.cfg Lei On Fri, Jul 20, 2012 at 8:20 PM, Prem Karat prem.ka...@linux.vnet.ibm.com wrote: Folks, Please find the result of upstream testing. This time we got a kernel panic error while compiling mainline kernel (3.5.rc7). Hence we could verify only mainline qemu-kvm. We are analysing the failures and we will raise the bugs with the appropriate community. Host Kernel: Kernel: 3.1.0-7.fc16.x86_64 KVM Version: 1.1.50 (qemu-kvm-devel) Date: Thu Jul 19 17:51:29 2012 Stat: 59 tests executed - 40 have passed 19 Failed Number of Bugs raised: 2 https://bugzilla.kernel.org/show_bug.cgi?id=44901 https://github.com/autotest/autotest/issues/467 Tests Failed: .. Test Name ResultRun time .. kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.ffsb FAIL 29 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.disktest FAIL 24 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.hackbench FAIL 22 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.cpu_hotplug FAIL 57 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.block_stream FAIL 159 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.linux_s3 FAIL 303 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.boot_guest.qemu_boot_cpu_model FAIL 2280 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.boot_guest.qemu_boot_cpu_model_and_flags FAIL 2483 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_boot_guest_and_try_flags_under_load FAIL 2859 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_online_offline_guest_CPUs FAIL 2619 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_migration_with_additional_flags FAIL 2665 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_throttle FAIL2 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_throttle_multi FAIL 344 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.cpu_share FAIL1 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.cpuset_cpus FAIL1 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.freezer FAIL2 - Tests Passed: ... Test Name ResultRun time ... kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.dbench PASS 131 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.ebizzy PASS 22 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.stress PASS 88 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.sleeptest PASS 55 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.iozone PASS 540 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.jumbo PASS 537 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_bandwidth PASS 28
Re: [Autotest] Biweekly upstream qemu-kvm test report (using autotest + manual) - Week 28
* On 2012-07-20 22:52:21 +0800, lei yang (yanglei.f...@gmail.com) wrote: Hi seems there is no virtio_console testing.which I have no one pass and why some of the below cases is mannual, and they are not in the Because we have no guest agent test case in autotest now. though I'm working on it. lol defalut tests.cfg Lei On Fri, Jul 20, 2012 at 8:20 PM, Prem Karat prem.ka...@linux.vnet.ibm.com wrote: Folks, Please find the result of upstream testing. This time we got a kernel panic error while compiling mainline kernel (3.5.rc7). Hence we could verify only mainline qemu-kvm. We are analysing the failures and we will raise the bugs with the appropriate community. Host Kernel: Kernel: 3.1.0-7.fc16.x86_64 KVM Version: 1.1.50 (qemu-kvm-devel) Date: Thu Jul 19 17:51:29 2012 Stat: 59 tests executed - 40 have passed 19 Failed Number of Bugs raised: 2 https://bugzilla.kernel.org/show_bug.cgi?id=44901 https://github.com/autotest/autotest/issues/467 Tests Failed: .. Test Name ResultRun time .. kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.ffsb FAIL 29 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.disktest FAIL 24 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.hackbench FAIL 22 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.cpu_hotplug FAIL 57 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.block_stream FAIL 159 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.linux_s3 FAIL 303 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.boot_guest.qemu_boot_cpu_model FAIL 2280 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.boot_guest.qemu_boot_cpu_model_and_flags FAIL 2483 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_boot_guest_and_try_flags_under_load FAIL 2859 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_online_offline_guest_CPUs FAIL 2619 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_migration_with_additional_flags FAIL 2665 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_throttle FAIL2 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_throttle_multi FAIL 344 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.cpu_share FAIL1 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.cpuset_cpus FAIL1 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.freezer FAIL2 - Tests Passed: ... Test Name ResultRun time ... kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.dbench PASS 131 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.ebizzy PASS 22 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.stress PASS 88 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.sleeptest PASS 55 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.iozone PASS 540 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.jumbo
Re: [Autotest] Biweekly upstream qemu-kvm test report (using autotest + manual) - Week 28
On Fri, Jul 20, 2012 at 11:18 PM, Qingtang Zhou qz...@redhat.com wrote: * On 2012-07-20 22:52:21 +0800, lei yang (yanglei.f...@gmail.com) wrote: Hi seems there is no virtio_console testing.which I have no one pass and why some of the below cases is mannual, and they are not in the Because we have no guest agent test case in autotest now. though I'm working on it. lol The guest agent testcase you metioned, is it the manual cases in this thead? It seems we it select some cases not all the case to do the Biweekly upstream test, is there some stratigies to select which cases to run defalut tests.cfg Lei On Fri, Jul 20, 2012 at 8:20 PM, Prem Karat prem.ka...@linux.vnet.ibm.com wrote: Folks, Please find the result of upstream testing. This time we got a kernel panic error while compiling mainline kernel (3.5.rc7). Hence we could verify only mainline qemu-kvm. We are analysing the failures and we will raise the bugs with the appropriate community. Host Kernel: Kernel: 3.1.0-7.fc16.x86_64 KVM Version: 1.1.50 (qemu-kvm-devel) Date: Thu Jul 19 17:51:29 2012 Stat: 59 tests executed - 40 have passed 19 Failed Number of Bugs raised: 2 https://bugzilla.kernel.org/show_bug.cgi?id=44901 https://github.com/autotest/autotest/issues/467 Tests Failed: .. Test Name ResultRun time .. kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.ffsb FAIL 29 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.disktest FAIL 24 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.hackbench FAIL 22 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.cpu_hotplug FAIL 57 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.block_stream FAIL 159 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.linux_s3 FAIL 303 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.boot_guest.qemu_boot_cpu_model FAIL 2280 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.boot_guest.qemu_boot_cpu_model_and_flags FAIL 2483 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_boot_guest_and_try_flags_under_load FAIL 2859 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_online_offline_guest_CPUs FAIL 2619 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_migration_with_additional_flags FAIL 2665 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_throttle FAIL2 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_throttle_multi FAIL 344 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.cpu_share FAIL1 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.cpuset_cpus FAIL1 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.cgroup.freezer FAIL2 - Tests Passed: ... Test Name ResultRun time ... kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.dbench PASS 131 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.ebizzy PASS 22 kvm.qed.virtio_blk.smp2.virtio_net.RHEL.6.2.x86_64.autotest.stress PASS 88