From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>, Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KVM call minutes for Apr 26
Date: Thu, 28 Apr 2011 18:31:08 -0300 [thread overview]
Message-ID: <1304026270.2016.11.camel@freedom> (raw)
In-Reply-To: <4DB73951.9050809@codemonkey.ws>
On Tue, 2011-04-26 at 16:29 -0500, Anthony Liguori wrote:
> On 04/26/2011 11:47 AM, Lucas Meneghel Rodrigues wrote:
> > On Tue, 2011-04-26 at 17:58 +0300, Avi Kivity wrote:
> >> On 04/26/2011 05:41 PM, Chris Wright wrote:
> >>> - having basic common config could be useful
>
> Hi Lucas,
>
> Could you send your suggested config as a patch to qemu.git? Even
> better if it was automatically invoked via a make autotest target
> although if you supply the config, I'll happily patch the Makefile.
>
> Regards,
>
> Anthony Liguori
So Anthony, after hearing quite a lot of feedback from our colleagues,
I'll start working on a 'make autotest' target for qemu and qemu-kvm.
A lot of compromises will have to be made here, I was thinking on a very
minimum setup where folks can get unittests, followed by booting,
rebooting, and single host migration, using a minimal fedora guest
image, that 'make autotest' would download.
Meanwhile, here is Avi's config file translated to a more current
autotest state. I don't think we should rush into putting this into
qemu's repo, as I am aiming for having this more transparent to the
user. Just publishing here FYI.
include tests_base.cfg
include cdkeys.cfg
image_name(_.*)? ?<= /tmp/kvm_autotest_root/images/
cdrom(_.*)? ?<= /tmp/kvm_autotest_root/
floppy ?<= /tmp/kvm_autotest_root/
Linux..unattended_install:
kernel ?<= /tmp/kvm_autotest_root/
initrd ?<= /tmp/kvm_autotest_root/
variants:
# The variant names are the testset names
- @regression:
# We want qemu-kvm for this run
qemu_binary = /usr/bin/qemu-kvm
qemu_img_binary = /usr/bin/qemu-img
only qcow2
only rtl8139
only ide
only smp2
only no_pci_assignable
only smallpages
only Fedora.14 Win7
only unattended_install.cdrom, boot, reboot, migrate, shutdown
abort_on_error = yes
kill_vm.* ?= no
kill_unresponsive_vms.* ?= no
# Put the testset you want here
only regression
prev parent reply other threads:[~2011-04-28 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 14:41 [Qemu-devel] KVM call minutes for Apr 26 Chris Wright
2011-04-26 14:58 ` Avi Kivity
2011-04-26 16:47 ` Lucas Meneghel Rodrigues
2011-04-26 21:29 ` Anthony Liguori
2011-04-28 21:31 ` Lucas Meneghel Rodrigues [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=1304026270.2016.11.camel@freedom \
--to=lmr@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).