From: Ryan Harper <ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Alexey Eremenko
<alexey.eremenko-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Question about KVM-test
Date: Tue, 30 Oct 2007 09:46:43 -0500 [thread overview]
Message-ID: <20071030144643.GA26153@us.ibm.com> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E032160C95C582-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
* Alexey Eremenko <alexey.eremenko-atKUWr5tajBWk0Htik3J/w@public.gmane.org> [2007-10-30 04:26]:
>
> It seems nice !
>
> But is there any documentation ? I don't know how-to start it.
Have you read the wiki page?
http://kvm.qumranet.com/kvmwiki/KVMTest
basically, you want to use kvm-test-record where you would normally use
qemu. So, if you launch your guest with:
qemu -hda /dev/hda1 -boot d -snapshot
You would run:
kvm-test-record -hda /dev/hda1 -boot d -snapshot
In the screen that pops up, there is a menu item ("Barriers") where you
can make a barrier. When you are done making barriers for this guest
run, you can replay the session using:
kvm-test-replay in the same directory where the vm.log and screenshots
were recorded. kvm-test-replay will re-run qemu as you invoked it with
kvm-test-record and attempt to inject the same inputs at the recorded
time intervals and match the barriers if any exist.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-30 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 9:22 Question about KVM-test Alexey Eremenko
[not found] ` <64F9B87B6B770947A9F8391472E032160C95C582-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-10-30 14:46 ` Ryan Harper [this message]
2007-10-30 15:08 ` Alexey Eremenko
[not found] ` <64F9B87B6B770947A9F8391472E032160C95C585-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-10-30 16:10 ` Ryan Harper
2007-10-31 9:49 ` Anthony Liguori
2007-10-31 10:09 ` Alexey Eremenko
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=20071030144643.GA26153@us.ibm.com \
--to=ryanh-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=alexey.eremenko-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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