All,
In order to properly test VM resource sequestration/security, we need a
way to have multiple VMs running and have test-control over the
separated resources. However, the current Cartesian setup for both KVM
and Libvirt does not support this.
Essentially and w/ minimal breaking of existing tests, we need a way to
have all host resources under the control of subtest variants.
Currently the order is:
include base.cfg
include subtests.cfg
include guest-os.cfg
include guest-hw.cfg
include cdkeys.cfg
include virtio-win.cfg
Finally we mangle the parameters image_name(_.*)?, cdrom(_.*)?, floppy,
kernel, initrd. Therefor, test variants will have a hard time specify
their own special locations for image_name(_.*)?, cdrom(_.*)?, floppy,
kernel, initrd.
-----
My hunch is that making the needed changes will impact the
unattended_install test. However, I think it's good if we fix (what I
see as a somewhat broken setup) this earlier rather than later.
Here's what I see as the work list and dependencies (comments/additions?)
* Correct Cartesian config. such that subtests.cfg variants may modify
image_name(_.*)?, cdrom(_.*)?, floppy, kernel, initrd, and possibly
other parameters.
* Fixup core virt code:
* virt_env_process
* virt_vm
* virt_utils
* virt_storage
* Fixup top-layer code:
* libvirt_vm
* kvm_vm
* kvm_monitor
* Fixup/Impliment tests
* unattended_install variants
* Onkar's multi-vm patches
* Onkar's svirt test-modules
* Other related tests?
* Other tests(windows?) that break b/c Cartesian changes
If anyone finds any of the above an "itch to scratch", please speak up,
we'd love the help. Otherwise, if nobody else wants to, I can take a
stab at fixing up the Cartesian setup to support resrouce separation +
optional test-code modification. With that out of the way, the
dependent items can continue in parallel to save time.
Any feedback? Concerns? How about Volunteers? :D
Thanks in advance.
--
Chris Evich, RHCA, RHCE, RHCDS, RHCSS
Quality Assurance Engineer
e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214
_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
