On Tue, Nov 16, 2010 at 03:32:40PM +0800, Jason Wang wrote:
> Amos Kong writes:
> > KVM-test: Add a new bonding subtest
> >
> > From: Amos Kong <[email protected]>
> >
> > In this test, execute bonding_setup.py to setup bonding of guest, do
> > basic transfer test, and repeatedly put down/up interfaces by set_link for
> > testing high availability.
> >
> > there is a known issue of serial login, load another patch
> > (http://patchwork.test.kernel.org/patch/2720/)
> > when you test bonding test script.
> >
> > Changes from v1:
> > - Add file transfer test
> > - Setup bonding by serial
> > - Fix bonding_setup.py
> >
> > Changes from v2:
> > - Drop ping test
> > - Assign mac of nic1 to bond0
> > - Do some basic test before testing high availability
> > - Repeatedly down/up link by monitor cmd
> >
> > Signed-off-by: Feng Yang <[email protected]>
> > Signed-off-by: Amos Kong <[email protected]>
...
> > + @param test: Kvm test object.
> > + @param params: Dictionary with the test parameters.
> > + @param env: Dictionary with test environment.
> > + """
> > + def control_link_loop(vm, termination_event):
> > + logging.info("Repeatedly put down/up interfaces by set_link")
> > + while True:
> > + for i in range(len(params.get("nics").split())):
> > + linkname = "%s.%s" % (params.get("nic_model"), i)
>
> Better solution here is to generate a id for each nic devices and use
> kvm_utils.get_subdict_names() to enumerate the nics.
parameter 'id' is not supported in old qemu-kvm, we could not use
'netdev id', 'device id'. If we create a special 'id' for each nic,
it's difficut to manage them. So I'll keep my method.
_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
