[libvirt] [PATCH RFC 7/9] volume: Convert virStorageVolObj[List] to use virPoolObj[Table]

Use the virPoolObj[Table] object management model in order to manage the storage volume objects. While making the adjustments to use the new model, there are some code formatting adjustments that were also made with the goal to follow more recent code flow and layout. Signed-off-by: John Ferlan

[libvirt] [PATCH RFC 3/9] nodedev: Convert virNodeDevObj[List] to use virPoolObj[Table]

Use the virPoolObj[Table] object management model in order to manage the Node Device objects. While making the adjustments to use the new model, there are some code formatting adjustments that were also made with the goal to follow more recent code flow and layout. For API's that were static,

[libvirt] [PATCH RFC 6/9] secret: Convert virSecretObj[List] to use virPoolObj[Table]

Use the virPoolObj[Table] object management model in order to manage the Secret objects. While making the adjustments to use the new model, there are some code formatting adjustments that were also made with the goal to follow more recent code flow and layout. Signed-off-by: John Ferlan

[libvirt] [PATCH RFC 4/9] interface: Convert virInterfaceObj[List] to use virPoolObj[Table]

Use the virPoolObj[Table] object management model in order to manage the Interface objects. While making the adjustments to use the new model, there are some code formatting adjustments that were also made with the goal to follow more recent code flow and layout. All interface object management

[libvirt] [PATCH RFC 5/9] nwfilter: Convert virNWFilterObj[List] to use virPoolObj[Table]

Use the virPoolObj[Table] object management model in order to manage the NWFilter objects. While making the adjustments to use the new model, there are some code formatting adjustments that were also made with the goal to follow more recent code flow and layout. All nwfilter object management

[libvirt] [PATCH RFC 1/9] conf: Modify gendispatch.pl to make ACL argument opaque

The various drivers each have vir*EnsureACL and vir*CheckACL API's which are generated on the fly by gendispatch to include the driver typed "def" name as the last argument based on the API being checked and the driver name (e.g. Node, Interface, Secrets, etc.). Rather than having that name by

[libvirt] [PATCH RFC 0/9] Introduce virPoolObj[Table]Ptr data/API's

Based of current top of git commit id '5620c6095'... I imagine things will change while this is on-list, so if there is the desire to create your own branch that's your starting point! This is perhaps more than an RFC considering I've added comments already (at least one reason why the insertions

[libvirt] [PATCH RFC 2/9] conf: Introduce virPoolObj and virPoolTableObj and PoolObj API's

Introduce a new generic virPoolObj[Ptr] and virPoolObjTable[Ptr] in order to generically manage driver lists of objects rather than the current hodgepodge of some drivers using a forward linked list and other drivers using a single UUID only based hash table to look up objects. The concept is to

Re: [libvirt] [PATCH 2/2] apparmor: don't fail on non-apparmor

Hi, Jim, On Thu, Feb 09, 2017 at 09:30:16AM -0700, Jim Fehlig wrote: > Guido Günther wrote: > > On Fri, Feb 03, 2017 at 10:32:12AM -0700, Jim Fehlig wrote: > >> If the apparmor security driver is loaded/enabled and domain config > >> contains a element whose type attribute is not 'apparmor', > >>

[libvirt] [PATCH] libxl: implement virDomainObjCheckIsActive

Add function which raises error if domain is not active Signed-off-by: Sagar Ghuge --- src/conf/domain_conf.c | 13 + src/conf/domain_conf.h | 1 + src/libxl/libxl_driver.c | 4 +--- 3 files changed, 15 insertions(+), 3 deletions(-) diff --git