search for: msg00108

Hi, We are trying to compile Libvirt 1.02 from source for an RHEL4 target. Our virtualization hosts are running the fedora 17/ RHEL6 with the latest standard libvirt binaries. This is where VMs will be created. But our user/development machines are RHEL4 and we would like users to be able to use virsh/libvirt/python to control the Vms running on RHEL6/fedora17 remotely from the their RHEL4

This series should be ready for merge v6: - rebase on master - changes according to last comments Matteo Cafasso (6): filesystem_walk: fixed root inode listing daemon: refactor tsk code lib: rename tsk internal function New API: internal_find_inode New API: find_inode find_inode: added API tests daemon/tsk.c | 155 ++++++++++++++++++++++++++++++-------------

As mentioned in my reviews, I wonder if we should make our python callbacks look a bit more Pythonic by having kwargs added for each new flag that we want to expose. The idea was first floated here: https://www.redhat.com/archives/libguestfs/2018-April/msg00108.html Note that with my proposal, there is no need for a python script to expose a global API_VERSION variable; new flags are added using a Python API that is backwards-compatible. In fact, with introspection, we can even get away with the user not having to write a can_fast_zero; the mere presenc...