From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: Updated versoin of kvm-xfstests available
Date: Sat, 9 Aug 2014 19:45:56 -0400 [thread overview]
Message-ID: <20140809234556.GA11072@thunk.org> (raw)
I've uploaded a new set of precompiled kvm-xfstests test appliances
at:
https://www.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests
This new version has an updated xfstests, with more of the tests
enabled. The root_fs image is 40% smaller, and if you want to build
your own root_fs.img, it's much faster and convenient to do so now.
All ext4 developers are strongly encouraged to test their patches
using xfstests before sending them out for review; you are free to use
your own installation of xfstests, but if you want something simple
and turn-key, so there can be no excuses not to test, this is what
kvm-xfstests is for. :-)
Please do at least "smoke" testing, and if you are working on a major
new feature, doing a full run using "-g auto" is much appreciated.
Once I'm done running my baseline, I'll send out the results for your
convenience; if your patches cause any regressions, *please* take a
look and figure out why, since that will save me a lot of time and
allow your patches to get merged that much more quickly.
- Ted
Quick start instructions:
0. Make sure qemu with kvm support is installed on your system.
1. Run the following commands:
git clone git://git.kernel.org/pub/scm/fs/ext2/xfstests-bld.git fstests
cd fstests/kvm-xfstests
wget -O test_appliance/root_fs.img https://www.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests/root_fs.img.i386
Substitute "i386" for "x86_64" in the above URL if you want to test
using a native 64-bit userspace. It should be possible to use the
32-bit userspace with a 64-bit kernel, although you may run into some
rough spots via-a-vis compat ioctls working correctly. (If you do,
let me know; those are bugs that should be fixed. :-)
2. Take a look at the "config" file and either edit that file in
place, or put override values in ~/.config/kvm-xfstests or
config.custom. The latter is preferred.
3. Build a kernel with all of the necessary drives for kvm built into
the kernel (i.e., no modules!). There are some sample kernel
configs in the kernel-configs directory.
4. Run "./kvm-xfstests smoke" to do a quick test. Or "./kvm-xfstests
-g auto" to do a full test. You can also run specific tests on
specific configurations, i.e., "./kvm-xfstests -c bigalloc
generic/013 generic/127".
For more information, please see:
https://git.kernel.org/cgit/fs/ext2/xfstests-bld.git/tree/kvm-xfstests/README
GPL Compliance information can be found here:
https://www.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests/README
next reply other threads:[~2014-08-09 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 23:45 Theodore Ts'o [this message]
2014-08-12 16:08 ` Updated version of kvm-xfstests available Theodore Ts'o
2014-08-12 16:10 ` Theodore Ts'o
2014-08-12 16:10 ` Theodore Ts'o
2014-08-23 17:35 ` Eric Whitney
2014-09-08 2:01 ` Theodore Ts'o
2014-10-28 15:20 ` Theodore Ts'o
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=20140809234556.GA11072@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.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).