On 12/10/2012 09:09 AM, David Mitchell wrote:
On Dec 10, 2012, at 8:28 AM, David Mitchell wrote:
I think I can probably manage to have some kind of script which can help ensure that my servers are in sync using only the libvirt API and ignoring the config files. I think I am still a little unclear on exactly how transient transient is. In my mind only the persistent and defined objects would actually have their configuration saved in a file and persist across reboots. It's surprising to me that so-called transient objects are also saved in config files and can persist across reboots.
Transient data is saved so that it can survive libvirtd restarts; but it should not survive host restarts. Contents in /var/libvirt should not survive a reboot.
I should probably add that part of the confusion to me seems to be related to the fact that I can't find a way to have virsh tell me if something is persistent or transient, at least with respect to a network object. There are specific flags for domains but not for other object types.
[Your mailer doesn't wrap long lines, which makes it a bit harder to read] # dump the persistent definition: virsh net-dumpxml $net --inactive # dump the transient definition, if the network is running: virsh net-dumpxml $net # determine which networks are persistent vs. transient: virsh net-list --all This design mirrors the same things done for domains. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org