Hi,
No problem, and no shame in asking, it's quite likely the most
complicated and confusing topic. Note, I don't think you can run smp on
just qemu, I think you need kvm for that. Assuming it's just the
up/smp2 filter you're after, there's actually an even easier approach:
Remove the 'only smp2' line from the @qemu_kvm_f16_quick variant as you
did, and keep the 'only qemu_kvm_f16_quick' at the end. Then, from the
command-line:
# bin/autotest -a only=smp2 tests/kvm/control
...
14:02:28 INFO | Test 1: smp2.Fedora.16.64.unattended_install.cdrom
14:02:28 INFO | Test 2: smp2.Fedora.16.64.boot
14:02:28 INFO | Test 3: smp2.Fedora.16.64.shutdown
...
# bin/autotest -a only=up tests/kvm/control
...
14:06:54 INFO | Test 1: Fedora.16.64.unattended_install.cdrom
14:06:54 INFO | Test 2: Fedora.16.64.boot
14:06:54 INFO | Test 3: Fedora.16.64.shutdown
...
However, if you need to do more complicated filters (beyond just only=up
or only=smp2) then I'd use the approach I outlined in my first reply.
For example, to changing both smp/up and networking between runs, you'd
first define:
...tests.cfg...(at end of variants block)
- @qemu_kvm_f16_custom:
# We want qemu-kvm for this run
qemu_binary = /usr/bin/qemu-kvm
qemu_img_binary = /usr/bin/qemu-img
qemu_io_binary = /usr/bin/qemu-io
only qcow2
# only rtl8139
only ide
# only smp2
only no_9p_export
only no_pci_assignable
only smallpages
only Fedora.16.64
only unattended_install.cdrom, boot, shutdown
# Choose your test list from the testsets defined
#only qemu_kvm_f16_quick
variants:
- @one:
only rtl8139
only smp2
only qemu_kvm_f16_custom
- @two:
only e1000
only up
only qemu_kvm_f16_custom
Then from the command-line, you'd run:
# bin/autotest -a only=one tests/kvm/control
and
# bin/autotest -a only=two tests/kvm/control
Let me know if you're still having problems or can't figure it out, I'm
happy to help.
--
Chris Evich, RHCA, RHCE, RHCDS, RHCSS
Quality Assurance Engineer
e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214
On 03/28/2012 04:07 PM, Richa Marwaha wrote:
>
> Hi Chris
> Thanks a lot for the information. I tried to do the steps you wrote below
> but that somehow does not seem to work for me, I am pretty sure I am
> missing something.
> The documents are really good but since I am really new I still don't know
> all the options that are in the KVM autotest and KVM itself, kindly excuse
> me for asking silly question. So just for my try I tried to use the steps
> below to run the qemu_f16_quick.
> So I created a variant
> -one : (this has all the options that are in the qemu_f16_quick in
> tests.cfg)
> then I created
> -@qemu_quick:
> only one
> and at the command line I specified
> only=qemu_quick
>
> then when I run the ../../common_lib/cartesian_config.py tests.cfg
> I get a lot of dict for other linux releases in autotests whereas in
> reality it should just show
> dict 1: e1000.Fedora.16.64.unattended_install.cdrom
> dict 2: e1000.Fedora.16.64.boot
> dict 3: e1000.Fedora.16.64.shutdown
>
> I am missing something .... just dont know what.
>
> Regards,
> Richa Marwaha
> LTC Security
> Email address:rmar...@us.ibm.com
>
>
>
> From: Chris Evich<cev...@redhat.com>
>
> To: autotest@test.kernel.org
>
> Date: 03/26/2012 03:51 PM
>
> Subject: Re: [Autotest] KVM autotests
>
> Sent by: autotest-boun...@test.kernel.org
>
>
>
>
>
>
>
> Hello,
>
> Yes, what you describe is possible, though (as with most things
> cartesian related) not entirely obvious. The trick here is to setup
> variant shortnames that include the test filters, then reference the
> shortnames from the command-line. For example (using letters as
> simplified variant names):
>
> variants:
> - A:
> - B:
> - C:
> - X:
> - Y:
> - Z:
>
> # shortnames
> variants:
> @one:
> only A B C
> @two:
> only X Y Z
>
> Assuming there aren't any other top-level filters active (i.e. comment
> out the default 'only qemu_kvm_f16_quick'). You just have to write
> something like the '#shortnames' block above. Then, pass 'only=one' as
> a command-line argument to autotest on the first run, then 'only=two' on
> the second run. The effect will be running A, B, and C the first time,
> then X,Y and Z the second time. You're free to define the shortnames
> however you want, and/or including application of the other filters at
> that level.
>
> I'm sure you're head is spinning now, but I did actually try the above
> and it works. Otherwise, you may ease the symptoms of
> Cartesian-Configuration syndrome with a cup of coffee/tea and a read
> through the new wiki docs on 'Cartesian Configuration'. Shameless-plug:
> I wrote the docs, so please let me know your feedback :)
>
> N.B. We know the inter-document links are broken :(
>
> On 03/26/2012 02:51 PM, Richa Marwaha wrote:
>>
>> Hi
>> I am running the KVM autotests and trying to run it with different
> options
>> in tests.cfg. For example in tests.cfg
>> If I comment out the only up option in tests.cfg n then run the dict I
> see
>> the following
>>
>>
>> dict 1: e1000.Fedora.16.64.unattended_install.cdrom
>> dict 2: e1000.Fedora.16.64.boot
>> dict 3: e1000.Fedora.16.64.shutdown
>> dict 4: smp2.e1000.Fedora.16.64.unattended_install.cdrom
>> dict 5: smp2.e1000.Fedora.16.64.boot
>> dict 6: smp2.e1000.Fedora.16.64.shutdown
>>
>> Is there a way that I can run dict1,2,3 in one iteration and then 4,5,6
> in
>> other one instead of all running in one iteration.
>>
>> In other words is there a way to run these tests separately rather than
>> together.
>> Thanks a lot
>> Regards,
>> Richa Marwaha
>> LTC Security
>> Email address:rmar...@us.ibm.com
_______________________________________________
Autotest mailing list
Autotest@test.kernel.org
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
