Re: Biweekly upstream qemu-kvm test report (using autotest) - Week 35

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Lucas,

We use both qed and raw image types.

Regards,
Santwana
On Thu, 2012-08-30 at 12:03 -0300, Lucas Meneghel Rodrigues wrote:
> On Thu, Aug 30, 2012 at 8:37 AM, santwana <santwana@xxxxxxxxxxxxxxxxxx> wrote:
> > Hi All,
> >
> > Please find the results of upstream testing.
> >
> > We are evaluating the failures and will be raising the issues with the
> > appropriate community.
> >
> > Environment:
> > Host Kernel: 3.5.0-rc6
> > KVM Version: 1.1.90
> > Date: Thu Aug 30 15:29:06 2012
> > Stats: 41 tests executed (26 tests passed, 15 tests failed)
> >
> > Tests Passed:
> >
> > ...........................................................................................................................
> >
> > TestName
> > ...........................................................................................................................
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.balloon_check
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.balloon_check.balloon-migrate
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.balloon_check.balloon-shutdown_enlarge
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.balloon_check.balloon-shutdown_evict
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.dd_test.readonly.disk2null
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.dd_test.readonly.zero2disk
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.dd_test.readwrite.disk2null
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.dd_test.readwrite.zero2disk
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.autotest.disktest
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.autotest.ebizzy
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.autotest.ffsb
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.autotest.hackbench
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.autotest.iozone
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.autotest.sleeptest
> 
> ^ You might remove sleeptest from the set of tests, as it's more of a
> sanity check of autotest
> 
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.autotest.stress
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.block_stream
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.boot
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_bandwidth
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cgroup.cpuset_cpus_switching
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cgroup.cpu_share
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cgroup.devices_access
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cgroup.freezer
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cgroup.memory_move
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.jumbo
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.shutdown
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.unattended_install.cdrom.extra_cdrom_ks
> > ...........................................................................................................................
> >
> > Tests Failed:
> >
> > ...........................................................................................................................
> >
> > TestName
> > ...........................................................................................................................
> >
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.cpuflags.boot_guest.qemu_boot_fail_cpu_model
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.cpuflags.boot_guest.qemu_warn_boot_check_cpu_model
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.cpuflags.interface.qemu_cpu_cpuid
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.cpuflags.interface.qemu_cpu_dump
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.64.cpuflags.interface.qemu_cpu_model
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_throttle
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cgroup.blkio_throttle_multi
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cgroup.cpuset_cpus
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cgroup.memory_limit
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cpuflags.boot_guest.qemu_boot_cpu_model
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cpuflags.boot_guest.qemu_boot_cpu_model_and_flags
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_boot_guest_and_try_flags_under_load
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_migration_with_additional_flags
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.cpuflags.stress_guest.qemu_test_online_offline_guest_CPUs
> > kvm.qed.virtio_blk.smp4.virtio_net.RHEL.6.2.x86_64.linux_s3
> 
> Interesting thing here is that you guys are using qed as the default
> image type. Is this part of the test plan? (internally we only use
> qcow2)
> 
> > Regards,
> > Santwana
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to majordomo@xxxxxxxxxxxxxxx
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> 


--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux