(re-send of patches w/ lost implimentations re-written)
The current implementation of libvirt vm requires a
vm login upon vm start, which is unnecessary and
conflict with tests such as boot_savevm. Now, we
can simplify the entire processing code by removing
the login and dropping wait_for_start method.
The behavior of vm.create() between libvirt and kvm
still differs in that libvirt only uses create() for
installs. This should be corrected in the future so
the vm class implimentation matches better.
Two new functions were defined for libvirt and
two vm class methods were written. A private function
was added to uniformly generate VM save filenames when
they aren't specified. The other four new functions
allow save/restore of VMs with or without an explicit
filename.
For now, the changes involving libvirt vm.start()
don't appear to affect other tests. With that change
and the new functions, it's possible to make
an initial implimentation of the KVM boot_savevm
test under libvirt. Only minimal changes were required
to the test code from it's KVM version.
With implimentation of a working libvirt.monitor and
some minor updates to the kvm monitor class, both
environments could eventually share the same test code.
Until then I suggest we maintain the two seperately.
Chris Evich (5):
libvirt subtest: Copy kvm boot_savevm subtest
libvirt subtest: Convert boot_savevm for use with libvirt
libvirt subtest config: Reduce boot_savevm login timeout similar to
KVM test
libvirt_vm: Fix vm.wait_for_start()
libvirt.vm class: Impliment four methods
client/tests/libvirt/subtests.cfg.sample | 2 +-
client/tests/{kvm => libvirt}/tests/boot_savevm.py | 33 ++---
client/virt/libvirt_vm.py | 135 ++++++++++++++------
3 files changed, 111 insertions(+), 59 deletions(-)
copy client/tests/{kvm => libvirt}/tests/boot_savevm.py (66%)
_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
