Refactored the cross use of netcf and interface for the interface driver into
only interface driver references. Made netcf the primary backend provider for
the interface driver. Added a udev based read-only interface driver backend to
be used when netcf support is not built in.
Untested:
* udev: Does it display devices that are part of a bond.
* netcf: developed all this on distros without netcf support.
Unknown:
* Should virInterfaceGetXMLDesc() be implemented for the udev backend?
It will as a result contain a lot less info than the netcf based backend
would for the same device (e.g. does the device start on boot).
Doug Goldstein (2):
build: define WITH_INTERFACE for the driver
interface: add udev based backend for virInterface
configure.ac | 37 ++-
daemon/Makefile.am | 2 +-
daemon/libvirtd.c | 8 +-
src/Makefile.am | 34 ++-
.../{netcf_driver.c => interface_backend_netcf.c} | 2 +-
src/interface/interface_backend_udev.c | 377 ++++++++++++++++++++
.../{netcf_driver.h => interface_driver.h} | 0
tests/virdrivermoduletest.c | 2 +-
tools/virsh.c | 4 +-
9 files changed, 449 insertions(+), 17 deletions(-)
rename src/interface/{netcf_driver.c => interface_backend_netcf.c} (99%)
create mode 100644 src/interface/interface_backend_udev.c
rename src/interface/{netcf_driver.h => interface_driver.h} (100%)
--
1.7.8.6
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list