On 09/06/2012 12:53 PM, Daniel P. Berrange wrote: > FYI in case you don't already know, you can also run libvirt builds > directly from the source tree, rather than needing to run 'make intsall' > or install an updated RPM every time. my usual way of working is to > just stop the libvirtd process fro mthe RPM and then run > > $ cd $LIBVIRT_GIT > $ ./autogen.sh --system > $ make > $ su - > # ./daemon/libvirtd There is one small difference to running it this way rather than as a system service - it will be running in an unconfined/unrestricted state, so some things that may have otherwise failed due to a lack of permission, will succeed. So if you've changed anything related to what external programs are called, or what files/devices are accessed, it's usually a good idea to make a final test with a proper install (I tend to do that by running "make rpm" followed by an install of the rpms - there are yet other problems that don't show up if you simply run "make install"...) -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list