* KVM autotest tip of the week
@ 2011-07-06 4:28 Lucas Meneghel Rodrigues
2011-07-06 10:43 ` Stefan Hajnoczi
0 siblings, 1 reply; 3+ messages in thread
From: Lucas Meneghel Rodrigues @ 2011-07-06 4:28 UTC (permalink / raw)
To: Autotest mailing list, KVM mailing list, Virt devel
Cc: Dor Laor, Cleber Rosa, Michael Goldish, Jason Wang, Amos Kong
Hi guys,
On an effort to make KVM autotest better and more useful for our target
users (KVM developers), we are expanding documentation and writing
articles on how to get some commonly asked test jobs running (I plan on
get this going at least for some weeks).
So here is our first KVM autotest tip of the week
"How to install windows virtio drivers automatically with KVM autotest?"
http://autotest.kernel.org/wiki/KVMAutotest/InstallWinVirtio
So if you ever wondered how to do that, please take a look, and give us
your feedback.
Cheers,
The KVM autotest team
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: KVM autotest tip of the week
2011-07-06 4:28 KVM autotest tip of the week Lucas Meneghel Rodrigues
@ 2011-07-06 10:43 ` Stefan Hajnoczi
2011-07-06 13:05 ` Lucas Meneghel Rodrigues
0 siblings, 1 reply; 3+ messages in thread
From: Stefan Hajnoczi @ 2011-07-06 10:43 UTC (permalink / raw)
To: Lucas Meneghel Rodrigues
Cc: Autotest mailing list, KVM mailing list, Virt devel, Dor Laor,
Cleber Rosa, Michael Goldish, Jason Wang, Amos Kong
On Wed, Jul 6, 2011 at 5:28 AM, Lucas Meneghel Rodrigues <lmr@redhat.com> wrote:
> On an effort to make KVM autotest better and more useful for our target
> users (KVM developers), we are expanding documentation and writing
> articles on how to get some commonly asked test jobs running (I plan on
> get this going at least for some weeks).
Basic question for a future week:
How do I run a single test on a specific VM configuration (e.g. Fedora
guest, rtl8139, virtio-blk disk)?
Ideally this would use a pre-installed guest image (for userspace
tests). This would be very handy for reproducing test failures,
developing new tests, or just wanting to make sure a code change
doesn't break a specific test.
Stefan
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: KVM autotest tip of the week
2011-07-06 10:43 ` Stefan Hajnoczi
@ 2011-07-06 13:05 ` Lucas Meneghel Rodrigues
0 siblings, 0 replies; 3+ messages in thread
From: Lucas Meneghel Rodrigues @ 2011-07-06 13:05 UTC (permalink / raw)
To: Stefan Hajnoczi; +Cc: KVM mailing list, Virt devel, Autotest mailing list
On Wed, Jul 6, 2011 at 7:43 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Wed, Jul 6, 2011 at 5:28 AM, Lucas Meneghel Rodrigues <lmr@redhat.com> wrote:
>> On an effort to make KVM autotest better and more useful for our target
>> users (KVM developers), we are expanding documentation and writing
>> articles on how to get some commonly asked test jobs running (I plan on
>> get this going at least for some weeks).
>
> Basic question for a future week:
> How do I run a single test on a specific VM configuration (e.g. Fedora
> guest, rtl8139, virtio-blk disk)?
Ok, we just got ourselves the next weekly tip!
> Ideally this would use a pre-installed guest image (for userspace
> tests). This would be very handy for reproducing test failures,
> developing new tests, or just wanting to make sure a code change
> doesn't break a specific test.
Will think about a sensible way to make things easier.
Cheers,
Lucas
> Stefan
> --
> 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
>
--
Lucas
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-07-06 13:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-06 4:28 KVM autotest tip of the week Lucas Meneghel Rodrigues
2011-07-06 10:43 ` Stefan Hajnoczi
2011-07-06 13:05 ` Lucas Meneghel Rodrigues
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox