From: santwana <santwana@linux.vnet.ibm.com>
To: Lucas Meneghel Rodrigues <lookkas@gmail.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org
Subject: Re: Biweekly upstream qemu-kvm test report (using autotest) - Week 35
Date: Fri, 31 Aug 2012 17:34:28 +0530 [thread overview]
Message-ID: <1346414668.5040.1.camel@Santwana> (raw)
In-Reply-To: <CAJnY6jr3sZHe015_V_GXag9_RjAgAbgDzFU+b+i781skq3A90g@mail.gmail.com>
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@linux.vnet.ibm.com> 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@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
prev parent reply other threads:[~2012-08-31 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 11:37 Biweekly upstream qemu-kvm test report (using autotest) - Week 35 santwana
2012-08-30 15:03 ` Lucas Meneghel Rodrigues
2012-08-31 12:04 ` santwana [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1346414668.5040.1.camel@Santwana \
--to=santwana@linux.vnet.ibm.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lookkas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox