grthtrhthjhtyjytjytkergtrhtrjytjerhrfh4:24 29/09/2026a cei @s'z ddlZWnfeyrZzNz ddlZWn4ey\ZzdeevrHeWYdZ[n dZ[00WYdZ[n dZ[00ddlmZddlm Z m Z m Z m Z m Z mZmZmZmZmZedZe eeeegdfZe eeeegefZe eegdfZe egefZe eegdfZe eeegefZe eegdfZe egefZe ddeeege efZe ee fZe ee fZe ee fZ e ee fZ!Gdd d e"Z#e ee gdfeed d d Z$dee edd ddZ%de eedddZ&edeeeeeefdddddZ'edeeeeeddddZ'deeeeeeefefe eddddZ'deeeeefefe eddddZ(eeee ee fedddZ)ee ee feddd Z*eeeeed!d"d#Z+eeeed$d%d&Z,e dd'd(d)Z-dd*d+Z.dd,d-Z/d.d/Z0d0d1Z1d2d3Z2d4d5Z3d6d7Z4d8d9Z5d:d;Z6dd?Z8d@dAZ9dBdCZ:dDdEZ;dFdGZGdIdJdJe=Z?GdKdLdLe=Z@GdMdNdNe=ZAGdOdPdPe=ZBGdQdRdRe=ZCGdSdde=ZDGdTdUdUe=ZEGdVdWdWe=ZFGdXdYdYe=ZGGdZd[d[e=ZHGd\d]d]e=ZIGd^d_d_e=ZJGd`dadae=ZKdbZLdcZMddZNdeZOdfZPdgZQdhZRdZSdbZTdcZUdbZVdcZWdeZXdZYdbZZdcZ[ddZ\dbZ]dcZ^dbZ_dcZ`ddZadeZbdfZcdgZddiZedjZfdkZgdZhdbZidcZjdbZkdcZldZmdbZndcZoddZpdZqdbZrdbZsdcZtdbZudcZvdeZwdjZxdlZydmZzdnZ{doZ|dpZ}dqZ~drZdbZdbZdcZdeZdjZdlZdmZdnZdoZdsZdtZduZdvZdwZdxZdyZdzZdbZdcZdbZdcZdeZdjZdlZdmZdbZdcZdeZdjZdlZdmZdnZdoZdsZdtZduZdvZdwZdxZdyZdzZd{Zd|Zd}Zd~ZdZdZdZdZdZdpZdqZdrZdbZdcZdeZdjZdbZdcZdeZdjZdlZdmZdnZdoZdsZdtZduZdvZdwZdxZdyZdzZd{Zd|Zd}Zd~ZdbZdZdhZdZdbZdcZdbZdcZdbZdcZdeZdjZdlZdbZdcZdeZdjZdbZdcZdbZdbZdZdbZdcZddZdeZdfZdnZdbZdcZdeZdjZdlZdmZdnZdbZdcZdZdbZdbZdcZdeZdbZdcZdeZdbZdbZdcZdeZdjZdbZdcZdeZdbZdcZdZdbZdcZddZdZdbZ dcZ ddZ dbZ dcZ deZdjZdlZdZdbZdcZddZdeZdZdbZdZdbZdcZdeZdjZdlZdmZdbZdZ dbZ!dcZ"dZ#dbZ$dcZ%deZ&dZ'dbZ(dcZ)dZ*dbZ+dcZ,dZ-dbZ.dcZ/dZ0dbZ1dZ2dbZ3dcZ4ddZ5dZ6dbZ7dcZ8dZ9dbZ:dcZ;dZddZ?deZ@dfZAdgZBdiZCdjZDdkZEdZFdZGdZHdZIdZJdZKdlZLdZMdZNdZOdZPdZQdZRdZSdZTdZUdZVdZWdZXdbZYdcZZdZ[dbZ\dZ]dbZ^dcZ_ddZ`deZadZbdbZcdcZddZedbZfdcZgddZhdeZidfZjdZkdbZldcZmddZndeZodfZpdgZqdiZrdZsdbZtdcZuddZvdeZwdfZxdgZydiZzdjZ{dkZ|dZ}dbZ~dZdbZdcZddZdeZdfZdgZdiZdjZdZdbZdZdbZdcZddZdeZdfZdgZdbZdcZdbZdcZdbZdcZdZdbZdbZdcZdeZdjZdlZdmZdnZdoZdZdbZdcZdZdbZdcZddZdeZdfZdgZdiZdjZdkZdZdZdbZdcZddZdeZdfZdZdbZdcZdZdbZdcZddZdeZdfZdZdbZdcZddZdbZdcZdZdbZdbZdcZdZdbZdcZdeZdZdbZdcZddZdeZdfZdgZdiZdjZdkZdZdZdZdZdZdbZdcZdeZdZdbZdcZdbZdcZdeZdjZdlZdmZdnZdoZdsZdtZduZdvZdwZdxZdyZdzZd{Zd|Zd}Zd~ZdZdbZdZdbZdcZdZdZdbZdcZddZdbZdZdZdZdbZdcZddZdeZdfZdgZdiZ djZ dkZ dZ dZ dZdZdZdZdbZdcZddZdeZdfZdgZdiZdjZdkZdZdZdZdZdZdZ dlZ!dZ"dZ#dZ$dZ%dZ&dZ'dZ(dZ)dZ*dZ+dZ,dZ-dZ.dZ/dZ0dmZ1dZ2dZ3dZ4dZ5dZ6dZ7dZ8dZ9dZ:dZ;dZdZ?dZ@dZAdZBdZCdZDdZEdZFdZGdZHdZIdZJdZKdZLdZMdZNdZOdZPdnZQdZRdbZSdcZTdeZUdjZVdlZWdZXdbZYdcZZddZ[deZ\dfZ]dgZ^diZ_djZ`dkZadZbdZcdbZddbZedcZfdeZgdjZhdbZidbZjdZkdbZldcZmdeZndjZodlZpdZqdbZrdZsdbZtdcZuddZvdeZwdfZxdgZydiZzdjZ{dbZ|dcZ}deZ~djZdlZdmZdnZdoZdsZdtZdbZdcZdeZdbZdbZdcZdeZdjZdlZdmZdnZdoZdsZdtZduZdbZdcZdeZdjZdbZdZdbZdcZddZdeZdfZdgZdiZdbZdcZdeZdjZdlZdmZdnZdoZdsZdtZduZdbZdcZdeZdjZdlZdmZdnZdZdbZdcZdeZdjZdlZdbZdcZdeZdjZdZdbZdcZddZdeZdfZdgZdiZdjZdkZdZdZdZdZdZdZdlZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdmZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdnZdZdZdZdZdZdZdZdZdZdbZdcZ dZ dbZ dcZ ddZ deZdfZdgZdiZdjZdkZdZdZdZdZdZdZdlZdZdZdZdZdZdZ dZ!dZ"dZ#dZ$dZ%dZ&dZ'dZ(dZ)dmZ*dZ+dZ,dZ-dZ.dZ/dZ0dZ1dZ2dZ3dZ4dZ5dZ6dZ7dZ8dZ9dZ:dZ;dZdZ?dZ@dZAdZBdZCdZDdZEdZFdZGdZHdZIdnZJdZKdZLdZMdZNdZOdZPdZQdZRdZSdZTdÐZUdĐZVdŐZWdƐZXdǐZYdȐZZdɐZ[dʐZ\dːZ]d̐Z^d͐Z_dΐZ`dϐZadАZbdѐZcdҐZddӐZedԐZfdՐZgd֐ZhdאZidؐZjdِZkdڐZldېZmdܐZndݐZodސZpdߐZqdZrdZsdZtdZudZvdZwdZxdZydZzdZ{dbZ|dcZ}deZ~djZdZdbZdbZdbZdZdbZdcZddZdeZdfZdgZdiZdjZdkZdbZdcZddZdeZdfZdgZdbZdbZdbZdbZdZdbZdZdbZdcZddZdZdbZdcZdbZdcZdZdbZdcZddZdeZdZdbZdcZdZdbZdcZddZdeZdfZdgZdiZdjZdkZdZdZdZdbZdZdbZdbZdbZdZdbZdZdbZdcZddZdZdbZdcZdbZdhZdhZdZdbZdcZdbZdcZddZdeZdfZdgZdbZdZdbZdZdbZdZdbZdcZddZdeZdfZdZdbZdcZdeZdjZdZdbZdcZdeZdbZdZdbZdZdbZdZdbZdcZddZdeZdfZdZdbZdcZddZdeZdbZdcZdeZdZdbZdcZdbZdZdbZdbZdcZdeZdZdbZdcZddZdeZdfZdbZdZ dbZ dcZ ddZ deZ dfZdgZdiZdjZdkZdbZdbZdcZdeZdjZdbZdbZdeZdbZdcZddZdeZdfZdgZ diZ!dZ"dhZ#dZ$dbZ%dcZ&dZ'dZ(dZ)dZ*dZ+dZ,dZ-dZ.dZ/dZ0dZ1dZ2dZ3dZ4dZ5dZ6dZ7dZ8dZ9dZ:dZ;dZ<dZ=dZ>dZ?dZ@dZAdZBdZCdZDdZEd ZFd ZGd ZHd ZId ZJdZKdZLdZMdZNdZOdZPdZQdZRdZSdZTdZUdZVdZWdZXdZYdZZdZ[dZ\d Z]d!Z^d"Z_d#Z`d$Zad%Zbd&Zcd'Zdd(Zed)Zfd*Zgd+Zhd)Zid,Zjd-Zkd.Zld/Zmd0Znd1Zod&Zpd2Zqd-Zrd3Zsd4Ztd)Zud5Zvd6Zwd7Zxd8Zyd9Zzd:Z{d;Z|d<Z}d=Z~d>Zd?Zd)Zd@ZdAZdBZdCZdDZdEZdFZdGZdHZdIZdJZdKZdLZdMZdNZdOZdPZdQZdRZd)ZdSZdTZdUZdVZdWZdXZdYZdZZd[Zd\Zd]Zd^Zd_Zd`ZdaZdbZdcZddZdeZdfZdgZdhZdiZdjZdkZdlZdmZdnZdoZdpZdqZdrZdsZdtZduZdvZdwZdxZdyZdzZd{Zd|Zd}Zd~ZdZdZÐdZĐdZŐdZƐdZǐdZȐdZɐdZʐdZːdZ̐dZ͐dZΐdZϐdZАdZѐdZҐdZӐdZԐdZՐdZ֐dZאdZؐdZِdZڐdZېdZܐdZݐdZdZߐdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdZdÐZdĐZdŐZ d)Z dƐZ dǐZ dȐZ dɐZdʐZdːZd̐Zd͐ZdΐZdϐZdАZdѐZdҐZdӐZdԐZdՐZd֐ZdאZdؐZdِZdڐZdېZ dܐZ!dݐZ"dސZ#dߐZ$dZ%dZ&dZ'dZ(dZ)dZ*dZ+d)Z,dZ-dZ.dZ/dZ0dZ1dZ2dZ3dZ4dZ5dZ6dZ7dZ8dZ9dZ:dZ;dZ<dZ=dZ>dZ?dZ@dZAdZBdZCd)ZDdZEdZFdZGdZHdZIdZJdZKdZLd)ZMdZNdZOdZPdZQdZRd ZSd ZTd ZUd ZVd ZWdZXdZYdZZdZ[dZ\dZ]dZ^dZ_dZ`dZadZbdZcdZddZedZfdZgdZhdZid Zjd!Zkd"Zld#Zmd$Znd%Zod&Zpd'Zqd(Zrd)Zsd*Ztd+Zud,Zvd-Zwd.Zxd/Zyd0Zzd1Z{d2Z|d3Z}d4Z~d5Zd6Zd7Zd8Zd9Zd:Zd;Zd<Zd=Zd>Zd?Zd@ZdAZdBZdCZdDZdEZdFZdGZdHZdIZdJZdKZdLZdMZdNZdOZdZdPZdQZdRZdSZdTZdUZdVZdWZdXZdYZdZZd[Zd\Zd]Zd^Zd_Zd`ZdaZdbZdcZddZdZdZdZdZdZdZdZdeZdfZdgZdhZdiZdjZdkZdlZdmZdnZdoZdpZdqZÐdrZĐdsZŐdtZƐduZǐdvZȐdwZɐdxZʐdyZːdzZ̐d{Z͐d|Zΐd}Zϐd~ZАdZѐdZҐdZӐdZԐdZՐdZ֐dZאdZؐdZِdZڐdZېdZܐdZݐdZސdZߐdZdZdZdZdZdZdZdS(NzNo module named) TracebackType) AnyCallableDictListOptionaloverloadTupleTypeTypeVarUnion_T virConnect virDomainc@seZdZeddddZeedddZeeddd Zeedd d Z eedd d Z eedddZ eedddZ eedddZ eedddZeedddZdS) libvirtErrorN)defmsgreturncCs4t}|dur|}n|d}t||||_dSN) libvirtmodvirGetLastError Exception__init__err)selfrrmsgr-/usr/lib64/python3.9/site-packages/libvirt.pyr-s  zlibvirtError.__init__rcCs|jdurdS|jdS)Nrrrrrrget_error_code;s zlibvirtError.get_error_codecCs|jdurdS|jdS)Nrr rrrget_error_domain@s zlibvirtError.get_error_domaincCs|jdurdS|jdSrrr rrrget_error_messageEs zlibvirtError.get_error_messagecCs|jdurdS|jdS)Nrr rrrget_error_levelJs zlibvirtError.get_error_levelcCs|jdurdS|jdS)Nrr rrrget_str1Os zlibvirtError.get_str1cCs|jdurdS|jdS)Nrr rrrget_str2Ts zlibvirtError.get_str2cCs|jdurdS|jdS)Nrr rrrget_str3Ys zlibvirtError.get_str3cCs|jdurdS|jdS)Nrr rrrget_int1^s zlibvirtError.get_int1cCs|jdurdS|jdS)Nrr rrrget_int2cs zlibvirtError.get_int2)__name__ __module__ __qualname__strrrintr!r#r$r&r(r*r,r.r0rrrrr,sr)fctxrcCs t||S)zRegister a Python function for error reporting. The function is called back as f(ctx, error), with error being a list of information about the error being raised. Returns 1 in case of success.)rZvirRegisterErrorHandler)r6r7rrrregisterErrorHandlerlsr8)uriauthflagsrcCs(t|||}|durtdt|dS)a This function should be called first to get a connection to the Hypervisor. If necessary, authentication will be performed fetching credentials via the callback. See :py:func:`open` for notes about environment variables which can have an effect on opening drivers and freeing the connection resources. :param str uri: (Optional) connection URI, see https://libvirt.org/uri.html :param auth: a list that contains 3 items: - a list of supported credential types - a callable that takes 2 arguments (credentials, user-data) and returns 0 on succcess and -1 on errors. The credentials argument is a list of credentials that libvirt (actually the ESX driver) would like to request. An element of this list is itself a list containing 5 items (4 inputs, 1 output): - the credential type, e.g. :py:const:`libvirt.VIR_CRED_AUTHNAME` - a prompt to be displayed to the user - a challenge, the ESX driver sets this to the hostname to allow automatic distinction between requests for ESX and vCenter credentials - a default result for the request - a place to store the actual result for the request - user data that will be passed to the callable as second argument :param int flags: bitwise-OR of virConnectFlags :returns: a :py:class:`virConnect` instance on success. :raises libvirtError: on errors. NzvirConnectOpenAuth() failed_obj)rZvirConnectOpenAuthrr)r9r:r;retrrropenAuthtsr?)namercCs0|durt}n t|}|dur,td|S)aIf no name parameter is passed (or name is None) then the version of the libvirt library is returned as an integer. If a name is passed and it refers to a driver linked to the libvirt library, then this returns a tuple of (library version, driver version). If the name passed refers to a non-existent driver, then you will get the exception 'no support for hypervisor'. Versions numbers are integers: 1000000*major + 1000*minor + release.NzvirGetVersion() failed)rZ virGetVersionrr@r>rrr getVersions   rB)watchfdeventopaque opaquecompatrcCsdSNrrCrDrErFrGrrr_eventInvokeHandleCallbacksrJcCsdSrHrrIrrrrJscCsB|r|}|}nt|tsJ|d}|d}t|||||dS)z4 Invoke the Event Impl Handle Callback in C rr"N) isinstancetuplerZvirEventInvokeHandleCallback)rCrDrErFrGcallbackopaque_rrrrJs)timerrFrGrcCs>|r|}|}nt|tsJ|d}|d}t|||dS)z5 Invoke the Event Impl Timeout Callback in C rr"N)rKrLrZvirEventInvokeTimeoutCallback)rOrFrGrMrNrrr_eventInvokeTimeoutCallbacksrP)rCrDeventscbDatarcCs"|d}|d}|||||dSNcbrFrr)rCrDrQrRrTrFrrr_dispatchEventHandleCallbacksrU)rOrRrcCs|d}|d}|||dSrSr)rOrRrTrFrrr_dispatchEventTimeoutCallbacks rV)rDrQrTrFrcCs,||d}t|||}|dkr(td|S)a( register a callback for monitoring file handle events @fd: file handle to monitor for events @events: bitset of events to watch from virEventHandleType constants @cb: callback to invoke when an event occurs @opaque: user data to pass to callback Example callback prototype is: def cb(watch, # int id of the handle fd, # int file descriptor the event occurred on events, # int bitmap of events that have occurred opaque): # opaque data passed to eventAddHandle rTrFzvirEventAddHandle() failed)rvirEventAddHandler)rDrQrTrFrRr>rrrrYs  rY)timeoutrTrFrcCs*||d}t||}|dkr&td|S)a register a callback for a timer event @timeout: time between events in milliseconds @cb: callback to invoke when an event occurs @opaque: user data to pass to callback Setting timeout to -1 will disable the timer. Setting the timeout to zero will cause it to fire on every event loop iteration. Example callback prototype is: def cb(timer, # int id of the timer opaque): # opaque data passed to eventAddTimeout rWrXzvirEventAddTimeout() failed)rvirEventAddTimeoutr)rZrTrFrRr>rrrr[s   r[)rFrcCst|d|ddS)a  Execute callback which frees the opaque buffer @opaque: the opaque object passed to addHandle or addTimeout WARNING: This function should not be called from any call by libvirt's core. It will most probably cause deadlock in C-level libvirt code. Instead it should be scheduled and called from implementation's stack. See https://libvirt.org/html/libvirt-libvirt-event.html#virEventAddHandleFunc for more information. This function is not dependent on any event loop implementation. rr"N)rvirEventInvokeFreeCallback)rFrrrr\sr\cCs$t|}|durtdt|dS)aThis function should be called first to get a connection to the Hypervisor and xen store If @name is None, if the LIBVIRT_DEFAULT_URI environment variable is set, then it will be used. Otherwise if the client configuration file has the "uri_default" parameter set, then it will be used. Finally probing will be done to determine a suitable default driver to activate. This involves trying each hypervisor in turn until one successfully opens. If connecting to an unprivileged hypervisor driver which requires the libvirtd daemon to be active, it will automatically be launched if not already running. This can be prevented by setting the environment variable LIBVIRT_AUTOSTART=0 URIs are documented at https://libvirt.org/uri.html virConnectClose should be used to release the resources after the connection is no longer needed. NzvirConnectOpen() failedr<)rZvirConnectOpenrrrArrropen:s r]cCs$t|}|durtdt|dS)aThis function should be called first to get a restricted connection to the library functionalities. The set of APIs usable are then restricted on the available methods to control the domains. See virConnectOpen for notes about environment variables which can have an effect on opening drivers and freeing the connection resources URIs are documented at https://libvirt.org/uri.html NzvirConnectOpenReadOnly() failedr<)rZvirConnectOpenReadOnlyrrrArrr openReadOnlyRs r^cCst}|dkrtd|S)a0Registers a default event implementation based on the poll() system call. This is a generic implementation that can be used by any client application which does not have a need to integrate with an external event loop impl. For proper event handling, it is important that the event implementation is registered before a connection to the Hypervisor is opened. Once registered, the application has to invoke virEventRunDefaultImpl() in a loop to process events. Failure to do so may result in connections being closed unexpectedly as a result of keepalive timeout. The default event loop fully supports handle and timeout events, but only wakes up on events registered by libvirt API calls such as virEventAddHandle() or virConnectDomainEventRegisterAny(). rXz$virEventRegisterDefaultImpl() failed)rvirEventRegisterDefaultImplrr>rrrr_dsr_cCst||||||dS)aRegisters an event implementation, to allow integration with an external event loop. Applications would use this to integrate with the libglib2 event loop, or libevent or the QT event loop. For proper event handling, it is important that the event implementation is registered before a connection to the Hypervisor is opened. Use of the virEventAddHandle() and similar APIs require that the corresponding handler is registered. Use of the virConnectDomainEventRegisterAny() and similar APIs requires that the three timeout handlers are registered. Likewise, the three timeout handlers must be registered if the remote server has been configured to send keepalive messages, or if the client intends to call virConnectSetKeepAlive(), to avoid either side from unexpectedly closing the connection due to inactivity. If an application does not need to integrate with an existing event loop implementation, then the virEventRegisterDefaultImpl() method can be used to setup the generic libvirt implementation. Once registered, the event loop implementation cannot be changed, and must be run continuously. Note that callbacks may remain registered for a short time even after calling virConnectClose on all open connections, so it is not safe to stop running the event loop immediately after closing the connection. N)rvirEventRegisterImpl)Z addHandleZ updateHandleZ removeHandleZ addTimeoutZ updateTimeoutZ removeTimeoutrrrraysracCst|}|dkrtd|S)zUnregister a callback from a file handle. This function requires that an event loop has previously been registered with virEventRegisterImpl() or virEventRegisterDefaultImpl(). rXzvirEventRemoveHandle() failed)rvirEventRemoveHandler)rCr>rrrrbs rbcCst|}|dkrtd|S)zUnregister a callback for a timer. This function requires that an event loop has previously been registered with virEventRegisterImpl() or virEventRegisterDefaultImpl(). rXzvirEventRemoveTimeout() failed)rvirEventRemoveTimeoutr)rOr>rrrrcs rccCst}|dkrtd|S)aRun one iteration of the event loop. Applications will generally want to have a thread which invokes this method in an infinite loop. Furthermore, it is wise to set up a pipe-to-self handler (via virEventAddHandle()) or a timeout (via virEventAddTimeout()) before calling this function, as it will block forever if there are no registered events. static bool quit; while (!quit) { if (virEventRunDefaultImpl() < 0) ...print error... } rXzvirEventRunDefaultImpl() failed)rvirEventRunDefaultImplrr`rrrrdsrdcCst||dS)zChange event set for a monitored file handle. This function requires that an event loop has previously been registered with virEventRegisterImpl() or virEventRegisterDefaultImpl(). Will not fail if fd exists. N)rvirEventUpdateHandle)rCrQrrrresrecCst||dS)afChange frequency for a timer. This function requires that an event loop has previously been registered with virEventRegisterImpl() or virEventRegisterDefaultImpl(). Setting frequency to -1 will disable the timer. Setting the frequency to zero will cause it to fire on every event loop iteration. Will not fail if timer exists. N)rvirEventUpdateTimeout)rOrZrrrrfs rfcCs t}|S)zProvide a pointer to the last error caught at the library level The error object is kept in thread local storage, so separate threads can safely access this concurrently. )rrr`rrrrsrcCst}|dkrtd|S)z6Get the most recent error code (enum virErrorNumber). rXzvirGetLastErrorCode() failed)rvirGetLastErrorCoderr`rrrrgsrgcCst}|dkrtd|S)z8Get the most recent error domain (enum virErrorDomain). rXzvirGetLastErrorDomain() failed)rvirGetLastErrorDomainrr`rrrrhsrhcCst}|durtd|S)z"Get the most recent error message NzvirGetLastErrorMessage() failed)rvirGetLastErrorMessagerr`rrrrisricCst}|dkrtd|S)aInitialize the library. This method is invoked automatically by any of the virConnectOpen() API calls, and by virGetVersion(). Since release 1.0.0, there is no need to call this method even in a multithreaded application, since initialization is performed in a thread safe manner; but applications using an older version of the library should manually call this before setting up competing threads that attempt virConnectOpen in parallel. The only other time it would be necessary to call virInitialize is if the application did not invoke virConnectOpen as its first API call, such as when calling virEventRegisterImpl() before setting up connections, or when using virSetErrorFunc() to alter error reporting of the first connection attempt. rXzvirInitialize() failed)r virInitializerr`rrrrjsrjcCs tdS)zReset the last error caught at the library level. The error object is kept in thread local storage, so separate threads can safely access this concurrently, only resetting their own error object. N)rvirResetLastErrorrrrrrksrkc@seZdZdfddZddZddZdd Zd d Zd d ZddZ ddZ dgddZ ddZ dhddZ diddZdjddZddZdkdd Zdld!d"Zdmd#d$Zd%d&Zd'd(Zdnd)d*Zdod+d,Zdpd-d.Zdqd/d0Zdrd1d2Zdsd3d4Zdtd5d6Zdud7d8Zdvd9d:Zdwd;d<Zdxd=d>Z dyd?d@Z!dzdAdBZ"d{dCdDZ#dEdFZ$d|dGdHZ%d}dIdJZ&d~dKdLZ'ddMdNZ(ddOdPZ)ddQdRZ*dSdTZ+ddUdVZ,ddWdXZ-ddYdZZ.d[d\Z/dd]d^Z0d_d`Z1ddadbZ2ddcddZ3ddedfZ4ddgdhZ5ddidjZ6ddkdlZ7ddmdnZ8ddodpZ9ddqdrZ:ddsdtZ;ddudvZ<ddwdxZ=ddydzZ>d{d|Z?dd}d~Z@dddZAdddZBddZCdddZDddZEddZFddZGddZHdddZIdddZJdddZKdddZLdddZMdddZNddZOddZPdddZQdddZRddZSdddZTdddZUdddZVdddZWdddZXdddZYdddZZdddZ[dddZ\dddZ]dddZ^dddZ_dddZ`dddZaddd„ZbddĄZcdddƄZddddȄZedddʄZfddd̄Zgddd΄ZhdddЄZiddd҄ZjdddԄZkdddքZlddd؄ZmddڄZnddd܄ZodddބZpdddZqdddZrddZsdddZtddZudddZvdddZwddZxdddZyddZzdddZ{ddZ|ddZ}dddZ~dddZddZddZdÐddZdĐddZdŐddZdƐddZdǐd d ZdȐd d Zdɐd dZdʐddZddZddZdːddZd̐ddZd͐ddZdΐddZdϐddZdАdd Zd!d"Zdѐd#d$ZdҐd%d&ZdӐd'd(ZdԐd)d*Zd+d,ZdՐd-d.Zd/d0Zd֐d1d2Zdאd3d4Zdؐd5d6Zdِd7d8Zdڐd9d:Zdېd;d<Zdܐd=d>Zdݐd?d@ZdAdBZdCdDZdސdEdFZdߐdGdHZddIdJZdKdLZddMdNZdeedOdPdQdRZdeedSdPdTdUZdeeeddVdWdXZdeeeedYdZd[ZdeeeedYd\d]ZdeedPd^d_Zdeeed`dadbZdeeeeedcdddeZdS(rNcCs.||_t|jdvr$tdt|||_dSN)Z PyCapsuleZ PyCObjectz&Expected a wrapped C Object but got %s_conntyper1r_orconnr=rrrrszvirDomain.__init__cCs |jdurt|jd|_dSrH)rprZ virDomainFreer rrr__del__s  zvirDomain.__del__cCs|jSrHrnr rrrconnect"szvirDomain.connectcCs t|jSz"Get C pointer to underlying object)rZvirDomain_pointerrpr rrr c_pointer%szvirDomain.c_pointercCst|j}|S)z,Get the hypervisor ID number for the domain )rZvirDomainGetIDrprr>rrrID-s z virDomain.IDcCs t|j}|durtd|S)z)Get the type of domain operation system. NzvirDomainGetOSType() failed)rZvirDomainGetOSTyperprrxrrrOSType2s zvirDomain.OSTypecCs t|j}|durtd|S)z0Extract the UUID unique Identifier of a domain. NzvirDomainGetUUID() failed)rZvirDomainGetUUIDrprrxrrrUUID=s zvirDomain.UUIDcCs t|j}|durtd|S)z4Fetch globally unique ID of the domain as a string. NzvirDomainGetUUIDString() failed)rZvirDomainGetUUIDStringrprrxrrr UUIDStringDs zvirDomain.UUIDStringrcCs"t|j|}|durtd|S)aProvide an XML description of the domain. The description may be reused later to relaunch the domain with virDomainCreateXML(). No security-sensitive data will be included unless @flags contains VIR_DOMAIN_XML_SECURE; this flag is rejected on read-only connections. If @flags includes VIR_DOMAIN_XML_INACTIVE, then the XML represents the configuration that will be used on the next boot of a persistent domain; otherwise, the configuration represents the currently running domain. If @flags contains VIR_DOMAIN_XML_UPDATE_CPU, then the portion of the domain XML describing CPU capabilities is modified to match actual capabilities of the host. If @flags contains VIR_DOMAIN_XML_MIGRATABLE, the XML is altered to assist in migrations, since the source and destination may be running different libvirt versions. This may include trimming redundant or default information that might confuse an older recipient, or exposing internal details that aid a newer recipient; this flag is rejected on read-only connections, and the resulting XML might not validate against the schema, so it is mainly for internal use. NzvirDomainGetXMLDesc() failed)rZvirDomainGetXMLDescrprrr;r>rrrXMLDescOszvirDomain.XMLDesccCs t|j}|dkrtd|S)zRequests that the current background job be aborted at the soonest opportunity. In case the job is a migration in a post-copy mode, virDomainAbortJob will report an error (see virDomainMigrateStartPostCopy for more details). rXzvirDomainAbortJob() failed)rZvirDomainAbortJobrprrxrrrabortJobjs zvirDomain.abortJobcCs"t|j|}|dkrtd|S)a'Requests that the current background job be aborted at the soonest opportunity. In case the job is a migration in a post-copy mode, this function will report an error unless VIR_DOMAIN_ABORT_JOB_POSTCOPY flag is used (see virDomainMigrateStartPostCopy for more details). rXzvirDomainAbortJobFlags() failed)rZvirDomainAbortJobFlagsrprr}rrr abortJobFlagstszvirDomain.abortJobFlagscCs$t|j||}|dkr td|S)a=Dynamically add an IOThread to the domain. It is left up to the underlying virtual hypervisor to determine the valid range for an @iothread_id and determining whether the @iothread_id already exists. Note that this call can fail if the underlying virtualization hypervisor does not support it or if growing the number is arbitrarily limited. This function requires privileged access to the hypervisor. @flags may include VIR_DOMAIN_AFFECT_LIVE or VIR_DOMAIN_AFFECT_CONFIG. Both flags may be set. If VIR_DOMAIN_AFFECT_LIVE is set, the change affects a running domain and may fail if domain is not alive. If VIR_DOMAIN_AFFECT_CONFIG is set, the change affects persistent state, and will fail for transient domains. If neither flag is specified (that is, @flags is VIR_DOMAIN_AFFECT_CURRENT), then an inactive domain modifies persistent setup, while an active domain is hypervisor-dependent on whether just live or both live and persistent state is changed. rXzvirDomainAddIOThread() failed)rZvirDomainAddIOThreadrprrZ iothread_idr;r>rrr addIOThread~szvirDomain.addIOThreadcCs$t|j||}|dkr td|S)aSet how long to wait for a response from guest agent commands. By default, agent commands block forever waiting for a response. @timeout must be a value from virDomainAgentResponseTimeoutValues or positive: VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_BLOCK(-2): meaning to block forever waiting for a result. VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_DEFAULT(-1): use default timeout value. VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_NOWAIT(0): does not wait. positive value: wait for @timeout seconds In all guest-agent based APIs when a timeout happens if an actual command was send to the guest agent the returned error code will be VIR_ERR_AGENT_COMMAND_TIMEOUT. rXz)virDomainAgentSetResponseTimeout() failed)rZ virDomainAgentSetResponseTimeoutrpr)rrZr;r>rrragentSetResponseTimeoutsz!virDomain.agentSetResponseTimeoutcCs"t|j|}|dkrtd|S)a5Create a virtual device attachment to backend. This function, having hotplug semantics, is only allowed on an active domain. For compatibility, this method can also be used to change the media in an existing CDROM/Floppy device, however, applications are recommended to use the virDomainUpdateDeviceFlags method instead. Be aware that hotplug changes might not persist across a domain going into S4 state (also known as hibernation) unless you also modify the persistent domain definition. rXzvirDomainAttachDevice() failed)rZvirDomainAttachDevicerprrxmlr>rrr attachDevices zvirDomain.attachDevicecCs$t|j||}|dkr td|S)aAttach a virtual device to a domain, using the flags parameter to control how the device is attached. VIR_DOMAIN_AFFECT_CURRENT specifies that the device allocation is made based on current domain state. VIR_DOMAIN_AFFECT_LIVE specifies that the device shall be allocated to the active domain instance only and is not added to the persisted domain configuration. VIR_DOMAIN_AFFECT_CONFIG specifies that the device shall be allocated to the persisted domain configuration only. Note that the target hypervisor must return an error if unable to satisfy flags. E.g. the hypervisor driver will return failure if LIVE is specified but it only supports modifying the persisted device allocation. For compatibility, this method can also be used to change the media in an existing CDROM/Floppy device, however, applications are recommended to use the virDomainUpdateDeviceFlag method instead. Be aware that hotplug changes might not persist across a domain going into S4 state (also known as hibernation) unless you also modify the persistent domain definition. rXz#virDomainAttachDeviceFlags() failed)rZvirDomainAttachDeviceFlagsrprrrr;r>rrrattachDeviceFlagsszvirDomain.attachDeviceFlagscCs$t|j||}|dur td|S)zCFetch list of public SSH authorized keys for given user in domain. Nz&virDomainAuthorizedSSHKeysGet() failed)rZvirDomainAuthorizedSSHKeysGetrpr)ruserr;r>rrrauthorizedSSHKeysGetszvirDomain.authorizedSSHKeysGetcCs&t|j|||}|dkr"td|S)zGManipulate set of public SSH authorized keys for given user in domain. rXz&virDomainAuthorizedSSHKeysSet() failed)rZvirDomainAuthorizedSSHKeysSetrpr)rrkeysr;r>rrrauthorizedSSHKeysSetszvirDomain.authorizedSSHKeysSetcCs t|j}|dkrtd|S)z(Extract the autostart flag for a domain rXzvirDomainGetAutostart() failed)rZvirDomainGetAutostartrprrxrrr autostarts zvirDomain.autostartcCs t|j}|dkrtd|S)zProvides a boolean value indicating whether the domain is configured to be automatically started the next time the host machine boots only. rXz"virDomainGetAutostartOnce() failed)rZvirDomainGetAutostartOncerprrxrrr autostartOnces zvirDomain.autostartOncecCs&t|j|||}|dkr"td|S)a Start a point-in-time backup job for the specified disks of a running domain. A backup job is a domain job and thus mutually exclusive with any other domain job such as migration. For now, backup jobs are also mutually exclusive with any other block job on the same device, although this restriction may be lifted in a future release. Progress of the backup job can be tracked via virDomainGetJobStats(). Completion of the job is also announced asynchronously via VIR_DOMAIN_EVENT_ID_JOB_COMPLETED event. There are two fundamental backup approaches. The first, called a push model, instructs the hypervisor to copy the state of the guest disk to the designated storage destination (which may be on the local file system or a network device). In this mode, the hypervisor writes the content of the guest disk to the destination, then emits VIR_DOMAIN_EVENT_ID_JOB_COMPLETED when the backup is either complete or failed (the backup image is invalid if the job fails or virDomainAbortJob() is used prior to the event being emitted). This kind of the job finishes automatically. Users can determine success by using virDomainGetJobStats() with VIR_DOMAIN_JOB_STATS_COMPLETED flag. The second, called a pull model, instructs the hypervisor to expose the state of the guest disk over an NBD export. A third-party client can then connect to this export and read whichever portions of the disk it desires. In this mode libvirt has to be informed via virDomainAbortJob() when the third-party NBD client is done and the backup resources can be released. The @backupXML parameter contains details about the backup in the top-level element , including which backup mode to use, whether the backup is incremental from a previous checkpoint, which disks participate in the backup, the destination for a push model backup, and the temporary storage and NBD server details for a pull model backup. virDomainBackupGetXMLDesc() can be called to learn actual values selected. For more information, see https://libvirt.org/formatbackup.html#backup-xml The @checkpointXML parameter is optional; if non-None, then libvirt behaves as if virDomainCheckpointCreateXML() were called to create a checkpoint atomically covering the same point in time as the backup. The VIR_DOMAIN_BACKUP_BEGIN_REUSE_EXTERNAL specifies that the output or temporary files described by the @backupXML document were created by the caller with correct format and size to hold the backup or temporary data. When the VIR_DOMAIN_BACKUP_BEGIN_PRESERVE_SHUTDOWN_DOMAIN flag is used libvirt will not terminate the VM if the guest OS shuts down while the backup is running. The VM will be kept in the VIR_DOMAIN_PAUSED state until the backup job finishes or until it's resumed via virDomainResume. The creation of a new checkpoint allows for future incremental backups. Note that some hypervisors may require a particular disk format, such as qcow2, in order to take advantage of checkpoints, while allowing arbitrary formats if checkpoints are not involved. rXzvirDomainBackupBegin() failed)rZvirDomainBackupBeginrpr)rZ backupXMLZ checkpointXMLr;r>rrr backupBegins=zvirDomain.backupBegincCs"t|j|}|durtd|S)aNQueries the configuration of the active backup job. In some cases, a user can start a backup job without supplying all details and rely on libvirt to fill in the rest (for example, selecting the port used for an NBD export). This API can then be used to learn what default values were chosen. Nz"virDomainBackupGetXMLDesc() failed)rZvirDomainBackupGetXMLDescrprr}rrrbackupGetXMLDesc9szvirDomain.backupGetXMLDesccCs"t|j|}|durtd|S)zGet the blkio parameters Nz$virDomainGetBlkioParameters() failed)rZvirDomainGetBlkioParametersrprr}rrrblkioParametersIszvirDomain.blkioParameterscCs*t|j|||||}|dkr&td|S)aCommit changes that were made to temporary top-level files within a disk image backing file chain into a lower-level base file. In other words, take all the difference between @base and @top, and update @base to contain that difference; after the commit, any portion of the chain that previously depended on @top will now depend on @base, and all files after @base up to and including @top will now be invalidated. A typical use of this command is to reduce the length of a backing file chain after taking an external disk snapshot. To move data in the opposite direction, see virDomainBlockPull(). This command starts a long-running commit block job, whose status may be tracked by virDomainBlockJobInfo() with a job type of VIR_DOMAIN_BLOCK_JOB_TYPE_COMMIT, and the operation can be aborted with virDomainBlockJobAbort(). When finished, an asynchronous event is raised to indicate the final status, and the job no longer exists. If the job is aborted, it is up to the hypervisor whether starting a new job will resume from the same point, or start over. As a special case, if @top is the active image (or None), and @flags includes VIR_DOMAIN_BLOCK_COMMIT_ACTIVE, the block job will have a type of VIR_DOMAIN_BLOCK_JOB_TYPE_ACTIVE_COMMIT, and operates in two phases. In the first phase, the contents are being committed into @base, and the job can only be canceled. The job transitions to the second phase when the block job event with state VIR_DOMAIN_BLOCK_JOB_READY is emitted for the given device. This information is also visible in the live XML as 'ready="yes"' attribute of the corresponding element. Once in the second phase, the user must choose whether to cancel the job (keeping @top as the active image, but now containing only the changes since the time the job ended) or to pivot the job (adjusting to @base as the active image, and invalidating @top). Be aware that this command may invalidate files even if it is aborted; the user is cautioned against relying on the contents of invalidated intermediate files such as @top (when @top is not the active image) without manually rebasing those files to use a backing file of a read-only copy of @base prior to the point where the commit operation was started (and such a rebase cannot be safely done until the commit has successfully completed). However, the domain itself will not have any issues; the active layer remains valid throughout the entire commit operation. Some hypervisors may support a shortcut where if @flags contains VIR_DOMAIN_BLOCK_COMMIT_DELETE, then this command will unlink all files that were invalidated, after the commit successfully completes. If @flags contains VIR_DOMAIN_BLOCK_COMMIT_RELATIVE, the name recorded into the overlay of the @top image (if there is such image) as the path to the new backing file will be kept relative to other images. The operation will fail if libvirt can't infer the name. By default, if @base is None, the commit target will be the bottom of the backing chain; if @flags contains VIR_DOMAIN_BLOCK_COMMIT_SHALLOW, then the immediate backing file of @top will be used instead. If @top is None, the active image at the top of the chain will be used. Some hypervisors place restrictions on how much can be committed, and might fail if @base is not the immediate backing file of @top, or if @top is the active layer in use by a running domain but @flags did not include VIR_DOMAIN_BLOCK_COMMIT_ACTIVE, or if @top is not the top-most file; restrictions may differ for online vs. offline domains. The @disk parameter is either an unambiguous source name of the block device (the sub-element, such as "/path/to/image"), or the device target shorthand (the sub-element, such as "vda"). Valid names can be found by calling virDomainGetXMLDesc() and inspecting elements within //domain/devices/disk. The @base and @top parameters can be either paths to files within the backing chain, or the device target shorthand (the sub-element, such as "vda") followed by an index to the backing chain enclosed in square brackets. Backing chain indexes can be found by inspecting //disk//backingStore/@index in the domain XML. Thus, for example, "vda[3]" refers to the backing store with index equal to "3" in the chain of disk "vda". The maximum bandwidth that will be used to do the commit can be specified with the @bandwidth parameter. If set to 0, there is no limit. If @flags includes VIR_DOMAIN_BLOCK_COMMIT_BANDWIDTH_BYTES, @bandwidth is in bytes/second; otherwise, it is in MiB/second. Values larger than 2^52 bytes/sec may be rejected due to overflow considerations based on the word size of both client and server, and values larger than 2^31 bytes/sec may cause overflow problems if later queried by virDomainGetBlockJobInfo() without scaling. Hypervisors may further restrict the range of valid bandwidth values. Some hypervisors do not support this feature and will return an error if bandwidth is not 0; in this case, it might still be possible for a later call to virDomainBlockJobSetSpeed() to succeed. The actual speed can be determined with virDomainGetBlockJobInfo(). rXzvirDomainBlockCommit() failed)rZvirDomainBlockCommitrpr)rdiskbasetop bandwidthr;r>rrr blockCommitTsZzvirDomain.blockCommitcCs(t|j||||}|dkr$td|S)zSCopy the guest-visible contents of a disk image to a new file described by destxml rXzvirDomainBlockCopy() failed)rZvirDomainBlockCopyrpr)rrZdestxmlparamsr;r>rrr blockCopyszvirDomain.blockCopycCs$t|j||}|dur td|S)z5Extract information about a domain block device size NzvirDomainGetBlockInfo() failed)rZvirDomainGetBlockInforprrpathr;r>rrr blockInfoszvirDomain.blockInfocCs$t|j||}|dur td|S)z(Get the I/O tunables for a block device Nz virDomainGetBlockIoTune() failed)rZvirDomainGetBlockIoTunerprrrr;r>rrr blockIoTuneszvirDomain.blockIoTunecCs$t|j||}|dkr td|S)aCancel the active block job on the given disk. The @disk parameter is either an unambiguous source name of the block device (the sub-element, such as "/path/to/image"), or (since 0.9.5) the device target shorthand (the sub-element, such as "vda"). Valid names can be found by calling virDomainGetXMLDesc() and inspecting elements within //domain/devices/disk. If the current block job for @disk is VIR_DOMAIN_BLOCK_JOB_TYPE_PULL, then by default, this function performs a synchronous operation and the caller may assume that the operation has completed when 0 is returned. However, BlockJob operations may take a long time to cancel, and during this time further domain interactions may be unresponsive. To avoid this problem, pass VIR_DOMAIN_BLOCK_JOB_ABORT_ASYNC in the @flags argument to enable asynchronous behavior, returning as soon as possible. When the job has been canceled, a BlockJob event will be emitted, with status VIR_DOMAIN_BLOCK_JOB_CANCELED (even if the ABORT_ASYNC flag was not used); it is also possible to poll virDomainBlockJobInfo() to see if the job cancellation is still pending. This type of job can be restarted to pick up from where it left off. If the current block job for @disk is VIR_DOMAIN_BLOCK_JOB_TYPE_COPY, then the default is to abort the mirroring and revert to the source disk; likewise, if the current job is VIR_DOMAIN_BLOCK_JOB_TYPE_ACTIVE_COMMIT, the default is to abort without changing the active layer of @disk. Adding @flags of VIR_DOMAIN_BLOCK_JOB_ABORT_PIVOT causes this call to fail with VIR_ERR_BLOCK_COPY_ACTIVE if the copy or commit is not yet ready; otherwise it will swap the disk over to the new active image to end the mirroring or active commit. An event will be issued when the job is ended, and it is possible to use VIR_DOMAIN_BLOCK_JOB_ABORT_ASYNC to control whether this command waits for the completion of the job. Restarting a copy or active commit job requires starting over from the beginning of the first phase. rXzvirDomainBlockJobAbort() failed)rZvirDomainBlockJobAbortrprrrrr blockJobAborts#zvirDomain.blockJobAbortcCs$t|j||}|dur td|S)z)Get progress information for a block job Nz!virDomainGetBlockJobInfo() failed)rZvirDomainGetBlockJobInforprrrrr blockJobInfoszvirDomain.blockJobInfocCs&t|j|||}|dkr"td|S)aLSet the maximum allowable bandwidth that a block job may consume. If bandwidth is 0, the limit will revert to the hypervisor default of unlimited. If @flags contains VIR_DOMAIN_BLOCK_JOB_SPEED_BANDWIDTH_BYTES, @bandwidth is in bytes/second; otherwise, it is in MiB/second. Values larger than 2^52 bytes/sec may be rejected due to overflow considerations based on the word size of both client and server, and values larger than 2^31 bytes/sec may cause overflow problems if later queried by virDomainGetBlockJobInfo() without scaling. Hypervisors may further restrict the range of valid bandwidth values. The @disk parameter is either an unambiguous source name of the block device (the sub-element, such as "/path/to/image"), or (since 0.9.5) the device target shorthand (the sub-element, such as "vda"). Valid names can be found by calling virDomainGetXMLDesc() and inspecting elements within //domain/devices/disk. rXz"virDomainBlockJobSetSpeed() failed)rZvirDomainBlockJobSetSpeedrprrrrr;r>rrrblockJobSetSpeedszvirDomain.blockJobSetSpeedcCs(t|j||||}|dur$td|S)z*Read the contents of domain's disk device NzvirDomainBlockPeek() failed)rZvirDomainBlockPeekrpr)rroffsetsizer;r>rrr blockPeek#szvirDomain.blockPeekcCs&t|j|||}|dkr"td|S)aPopulate a disk image with data from its backing image. Once all data from its backing image has been pulled, the disk no longer depends on a backing image. This function pulls data for the entire device in the background. Progress of the operation can be checked with virDomainGetBlockJobInfo() and the operation can be aborted with virDomainBlockJobAbort(). When finished, an asynchronous event is raised to indicate the final status. To move data in the opposite direction, see virDomainBlockCommit(). The @disk parameter is either an unambiguous source name of the block device (the sub-element, such as "/path/to/image"), or (since 0.9.5) the device target shorthand (the sub-element, such as "vda"). Valid names can be found by calling virDomainGetXMLDesc() and inspecting elements within //domain/devices/disk. The maximum bandwidth that will be used to do the copy can be specified with the @bandwidth parameter. If set to 0, there is no limit. If @flags includes VIR_DOMAIN_BLOCK_PULL_BANDWIDTH_BYTES, @bandwidth is in bytes/second; otherwise, it is in MiB/second. Values larger than 2^52 bytes/sec may be rejected due to overflow considerations based on the word size of both client and server, and values larger than 2^31 bytes/sec may cause overflow problems if later queried by virDomainGetBlockJobInfo() without scaling. Hypervisors may further restrict the range of valid bandwidth values. Some hypervisors do not support this feature and will return an error if bandwidth is not 0; in this case, it might still be possible for a later call to virDomainBlockJobSetSpeed() to succeed. The actual speed can be determined with virDomainGetBlockJobInfo(). This is shorthand for virDomainBlockRebase() with a None base. rXzvirDomainBlockPull() failed)rZvirDomainBlockPullrprrrrr blockPull.s zvirDomain.blockPullcCs(t|j||||}|dkr$td|S)aPopulate a disk image with data from its backing image chain, and setting the backing image to @base, or alternatively copy an entire backing chain to a new file @base. When @flags is 0, this starts a pull, where @base must be the absolute path of one of the backing images further up the chain, or None to convert the disk image so that it has no backing image. Once all data from its backing image chain has been pulled, the disk no longer depends on those intermediate backing images. This function pulls data for the entire device in the background. Progress of the operation can be checked with virDomainGetBlockJobInfo() with a job type of VIR_DOMAIN_BLOCK_JOB_TYPE_PULL, and the operation can be aborted with virDomainBlockJobAbort(). When finished, an asynchronous event is raised to indicate the final status, and the job no longer exists. If the job is aborted, a new one can be started later to resume from the same point. If @flags contains VIR_DOMAIN_BLOCK_REBASE_RELATIVE, the name recorded into the active disk as the location for @base will be kept relative. The operation will fail if libvirt can't infer the name. When @flags includes VIR_DOMAIN_BLOCK_REBASE_COPY, this starts a copy, where @base must be the name of a new file to copy the chain to. By default, the copy will pull the entire source chain into the destination file, but if @flags also contains VIR_DOMAIN_BLOCK_REBASE_SHALLOW, then only the top of the source chain will be copied (the source and destination have a common backing file). By default, @base will be created with the same file format as the source, but this can be altered by adding VIR_DOMAIN_BLOCK_REBASE_COPY_RAW to force the copy to be raw (does not make sense with the shallow flag unless the source is also raw), or by using VIR_DOMAIN_BLOCK_REBASE_REUSE_EXT to reuse an existing file which was pre-created with the correct format and metadata and sufficient size to hold the copy. In case the VIR_DOMAIN_BLOCK_REBASE_SHALLOW flag is used the pre-created file has to exhibit the same guest visible contents as the backing file of the original image. This allows a management app to pre-create files with relative backing file names, rather than the default of absolute backing file names; as a security precaution, you should generally only use reuse_ext with the shallow flag and a non-raw destination file. By default, the copy destination will be treated as type='file', but using VIR_DOMAIN_BLOCK_REBASE_COPY_DEV treats the destination as type='block' (affecting how virDomainGetBlockInfo() will report allocation after pivoting). A copy job has two parts; in the first phase, the @bandwidth parameter affects how fast the source is pulled into the destination, and the job can only be canceled by reverting to the source file; progress in this phase can be tracked via the virDomainBlockJobInfo() command, with a job type of VIR_DOMAIN_BLOCK_JOB_TYPE_COPY. The job transitions to the second phase when the job info states cur == end, and remains alive to mirror all further changes to both source and destination. The user must call virDomainBlockJobAbort() to end the mirroring while choosing whether to revert to source or pivot to the destination. An event is issued when the job ends, and depending on the hypervisor, an event may also be issued when the job transitions from pulling to mirroring. If the job is aborted, a new job will have to start over from the beginning of the first phase. Some hypervisors will restrict certain actions, such as virDomainSave() or virDomainDetachDevice(), while a copy job is active; they may also restrict a copy job to transient domains. The @disk parameter is either an unambiguous source name of the block device (the sub-element, such as "/path/to/image"), or the device target shorthand (the sub-element, such as "vda"). Valid names can be found by calling virDomainGetXMLDesc() and inspecting elements within //domain/devices/disk. The @base parameter can be either a path to a file within the backing chain, or the device target shorthand (the sub-element, such as "vda") followed by an index to the backing chain enclosed in square brackets. Backing chain indexes can be found by inspecting //disk//backingStore/@index in the domain XML. Thus, for example, "vda[3]" refers to the backing store with index equal to "3" in the chain of disk "vda". The maximum bandwidth that will be used to do the copy can be specified with the @bandwidth parameter. If set to 0, there is no limit. If @flags includes VIR_DOMAIN_BLOCK_REBASE_BANDWIDTH_BYTES, @bandwidth is in bytes/second; otherwise, it is in MiB/second. Values larger than 2^52 bytes/sec may be rejected due to overflow considerations based on the word size of both client and server, and values larger than 2^31 bytes/sec may cause overflow problems if later queried by virDomainGetBlockJobInfo() without scaling. Hypervisors may further restrict the range of valid bandwidth values. Some hypervisors do not support this feature and will return an error if bandwidth is not 0; in this case, it might still be possible for a later call to virDomainBlockJobSetSpeed() to succeed. The actual speed can be determined with virDomainGetBlockJobInfo(). When @base is None and @flags is 0, this is identical to virDomainBlockPull(). When @flags contains VIR_DOMAIN_BLOCK_REBASE_COPY, this command is shorthand for virDomainBlockCopy() where the destination XML encodes @base as a , @bandwidth is properly scaled and passed as a typed parameter, the shallow and reuse external flags are preserved, and remaining flags control whether the XML encodes a destination format of raw instead of leaving the destination identical to the source format or probed from the reused file. rXzvirDomainBlockRebase() failed)rZvirDomainBlockRebaserpr)rrrrr;r>rrr blockRebaseSsdzvirDomain.blockRebasecCs&t|j|||}|dkr"td|S)asResize a block device of domain while the domain is running. If @flags is 0, then @size is in kibibytes (blocks of 1024 bytes); since 0.9.11, if @flags includes VIR_DOMAIN_BLOCK_RESIZE_BYTES, @size is in bytes instead. @size is taken directly as the new size. Depending on the file format, the hypervisor may round up to the next alignment boundary. If @flag contains VIR_DOMAIN_BLOCK_RESIZE_CAPACITY (since 10.0.0) the hypervisor will resize the guest block device to fully fill the source. @size must be either set to zero, or to the exact size of the block device source. This is possible only for image formats with no metadata ('raw') and for source devices with limited capacity such as block devices. The @disk parameter is either an unambiguous source name of the block device (the sub-element, such as "/path/to/image"), or (since 0.9.5) the device target shorthand (the sub-element, such as "vda"). Valid names can be found by calling virDomainGetXMLDesc() and inspecting elements within //domain/devices/disk. Note that this call may fail if the underlying virtualization hypervisor does not support it; this call requires privileged access to the hypervisor. rXzvirDomainBlockResize() failed)rZvirDomainBlockResizerpr)rrrr;r>rrr blockResizeszvirDomain.blockResizecCs"t|j|}|durtd|S)z.Extracts block device statistics for a domain NzvirDomainBlockStats() failed)rZvirDomainBlockStatsrprrrr>rrr blockStatsszvirDomain.blockStatscCs$t|j||}|dur td|S)z@Extracts block device statistics parameters of a running domain Nz!virDomainBlockStatsFlags() failed)rZvirDomainBlockStatsFlagsrprrrrrblockStatsFlagsszvirDomain.blockStatsFlagscCs0t|j||}|dur tdt||d}|S)a: Create a new checkpoint using @xmlDesc, with a top-level element, on a running @domain. Note that @xmlDesc must validate against the XML schema. Typically, it is more common to create a new checkpoint as part of kicking off a backup job with virDomainBackupBegin(); however, it is also possible to start a checkpoint without a backup. See https://libvirt.org/formatcheckpoint.html#checkpoint-xml for more details on @xmlDesc. In particular, some hypervisors may require particular disk formats, such as qcow2, in order to support this command; where @xmlDesc can be used to limit the checkpoint to a working subset of the domain's disks. If @flags includes VIR_DOMAIN_CHECKPOINT_CREATE_REDEFINE, then this is a request to reinstate checkpoint metadata that was previously captured from virDomainCheckpointGetXMLDesc() before removing that metadata, rather than creating a new checkpoint. Note that while original creation can omit a number of elements from @xmlDesc (and libvirt will supply sane defaults based on the domain state at that point in time), a redefinition must supply more elements (as the domain may have changed in the meantime, so that libvirt no longer has a way to resupply correct defaults). Not all hypervisors support this flag. If @flags includes VIR_DOMAIN_CHECKPOINT_CREATE_REDEFINE_VALIDATE along with VIR_DOMAIN_CHECKPOINT_CREATE_REDEFINE the state of the metadata related to the disk state of the redefined checkpoint is validated. Note that hypervisors may require that the @domain is running to perform validation. If @flags includes VIR_DOMAIN_CHECKPOINT_CREATE_QUIESCE, then the libvirt will attempt to use guest agent to freeze and thaw all file systems in use within domain OS. However, if the guest agent is not present, an error is thrown. This flag is incompatible with VIR_DOMAIN_CHECKPOINT_CREATE_REDEFINE. Note: A checkpoint represents point in time after which blocks changed by the hypervisor are tracked. The tracking of changed blocks notes only whether a block was modified, but does not preserve the old contents. The main purpose of checkpoints is to enable incremental backups. But for a checkpoint to be useful for this purpose, a backup must be performed at the same time as the checkpoint is created. This is done via the virDomainBackupBegin API, which also allows to create a checkpoint at the same time. Creating checkpoints with virDomainCheckpointCreateXML is generally only useful for re-creating the libvirt metadata. Nz%virDomainCheckpointCreateXML() failedr<)rZvirDomainCheckpointCreateXMLrprvirDomainCheckpointrxmlDescr;r>_virDomain__tmprrrcheckpointCreateXMLs . zvirDomain.checkpointCreateXMLcCs0t|j||}|dur tdt||d}|S)z5Try to lookup a domain checkpoint based on its name. Nz(virDomainCheckpointLookupByName() failedr<)rZvirDomainCheckpointLookupByNamerprrrr@r;r>rrrrcheckpointLookupByName#s  z virDomain.checkpointLookupByNamecCs"t|j|}|durtd|S)zFExtract details about current state of control interface to a domain. Nz virDomainGetControlInfo() failed)rZvirDomainGetControlInforprr}rrr controlInfo/szvirDomain.controlInfocCs$t|j||}|dkr td|S)a^This method will dump the core of a domain on a given file for analysis. Note that for remote Xen Daemon the file path will be interpreted in the remote host. Hypervisors may require the user to manually ensure proper permissions on the file named by @to. If @flags includes VIR_DUMP_CRASH, then leave the guest shut off with a crashed state after the dump completes. If @flags includes VIR_DUMP_LIVE, then make the core dump while continuing to allow the guest to run; otherwise, the guest is suspended during the dump. VIR_DUMP_RESET flag forces reset of the guest after dump. The above three flags are mutually exclusive. Additionally, if @flags includes VIR_DUMP_BYPASS_CACHE, then libvirt will attempt to bypass the file system cache while creating the file, or fail if it cannot do so for the given system; this can allow less pressure on file system cache, but also risks slowing saves to NFS. For more control over the output format, see virDomainCoreDumpWithFormat(). rXzvirDomainCoreDump() failed)rZvirDomainCoreDumprpr)rtor;r>rrrcoreDump:szvirDomain.coreDumpcCs&t|j|||}|dkr"td|S)aThis method will dump the core of a domain on a given file for analysis. Note that for remote Xen Daemon the file path will be interpreted in the remote host. Hypervisors may require the user to manually ensure proper permissions on the file named by @to. @dumpformat controls which format the dump will have; use of VIR_DOMAIN_CORE_DUMP_FORMAT_RAW mirrors what virDomainCoreDump() will perform. Not all hypervisors are able to support all formats. If @flags includes VIR_DUMP_CRASH, then leave the guest shut off with a crashed state after the dump completes. If @flags includes VIR_DUMP_LIVE, then make the core dump while continuing to allow the guest to run; otherwise, the guest is suspended during the dump. VIR_DUMP_RESET flag forces reset of the guest after dump. The above three flags are mutually exclusive. Additionally, if @flags includes VIR_DUMP_BYPASS_CACHE, then libvirt will attempt to bypass the file system cache while creating the file, or fail if it cannot do so for the given system; this can allow less pressure on file system cache, but also risks slowing saves to NFS. rXz$virDomainCoreDumpWithFormat() failed)rZvirDomainCoreDumpWithFormatrpr)rrZ dumpformatr;r>rrrcoreDumpWithFormatRszvirDomain.coreDumpWithFormatcCs t|j}|dkrtd|S)aLaunch a defined domain. If the call succeeds the domain moves from the defined to the running domains pools. The domain will be paused only if restoring from managed state created from a paused domain. For more control, see virDomainCreateWithFlags(). rXzvirDomainCreate() failed)rZvirDomainCreaterprrxrrrcreatels zvirDomain.createcCs"t|j|}|dkrtd|S)aLaunch a defined domain. If the call succeeds the domain moves from the defined to the running domains pools. If the VIR_DOMAIN_START_PAUSED flag is set, or if the guest domain has a managed save image that requested paused state (see virDomainManagedSave()) the guest domain will be started, but its CPUs will remain paused. The CPUs can later be manually started using virDomainResume(). In all other cases, the guest domain will be running. If the VIR_DOMAIN_START_AUTODESTROY flag is set, the guest domain will be automatically destroyed when the virConnectPtr object is finally released. This will also happen if the client application crashes / loses its connection to the libvirtd daemon. Any domains marked for auto destroy will block attempts at migration. Hypervisors may also block save-to-file, or snapshots. If the VIR_DOMAIN_START_BYPASS_CACHE flag is set, and there is a managed save file for this domain (created by virDomainManagedSave()), then libvirt will attempt to bypass the file system cache while restoring the file, or fail if it cannot do so for the given system; this can allow less pressure on file system cache, but also risks slowing loads from NFS. If the VIR_DOMAIN_START_FORCE_BOOT flag is set, then any managed save file for this domain is discarded, and the domain boots from scratch. If @flags includes VIR_DOMAIN_START_RESET_NVRAM, then libvirt will discard any existing NVRAM file and re-initialize NVRAM from the pristine template. rXz!virDomainCreateWithFlags() failed)rZvirDomainCreateWithFlagsrprr}rrrcreateWithFlagsvszvirDomain.createWithFlagscCs$t|j||}|dkr td|S)a&Dynamically delete an IOThread from the domain. The @iothread_id to be deleted must not have a resource associated with it and can be any of the currently valid IOThread ID's. Note that this call can fail if the underlying virtualization hypervisor does not support it or if reducing the number is arbitrarily limited. This function requires privileged access to the hypervisor. @flags may include VIR_DOMAIN_AFFECT_LIVE or VIR_DOMAIN_AFFECT_CONFIG. Both flags may be set. If VIR_DOMAIN_AFFECT_LIVE is set, the change affects a running domain and may fail if domain is not alive. If VIR_DOMAIN_AFFECT_CONFIG is set, the change affects persistent state, and will fail for transient domains. If neither flag is specified (that is, @flags is VIR_DOMAIN_AFFECT_CURRENT), then an inactive domain modifies persistent setup, while an active domain is hypervisor-dependent on whether just live or both live and persistent state is changed. rXzvirDomainDelIOThread() failed)rZvirDomainDelIOThreadrprrrrr delIOThreadszvirDomain.delIOThreadcCs$t|j||}|dkr td|S)aDDelete an throttlegroup from the domain. @group cannot be None, and the @group to be deleted must not have a throttlefilter associated with it and can be any of the current valid group. @flags may include VIR_DOMAIN_AFFECT_LIVE or VIR_DOMAIN_AFFECT_CONFIG. Both flags may be set. If VIR_DOMAIN_AFFECT_LIVE is set, the change affects a running domain and may fail if domain is not alive. If VIR_DOMAIN_AFFECT_CONFIG is set, the change affects persistent state, and will fail for transient domains. If neither flag is specified (that is, @flags is VIR_DOMAIN_AFFECT_CURRENT), then an inactive domain modifies persistent setup, while an active domain is hypervisor-dependent on whether just live or both live and persistent state is changed. rXz"virDomainDelThrottleGroup() failed)rZvirDomainDelThrottleGrouprpr)rgroupr;r>rrrdelThrottleGroupszvirDomain.delThrottleGroupcCs t|j}|dkrtd|S)aDestroy the domain object. The running instance is shutdown if not down already and all resources used by it are given back to the hypervisor. This does not free the associated virDomainPtr object. This function may require privileged access. virDomainDestroy first requests that a guest terminate (e.g. SIGTERM), then waits for it to comply. After a reasonable timeout, if the guest still exists, virDomainDestroy will forcefully terminate the guest (e.g. SIGKILL) if necessary (which may produce undesirable results, for example unflushed disk cache in the guest). To avoid this possibility, it's recommended to instead call virDomainDestroyFlags, sending the VIR_DOMAIN_DESTROY_GRACEFUL flag. If the domain is transient and has any snapshot metadata (see virDomainSnapshotNum()), then that metadata will automatically be deleted when the domain quits. rXzvirDomainDestroy() failed)rZvirDomainDestroyrprrxrrrdestroys zvirDomain.destroycCs"t|j|}|dkrtd|S)aDestroy the domain object. The running instance is shutdown if not down already and all resources used by it are given back to the hypervisor. This does not free the associated virDomainPtr object. This function may require privileged access. Calling this function with no @flags set (equal to zero) is equivalent to calling virDomainDestroy, and after a reasonable timeout will forcefully terminate the guest (e.g. SIGKILL) if necessary (which may produce undesirable results, for example unflushed disk cache in the guest). Including VIR_DOMAIN_DESTROY_GRACEFUL in the flags will prevent the forceful termination of the guest, and virDomainDestroyFlags will instead return an error if the guest doesn't terminate by the end of the timeout; at that time, the management application can decide if calling again without VIR_DOMAIN_DESTROY_GRACEFUL is appropriate. If VIR_DOMAIN_DESTROY_REMOVE_LOGS flag is set then domain specific logs will be deleted as well if there are any. Note that not all deployments are be supported. For example in case of QEMU driver this flags is noop if virtlogd is not used for handling QEMU process output. Another alternative which may produce cleaner results for the guest's disks is to use virDomainShutdown() instead, but that depends on guest support (some hypervisor/guest combinations may ignore the shutdown request). rXzvirDomainDestroyFlags() failed)rZvirDomainDestroyFlagsrprr}rrr destroyFlagsszvirDomain.destroyFlagscCs"t|j|}|dkrtd|S)zThis is an equivalent of virDomainDetachDeviceFlags() when called with @flags parameter set to VIR_DOMAIN_AFFECT_LIVE. See virDomainDetachDeviceFlags() for more details. rXzvirDomainDetachDevice() failed)rZvirDomainDetachDevicerprrrrr detachDeviceszvirDomain.detachDevicecCs$t|j||}|dkr td|S)aDetach a virtual device from a domain, using the alias to specify the device. The value of @flags should be either VIR_DOMAIN_AFFECT_CURRENT, or a bitwise-or of values from VIR_DOMAIN_AFFECT_LIVE and VIR_DOMAIN_AFFECT_CURRENT, although hypervisors vary in which flags are supported. In contrast to virDomainDetachDeviceFlags() this API is asynchronous - it returns immediately after sending the detach request to the hypervisor. It's caller's responsibility to wait for VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event to signal actual device removal or for VIR_DOMAIN_EVENT_ID_DEVICE_REMOVAL_FAILED to signal rejected device removal. rXz#virDomainDetachDeviceAlias() failed)rZvirDomainDetachDeviceAliasrpr)raliasr;r>rrrdetachDeviceAliasszvirDomain.detachDeviceAliascCs$t|j||}|dkr td|S)a Detach a virtual device from a domain, using the flags parameter to control how the device is detached. VIR_DOMAIN_AFFECT_CURRENT specifies that the device allocation is removed based on current domain state. VIR_DOMAIN_AFFECT_LIVE specifies that the device shall be deallocated from the active domain instance only and is not from the persisted domain configuration. VIR_DOMAIN_AFFECT_CONFIG specifies that the device shall be deallocated from the persisted domain configuration only. Note that the target hypervisor must return an error if unable to satisfy flags. E.g. the hypervisor driver will return failure if LIVE is specified but it only supports removing the persisted device allocation. Some hypervisors may prevent this operation if there is a current block job running operation on the device being detached; in that case, use virDomainBlockJobAbort() to stop the block job first. Beware that depending on the hypervisor and device type, detaching a device from a running domain may be asynchronous. That is, calling virDomainDetachDeviceFlags may just request device removal while the device is actually removed later (in cooperation with a guest OS). Previously, this fact was ignored and the device could have been removed from domain configuration before it was actually removed by the hypervisor causing various failures on subsequent operations. To check whether the device was successfully removed, either recheck domain configuration using virDomainGetXMLDesc() or add a handler for the VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. In case the device is already gone when virDomainDetachDeviceFlags returns, the event is delivered before this API call ends. To help existing clients work better in most cases, this API will try to transform an asynchronous device removal that finishes shortly after the request into a synchronous removal. In other words, this API may wait a bit for the removal to complete in case it was not synchronous. Be aware that hotplug changes might not persist across a domain going into S4 state (also known as hibernation) unless you also modify the persistent domain definition. The supplied XML description of the device should be as specific as its definition in the domain XML. The set of attributes used to match the device are internal to the drivers. Using a partial definition, or attempting to detach a device that is not present in the domain XML, but shares some specific attributes with one that is present, may lead to unexpected results. rXz#virDomainDetachDeviceFlags() failed)rZvirDomainDetachDeviceFlagsrprrrrrdetachDeviceFlagss+zvirDomain.detachDeviceFlagscCs"t|j|}|durtd|S)z Extract errors on disk devices. NzvirDomainGetDiskErrors() failed)rZvirDomainGetDiskErrorsrprr}rrr diskErrorsLszvirDomain.diskErrorscCs"t|j|}|durtd|S)zAQuery the CPU affinity setting of the emulator process of domain Nz$virDomainGetEmulatorPinInfo() failed)rZvirDomainGetEmulatorPinInforprr}rrremulatorPinInfoSszvirDomain.emulatorPinInfocCs&t|j|||}|dkr"td|S)aMCalls FITRIM within the guest (hence guest agent may be required depending on hypervisor used). Either call it on each mounted filesystem (@mountPoint is None) or just on specified @mountPoint. @minimum hints that free ranges smaller than this may be ignored (this is a hint and the guest may not respect it). By increasing this value, the fstrim operation will complete more quickly for filesystems with badly fragmented free space, although not all blocks will be discarded. If @minimum is not zero, the command may fail. rXzvirDomainFSTrim() failed)rZvirDomainFSTrimrpr)rZ mountPointZminimumr;r>rrrfSTrim^s zvirDomain.fSTrimcCs"t|j|}|durtd|S)zjGet a list of mapping information for each mounted file systems within the specified guest and the disks. NzvirDomainGetFSInfo() failed)rZvirDomainGetFSInforprr}rrrfsInfoqszvirDomain.fsInfocCs$t|j||}|dur td|S)aExtracts CPU statistics for a running domain. On success it will return a list of data of dictionary type. If boolean total is False or 0, the first element of the list refers to CPU0 on the host, second element is CPU1, and so on. The format of data struct is as follows: [{cpu_time:xxx}, {cpu_time:xxx}, ...] If it is True or 1, it returns total domain CPU statistics in the format of [{cpu_time:xxx, user_time:xxx, system_time:xxx}] NzvirDomainGetCPUStats() failed)rZvirDomainGetCPUStatsrpr)rtotalr;r>rrr getCPUStatsxszvirDomain.getCPUStatscCs$t|j||}|dkr td|S)zmReload domain's graphics. This can be used to reload TLS certificates without restarting the domain. rXz virDomainGraphicsReload() failed)rZvirDomainGraphicsReloadrpr)rror;r>rrrgraphicsReloadszvirDomain.graphicsReloadcCs$t|j||}|dur td|S)z%Get aggregated info from guest agent NzvirDomainGetGuestInfo() failed)rZvirDomainGetGuestInforpr)rtypesr;r>rrr guestInfoszvirDomain.guestInfocCs"t|j|}|dkrtd|S)zBreturns a dictionary containing information regarding guest vcpus rXzvirDomainGetGuestVcpus() failed)rZvirDomainGetGuestVcpusrprr}rrr guestVcpusszvirDomain.guestVcpuscCs"t|j|}|dkrtd|S)z0Determine if the domain has a current snapshot. rXz$virDomainHasCurrentSnapshot() failed)rZvirDomainHasCurrentSnapshotrprr}rrrhasCurrentSnapshotszvirDomain.hasCurrentSnapshotcCs"t|j|}|dkrtd|S)zCheck if a domain has a managed save image as created by virDomainManagedSave(). Note that any running domain should not have such an image, as it should have been removed on restart. rXz%virDomainHasManagedSaveImage() failed)rZvirDomainHasManagedSaveImagerprr}rrrhasManagedSaveImageszvirDomain.hasManagedSaveImagecCs"t|j|}|durtd|S)zGet the hostname for that domain. If no hostname is found, then an error is raised with VIR_ERR_NO_HOSTNAME code. Dependent on hypervisor and @flags used, this may require a guest agent to be available. NzvirDomainGetHostname() failed)rZvirDomainGetHostnamerprr}rrrhostnameszvirDomain.hostnamecCs t|j}|durtd|S)zExtract information about a domain. Note that if the connection used to get the domain is limited only a partial set of the information can be extracted. NzvirDomainGetInfo() failed)rZvirDomainGetInforprrxrrrinfos zvirDomain.infocCs"t|j|}|dkrtd|S)zSend NMI to the guest rXzvirDomainInjectNMI() failed)rZvirDomainInjectNMIrprr}rrr injectNMIszvirDomain.injectNMIcCs$t|j||}|dur td|S)zPreturns a dictionary of domain interfaces along with their MAC and IP addresses Nz$virDomainInterfaceAddresses() failed)rZvirDomainInterfaceAddressesrpr)rsourcer;r>rrrinterfaceAddressesszvirDomain.interfaceAddressescCs$t|j||}|dur td|S)z2Get the bandwidth tunables for a interface device Nz(virDomainGetInterfaceParameters() failed)rZvirDomainGetInterfaceParametersrpr)rdevicer;r>rrrinterfaceParametersszvirDomain.interfaceParameterscCs"t|j|}|durtd|S)z2Extracts interface device statistics for a domain Nz virDomainInterfaceStats() failed)rZvirDomainInterfaceStatsrprrrrrinterfaceStatsszvirDomain.interfaceStatscCs"t|j|}|durtd|S)z>Query the CPU affinity setting of the IOThreads of the domain Nz!virDomainGetIOThreadInfo() failed)rZvirDomainGetIOThreadInforprr}rrr ioThreadInfoszvirDomain.ioThreadInfocCs t|j}|dkrtd|S)z-Determine if the domain is currently running rXzvirDomainIsActive() failed)rZvirDomainIsActiverprrxrrrisActives zvirDomain.isActivecCs t|j}|dkrtd|S)zsDetermine if the domain has a persistent configuration which means it will still exist after shutting down rXzvirDomainIsPersistent() failed)rZvirDomainIsPersistentrprrxrrr isPersistents zvirDomain.isPersistentcCs t|j}|dkrtd|S)z*Determine if the domain has been updated. rXzvirDomainIsUpdated() failed)rZvirDomainIsUpdatedrprrxrrr isUpdateds zvirDomain.isUpdatedcCs t|j}|durtd|S)FExtract information about an active job being processed for a domain. NzvirDomainGetJobInfo() failed)rZvirDomainGetJobInforprrxrrrjobInfos zvirDomain.jobInfocCs"t|j|}|durtd|S)rNzvirDomainGetJobStats() failed)rZvirDomainGetJobStatsrprr}rrrjobStats!szvirDomain.jobStatscCs"t|j|}|durtd|S)z&Get launch security info for a domain Nz'virDomainGetLaunchSecurityInfo() failed)rZvirDomainGetLaunchSecurityInforprr}rrrlaunchSecurityInfo(szvirDomain.launchSecurityInfocCs"t|j|}|dkrtd|S)aThis method will suspend a domain and save its memory contents to a file on disk. After the call, if successful, the domain is not listed as running anymore. The difference from virDomainSave() is that libvirt is keeping track of the saved state itself, and will reuse it once the domain is being restarted (automatically or via an explicit libvirt call). As a result any running domain is sure to not have a managed saved image. This also implies that managed save only works on persistent domains, since the domain must still exist in order to use virDomainCreate() to restart it. If @flags includes VIR_DOMAIN_SAVE_BYPASS_CACHE, then libvirt will attempt to bypass the file system cache while creating the file, or fail if it cannot do so for the given system; this can allow less pressure on file system cache, but also risks slowing saves to NFS. Normally, the managed saved state will remember whether the domain was running or paused, and start will resume to the same state. Specifying VIR_DOMAIN_SAVE_RUNNING or VIR_DOMAIN_SAVE_PAUSED in @flags will override the default saved into the file. These two flags are mutually exclusive. rXzvirDomainManagedSave() failed)rZvirDomainManagedSaverprr}rrr managedSave3szvirDomain.managedSavecCs$t|j||}|dkr td|S)aThis updates the definition of a domain stored in a saved state file. @dxml can be used to alter host-specific portions of the domain XML that will be used on the next start of the domain. For example, it is possible to alter the backing filename that is associated with a disk device. Normally, the saved state file will remember whether the domain was running or paused, and restore defaults to the same state. Specifying VIR_DOMAIN_SAVE_RUNNING or VIR_DOMAIN_SAVE_PAUSED in @flags will override the default saved into the file; omitting both leaves the file's default unchanged. These two flags are mutually exclusive. rXz&virDomainManagedSaveDefineXML() failed)rZvirDomainManagedSaveDefineXMLrpr)rdxmlr;r>rrrmanagedSaveDefineXMLNszvirDomain.managedSaveDefineXMLcCs"t|j|}|durtd|S)aThis method will extract the XML description of the managed save state file of a domain. No security-sensitive data will be included unless @flags contains VIR_DOMAIN_SAVE_IMAGE_XML_SECURE; this flag is rejected on read-only connections. Nz'virDomainManagedSaveGetXMLDesc() failed)rZvirDomainManagedSaveGetXMLDescrprr}rrrmanagedSaveGetXMLDescbszvirDomain.managedSaveGetXMLDesccCs"t|j|}|dkrtd|S)z/Remove any managed save image for this domain. rXz#virDomainManagedSaveRemove() failed)rZvirDomainManagedSaveRemoverprr}rrrmanagedSaveRemovenszvirDomain.managedSaveRemovecCs t|j}|dkrtd|S)zRetrieve the maximum amount of physical memory allocated to a domain. If domain is None, then this get the amount of memory reserved to Domain0 i.e. the domain where the application runs. rzvirDomainGetMaxMemory() failed)rZvirDomainGetMaxMemoryrprrxrrr maxMemoryus zvirDomain.maxMemorycCs t|j}|dkrtd|S)aRProvides the maximum number of virtual CPUs supported for the guest VM. If the guest is inactive, this is basically the same as virConnectGetMaxVcpus(). If the guest is running this will reflect the maximum number of virtual CPUs the guest was booted with. For more details, see virDomainGetVcpusFlags(). rXzvirDomainGetMaxVcpus() failed)rZvirDomainGetMaxVcpusrprrxrrrmaxVcpus~s zvirDomain.maxVcpuscCs"t|j|}|durtd|S)zGet the memory parameters Nz%virDomainGetMemoryParameters() failed)rZvirDomainGetMemoryParametersrprr}rrrmemoryParametersszvirDomain.memoryParameterscCs&t|j|||}|dur"td|S)z%Read the contents of domain's memory NzvirDomainMemoryPeek() failed)rZvirDomainMemoryPeekrpr)rstartrr;r>rrr memoryPeekszvirDomain.memoryPeekcCs t|j}|durtd|S)z(Extracts memory statistics for a domain NzvirDomainMemoryStats() failed)rZvirDomainMemoryStatsrprrxrrr memoryStatss zvirDomain.memoryStatscCs"t|j|}|durtd|S)z0Fetch list of messages reported against domain. NzvirDomainGetMessages() failed)rZvirDomainGetMessagesrprr}rrrmessagesszvirDomain.messagescCs&t|j|||}|dur"td|S)asRetrieves the appropriate domain element given by @type. If VIR_DOMAIN_METADATA_ELEMENT is requested parameter @uri must be set to the name of the namespace the requested elements belong to, otherwise must be None. If an element of the domain XML is not present, the resulting error will be VIR_ERR_NO_DOMAIN_METADATA. This method forms a shortcut for seeing information from virDomainSetMetadata() without having to go through virDomainGetXMLDesc(). @flags controls whether the live domain or persistent configuration will be queried. NzvirDomainGetMetadata() failed)rZvirDomainGetMetadatarprrror9r;r>rrrmetadatas zvirDomain.metadatac CsL|durd}n|j}t|j|||||}|dur:tdt|j|d}|S)a Migrate the domain object from its current host to the destination host given by dconn (a connection to the destination host). This function is similar to virDomainMigrate3, but it only supports a fixed set of parameters: @dname corresponds to VIR_MIGRATE_PARAM_DEST_NAME, @uri is VIR_MIGRATE_PARAM_URI, and @bandwidth is VIR_MIGRATE_PARAM_BANDWIDTH. virDomainFree should be used to free the resources after the returned domain object is no longer needed. NzvirDomainMigrate() failedr<)rprZvirDomainMigraterrrn) rdconnr;dnamer9rdconn__or>rrrrmigrates zvirDomain.migratec CsN|durd}n|j}t|j||||||}|durrrrrmigrate2s zvirDomain.migrate2cCsH|durd}n|j}t|j|||}|dur6tdt|j|d}|S)zMigrate the domain object from its current host to the destination host given by dconn (a connection to the destination host). NzvirDomainMigrate3() failedr<)rprZvirDomainMigrate3rrrn)rrrr;rr>rrrrmigrate3szvirDomain.migrate3cCst|j|}|S)zGet current size of the cache (in bytes) used for compressing repeatedly transferred memory pages during live migration. )rZ#virDomainMigrateGetCompressionCacherpr}rrrmigrateGetCompressionCachesz$virDomain.migrateGetCompressionCachecCst|j|}|S)z{Get the current value of the maximum downtime (in milliseconds) allowed during a migration of a guest. )rZvirDomainMigrateGetMaxDowntimerpr}rrrmigrateGetMaxDowntimeszvirDomain.migrateGetMaxDowntimecCs"t|j|}|dkrtd|S)z>Get currently configured maximum migration speed for a domain rXz$virDomainMigrateGetMaxSpeed() failed)rZvirDomainMigrateGetMaxSpeedrprr}rrrmigrateGetMaxSpeedszvirDomain.migrateGetMaxSpeedcCs$t|j||}|dkr td|S)aOSets size of the cache (in bytes) used for compressing repeatedly transferred memory pages during live migration. It's supposed to be called while the domain is being live-migrated as a reaction to migration progress and increasing number of compression cache misses obtained from virDomainGetJobStats. rXz,virDomainMigrateSetCompressionCache() failed)rZ#virDomainMigrateSetCompressionCacherpr)rZ cacheSizer;r>rrrmigrateSetCompressionCachesz$virDomain.migrateSetCompressionCachecCs$t|j||}|dkr td|S)zSets maximum tolerable time for which the domain is allowed to be paused at the end of live migration. It's supposed to be called while the domain is being live-migrated as a reaction to migration progress. rXz'virDomainMigrateSetMaxDowntime() failed)rZvirDomainMigrateSetMaxDowntimerpr)rdowntimer;r>rrrmigrateSetMaxDowntimeszvirDomain.migrateSetMaxDowntimecCs$t|j||}|dkr td|S)aOThe maximum bandwidth (in MiB/s) that will be used to do migration can be specified with the bandwidth parameter. Not all hypervisors will support a bandwidth cap. When VIR_DOMAIN_MIGRATE_MAX_SPEED_POSTCOPY is set in @flags, this API sets the maximum bandwidth for the post-copy phase of the migration. rXz$virDomainMigrateSetMaxSpeed() failed)rZvirDomainMigrateSetMaxSpeedrpr)rrr;r>rrrmigrateSetMaxSpeed$szvirDomain.migrateSetMaxSpeedcCs"t|j|}|dkrtd|S)aStarts post-copy migration. This function has to be called while migration (initiated with VIR_MIGRATE_POSTCOPY flag) is in progress. Traditional pre-copy migration iteratively walks through guest memory pages and migrates those that changed since the previous iteration. The iterative phase stops when the number of dirty pages is low enough so that the virtual CPUs can be paused, all dirty pages transferred to the destination, where the virtual CPUs are unpaused, and all this can happen within a predefined downtime period. It's clear that this process may never converge if downtime is too short and/or the guest keeps changing a lot of memory pages. When migration is switched to post-copy mode, the virtual CPUs are paused immediately, only a minimum set of pages is transferred, and the CPUs are unpaused on destination. The source keeps sending all remaining memory pages to the destination while the guest is already running there. Whenever the guest tries to read a memory page which has not been migrated yet, the hypervisor has to tell the source to transfer that page in a priority channel. To minimize such page faults, it is a good idea to run at least one iteration of pre-copy migration before switching to post-copy. Post-copy migration is guaranteed to converge since each page is transferred at most once no matter how fast it changes. On the other hand once the guest is running on the destination host, the migration can no longer be rolled back because none of the hosts has complete state. If this happens, libvirt will leave the domain paused on the source host with VIR_DOMAIN_PAUSED_POSTCOPY_FAILED reason. The domain on the destination host will remain running with VIR_DOMAIN_RUNNING_POSTCOPY_FAILED reason. It's up to the upper layer to decide what to do in such case. Because of this, libvirt will refuse to cancel post-copy migration via virDomainAbortJobFlags unless it is called with VIR_DOMAIN_ABORT_JOB_POSTCOPY, in which case the post-copy migration will be paused. Failed post-copy migration can be recovered once the cause for the failure (e.g., a network issue) is resolved by repeating the migration with an additional VIR_MIGRATE_POSTCOPY_RESUME flag. This will recreate the connection and resume migration from the point where it failed. This step can be repeated in case the migration breaks again. The following domain life cycle events are emitted during post-copy migration: VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY (on the source) -- migration entered post-copy mode. VIR_DOMAIN_EVENT_RESUMED_POSTCOPY (on the destination) -- the guest is running on the destination host while some of its memory pages still remain on the source host; neither the source nor the destination host contain a complete guest state from this point until migration finishes. VIR_DOMAIN_EVENT_RESUMED_MIGRATED (on the destination), VIR_DOMAIN_EVENT_STOPPED_MIGRATED (on the source) -- migration finished successfully and the destination host holds a complete guest state. VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY_FAILED (on the source), VIR_DOMAIN_EVENT_RESUMED_POSTCOPY_FAILED (on the destination) -- emitted when migration fails in post-copy mode and it's unclear whether any of the hosts has a complete guest state. Virtual CPUs on the destination are still running. The progress of a post-copy migration can be monitored normally using virDomainGetJobStats on the source host. Fetching statistics of a completed post-copy migration can also be done on the source host (by calling virDomainGetJobStats or listening to VIR_DOMAIN_EVENT_ID_JOB_COMPLETED event, but (in contrast to pre-copy migration) the statistics are not available on the destination host. Thus, VIR_DOMAIN_EVENT_ID_JOB_COMPLETED event is the only way of getting statistics of a completed post-copy migration of a transient domain (because the domain is removed after migration and there's no domain to run virDomainGetJobStats on). rXz&virDomainMigrateStartPostCopy() failed)rZvirDomainMigrateStartPostCopyrprr}rrrmigrateStartPostCopy/sDzvirDomain.migrateStartPostCopycCs(t|j||||}|dkr$td|S)aMigrate the domain object from its current host to the destination host given by duri. This function is similar to virDomainMigrateToURI3, but it only supports a fixed set of parameters: @dname corresponds to VIR_MIGRATE_PARAM_DEST_NAME, and @bandwidth corresponds to VIR_MIGRATE_PARAM_BANDWIDTH. The operation of this API hinges on the VIR_MIGRATE_PEER2PEER flag. If the VIR_MIGRATE_PEER2PEER flag IS set, the @duri parameter must be a valid libvirt connection URI, by which the source libvirt driver can connect to the destination libvirt. In other words, @duri corresponds to @dconnuri of virDomainMigrateToURI3. If the VIR_MIGRATE_PEER2PEER flag is NOT set, the @duri parameter takes a hypervisor specific URI used to initiate the migration. In this case @duri corresponds to VIR_MIGRATE_PARAM_URI of virDomainMigrateToURI3. rXzvirDomainMigrateToURI() failed)rZvirDomainMigrateToURIrpr)rZdurir;rrr>rrr migrateToURIxszvirDomain.migrateToURIc Cs,t|j||||||}|dkr(td|S)aIMigrate the domain object from its current host to the destination host given by @dconnuri. This function is similar to virDomainMigrateToURI3, but it only supports a fixed set of parameters: @miguri corresponds to VIR_MIGRATE_PARAM_URI, @dxml is VIR_MIGRATE_PARAM_DEST_XML, @dname is VIR_MIGRATE_PARAM_DEST_NAME, and @bandwidth corresponds to VIR_MIGRATE_PARAM_BANDWIDTH. The operation of this API hinges on the VIR_MIGRATE_PEER2PEER flag. If the VIR_MIGRATE_PEER2PEER flag IS set, the @dconnuri parameter must be a valid libvirt connection URI, by which the source libvirt driver can connect to the destination libvirt. In other words, @dconnuri has the same semantics as in virDomainMigrateToURI3. If the VIR_MIGRATE_PEER2PEER flag is NOT set, the @dconnuri must be None and the @miguri parameter takes a hypervisor specific URI used to initiate the migration. In this case @miguri corresponds to VIR_MIGRATE_PARAM_URI of virDomainMigrateToURI3. rXzvirDomainMigrateToURI2() failed)rZvirDomainMigrateToURI2rpr)rdconnuriZmigurirr;rrr>rrr migrateToURI2szvirDomain.migrateToURI2cCs&t|j|||}|dkr"td|S)zjMigrate the domain object from its current host to the destination host given by URI. rXzvirDomainMigrateToURI3() failed)rZvirDomainMigrateToURI3rpr)rrrr;r>rrr migrateToURI3szvirDomain.migrateToURI3cCst|j}|S)z$Get the public name for that domain )rZvirDomainGetNamerprxrrrr@s zvirDomain.namecCs"t|j|}|durtd|S)zGet the NUMA parameters Nz#virDomainGetNumaParameters() failed)rZvirDomainGetNumaParametersrprr}rrrnumaParametersszvirDomain.numaParameterscCs:|durd}n|j}t|j|||}|dkr6td|S)aThis opens the host interface associated with a channel device on a guest, if the host interface is supported. If @name is given, it can match either the device alias (e.g. "channel0"), or the virtio target name (e.g. "org.qemu.guest_agent.0"). If @name is omitted, then the first channel is opened. The channel is associated with the passed in @st stream, which should have been opened in non-blocking mode for bi-directional I/O. By default, when @flags is 0, the open will fail if libvirt detects that the channel is already in use by another client; passing VIR_DOMAIN_CHANNEL_FORCE will cause libvirt to forcefully remove the other client prior to opening this channel. NrXzvirDomainOpenChannel() failed)rprZvirDomainOpenChannelr)rr@str;st__or>rrr openChannels zvirDomain.openChannelcCs:|durd}n|j}t|j|||}|dkr6td|S)aThis opens the backend associated with a console, serial or parallel port device on a guest, if the backend is supported. If the @dev_name is omitted, then the first console or serial device is opened. The console is associated with the passed in @st stream, which should have been opened in non-blocking mode for bi-directional I/O. By default, when @flags is 0, the open will fail if libvirt detects that the console is already in use by another client; passing VIR_DOMAIN_CONSOLE_FORCE will cause libvirt to forcefully remove the other client prior to opening this console. If flag VIR_DOMAIN_CONSOLE_SAFE the console is opened only in the case where the hypervisor driver supports safe (mutually exclusive) console handling. Older servers did not support either flag, and also did not forbid simultaneous clients on a console, with potentially confusing results. When passing @flags of 0 in order to support a wider range of server versions, it is up to the client to ensure mutual exclusion. NrXzvirDomainOpenConsole() failed)rprZvirDomainOpenConsoler)rZdev_namerr;rr>rrr openConsoleszvirDomain.openConsolecCs&t|j|||}|dkr"td|S)aThis will attempt to connect the file descriptor @fd, to the graphics backend of @dom. If @dom has multiple graphics backends configured, then @idx will determine which one is opened, starting from @idx 0. To disable any authentication, pass the VIR_DOMAIN_OPEN_GRAPHICS_SKIPAUTH constant for @flags. The caller should use an anonymous socketpair to open @fd before invocation. This method can only be used when connected to a local libvirt hypervisor, over a UNIX domain socket. Attempts to use this method over a TCP connection will always fail rXzvirDomainOpenGraphics() failed)rZvirDomainOpenGraphicsrpr)ridxrDr;r>rrr openGraphics szvirDomain.openGraphicscCs$t|j||}|dkr td|S)aThis will create a socket pair connected to the graphics backend of @dom. One end of the socket will be returned on success, and the other end is handed to the hypervisor. If @dom has multiple graphics backends configured, then @idx will determine which one is opened, starting from @idx 0. To disable any authentication, pass the VIR_DOMAIN_OPEN_GRAPHICS_SKIPAUTH constant for @flags. This method can only be used when connected to a local libvirt hypervisor, over a UNIX domain socket. Attempts to use this method over a TCP connection will always fail. rXz virDomainOpenGraphicsFD() failed)rZvirDomainOpenGraphicsFDrpr)rrr;r>rrropenGraphicsFD s zvirDomain.openGraphicsFDcCs&t|j|||}|dkr"td|S)a]Attempt to have the guest enter the given @target power management suspension level. If @duration is non-zero, also schedule the guest to resume normal operation after that many seconds, if nothing else has resumed it earlier. Some hypervisors require that @duration be 0, for an indefinite suspension. Dependent on hypervisor used, this may require a guest agent to be available, e.g. QEMU. Beware that at least for QEMU, the domain's process will be terminated when VIR_NODE_SUSPEND_TARGET_DISK is used and a new process will be launched when libvirt is asked to wake up the domain. As a result of this, any runtime changes, such as device hotplug or memory settings, are lost unless such changes were made with VIR_DOMAIN_AFFECT_CONFIG flag. rXz&virDomainPMSuspendForDuration() failed)rZvirDomainPMSuspendForDurationrprrtargetZdurationr;r>rrrpMSuspendForDuration& szvirDomain.pMSuspendForDurationcCs"t|j|}|dkrtd|S)zInject a wakeup into the guest that previously used virDomainPMSuspendForDuration, rather than waiting for the previously requested duration (if any) to elapse. rXzvirDomainPMWakeup() failed)rZvirDomainPMWakeuprprr}rrrpMWakeup; szvirDomain.pMWakeupcCs"t|j|}|durtd|S)zGet all perf events setting. NzvirDomainGetPerfEvents() failed)rZvirDomainGetPerfEventsrprr}rrr perfEventsH szvirDomain.perfEventscCs$t|j||}|dkr td|S)zDynamically change the real CPUs which can be allocated to the emulator process of a domain. This function requires privileged access to the hypervisor. rXzvirDomainPinEmulator() failed)rZvirDomainPinEmulatorrpr)rcpumapr;r>rrr pinEmulatorO szvirDomain.pinEmulatorcCs&t|j|||}|dkr"td|S)zDynamically change the real CPUs which can be allocated to an IOThread. This function requires privileged access to the hypervisor. rXzvirDomainPinIOThread() failed)rZvirDomainPinIOThreadrpr)r iothread_valr r;r>rrr pinIOThreadW szvirDomain.pinIOThreadcCs$t|j||}|dkr td|S)Dynamically change the real CPUs which can be allocated to a virtual CPU. This function requires privileged access to the hypervisor. rXzvirDomainPinVcpu() failed)rZvirDomainPinVcpurpr)rvcpur r>rrrpinVcpu^ szvirDomain.pinVcpucCs&t|j|||}|dkr"td|S)rrXzvirDomainPinVcpuFlags() failed)rZvirDomainPinVcpuFlagsrpr)rrr r;r>rrr pinVcpuFlagse szvirDomain.pinVcpuFlagscCs"t|j|}|dkrtd|S)aTReboot a domain, the domain object is still usable thereafter, but the domain OS is being stopped for a restart. Note that the guest OS may ignore the request. Additionally, the hypervisor may check and support the domain 'on_reboot' XML setting resulting in a domain that shuts down instead of rebooting. If @flags is set to zero, then the hypervisor will choose the method of shutdown it considers best. To have greater control pass one or more of the virDomainRebootFlagValues. The order in which the hypervisor tries each shutdown method is undefined, and a hypervisor is not required to support all methods. To use guest agent (VIR_DOMAIN_REBOOT_GUEST_AGENT) the domain XML must have configured. Due to implementation limitations in some drivers (the qemu driver, for instance) it is not advised to migrate or save a guest that is rebooting as a result of this API. Migrating such a guest can lead to a plain shutdown on the destination. rXzvirDomainReboot() failed)rZvirDomainRebootrprr}rrrrebootp szvirDomain.rebootcCs$t|j||}|dkr td|S)aRename a domain. New domain name is specified in the second argument. Depending on each driver implementation it may be required that domain is in a specific state. There might be some attributes and/or elements in domain XML that if no value provided at XML defining time, libvirt will derive their value from the domain name. These are not updated by this API. Users are strongly advised to change these after the rename was successful. rXzvirDomainRename() failed)rZvirDomainRenamerpr)rnew_namer;r>rrrrename s zvirDomain.renamecCs"t|j|}|dkrtd|S)a8Reset a domain immediately without any guest OS shutdown. Reset emulates the power reset button on a machine, where all hardware sees the RST line set and reinitializes internal state. Note that there is a risk of data loss caused by reset without any guest OS shutdown. rXzvirDomainReset() failed)rZvirDomainResetrprr}rrrreset szvirDomain.resetcCs t|j}|dkrtd|S)a(Resume a suspended domain, the process is restarted from the state where it was frozen by calling virDomainSuspend(). This function may require privileged access Moreover, resume may not be supported if domain is in some special state like VIR_DOMAIN_PMSUSPENDED. rXzvirDomainResume() failed)rZvirDomainResumerprrxrrrresume s zvirDomain.resumecCs8|durd}n|j}t|j||}|dkr4td|S)z(revert the domain to the given snapshot NrXz"virDomainRevertToSnapshot() failed)rprZvirDomainRevertToSnapshotr)rZsnapr;Zsnap__or>rrrrevertToSnapshot szvirDomain.revertToSnapshotcCs"t|j|}|dkrtd|S)aThis method will suspend a domain and save its memory contents to a file or direcotry (based on the vmm) on disk. After the call, if successful,the domain is not listed as running anymore (this ends the life of a transient domain). Use virDomainRestore() to restore a domain after saving. See virDomainSaveFlags() and virDomainSaveParams() for more control. Also, a save file can be inspected or modified slightly with virDomainSaveImageGetXMLDesc() and virDomainSaveImageDefineXML(). rXzvirDomainSave() failed)rZ virDomainSaverpr)rrr>rrrsave s zvirDomain.savecCs&t|j|||}|dkr"td|S)aThis method will suspend a domain and save its memory contents to a file on disk. After the call, if successful, the domain is not listed as running anymore (this ends the life of a transient domain). Use virDomainRestore() to restore a domain after saving. If the hypervisor supports it, @dxml can be used to alter host-specific portions of the domain XML that will be used when restoring an image. For example, it is possible to alter the backing filename that is associated with a disk device, in order to prepare for file renaming done as part of backing up the disk device while the domain is stopped. If @flags includes VIR_DOMAIN_SAVE_BYPASS_CACHE, then libvirt will attempt to bypass the file system cache while creating the file, or fail if it cannot do so for the given system; this can allow less pressure on file system cache, but also risks slowing saves to NFS. Normally, the saved state file will remember whether the domain was running or paused, and restore defaults to the same state. Specifying VIR_DOMAIN_SAVE_RUNNING or VIR_DOMAIN_SAVE_PAUSED in @flags will override what state gets saved into the file. These two flags are mutually exclusive. A save file can be inspected or modified slightly with virDomainSaveImageGetXMLDesc() and virDomainSaveImageDefineXML(). Some hypervisors may prevent this operation if there is a current block job running; in that case, use virDomainBlockJobAbort() to stop the block job first. rXzvirDomainSaveFlags() failed)rZvirDomainSaveFlagsrpr)rrrr;r>rrr saveFlags szvirDomain.saveFlagscCs$t|j||}|dkr td|S)zRThis method will suspend a domain and save its memory contents to a file on disk. rXzvirDomainSaveParams() failed)rZvirDomainSaveParamsrprrrr;r>rrr saveParams szvirDomain.saveParamscCs t|j}|durtd|S)zPGet the scheduler parameters, the @params array will be filled with the values. Nz(virDomainGetSchedulerParameters() failed)rZvirDomainGetSchedulerParametersrprrxrrrschedulerParameters s zvirDomain.schedulerParameterscCs"t|j|}|durtd|S)zGet the scheduler parameters Nz-virDomainGetSchedulerParametersFlags() failed)rZ$virDomainGetSchedulerParametersFlagsrprr}rrrschedulerParametersFlags sz"virDomain.schedulerParametersFlagscCs t|j}|durtd|S)zGet the scheduler type. Nz"virDomainGetSchedulerType() failed)rZvirDomainGetSchedulerTyperprrxrrr schedulerType s zvirDomain.schedulerTypecCs:|durd}n|j}t|j|||}|dur6td|S)aTake a screenshot of current domain console as a stream. The image format is hypervisor specific. Moreover, some hypervisors supports multiple displays per domain. These can be distinguished by @screen argument. This call sets up a stream; subsequent use of stream API is necessary to transfer actual data, determine how much data is successfully transferred, and detect any errors. The screen ID is the sequential number of screen. In case of multiple graphics cards, heads are enumerated before devices, e.g. having two graphics cards, both with four heads, screen ID 5 addresses the second head on the second card. NzvirDomainScreenshot() failed)rprZvirDomainScreenshotr)rstreamZscreenr; stream__or>rrr screenshot s zvirDomain.screenshotcCs t|j}|durtd|S)z\Extract information about the domain security label. Only the first label will be returned. Nz"virDomainGetSecurityLabel() failed)rZvirDomainGetSecurityLabelrprrxrrr securityLabel1 s zvirDomain.securityLabelcCs t|j}|durtd|S)z\Extract information about the domain security label. A list of all labels will be returned. Nz&virDomainGetSecurityLabelList() failed)rZvirDomainGetSecurityLabelListrprrxrrrsecurityLabelList8 s zvirDomain.securityLabelListcCs*t|j|||||}|dkr&td|S)zSend key(s) to the guest. rXzvirDomainSendKey() failed)rZvirDomainSendKeyrpr)rcodesetZholdtimeZkeycodesZ nkeycodesr;r>rrrsendKeyC szvirDomain.sendKeycCs&t|j|||}|dkr"td|S)aSend a signal to the designated process in the guest The signal numbers must be taken from the virDomainProcessSignal enum. These will be translated to the corresponding signal number for the guest OS, by the guest agent delivering the signal. If there is no mapping from virDomainProcessSignal to the native OS signals, this API will report an error. If @pid_value is an integer greater than zero, it is treated as a process ID. If @pid_value is an integer less than zero, it is treated as a process group ID. All the @pid_value numbers are from the container/guest namespace. The value zero is not valid. Not all hypervisors will support sending signals to arbitrary processes or process groups. If this API is implemented the minimum requirement is to be able to use @pid_value == 1 (i.e. kill init). No other value is required to be supported. If the @signum is VIR_DOMAIN_PROCESS_SIGNAL_NOP then this API will simply report whether the process is running in the container/guest. rXz#virDomainSendProcessSignal() failed)rZvirDomainSendProcessSignalrpr)rZ pid_valueZsignumr;r>rrrsendProcessSignalJ szvirDomain.sendProcessSignalcCs"t|j|}|dkrtd|S)z`Configure the domain to be automatically started each time when the host machine boots. rXzvirDomainSetAutostart() failed)rZvirDomainSetAutostartrprrrr>rrr setAutostartg szvirDomain.setAutostartcCs"t|j|}|dkrtd|S)adConfigure the domain to be automatically started the next when the host machine boots. Note that autostart configured via the virDomain[Set|Get]AutostartOnce APIs is independent from the autostart configured via virDomain[Set|Get]Autostart. Enabling either of them will cause the VM to be started on the next boot. rXz"virDomainSetAutostartOnce() failed)rZvirDomainSetAutostartOncerprr'rrrsetAutostartOnceo szvirDomain.setAutostartOncecCs$t|j||}|dkr td|S)zChange the blkio tunables rXz$virDomainSetBlkioParameters() failed)rZvirDomainSetBlkioParametersrprrrrrsetBlkioParameters szvirDomain.setBlkioParameterscCs&t|j|||}|dkr"td|S)z+Change the I/O tunables for a block device rXz virDomainSetBlockIoTune() failed)rZvirDomainSetBlockIoTunerpr)rrrr;r>rrrsetBlockIoTune szvirDomain.setBlockIoTunecCs&t|j|||}|dkr"td|S)aSet the threshold level for delivering the VIR_DOMAIN_EVENT_ID_BLOCK_THRESHOLD if the device or backing chain element described by @dev is written beyond the set threshold level. The threshold level is unset once the event fires. The event might not be delivered at all if libvirtd was not running at the moment when the threshold was reached. Note that if the threshold level is reached for a top level image, the event is emitted for @dev corresponding to the disk target, and may also be reported with @dev corresponding to the disk target with an index corresponding to the 'index' attribute of 'source' in the live VM XML if the attribute is present. @dev can either be a disk target name (vda, sda) or disk target with index ( vda[4]). Without the index the top image in the backing chain will have the threshold set. The index corresponds to the 'index' attribute reported in the live VM XML for 'backingStore' or 'source' elements of a disk. If index is given the threshold is set for the corresponding image. In case when @dev does not contain index the VIR_DOMAIN_EVENT_ID_BLOCK_THRESHOLD event may be emitted twice, once for the disk device target without index and once containing the index. Note that the threshold event can be registered also for destinations of a 'virDomainBlockCopy' destination by using the 'index' of the 'mirror' source. Hypervisors report the last written sector of an image in the bulk stats API (virConnectGetAllDomainStats/virDomainListGetStats) as "block..allocation" in the VIR_DOMAIN_STATS_BLOCK group. The current threshold value is reported as "block..threshold". This event allows to use thin-provisioned storage which needs management tools to grow it without the need for polling of the data. rXz#virDomainSetBlockThreshold() failed)rZvirDomainSetBlockThresholdrpr)rdev thresholdr;r>rrrsetBlockThreshold szvirDomain.setBlockThresholdcCs&t|j|||}|dkr"td|S)aSets state of individual vcpus described by @cpumap via guest agent. Other vcpus are not modified. This API requires the VM to run. Various hypervisors or guest agent implementation may limit to operate on just 1 vCPU per call. @cpumap is a list of vCPU numbers. Its syntax is a comma separated list and a special markup using '-' and '^' (ex. '0-4', '0-3,^2'). The '-' denotes the range and the '^' denotes exclusive. The expression is sequentially evaluated, so "0-15,^8" is identical to "9-14,0-7,15" but not identical to "^8,0-15". Note that OSes (notably Linux) may require vCPU 0 to stay online to support low-level features a S3 sleep. rXzvirDomainSetGuestVcpus() failed)rZvirDomainSetGuestVcpusrpr)rr stater;r>rrr setGuestVcpus szvirDomain.setGuestVcpuscCs&t|j|||}|dkr"td|S)zDynamically allow changing the IOThread polling related parameters. This function requires privileged access to the hypervisor. rXz#virDomainSetIOThreadParams() failed)rZvirDomainSetIOThreadParamsrpr)rr rr;r>rrrsetIOThreadParams szvirDomain.setIOThreadParamscCs&t|j|||}|dkr"td|S)z5Change the bandwidth tunables for a interface device rXz(virDomainSetInterfaceParameters() failed)rZvirDomainSetInterfaceParametersrpr)rrrr;r>rrrsetInterfaceParameters sz virDomain.setInterfaceParameterscCs$t|j||}|dkr td|S)z4Set a launch security secret in the guest's memory. rXz(virDomainSetLaunchSecurityState() failed)rZvirDomainSetLaunchSecurityStaterprrrrrsetLaunchSecurityState sz virDomain.setLaunchSecurityStatecCs&t|j|||}|dkr"td|S)a?Changes the actions of lifecycle events for domain represented as $action in the domain XML. QEMU driver has a limitation that if all lifecycle events are set to destroy when the domain is started, it's not possible to change any action for running domain. rXz$virDomainSetLifecycleAction() failed)rZvirDomainSetLifecycleActionrpr)rroactionr;r>rrrsetLifecycleAction szvirDomain.setLifecycleActioncCs"t|j|}|dkrtd|S)aDynamically change the maximum amount of physical memory allocated to a domain. If domain is None, then this change the amount of memory reserved to Domain0 i.e. the domain where the application runs. This function may require privileged access to the hypervisor. This command is hypervisor-specific for whether active, persistent, or both configurations are changed; for more control, use virDomainSetMemoryFlags(). rXzvirDomainSetMaxMemory() failed)rZvirDomainSetMaxMemoryrprrmemoryr>rrr setMaxMemory s zvirDomain.setMaxMemorycCs"t|j|}|dkrtd|S)aDynamically change the target amount of physical memory allocated to a domain. If domain is None, then this change the amount of memory reserved to Domain0 i.e. the domain where the application runs. This function may require privileged access to the hypervisor. This command is hypervisor-specific for whether active, persistent, or both configurations are changed; for more control, use virDomainSetMemoryFlags(). rXzvirDomainSetMemory() failed)rZvirDomainSetMemoryrprr6rrr setMemory s zvirDomain.setMemorycCs$t|j||}|dkr td|S)aUDynamically change the target amount of physical memory allocated to a domain. If domain is None, then this change the amount of memory reserved to Domain0 i.e. the domain where the application runs. This function may require privileged access to the hypervisor. @flags may include VIR_DOMAIN_AFFECT_LIVE or VIR_DOMAIN_AFFECT_CONFIG. Both flags may be set. If VIR_DOMAIN_AFFECT_LIVE is set, the change affects a running domain and will fail if domain is not active. If VIR_DOMAIN_AFFECT_CONFIG is set, the change affects persistent state, and will fail for transient domains. If neither flag is specified (that is, @flags is VIR_DOMAIN_AFFECT_CURRENT), then an inactive domain modifies persistent setup, while an active domain is hypervisor-dependent on whether just live or both live and persistent state is changed. If VIR_DOMAIN_MEM_MAXIMUM is set, the change affects domain's maximum memory size rather than current memory size. Not all hypervisors can support all flag combinations. rXz virDomainSetMemoryFlags() failed)rZvirDomainSetMemoryFlagsrpr)rr7r;r>rrrsetMemoryFlags szvirDomain.setMemoryFlagscCs$t|j||}|dkr td|S)zChange the memory tunables rXz%virDomainSetMemoryParameters() failed)rZvirDomainSetMemoryParametersrprrrrrsetMemoryParameters( szvirDomain.setMemoryParameterscCs$t|j||}|dkr td|S)aGDynamically change the domain memory balloon driver statistics collection period. Use 0 to disable and a positive value to enable. @flags may include VIR_DOMAIN_AFFECT_LIVE or VIR_DOMAIN_AFFECT_CONFIG. Both flags may be set. If VIR_DOMAIN_AFFECT_LIVE is set, the change affects a running domain and will fail if domain is not active. If VIR_DOMAIN_AFFECT_CONFIG is set, the change affects persistent state, and will fail for transient domains. If neither flag is specified (that is, @flags is VIR_DOMAIN_AFFECT_CURRENT), then an inactive domain modifies persistent setup, while an active domain is hypervisor-dependent on whether just live or both live and persistent state is changed. Not all hypervisors can support all flag combinations. rXz&virDomainSetMemoryStatsPeriod() failed)rZvirDomainSetMemoryStatsPeriodrpr)rZperiodr;r>rrrsetMemoryStatsPeriod3 szvirDomain.setMemoryStatsPeriodcCs*t|j|||||}|dkr&td|S)aSets the appropriate domain element given by @type to the value of @metadata. A @type of VIR_DOMAIN_METADATA_DESCRIPTION is free-form text; VIR_DOMAIN_METADATA_TITLE is free-form, but no newlines are permitted, and should be short (although the length is not enforced). For these two options @key and @uri are irrelevant and must be set to None. For type VIR_DOMAIN_METADATA_ELEMENT @metadata must be well-formed XML belonging to namespace defined by @uri with local name @key. Passing None for @metadata says to remove that element from the domain XML (passing the empty string leaves the element present). The resulting metadata will be present in virDomainGetXMLDesc(), as well as quick access through virDomainGetMetadata(). @flags controls whether the live domain, persistent configuration, or both will be modified. rXzvirDomainSetMetadata() failed)rZvirDomainSetMetadatarprrrorkeyr9r;r>rrr setMetadataF szvirDomain.setMetadatacCs$t|j||}|dkr td|S)zChange the NUMA tunables rXz#virDomainSetNumaParameters() failed)rZvirDomainSetNumaParametersrprrrrrsetNumaParametersb szvirDomain.setNumaParameterscCs$t|j||}|dkr td|S)z5Enable or disable the particular list of perf events rXzvirDomainSetPerfEvents() failed)rZvirDomainSetPerfEventsrprrrrr setPerfEventsi szvirDomain.setPerfEventscCs"t|j|}|dkrtd|S) Change the scheduler parameters rXz(virDomainSetSchedulerParameters() failed)rZvirDomainSetSchedulerParametersrpr)rrr>rrrsetSchedulerParametersp sz virDomain.setSchedulerParameterscCs$t|j||}|dkr td|S)rBrXz-virDomainSetSchedulerParametersFlags() failed)rZ$virDomainSetSchedulerParametersFlagsrprrrrrsetSchedulerParametersFlagsw sz%virDomain.setSchedulerParametersFlagscCs&t|j|||}|dkr"td|S)zUAdd throttlegroup or change all of the throttlegroup options within specific domain. rXz"virDomainSetThrottleGroup() failed)rZvirDomainSetThrottleGrouprpr)rrrr;r>rrrsetThrottleGroup~ szvirDomain.setThrottleGroupcCs&t|j|||}|dkr"td|S)acSets the @user password to the value specified by @password. If @flags contain VIR_DOMAIN_PASSWORD_ENCRYPTED, the password is assumed to be encrypted by the method required by the guest OS. Please note that some hypervisors may require guest agent to be configured and running in order to be able to run this API. rXz!virDomainSetUserPassword() failed)rZvirDomainSetUserPasswordrpr)rrpasswordr;r>rrrsetUserPassword szvirDomain.setUserPasswordcCs&t|j|||}|dkr"td|S)aFEnables/disables individual vcpus described by @vcpumap in the hypervisor. Various hypervisor implementations may limit to operate on just 1 hotpluggable entity (which may contain multiple vCPUs on certain platforms). Note that OSes and hypervisors may require vCPU 0 to stay online. rXzvirDomainSetVcpu() failed)rZvirDomainSetVcpurpr)rZvcpumapr/r;r>rrrsetVcpu szvirDomain.setVcpucCs"t|j|}|dkrtd|S)aDynamically change the number of virtual CPUs used by the domain. Note that this call may fail if the underlying virtualization hypervisor does not support it or if growing the number is arbitrarily limited. This function may require privileged access to the hypervisor. Note that if this call is executed before the guest has finished booting, the guest may fail to process the change. This command only changes the runtime configuration of the domain, so can only be called on an active domain. It is hypervisor-dependent whether it also affects persistent configuration; for more control, use virDomainSetVcpusFlags(). rXzvirDomainSetVcpus() failed)rZvirDomainSetVcpusrpr)rnvcpusr>rrrsetVcpus s zvirDomain.setVcpuscCs$t|j||}|dkr td|S)aPDynamically change the number of virtual CPUs used by the domain. Note that this call may fail if the underlying virtualization hypervisor does not support it or if growing the number is arbitrarily limited. This function may require privileged access to the hypervisor. @flags may include VIR_DOMAIN_AFFECT_LIVE to affect a running domain (which may fail if domain is not active), or VIR_DOMAIN_AFFECT_CONFIG to affect the next boot via the XML description of the domain. Both flags may be set. If neither flag is specified (that is, @flags is VIR_DOMAIN_AFFECT_CURRENT), then an inactive domain modifies persistent setup, while an active domain is hypervisor-dependent on whether just live or both live and persistent state is changed. Note that if this call is executed before the guest has finished booting, the guest may fail to process the change. If @flags includes VIR_DOMAIN_VCPU_MAXIMUM, then VIR_DOMAIN_AFFECT_LIVE must be clear, and only the maximum virtual CPU limit is altered; generally, this value must be less than or equal to virConnectGetMaxVcpus(). Otherwise, this call affects the current virtual CPU limit, which must be less than or equal to the maximum limit. Note that hypervisors may not allow changing the maximum vcpu count if processor topology is specified. If @flags includes VIR_DOMAIN_VCPU_GUEST, then the state of processors is modified inside the guest instead of the hypervisor. This flag can only be used with live guests and is incompatible with VIR_DOMAIN_VCPU_MAXIMUM. The usage of this flag may require a guest agent configured. Not all hypervisors can support all flag combinations. rXzvirDomainSetVcpusFlags() failed)rZvirDomainSetVcpusFlagsrpr)rrIr;r>rrr setVcpusFlags s zvirDomain.setVcpusFlagscCs t|j}|dkrtd|S)akShutdown a domain, the domain object is still usable thereafter, but the domain OS is being stopped. Note that the guest OS may ignore the request. Additionally, the hypervisor may check and support the domain 'on_poweroff' XML setting resulting in a domain that reboots instead of shutting down. For guests that react to a shutdown request, the differences from virDomainDestroy() are that the guests disk storage will be in a stable state rather than having the (virtual) power cord pulled, and this command returns as soon as the shutdown request is issued rather than blocking until the guest is no longer running. If the domain is transient and has any snapshot metadata (see virDomainSnapshotNum()), then that metadata will automatically be deleted when the domain quits. rXzvirDomainShutdown() failed)rZvirDomainShutdownrprrxrrrshutdown s zvirDomain.shutdowncCs"t|j|}|dkrtd|S)aNShutdown a domain, the domain object is still usable thereafter but the domain OS is being stopped. Note that the guest OS may ignore the request. Additionally, the hypervisor may check and support the domain 'on_poweroff' XML setting resulting in a domain that reboots instead of shutting down. For guests that react to a shutdown request, the differences from virDomainDestroy() are that the guest's disk storage will be in a stable state rather than having the (virtual) power cord pulled, and this command returns as soon as the shutdown request is issued rather than blocking until the guest is no longer running. If the domain is transient and has any snapshot metadata (see virDomainSnapshotNum()), then that metadata will automatically be deleted when the domain quits. If @flags is set to zero, then the hypervisor will choose the method of shutdown it considers best. To have greater control pass one or more of the virDomainShutdownFlagValues. The order in which the hypervisor tries each shutdown method is undefined, and a hypervisor is not required to support all methods. To use guest agent (VIR_DOMAIN_SHUTDOWN_GUEST_AGENT) the domain XML must have configured. rXzvirDomainShutdownFlags() failed)rZvirDomainShutdownFlagsrprr}rrr shutdownFlags szvirDomain.shutdownFlagscCs0t|j||}|dur tdt||d}|S)a6Creates a new snapshot of a domain based on the snapshot xml contained in xmlDesc, with a top-level element . If @flags is 0, the domain can be active, in which case the snapshot will be a full system snapshot (capturing both disk state, and runtime VM state such as RAM contents), where reverting to the snapshot is the same as resuming from hibernation (TCP connections may have timed out, but everything else picks up where it left off); or the domain can be inactive, in which case the snapshot includes just the disk state prior to booting. The newly created snapshot becomes current (see virDomainSnapshotCurrent()), and is a child of any previous current snapshot. If @flags includes VIR_DOMAIN_SNAPSHOT_CREATE_VALIDATE, then @xmlDesc is validated against the XML schema. If @flags includes VIR_DOMAIN_SNAPSHOT_CREATE_REDEFINE, then this is a request to reinstate snapshot metadata that was previously captured from virDomainSnapshotGetXMLDesc() before removing that metadata, rather than creating a new snapshot. This can be used to recreate a snapshot hierarchy on a destination, then remove it on the source, in order to allow migration (since migration normally fails if snapshot metadata still remains on the source machine). Note that while original creation can omit a number of elements from @xmlDesc (and libvirt will supply sane defaults based on the domain state at that point in time), a redefinition must supply more elements (as the domain may have changed in the meantime, so that libvirt no longer has a way to resupply correct defaults). When redefining snapshot metadata, the domain's current snapshot will not be altered unless the VIR_DOMAIN_SNAPSHOT_CREATE_CURRENT flag is also present. It is an error to request the VIR_DOMAIN_SNAPSHOT_CREATE_CURRENT flag without VIR_DOMAIN_SNAPSHOT_CREATE_REDEFINE. On some hypervisors, redefining an existing snapshot can be used to alter host-specific portions of the domain XML to be used during revert (such as backing filenames associated with disk devices), but must not alter guest-visible layout. When redefining a snapshot name that does not exist, the hypervisor may validate that reverting to the snapshot appears to be possible (for example, disk images have snapshot contents by the requested name). Not all hypervisors support these flags. If @flags includes VIR_DOMAIN_SNAPSHOT_CREATE_NO_METADATA, then the domain's disk images are modified according to @xmlDesc, but libvirt does not track any metadata (similar to immediately calling virDomainSnapshotDelete() with VIR_DOMAIN_SNAPSHOT_DELETE_METADATA_ONLY). This flag is incompatible with VIR_DOMAIN_SNAPSHOT_CREATE_REDEFINE. If @flags includes VIR_DOMAIN_SNAPSHOT_CREATE_HALT, then the domain will be inactive after the snapshot completes, regardless of whether it was active before; otherwise, a running domain will still be running after the snapshot. This flag is invalid on transient domains, and is incompatible with VIR_DOMAIN_SNAPSHOT_CREATE_REDEFINE. If @flags includes VIR_DOMAIN_SNAPSHOT_CREATE_LIVE, then the domain is not paused while creating the snapshot. This increases the size of the memory dump file, but reduces downtime of the guest while taking the snapshot. Some hypervisors only support this flag during external snapshots. If @flags includes VIR_DOMAIN_SNAPSHOT_CREATE_DISK_ONLY, then the snapshot will be limited to the disks described in @xmlDesc, and no VM state will be saved. For an active guest, the disk image may be inconsistent (as if power had been pulled), and specifying this with the VIR_DOMAIN_SNAPSHOT_CREATE_HALT flag risks data loss. If @flags includes VIR_DOMAIN_SNAPSHOT_CREATE_QUIESCE, then the libvirt will attempt to use guest agent to freeze and thaw all file systems in use within domain OS. However, if the guest agent is not present, an error is thrown. Moreover, this flag requires VIR_DOMAIN_SNAPSHOT_CREATE_DISK_ONLY to be passed as well. For better control and error recovery users should invoke virDomainFSFreeze manually before taking the snapshot and then virDomainFSThaw to restore the VM rather than using VIR_DOMAIN_SNAPSHOT_CREATE_QUIESCE. By default, if the snapshot involves external files, and any of the destination files already exist as a non-empty regular file, the snapshot is rejected to avoid losing contents of those files. However, if @flags includes VIR_DOMAIN_SNAPSHOT_CREATE_REUSE_EXT, then the destination files must be pre-created manually with the correct image format and metadata including backing store path (this allows a management app to pre-create files with relative backing file names, rather than the default of creating with absolute backing file names). Note that only the file specified in the snapshot XML is inserted as a snapshot thus setting incorrect metadata in the pre-created image may lead to the VM being unable to start or other block jobs may fail. Be aware that although libvirt prefers to report errors up front with no other effect, some hypervisors have certain types of failures where the overall command can easily fail even though the guest configuration was partially altered (for example, if a disk snapshot request for two disks fails on the second disk, but the first disk alteration cannot be rolled back). If this API call fails, it is therefore normally necessary to follow up with virDomainGetXMLDesc() and check each disk to determine if any partial changes occurred. However, if @flags contains VIR_DOMAIN_SNAPSHOT_CREATE_ATOMIC, then libvirt guarantees that this command will not alter any disks unless the entire set of changes can be done atomically, making failure recovery simpler (note that it is still possible to fail after disks have changed, but only in the much rarer cases of running out of memory or disk space). Some hypervisors may prevent this operation if there is a current block copy operation; in that case, use virDomainBlockJobAbort() to stop the block copy first. virDomainSnapshotFree should be used to free the resources after the snapshot object is no longer needed. Nz#virDomainSnapshotCreateXML() failedr<)rZvirDomainSnapshotCreateXMLrprvirDomainSnapshotrrrrsnapshotCreateXML s n zvirDomain.snapshotCreateXMLcCs.t|j|}|durtdt||d}|S)zGet the current snapshot for a domain, if any. virDomainSnapshotFree should be used to free the resources after the snapshot object is no longer needed. Nz!virDomainSnapshotCurrent() failedr<)rZvirDomainSnapshotCurrentrprrN)rr;r>rrrrsnapshotCurrent s  zvirDomain.snapshotCurrentcCs"t|j|}|durtd|S)z8collect the list of snapshot names for the given domain Nz#virDomainSnapshotListNames() failed)rZvirDomainSnapshotListNamesrprr}rrrsnapshotListNames szvirDomain.snapshotListNamescCs0t|j||}|dur tdt||d}|S)z3Try to lookup a domain snapshot based on its name. Nz&virDomainSnapshotLookupByName() failedr<)rZvirDomainSnapshotLookupByNamerprrNrrrrsnapshotLookupByName s  zvirDomain.snapshotLookupByNamecCs"t|j|}|dkrtd|S)aHProvides the number of domain snapshots for this domain. This function will accept VIR_DOMAIN_SNAPSHOT_LIST_TOPOLOGICAL in @flags only if virDomainSnapshotListNames() can honor it, although the flag has no other effect here. By default, this command covers all snapshots. It is also possible to limit things to just snapshots with no parents, when @flags includes VIR_DOMAIN_SNAPSHOT_LIST_ROOTS. Additional filters are provided via the same @flags values as documented in virDomainListAllSnapshots(). rXzvirDomainSnapshotNum() failed)rZvirDomainSnapshotNumrprr}rrr snapshotNum s zvirDomain.snapshotNumcCs$t|j||}|dkr td|S)zCalculate the current domain's memory dirty rate in next @seconds. The calculated dirty rate information is available by calling virConnectGetAllDomainStats. rXz$virDomainStartDirtyRateCalc() failed)rZvirDomainStartDirtyRateCalcrpr)rZsecondsr;r>rrrstartDirtyRateCalc szvirDomain.startDirtyRateCalccCs"t|j|}|durtd|S)zExtract domain state. NzvirDomainGetState() failed)rZvirDomainGetStaterprr}rrrr/ szvirDomain.statecCs t|j}|dkrtd|S)aSuspends an active domain, the process is frozen without further access to CPU resources and I/O but the memory used by the domain at the hypervisor level will stay allocated. Use virDomainResume() to reactivate the domain. This function may require privileged access. Moreover, suspend may not be supported if domain is in some special state like VIR_DOMAIN_PMSUSPENDED. rXzvirDomainSuspend() failed)rZvirDomainSuspendrprrxrrrsuspend s zvirDomain.suspendcCs t|j}|dkrtd|S)a Undefine a domain. If the domain is running, it's converted to transient domain, without stopping it. If the domain is inactive, the domain configuration is removed. If the domain has a managed save image (see virDomainHasManagedSaveImage()), or if it is inactive and has any snapshot metadata (see virDomainSnapshotNum()) or checkpoint metadata (see virDomainListAllCheckpoints()), then the undefine will fail. See virDomainUndefineFlags() for more control. rXzvirDomainUndefine() failed)rZvirDomainUndefinerprrxrrrundefine s zvirDomain.undefinecCs"t|j|}|dkrtd|S)aSUndefine a domain. If the domain is running, it's converted to transient domain, without stopping it. If the domain is inactive, the domain configuration is removed. If the domain has a managed save image (see virDomainHasManagedSaveImage()), then including VIR_DOMAIN_UNDEFINE_MANAGED_SAVE in @flags will also remove that file, and omitting the flag will cause the undefine process to fail. If the domain is inactive and has any snapshot metadata (see virDomainSnapshotNum()), then including VIR_DOMAIN_UNDEFINE_SNAPSHOTS_METADATA in @flags will also remove that metadata. Omitting the flag will cause the undefine of an inactive domain with snapshots to fail. Active domains will retain snapshot metadata until the (now-transient) domain halts, regardless of whether this flag is present. On hypervisors that support snapshots, but where snapshots do not use libvirt metadata, this flag has no effect. If the domain is inactive and has any checkpoint metadata (see virDomainListAllCheckpoints()), then including VIR_DOMAIN_UNDEFINE_CHECKPOINTS_METADATA in @flags will also remove that metadata. Omitting the flag will cause the undefine of an inactive domain with checkpoints to fail. Active domains will retain checkpoint metadata until the (now-transient) domain halts, regardless of whether this flag is present. On hypervisors that support checkpoints, but where checkpoints do not use libvirt metadata, this flag has no effect. If the domain has any nvram specified, the undefine process will fail unless VIR_DOMAIN_UNDEFINE_KEEP_NVRAM is specified, or if VIR_DOMAIN_UNDEFINE_NVRAM is specified to remove the nvram file. rXzvirDomainUndefineFlags() failed)rZvirDomainUndefineFlagsrprr}rrr undefineFlags s zvirDomain.undefineFlagscCs$t|j||}|dkr td|S)aChange a virtual device on a domain, using the flags parameter to control how the device is changed. VIR_DOMAIN_AFFECT_CURRENT specifies that the device change is made based on current domain state. VIR_DOMAIN_AFFECT_LIVE specifies that the device shall be changed on the active domain instance only and is not added to the persisted domain configuration. VIR_DOMAIN_AFFECT_CONFIG specifies that the device shall be changed on the persisted domain configuration only. Note that the target hypervisor must return an error if unable to satisfy flags. E.g. the hypervisor driver will return failure if LIVE is specified but it only supports modifying the persisted device allocation. This method is used for actions such changing CDROM/Floppy device media, altering the graphics configuration such as password, reconfiguring the NIC device backend connectivity, etc. The supplied XML description of the device should contain all the information that is found in the corresponding domain XML. Leaving out any piece of information may be treated as a request for its removal, which may be denied. For instance, when users want to change CDROM media only for live XML, they must provide live disk XML as found in the corresponding live domain XML with only the disk path changed. rXz#virDomainUpdateDeviceFlags() failed)rZvirDomainUpdateDeviceFlagsrprrrrrupdateDeviceFlags szvirDomain.updateDeviceFlagscCs"t|j|}|durtd|S)z=Query the CPU affinity setting of all virtual CPUs of domain Nz virDomainGetVcpuPinInfo() failed)rZvirDomainGetVcpuPinInforprr}rrr vcpuPinInfo0 szvirDomain.vcpuPinInfocCs t|j}|durtd|S)z^Extract information about virtual CPUs of domain, store it in info array and also in cpumaps. NzvirDomainGetVcpus() failed)rZvirDomainGetVcpusrprrxrrrvcpus7 s zvirDomain.vcpuscCs"t|j|}|dkrtd|S)anQuery the number of virtual CPUs used by the domain. Note that this call may fail if the underlying virtualization hypervisor does not support it. This function may require privileged access to the hypervisor. If @flags includes VIR_DOMAIN_AFFECT_LIVE, this will query a running domain (which will fail if domain is not active); if it includes VIR_DOMAIN_AFFECT_CONFIG, this will query the XML description of the domain. It is an error to set both flags. If neither flag is set (that is, VIR_DOMAIN_AFFECT_CURRENT), then the configuration queried depends on whether the domain is currently running. If @flags includes VIR_DOMAIN_VCPU_MAXIMUM, then the maximum virtual CPU limit is queried. Otherwise, this call queries the current virtual CPU count. If @flags includes VIR_DOMAIN_VCPU_GUEST, then the state of the processors is queried in the guest instead of the hypervisor. This flag is only usable on live domains. Guest agent may be needed for this flag to be available. rXzvirDomainGetVcpusFlags() failed)rZvirDomainGetVcpusFlagsrprr}rrr vcpusFlagsB szvirDomain.vcpusFlagsrNr;rcs0tj|}|durtdfdd|DS)z9List all snapshots and returns a list of snapshot objectsNz"virDomainListAllSnapshots() failedcsg|]}t|dqSr<)rN.0Zsnapptrr rr e z.virDomain.listAllSnapshots..)rZvirDomainListAllSnapshotsrprr}rr rlistAllSnapshots_ szvirDomain.listAllSnapshotsrcs0tj|}|durtdfdd|DS)z=List all checkpoints and returns a list of checkpoint objectsNz$virDomainListAllCheckpoints() failedcsg|]}t|dqSr])rr_Zchkptrr rrr`m raz0virDomain.listAllCheckpoints..)rZvirDomainListAllCheckpointsrprr}rr rlistAllCheckpointsg szvirDomain.listAllCheckpoints)filesr;rcCs$t|j||}|dkr td|S)aLaunch a defined domain. If the call succeeds the domain moves from the defined to the running domains pools. @files provides an array of file descriptors which will be made available to the 'init' process of the guest. The file handles exposed to the guest will be renumbered to start from 3 (ie immediately following stderr). This is only supported for guests which use container based virtualization technology. If the VIR_DOMAIN_START_PAUSED flag is set, or if the guest domain has a managed save image that requested paused state (see virDomainManagedSave()) the guest domain will be started, but its CPUs will remain paused. The CPUs can later be manually started using virDomainResume(). In all other cases, the guest domain will be running. If the VIR_DOMAIN_START_AUTODESTROY flag is set, the guest domain will be automatically destroyed when the virConnectPtr object is finally released. This will also happen if the client application crashes / loses its connection to the libvirtd daemon. Any domains marked for auto destroy will block attempts at migration, save-to-file, or snapshots. If the VIR_DOMAIN_START_BYPASS_CACHE flag is set, and there is a managed save file for this domain (created by virDomainManagedSave()), then libvirt will attempt to bypass the file system cache while restoring the file, or fail if it cannot do so for the given system; this can allow less pressure on file system cache, but also risks slowing loads from NFS. If the VIR_DOMAIN_START_FORCE_BOOT flag is set, then any managed save file for this domain is discarded, and the domain boots from scratch. rXz!virDomainCreateWithFiles() failed)rZvirDomainCreateWithFilesrpr)rrer;r>rrrcreateWithFileso s!zvirDomain.createWithFiles) mountpointsr;rcCs$t|j||}|dkr td|S)z.Freeze specified filesystems within the guest rXzvirDomainFSFreeze() failed)rZvirDomainFSFreezerprrrgr;r>rrrfsFreeze szvirDomain.fsFreezecCs$t|j||}|dkr td|S)z,Thaw specified filesystems within the guest rXzvirDomainFSThaw() failed)rZvirDomainFSThawrprrhrrrfsThaw szvirDomain.fsThawcCs"t|j|}|durtd|S)z%Extract information about guest time NzvirDomainGetTime() failed)rZvirDomainGetTimerprr}rrrgetTime szvirDomain.getTime)timer;rcCs$t|j||}|dkr td|S)zSet guest time to the given value. @time is a dict containing 'seconds' field for seconds and 'nseconds' field for nanoseconds rXzvirDomainSetTime() failed)rZvirDomainSetTimerpr)rrlr;r>rrrsetTime szvirDomain.setTime)r@rer;rcCs&t|j|||}|dkr"td|S)aAssociate the array of FDs passed as @fds with the domain object under @name. The FDs are associated as long as the connection used to associated exists and are disposed of afterwards. FD may still be kept open by the hypervisor for as long as it's needed. Security labelling (e.g. via the selinux) may be applied on the passed FDs when requiredg for usage by the VM. By default libvirt does not restore the seclabels on the FDs afterwards to avoid keeping it open unnecessarily. Restoring of the security label can be requested by passing either VIR_DOMAIN_FD_ASSOCIATE_SECLABEL_RESTORE for a best-effort attempt to restore the security label after use. Requesting the restore of security label will require that the file descriptors are kept open for the whole time they are used by the hypervisor, or other additional overhead. In certain cases usage of the fd group would imply read-only access. Passing VIR_DOMAIN_FD_ASSOCIATE_SECLABEL_WRITABLE in @flags ensures that a writable security label is picked in case when the file represented by the fds may be used in write mode. rXzvirDomainFDAssociate() failed)rZvirDomainFDAssociaterpr)rr@rer;r>rrr FDAssociate szvirDomain.FDAssociate)N)r)r)r)r)r)r)Nr)r)r)r)rr)Nr)r)r)r)r)r)r)rr)rr)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)rr)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)rNNr)NrNNr)r)r)r)r)r)r)r)r)rNr)NNNrNr)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)Nr)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)Nr)Nr)r)Nr)r)r1r2r3rrsrurwryrzr{r|r~rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr@rrrrrrrr r r rrrrrrrrrrrrrr!r"r#r%r&r(r)r*r+r.r0r1r2r3r5r8r9r:r;r<r?r@rArCrDrErGrHrJrKrLrMrOrPrQrRrSrTr/rUrVrWrXrYrZr[r5rrbrdrfr4rirjrkrmrnrrrrrs\         B  c   ,  % i ! 4   $     4                       I                '       $        %  t   %!    &  c@seZdZd5ddZddZddZdd Zd6d d Zd dZddZ d7ddZ ddZ ddZ ddZ ddZddZddZd8dd Zd!d"Zd9d#d$Zd%d&Zd'd(Zd)d*Zd:d+d,Zd-d.Zd;d/d0Zdrrr DHCPLeases szvirNetwork.DHCPLeasescCs t|j}|durtd|S)z1Extract the UUID unique Identifier of a network. NzvirNetworkGetUUID() failed)rZvirNetworkGetUUIDrprrxrrrr{ s zvirNetwork.UUIDcCs t|j}|durtd|S)z5Fetch globally unique ID of the network as a string. Nz virNetworkGetUUIDString() failed)rZvirNetworkGetUUIDStringrprrxrrrr| s zvirNetwork.UUIDStringcCs"t|j|}|durtd|S)aProvide an XML description of the network. The description may be reused later to relaunch the network with virNetworkCreateXML(). Normally, if a network included a physical function, the output includes all virtual functions tied to that physical interface. If @flags includes VIR_NETWORK_XML_INACTIVE, then the expansion of virtual interfaces is not performed. NzvirNetworkGetXMLDesc() failed)rZvirNetworkGetXMLDescrprr}rrrr~ szvirNetwork.XMLDesccCs t|j}|dkrtd|S)z*Extract the autostart flag for a network. rXzvirNetworkGetAutostart() failed)rZvirNetworkGetAutostartrprrxrrrrs zvirNetwork.autostartcCs t|j}|durtd|S)zyProvides a bridge interface name to which a domain may connect a network interface in order to join the network. Nz virNetworkGetBridgeName() failed)rZvirNetworkGetBridgeNamerprrxrrr bridgeNames zvirNetwork.bridgeNamecCs t|j}|dkrtd|S)zCreate and start a defined network. If the call succeed the network moves from the defined to the running networks pools. rXzvirNetworkCreate() failed)rZvirNetworkCreaterprrxrrrr"s zvirNetwork.createcCs t|j}|dkrtd|S)a Destroy the network object. The running instance is shutdown if not down already and all resources used by it are given back to the hypervisor. This does not free the associated virNetworkPtr object. This function may require privileged access rXzvirNetworkDestroy() failed)rZvirNetworkDestroyrprrxrrrr*s zvirNetwork.destroycCs t|j}|dkrtd|S)z.Determine if the network is currently running rXzvirNetworkIsActive() failed)rZvirNetworkIsActiverprrxrrrr4s zvirNetwork.isActivecCs t|j}|dkrtd|S)ztDetermine if the network has a persistent configuration which means it will still exist after shutting down rXzvirNetworkIsPersistent() failed)rZvirNetworkIsPersistentrprrxrrrr;s zvirNetwork.isPersistentcCs&t|j|||}|dur"td|S)aRetrieves the appropriate network element given by @type. If VIR_NETWORK_METADATA_ELEMENT is requested parameter @uri must be set to the name of the namespace the requested elements belong to, otherwise must be None. If an element of the network XML is not present, the resulting error will be VIR_ERR_NO_NETWORK_METADATA. This method forms a shortcut for seeing information from virNetworkSetMetadata() without having to go through virNetworkGetXMLDesc(). @flags controls whether the live network state or persistent configuration will be queried. NzvirNetworkGetMetadata() failed)rZvirNetworkGetMetadatarprrrrrrCs zvirNetwork.metadatacCst|j}|S)z%Get the public name for that network )rZvirNetworkGetNamerprxrrrr@Us zvirNetwork.namecCs0t|j||}|dur tdt||d}|S)zCreate a new network port, based on an XML description similar to the one returned by virNetworkPortGetXMLDesc() virNetworkPortFree should be used to free the resources after the network port object is no longer needed. Nz virNetworkPortCreateXML() failedr<)rZvirNetworkPortCreateXMLrprvirNetworkPort)rZxmldescr;r>_virNetwork__tmprrr portCreateXMLZs  zvirNetwork.portCreateXMLcCs.t|j|}|durtdt||d}|S)=Try to lookup a port on the given network based on its UUID. Nz#virNetworkPortLookupByUUID() failedr<)rZvirNetworkPortLookupByUUIDrprrr)ruuidr>rsrrrportLookupByUUIDjs  zvirNetwork.portLookupByUUIDcCs.t|j|}|durtdt||d}|S)ruNz)virNetworkPortLookupByUUIDString() failedr<)rZ virNetworkPortLookupByUUIDStringrprrr)ruuidstrr>rsrrrportLookupByUUIDStringvs  z!virNetwork.portLookupByUUIDStringcCs"t|j|}|dkrtd|S)zWConfigure the network to be automatically started when the host machine boots. rXzvirNetworkSetAutostart() failed)rZvirNetworkSetAutostartrprr'rrrr(~szvirNetwork.setAutostartcCs*t|j|||||}|dkr&td|S)aSets the appropriate network element given by @type to the value of @metadata. A @type of VIR_NETWORK_METADATA_DESCRIPTION is free-form text; VIR_NETWORK_METADATA_TITLE is free-form, but no newlines are permitted, and should be short (although the length is not enforced). For these two options @key and @uri are irrelevant and must be set to None. For type VIR_NETWORK_METADATA_ELEMENT @metadata must be well-formed XML belonging to namespace defined by @uri with local name @key. Passing None for @metadata says to remove that element from the network XML (passing the empty string leaves the element present). The resulting metadata will be present in virNetworkGetXMLDesc(), as well as quick access through virNetworkGetMetadata(). @flags controls whether the live network state, persistent configuration, or both will be modified. rXzvirNetworkSetMetadata() failed)rZvirNetworkSetMetadatarprr=rrrr?szvirNetwork.setMetadatacCs t|j}|dkrtd|S)z9Undefine a network but does not stop it if it is running rXzvirNetworkUndefine() failed)rZvirNetworkUndefinerprrxrrrrVs zvirNetwork.undefinecCs*t|j|||||}|dkr&td|S)z|Update the definition of an existing network, either its live running state, its persistent configuration, or both. rXzvirNetworkUpdate() failed)rZvirNetworkUpdaterpr)rZcommandsectionZ parentIndexrr;r>rrrupdateszvirNetwork.updaterrr\cs0tj|}|durtdfdd|DS)zHList all ports on the network and returns a list of network port objectsNzvirNetworkListAllPorts() failedcsg|]}t|dqSr])rrr_Zdomptrr rrr`raz+virNetwork.listAllPorts..)rZvirNetworkListAllPortsrprr}rr r listAllPortsszvirNetwork.listAllPorts)N)Nr)r)r)r)r)r)r)r1r2r3rrsrurwrpr{r|r~rrqrrrrrr@rtrwryr(r?rVr{r5rr}rrrrro s0          roc@steZdZdddddZddZddZd d Zd d Zd dZddZ dddZ dddZ dddZ dddZ dS)rrNrcCs8||_||_t|jdvr.tdt|||_dSrl)_netrurnror1rrp)rnetr=rrrrs  zvirNetworkPort.__init__cCs |jdurt|jd|_dSrH)rprZvirNetworkPortFreer rrrrss  zvirNetworkPort.__del__cCs|jSrHrtr rrrruszvirNetworkPort.connectcCs|jSrH)r~r rrrnetworkszvirNetworkPort.networkcCs t|jSrv)rZvirNetworkPort_pointerrpr rrrrwszvirNetworkPort.c_pointercCs t|j}|durtd|S)z6Extract the UUID unique Identifier of a network port. NzvirNetworkPortGetUUID() failed)rZvirNetworkPortGetUUIDrprrxrrrr{s zvirNetworkPort.UUIDcCs t|j}|durtd|S)z:Fetch globally unique ID of the network port as a string. Nz$virNetworkPortGetUUIDString() failed)rZvirNetworkPortGetUUIDStringrprrxrrrr|s zvirNetworkPort.UUIDStringrcCs"t|j|}|durtd|S)zProvide an XML description of the network port. The description may be reused later to recreate the port with virNetworkPortCreateXML(). Nz!virNetworkPortGetXMLDesc() failed)rZvirNetworkPortGetXMLDescrprr}rrrr~szvirNetworkPort.XMLDesccCs"t|j|}|dkrtd|S)zDelete the network port. This does not free the associated virNetworkPortPtr object. It is the caller's responsibility to ensure the port is not still in use by a virtual machine before deleting port. rXzvirNetworkPortDelete() failed)rZvirNetworkPortDeleterprr}rrrdeleteszvirNetworkPort.deletecCs"t|j|}|durtd|S)zGet the port parameters Nz$virNetworkPortGetParameters() failed)rZvirNetworkPortGetParametersrprr}rrr parametersszvirNetworkPort.parameterscCs$t|j||}|dkr td|S)zChange the port tunables rXz$virNetworkPortSetParameters() failed)rZvirNetworkPortSetParametersrprrrrr setParametersszvirNetworkPort.setParameters)N)r)r)r)r)r1r2r3rrsrurrwr{r|r~rrrrrrrrrs   rrc@sleZdZdddZddZddZdd Zd d Zdd dZdddZ dddZ ddZ ddZ ddZ dS) virInterfaceNcCs.||_t|jdvr$tdt|||_dSrlrmrqrrrr szvirInterface.__init__cCs |jdurt|jd|_dSrH)rprZvirInterfaceFreer rrrrss  zvirInterface.__del__cCs|jSrHrtr rrrruszvirInterface.connectcCs t|jSrv)rZvirInterface_pointerrpr rrrrwszvirInterface.c_pointercCs t|j}|durtd|S)z\Get the MAC for an interface as string. For more information about MAC see RFC4122. Nz!virInterfaceGetMACString() failed)rZvirInterfaceGetMACStringrprrxrrr MACString!s zvirInterface.MACStringrcCs"t|j|}|durtd|S)a@VIR_INTERFACE_XML_INACTIVE - return the static configuration, suitable for use redefining the interface via virInterfaceDefineXML() Provide an XML description of the interface. If VIR_INTERFACE_XML_INACTIVE is set, the description may be reused later to redefine the interface with virInterfaceDefineXML(). If it is not set, the ip address and netmask will be the current live setting of the interface, not the settings from the config files. NzvirInterfaceGetXMLDesc() failed)rZvirInterfaceGetXMLDescrprr}rrrr~)s zvirInterface.XMLDesccCs"t|j|}|dkrtd|S)aKActivate an interface (i.e. call "ifup"). If there was an open network config transaction at the time this interface was defined (that is, if virInterfaceChangeBegin() had been called), the interface will be brought back down (and then undefined) if virInterfaceChangeRollback() is called. rXzvirInterfaceCreate() failed)rZvirInterfaceCreaterprr}rrrr8szvirInterface.createcCs"t|j|}|dkrtd|S)adeactivate an interface (ie call "ifdown") This does not remove the interface from the config, and does not free the associated virInterfacePtr object. If there is an open network config transaction at the time this interface is destroyed (that is, if virInterfaceChangeBegin() had been called), and if the interface is later undefined and then virInterfaceChangeRollback() is called, the restoral of the interface definition will also bring the interface back up. rXzvirInterfaceDestroy() failed)rZvirInterfaceDestroyrprr}rrrrDs zvirInterface.destroycCs t|j}|dkrtd|S)z0Determine if the interface is currently running rXzvirInterfaceIsActive() failed)rZvirInterfaceIsActiverprrxrrrrSs zvirInterface.isActivecCst|j}|S)z'Get the public name for that interface )rZvirInterfaceGetNamerprxrrrr@Zs zvirInterface.namecCs t|j}|dkrtd|S)aUndefine an interface, ie remove it from the config. This does not free the associated virInterfacePtr object. Normally this change in the interface configuration is permanent/persistent, but if virInterfaceChangeBegin() has been previously called (i.e. if an interface config transaction is open), the removal of the interface definition will only become permanent if virInterfaceChangeCommit() is called prior to the next reboot of the system running libvirtd. Prior to that time, the definition can be explicitly restored using virInterfaceChangeRollback(), or will be automatically restored during the next reboot of the system running libvirtd. rXzvirInterfaceUndefine() failed)rZvirInterfaceUndefinerprrxrrrrV_s zvirInterface.undefine)N)r)r)r)r1r2r3rrsrurwrr~rrrr@rVrrrrr s   rc@seZdZd7ddZddZddZdd Zd d Zd d Zd8ddZ ddZ d9ddZ d:ddZ d;ddZ dd+d,Zd-d.Zd/d0Zd1d2Zd?eed3d4d5d6ZdS)@virStoragePoolNcCs.||_t|jdvr$tdt|||_dSrlrmrqrrrrrszvirStoragePool.__init__cCs |jdurt|jd|_dSrH)rprZvirStoragePoolFreer rrrrsxs  zvirStoragePool.__del__cCs|jSrHrtr rrrru}szvirStoragePool.connectcCs t|jSrv)rZvirStoragePool_pointerrpr rrrrwszvirStoragePool.c_pointercCs t|j}|durtd|S)z6Extract the UUID unique Identifier of a storage pool. NzvirStoragePoolGetUUID() failed)rZvirStoragePoolGetUUIDrprrxrrrr{s zvirStoragePool.UUIDcCs t|j}|durtd|S)z:Fetch globally unique ID of the storage pool as a string. Nz$virStoragePoolGetUUIDString() failed)rZvirStoragePoolGetUUIDStringrprrxrrrr|s zvirStoragePool.UUIDStringrcCs"t|j|}|durtd|S)zFetch an XML document describing all aspects of the storage pool. This is suitable for later feeding back into the virStoragePoolCreateXML method. Nz!virStoragePoolGetXMLDesc() failed)rZvirStoragePoolGetXMLDescrprr}rrrr~szvirStoragePool.XMLDesccCs t|j}|dkrtd|S)z.Extract the autostart flag for a storage pool rXz#virStoragePoolGetAutostart() failed)rZvirStoragePoolGetAutostartrprrxrrrrs zvirStoragePool.autostartcCs"t|j|}|dkrtd|S)zCurrently only filesystem pool accepts flags VIR_STORAGE_POOL_BUILD_OVERWRITE and VIR_STORAGE_POOL_BUILD_NO_OVERWRITE. Build the underlying storage pool rXzvirStoragePoolBuild() failed)rZvirStoragePoolBuildrprr}rrrbuildszvirStoragePool.buildcCs"t|j|}|dkrtd|S)z Starts an inactive storage pool rXzvirStoragePoolCreate() failed)rZvirStoragePoolCreaterprr}rrrrszvirStoragePool.createcCs2t|j||}|dur tdt|j|d}|S)aCreate a storage volume within a pool based on an XML description. Not all pools support creation of volumes. Since 1.0.1 VIR_STORAGE_VOL_CREATE_PREALLOC_METADATA in flags can be used to get higher performance with qcow2 image files which don't support full preallocation, by creating a sparse image file with metadata. virStorageVolFree should be used to free the resources after the storage volume object is no longer needed. NzvirStorageVolCreateXML() failedr<)rZvirStorageVolCreateXMLrpr virStorageVolrn)rrr;r>_virStoragePool__tmprrr createXMLs zvirStoragePool.createXMLcCsH|durd}n|j}t|j|||}|dur6tdt|j|d}|S)aICreate a storage volume in the parent pool, using the 'clonevol' volume as input. Information for the new volume (name, perms) are passed via a typical volume XML description. Since 1.0.1 VIR_STORAGE_VOL_CREATE_PREALLOC_METADATA in flags can be used to get higher performance with qcow2 image files which don't support full preallocation, by creating a sparse image file with metadata. virStorageVolFree should be used to free the resources after the storage volume object is no longer needed. Nz#virStorageVolCreateXMLFrom() failedr<)rprZvirStorageVolCreateXMLFromrrrn)rrZclonevolr;Z clonevol__or>rrrr createXMLFroms zvirStoragePool.createXMLFromcCs"t|j|}|dkrtd|S)zDelete the underlying pool resources. This is a non-recoverable operation. The virStoragePoolPtr object itself is not free'd. rXzvirStoragePoolDelete() failed)rZvirStoragePoolDeleterprr}rrrrszvirStoragePool.deletecCs t|j}|dkrtd|S)a/Destroy an active storage pool. This will deactivate the pool on the host, but keep any persistent config associated with it. If it has a persistent config it can later be restarted with virStoragePoolCreate(). This does not free the associated virStoragePoolPtr object. rXzvirStoragePoolDestroy() failed)rZvirStoragePoolDestroyrprrxrrrrs zvirStoragePool.destroycCs t|j}|durtd|S)zExtract information about a storage pool. Note that if the connection used to get the domain is limited only a partial set of the information can be extracted. NzvirStoragePoolGetInfo() failed)rZvirStoragePoolGetInforprrxrrrrs zvirStoragePool.infocCs t|j}|dkrtd|S)z3Determine if the storage pool is currently running rXzvirStoragePoolIsActive() failed)rZvirStoragePoolIsActiverprrxrrrrs zvirStoragePool.isActivecCs t|j}|dkrtd|S)zyDetermine if the storage pool has a persistent configuration which means it will still exist after shutting down rXz#virStoragePoolIsPersistent() failed)rZvirStoragePoolIsPersistentrprrxrrrrs zvirStoragePool.isPersistentcCs t|j}|durtd|S)zElist the storage volumes, stores the pointers to the names in @names Nz"virStoragePoolListVolumes() failed)rZvirStoragePoolListVolumesrprrxrrr listVolumes"s zvirStoragePool.listVolumescCst|j}|S)z2Fetch the locally unique name of the storage pool )rZvirStoragePoolGetNamerprxrrrr@-s zvirStoragePool.namecCs t|j}|dkrtd|S)z2Fetch the number of storage volumes within a pool rXz#virStoragePoolNumOfVolumes() failed)rZvirStoragePoolNumOfVolumesrprrxrrr numOfVolumes2s zvirStoragePool.numOfVolumescCs"t|j|}|dkrtd|S)zRequest that the pool refresh its list of volumes. This may involve communicating with a remote server, and/or initializing new devices at the OS layer rXzvirStoragePoolRefresh() failed)rZvirStoragePoolRefreshrprr}rrrrefresh9szvirStoragePool.refreshcCs"t|j|}|dkrtd|S)z\Configure the storage pool to be automatically started when the host machine boots. rXz#virStoragePoolSetAutostart() failed)rZvirStoragePoolSetAutostartrprr'rrrr(BszvirStoragePool.setAutostartcCs0t|j|}|durtdt|j|d}|S)zFetch a pointer to a storage volume based on its name within a pool virStorageVolFree should be used to free the resources after the storage volume object is no longer needed. Nz"virStorageVolLookupByName() failedr<)rZvirStorageVolLookupByNamerprrrn)rr@r>rrrrstorageVolLookupByNameJs z%virStoragePool.storageVolLookupByNamecCs t|j}|dkrtd|S)z"Undefine an inactive storage pool rXzvirStoragePoolUndefine() failed)rZvirStoragePoolUndefinerprrxrrrrVVs zvirStoragePool.undefinerr\cs0tj|}|durtdfdd|DS)zEList all storage volumes and returns a list of storage volume objectsNz%virStoragePoolListAllVolumes() failedcsg|]}tj|dqSr])rrn)r_Zvolptrr rrr`fraz1virStoragePool.listAllVolumes..)rZvirStoragePoolListAllVolumesrprr}rr rlistAllVolumes`szvirStoragePool.listAllVolumes)N)r)r)r)r)r)r)r)r)r1r2r3rrsrurwr{r|r~rrrrrrrrrrrr@rrr(rrVr5rrrrrrrqs2            rc@seZdZdZd&ddZddZddZd d Zd'd d Zd(ddZ d)ddZ ddZ d*ddZ ddZ ddZddZd+ddZddZd,d d!Zd-d"d#Zd.d$d%ZdS)/riNcCs.||_t|jdvr$tdt|||_dSrlrmrqrrrroszvirStorageVol.__init__cCs |jdurt|jd|_dSrH)rprZvirStorageVolFreer rrrrsus  zvirStorageVol.__del__cCs|jSrHrtr rrrruzszvirStorageVol.connectcCs t|jSrv)rZvirStorageVol_pointerrpr rrrrw}szvirStorageVol.c_pointerrcCs"t|j|}|durtd|S)zKFetch an XML document describing all aspects of the storage volume Nz virStorageVolGetXMLDesc() failed)rZvirStorageVolGetXMLDescrprr}rrrr~szvirStorageVol.XMLDesccCs"t|j|}|dkrtd|S)z(Delete the storage volume from the pool rXzvirStorageVolDelete() failed)rZvirStorageVolDeleterprr}rrrrszvirStorageVol.deletecCs<|durd}n|j}t|j||||}|dkr8td|S)a'Download the content of the volume as a stream. If @length is zero, then the remaining contents of the volume after @offset will be downloaded. Please note that the stream transports the volume itself as is, so the downloaded data may not correspond to guest OS visible state in cases when a complex storage format such as qcow2 or vmdk is used. If VIR_STORAGE_VOL_DOWNLOAD_SPARSE_STREAM is set in @flags effective transmission of holes is enabled. This assumes using the @stream with combination of virStreamSparseRecvAll() or virStreamRecvFlags(stream, ..., flags = VIR_STREAM_RECV_STOP_AT_HOLE) for honouring holes sent by server. This call sets up an asynchronous stream; subsequent use of stream APIs is necessary to transfer the actual data, determine how much data is successfully transferred, and detect any errors. The results will be unpredictable if another active stream is writing to the storage volume. NrXzvirStorageVolDownload() failed)rprZvirStorageVolDownloadrrrrlengthr;r r>rrrdownloadszvirStorageVol.downloadcCs t|j}|durtd|S)Extract information about a storage volume. Note that if the connection used to get the domain is limited only a partial set of the information can be extracted. NzvirStorageVolGetInfo() failed)rZvirStorageVolGetInforprrxrrrrs zvirStorageVol.infocCs"t|j|}|durtd|S)rNz"virStorageVolGetInfoFlags() failed)rZvirStorageVolGetInfoFlagsrprr}rrr infoFlagsszvirStorageVol.infoFlagscCs t|j}|durtd|S)zFetch the storage volume key. This is globally unique, so the same volume will have the same key no matter what host it is accessed from NzvirStorageVolGetKey() failed)rZvirStorageVolGetKeyrprrxrrrr>s zvirStorageVol.keycCst|j}|S)zQFetch the storage volume name. This is unique within the scope of a pool )rZvirStorageVolGetNamerprxrrrr@s zvirStorageVol.namecCs t|j}|durtd|S)aFetch the storage volume path. Depending on the pool configuration this is either persistent across hosts, or dynamically assigned at pool startup. Consult pool documentation for information on getting the persistent naming NzvirStorageVolGetPath() failed)rZvirStorageVolGetPathrprrxrrrrs zvirStorageVol.pathcCs$t|j||}|dkr td|S)aXChanges the capacity of the storage volume @vol to @capacity. The operation will fail if the new capacity requires allocation that would exceed the remaining free space in the parent pool. The contents of the new capacity will appear as all zero bytes. The capacity value will be rounded to the granularity supported by the hypervisor. Normally, the operation will attempt to affect capacity with a minimum impact on allocation (that is, the default operation favors a sparse resize). If @flags contains VIR_STORAGE_VOL_RESIZE_ALLOCATE, then the operation will ensure that allocation is sufficient for the new capacity; this may make the operation take noticeably longer. Normally, the operation treats @capacity as the new size in bytes; but if @flags contains VIR_STORAGE_VOL_RESIZE_DELTA, then @capacity represents the size difference to add to the current size. It is up to the storage pool implementation whether unaligned requests are rounded up to the next valid boundary, or rejected. Normally, this operation should only be used to enlarge capacity; but if @flags contains VIR_STORAGE_VOL_RESIZE_SHRINK, it is possible to attempt a reduction in capacity even though it might cause data loss. If VIR_STORAGE_VOL_RESIZE_DELTA is also present, then @capacity is subtracted from the current size; without it, @capacity represents the absolute new size regardless of whether it is larger or smaller than the current size. rXzvirStorageVolResize() failed)rZvirStorageVolResizerpr)rZcapacityr;r>rrrresizeszvirStorageVol.resizecCs.t|j}|durtdt|j|d}|S)zFetch a storage pool which contains a particular volume virStoragePoolFree should be used to free the resources after the storage pool object is no longer needed. Nz%virStoragePoolLookupByVolume() failedr<)rZvirStoragePoolLookupByVolumerprrrn)rr>Z_virStorageVol__tmprrrstoragePoolLookupByVolumes  z'virStorageVol.storagePoolLookupByVolumecCs<|durd}n|j}t|j||||}|dkr8td|S)apUpload new content to the volume from a stream. This call will fail if @offset + @length exceeds the size of the volume. Otherwise, if @length is non-zero, an error will be raised if an attempt is made to upload greater than @length bytes of data. Please note that the stream transports the volume itself as is, so the downloaded data may not correspond to guest OS visible state in cases when a complex storage format such as qcow2 or vmdk is used. If VIR_STORAGE_VOL_UPLOAD_SPARSE_STREAM is set in @flags effective transmission of holes is enabled. This assumes using the @stream with combination of virStreamSparseSendAll() or virStreamSendHole() to preserve source file sparseness. This call sets up an asynchronous stream; subsequent use of stream APIs is necessary to transfer the actual data, determine how much data is successfully transferred, and detect any errors. The results will be unpredictable if another active stream is writing to the storage volume. When the data stream is closed whether the upload is successful or not an attempt will be made to refresh the target storage pool if an asynchronous build is not running in order to reflect pool and volume changes as a result of the upload. Depending on the target volume storage backend and the source stream type for a successful upload, the target volume may take on the characteristics from the source stream such as format type, capacity, and allocation. NrXzvirStorageVolUpload() failed)rprZvirStorageVolUploadrrrrrupload szvirStorageVol.uploadcCs"t|j|}|dkrtd|S)aEnsure data previously on a volume is not accessible to future reads. The data to be wiped may include the format and possibly size information, so non-raw images might become raw with a different size. It is storage backend dependent whether the format and size information is regenerated once the initial volume wipe is completed. Depending on the actual volume representation, this call may not overwrite the physical location of the volume. For instance, files stored journaled, log structured, copy-on-write, versioned, and network file systems are known to be problematic. rXzvirStorageVolWipe() failed)rZvirStorageVolWiperprr}rrrwipe1s zvirStorageVol.wipecCs$t|j||}|dkr td|S)aSimilar to virStorageVolWipe, but one can choose between different wiping algorithms. Also note, that depending on the actual volume representation, this call may not really overwrite the physical location of the volume. For instance, files stored journaled, log structured, copy-on-write, versioned, and network file systems are known to be problematic. rXz!virStorageVolWipePattern() failed)rZvirStorageVolWipePatternrpr)r algorithmr;r>rrr wipePatternBszvirStorageVol.wipePattern)N)r)r)r)r)r)r)r)r)r1r2r3 streamBufSizerrsrurwr~rrrrr>r@rrrrrrrrrrrhs$    !    & rc @sf eZdZdddZddZdddZdd d Zdd d Zdd dZdddZ dddZ ddZ dddZ dddZ dddZdddZddZddd Zdd!d"Zdd#d$Zdd%d&Zdd'd(Zdd)d*Zdd+d,Zd-d.Zd/d0Zdd1d2Zd3d4Zdd5d6Zd7d8Zd9d:Zd;d<Zd=d>Z dd?d@Z!ddAdBZ"ddCdDZ#dEdFZ$ddGdHZ%ddIdJZ&dKdLZ'dMdNZ(dOdPZ)ddQdRZ*dSdTZ+dUdVZ,dWdXZ-dYdZZ.d[d\Z/d]d^Z0d_d`Z1dadbZ2dcddZ3ddedfZ4dgdhZ5didjZ6dkdlZ7dmdnZ8dodpZ9dqdrZ:dsdtZ;dudvZd{d|Z?dd}d~Z@ddZAdddZBddZCddZDddZEdddZFdddZGdddZHddZIdddZJddZKddZLddZMddZNdddZOddZPddZQddZRddZSddZTddZUdddZVddZWddZXdddZYddZZddZ[ddZ\ddZ]dddZ^dddZ_dddZ`dddZaddd„ZbddĄZcddƄZdddȄZedddʄZfdd̄Zgddd΄ZhdddЄZiddd҄ZjddԄZkddքZldd؄ZmddڄZndd܄ZoddބZpdddZqddZrddZsddddZtddddZuevewexevexeveyddddZze{ddddZ|e{e}ddddZ~deeddddZdeeeeefedddZdeeefedddZdeeeefedddZdeeeefedddZdeeeeeefedddZdeeeeeeefedddZdeeeeeeeefed d d Zdeeeeeefdd d dZdeeeeeeefedddZdeeeeefedddZdeeeefedddZdeeeefedddZdeeeefedddZdeeeefedddZdeeeefedd d!Zdeeeefed"d#d$Zdeeeeefed%d&d'Zdeeeefedd(d)Zdeeeefed*d+d,Zdeeefeeefed"d-d.Zdeeeefedd/d0Zdeeeeefed1d2d3Zdeeeeeeefed4d5d6Zdeeeeeefed7d8d9Zdeeeeefed:d;d<Zdeeeeeefed=d>d?Zedd@dAdBZdCeeeeefedDdEdFZdCeeeeefed1dGdHZedd@dIdJZevdCeee}edKdLdMZevdeee}edNdOdPZdQeeeeefedRdSdTZdQeeefedUdVdWZedd@dXdYZevdQeee}edZd[d\Zd]eeeeefed^d_d`Zd]eeefedadbdcZedd@dddeZevd]eee}edfdgdhZdieeeeefedjdkdlZdieeefedmdndoZedd@dpdqZevdieee}edrdsdtZdeeddudvdwZdeedQdudxdyZdeedCdudzd{Zdeed|dud}d~Zdeed]duddZdeedduddZdeedduddZdeediduddZeeeefedddZddddZee}edddZdeeeeddddZdeeeedeeeffdddZdedeeeedeeeffdddZdS(rNcCs(t|jdvrtdt|||_dSrl)ror1rrp)rr=rrrrPszvirConnect.__init__cCs t|jSrv)rZvirConnect_pointerrpr rrrrwUszvirConnect.c_pointerrcCs(t|j||||}|dkr$td|S)z3Allocate or free some pages in the huge pages pool rXzvirNodeAllocPages() failed)rZvirNodeAllocPagesrpr)rpages startCellZ cellCountr;r>rrr allocPages]szvirConnect.allocPagescCs$t|j||}|dur td|S)zQComputes the most feature-rich CPU which is compatible with all given host CPUs. NzvirConnectBaselineCPU() failed)rZvirConnectBaselineCPUrpr)rxmlCPUsr;r>rrr baselineCPUdszvirConnect.baselineCPUc Cs,t|j||||||}|dur(td|S)z|Computes the most feature-rich CPU which is compatible with all given CPUs and can be provided by the specified hypervisor. Nz(virConnectBaselineHypervisorCPU() failed)rZvirConnectBaselineHypervisorCPUrpr)remulatorarchmachinevirttyperr;r>rrrbaselineHypervisorCPUksz virConnect.baselineHypervisorCPUcCs"t|j|}|dkrtd|S)aThis function creates a restore point to which one can return later by calling virInterfaceChangeRollback(). This function should be called before any transaction with interface configuration. Once it is known that a new configuration works, it can be committed via virInterfaceChangeCommit(), which frees the restore point. If virInterfaceChangeBegin() is called when a transaction is already opened, this function will fail, and a VIR_ERR_INVALID_OPERATION will be logged. rXz virInterfaceChangeBegin() failed)rZvirInterfaceChangeBeginrprr}rrr changeBeginvs zvirConnect.changeBegincCs"t|j|}|dkrtd|S)a*This commits the changes made to interfaces and frees the restore point created by virInterfaceChangeBegin(). If virInterfaceChangeCommit() is called when a transaction is not opened, this function will fail, and a VIR_ERR_INVALID_OPERATION will be logged. rXz!virInterfaceChangeCommit() failed)rZvirInterfaceChangeCommitrprr}rrr changeCommitszvirConnect.changeCommitcCs"t|j|}|dkrtd|S)a1This cancels changes made to interfaces settings by restoring previous state created by virInterfaceChangeBegin(). If virInterfaceChangeRollback() is called when a transaction is not opened, this function will fail, and a VIR_ERR_INVALID_OPERATION will be logged. rXz#virInterfaceChangeRollback() failed)rZvirInterfaceChangeRollbackrprr}rrrchangeRollbackszvirConnect.changeRollbackcCs&t|j}d|_|dkr"td|S)aThis function closes the connection to the Hypervisor. This should not be called if further interaction with the Hypervisor are needed especially if there is running domain which need further monitoring by the application. Connections are reference counted; the count is explicitly increased by the initial open (virConnectOpen, virConnectOpenAuth, and the like) as well as virConnectRef; it is also temporarily increased by other API that depend on the connection remaining alive. The open and every virConnectRef call should have a matching virConnectClose, and all other references will be released after the corresponding operation completes. NrXzvirConnectClose() failed)rvirConnectCloserprrxrrrcloses zvirConnect.closecCs$t|j||}|dkr td|S)zCompares the given CPU description with the host CPU. See virConnectCompareHypervisorCPU() if you want to consider hypervisor abilities and compare the CPU to the CPU which a hypervisor is able to provide on the host. rXzvirConnectCompareCPU() failed)rZvirConnectCompareCPUrprrrr;r>rrr compareCPUszvirConnect.compareCPUc Cs,t|j||||||}|dkr(td|S)aCompares the given CPU description with the CPU the specified hypervisor is able to provide on the host. Any of @emulator, @arch, @machine, and @virttype parameters may be None; libvirt will choose sensible defaults tailored to the host and its current configuration. This is different from virConnectCompareCPU() which compares the CPU definition with the host CPU without considering any specific hypervisor and its abilities. rXz'virConnectCompareHypervisorCPU() failed)rZvirConnectCompareHypervisorCPUrpr)rrrrrZxmlCPUr;r>rrrcompareHypervisorCPUs zvirConnect.compareHypervisorCPUcCs0t|j||}|dur tdt||d}|S)zDeprecated after 0.4.6. Renamed to virDomainCreateXML() providing identical functionality. This existing name will be left indefinitely for API compatibility. NzvirDomainCreateLinux() failedr<)rZvirDomainCreateLinuxrprrrrr;r>_virConnect__tmprrr createLinuxs  zvirConnect.createLinuxcCs0t|j||}|dur tdt||d}|S)a6Launch a new guest domain, based on an XML description similar to the one returned by virDomainGetXMLDesc() This function may require privileged access to the hypervisor. The domain is not persistent, so its definition will disappear when it is destroyed, or if the host is restarted (see virDomainDefineXML() to define persistent domains). If the VIR_DOMAIN_START_PAUSED flag is set, the guest domain will be started, but its CPUs will remain paused. The CPUs can later be manually started using virDomainResume. If the VIR_DOMAIN_START_AUTODESTROY flag is set, the guest domain will be automatically destroyed when the virConnectPtr object is finally released. This will also happen if the client application crashes / loses its connection to the libvirtd daemon. Any domains marked for auto destroy will block attempts at migration. Hypervisors may also block save-to-file, or snapshots. If @flags includes VIR_DOMAIN_START_RESET_NVRAM, then libvirt will discard any existing NVRAM file and re-initialize NVRAM from the pristine template. virDomainFree should be used to free the resources after the domain object is no longer needed. NzvirDomainCreateXML() failedr<)rZvirDomainCreateXMLrprrrrrrrs  zvirConnect.createXMLcCs.t|j|}|durtdt||d}|S)ayDefine a domain, but does not start it. This definition is persistent, until explicitly undefined with virDomainUndefine(). A previous definition for this domain with the same UUID and name would be overridden if it already exists. virDomainFree should be used to free the resources after the domain object is no longer needed. NzvirDomainDefineXML() failedr<)rZvirDomainDefineXMLrprrrrr>rrrr defineXMLs  zvirConnect.defineXMLcCs0t|j||}|dur tdt||d}|S)azDefines a domain, but does not start it. This definition is persistent, until explicitly undefined with virDomainUndefine(). A previous definition for this domain with the same UUID and name would be overridden if it already exists. virDomainFree should be used to free the resources after the domain object is no longer needed. Nz virDomainDefineXMLFlags() failedr<)rZvirDomainDefineXMLFlagsrprrrrr;r>rrrrdefineXMLFlags s  zvirConnect.defineXMLFlagscCs&t|j|||}|dur"td|S)zReads native configuration data describing a domain, and generates libvirt domain XML. The format of the native data is hypervisor dependent. Nz&virConnectDomainXMLFromNative() failed)rZvirConnectDomainXMLFromNativerpr)r nativeFormatZ nativeConfigr;r>rrrdomainXMLFromNativeszvirConnect.domainXMLFromNativecCs&t|j|||}|dur"td|S)aReads a domain XML configuration document, and generates a native configuration file describing the domain. The format of the native data is hypervisor dependent. Note that certain hypervisor drivers such as the QEMU driver configure many aspects of the domain dynamically via hypervisor APIs and that may not be part of the returned native configuration format. Similarly certain resources are passed to the hypervisor via file descriptors, which are not part of the native configuration returned by this API. Such configuration is thus not trivially usable outside of libvirt. Nz$virConnectDomainXMLToNative() failed)rZvirConnectDomainXMLToNativerpr)rrZ domainXmlr;r>rrrdomainXMLToNative s zvirConnect.domainXMLToNativecCs&t|j|||}|dur"td|S)aTalks to a storage backend and attempts to auto-discover the set of available storage pool sources. e.g. For iSCSI this would be a set of iSCSI targets. For NFS this would be a list of exported paths. The srcSpec (optional for some storage pool types, e.g. local ones) is an instance of the storage pool's source element specifying where to look for the pools. srcSpec is not required for some types (e.g., those querying local storage resources only) Nz)virConnectFindStoragePoolSources() failed)rZ virConnectFindStoragePoolSourcesrpr)rroZsrcSpecr;r>rrrfindStoragePoolSources4s z!virConnect.findStoragePoolSourcescCs"t|j|}|durtd|S)zGet node CPU information NzvirNodeGetCPUMap() failed)rZvirNodeGetCPUMaprprr}rrr getCPUMapGszvirConnect.getCPUMapcCs$t|j||}|dur td|S)z&Get the list of supported CPU models. Nz#virConnectGetCPUModelNames() failed)rZvirConnectGetCPUModelNamesrpr)rrr;r>rrrgetCPUModelNamesNszvirConnect.getCPUModelNamescCs$t|j||}|dur td|S)zExtract node's CPU statistics. NzvirNodeGetCPUStats() failed)rZvirNodeGetCPUStatsrpr)rZcpuNumr;r>rrrrUszvirConnect.getCPUStatscCs t|j}|durtd|S)z2Provides capabilities of the hypervisor / driver. Nz"virConnectGetCapabilities() failed)rZvirConnectGetCapabilitiesrprrxrrrgetCapabilities`s zvirConnect.getCapabilitiescCs$t|j||}|dur td|S)z1Returns the available memory for a list of cells Nz"virNodeGetCellsFreeMemory() failed)rZvirNodeGetCellsFreeMemoryrpr)rrmaxCellsr>rrrgetCellsFreeMemorykszvirConnect.getCellsFreeMemorycCs*t|j|||||}|dur&td|S)zQuery domain capabilities Nz(virConnectGetDomainCapabilities() failed)rZvirConnectGetDomainCapabilitiesrpr)rZ emulatorbinrrrr;r>rrrgetDomainCapabilitiesvsz virConnect.getDomainCapabilitiescCst|j}|S)zprovides the free memory available on the Node Note: most libvirt APIs provide memory sizes in kibibytes, but in this function the returned value is in bytes. Divide by 1024 as necessary. )rZvirNodeGetFreeMemoryrprxrrr getFreeMemorys zvirConnect.getFreeMemorycCs(t|j||||}|dur$td|S)zIReturns the number of available pages for a list of cells and page sizes NzvirNodeGetFreePages() failed)rZvirNodeGetFreePagesrpr)rrrrr;r>rrr getFreePagesszvirConnect.getFreePagescCs t|j}|durtd|S)a=This returns a system hostname on which the hypervisor is running (based on the result of the gethostname system call, but possibly expanded to a fully-qualified domain name via getaddrinfo). If we are connected to a remote system, then this returns the hostname of the remote system. NzvirConnectGetHostname() failed)rZvirConnectGetHostnamerprrxrrr getHostnames zvirConnect.getHostnamecCs t|j}|durtd|S)zjExtract hardware information about the Node. Note that the memory size is reported in MiB instead of KiB. NzvirNodeGetInfo() failed)rZvirNodeGetInforprrxrrrgetInfos zvirConnect.getInfocCs t|j}|dkrtd|S)z3Returns the libvirt version of the connection host rXz virConnectGetLibVersion() failed)rZvirConnectGetLibVersionrprrxrrr getLibVersions zvirConnect.getLibVersioncCs"t|j|}|dkrtd|S)aProvides the maximum number of virtual CPUs supported for a guest VM of a specific type. The 'type' parameter here corresponds to the 'type' attribute in the element of the XML. This API doesn't take emulator limits into consideration, hence the returned value is not guaranteed to be usable. It is recommended to use virConnectGetDomainCapabilities() and look for "" in its output instead. rXzvirConnectGetMaxVcpus() failed)rZvirConnectGetMaxVcpusrpr)rror>rrr getMaxVcpusszvirConnect.getMaxVcpuscCs"t|j|}|durtd|S)zGet the node memory parameters Nz#virNodeGetMemoryParameters() failed)rZvirNodeGetMemoryParametersrprr}rrrgetMemoryParametersszvirConnect.getMemoryParameterscCs$t|j||}|dur td|S)z"Extract node's memory statistics. NzvirNodeGetMemoryStats() failed)rZvirNodeGetMemoryStatsrpr)rZcellNumr;r>rrrgetMemoryStatsszvirConnect.getMemoryStatscCs"t|j|}|durtd|S)z8Get platform specific information from the SEV firmware NzvirNodeGetSEVInfo() failed)rZvirNodeGetSEVInforprr}rrr getSEVInfoszvirConnect.getSEVInfocCs t|j}|durtd|S)z8Extract information about the hypervisor security model Nz virNodeGetSecurityModel() failed)rZvirNodeGetSecurityModelrprrxrrrgetSecurityModels zvirConnect.getSecurityModelcCs"t|j|}|durtd|S)zPrior creating a storage pool (for instance via virStoragePoolCreateXML or virStoragePoolDefineXML) it may be suitable to know what pool types are supported along with the file/disk formats for each pool. Nz-virConnectGetStoragePoolCapabilities() failed)rZ$virConnectGetStoragePoolCapabilitiesrprr}rrrgetStoragePoolCapabilitiessz%virConnect.getStoragePoolCapabilitiescCs"t|j|}|durtd|S)aThis returns the XML description of the sysinfo details for the host on which the hypervisor is running, in the same format as the element of a domain XML. This information is generally available only for hypervisors running with root privileges. NzvirConnectGetSysinfo() failed)rZvirConnectGetSysinforprr}rrr getSysinfoszvirConnect.getSysinfocCs t|j}|durtd|S)aXGet the name of the Hypervisor driver used. This is merely the driver name; for example, both KVM and QEMU guests are serviced by the driver for the qemu:// URI, so a return of "QEMU" does not indicate whether KVM acceleration is present. For more details about the hypervisor, use virConnectGetCapabilities(). NzvirConnectGetType() failed)rZvirConnectGetTyperprrxrrrgetTypes zvirConnect.getTypecCs t|j}|durtd|S)aThis returns the URI (name) of the hypervisor connection. Normally this is the same as or similar to the string passed to the virConnectOpen/virConnectOpenReadOnly call, but the driver may make the URI canonical. If name == None was passed to virConnectOpen, then the driver will return a non-None URI which can be used to connect to the same hypervisor later. NzvirConnectGetURI() failed)rZvirConnectGetURIrprrxrrrgetURI s zvirConnect.getURIcCs t|j}|dkrtd|S)z>Returns the running hypervisor version of the connection host rXzvirConnectGetVersion() failed)rZvirConnectGetVersionrprrxrrrrBs zvirConnect.getVersioncCs0t|j||}|dur tdt||d}|S)a[Define an inactive persistent physical host interface or modify an existing persistent one from the XML description. Normally this change in the interface configuration is immediately permanent/persistent, but if virInterfaceChangeBegin() has been previously called (i.e. if an interface config transaction is open), the new interface definition will only become permanent if virInterfaceChangeCommit() is called prior to the next reboot of the system running libvirtd. Prior to that time, it can be explicitly removed using virInterfaceChangeRollback(), or will be automatically removed during the next reboot of the system running libvirtd. virInterfaceFree should be used to free the resources after the interface object is no longer needed. NzvirInterfaceDefineXML() failedr<)rZvirInterfaceDefineXMLrprrrrrrinterfaceDefineXML&s  zvirConnect.interfaceDefineXMLcCs.t|j|}|durtdt||d}|S)zTry to lookup an interface on the given hypervisor based on its MAC. virInterfaceFree should be used to free the resources after the interface object is no longer needed. Nz&virInterfaceLookupByMACString() failedr<)rZvirInterfaceLookupByMACStringrprr)rZmacstrr>rrrrinterfaceLookupByMACString<s  z%virConnect.interfaceLookupByMACStringcCs.t|j|}|durtdt||d}|S)zTry to lookup an interface on the given hypervisor based on its name. virInterfaceFree should be used to free the resources after the interface object is no longer needed. Nz!virInterfaceLookupByName() failedr<)rZvirInterfaceLookupByNamerprrrr@r>rrrrinterfaceLookupByNameGs  z virConnect.interfaceLookupByNamecCs t|j}|dkrtd|S)zDetermine if the connection to the hypervisor is still alive A connection will be classed as alive if it is either local, or running over a channel (TCP or UNIX socket) which is not closed. rXzvirConnectIsAlive() failed)rZvirConnectIsAliverprrxrrrisAliveVs zvirConnect.isAlivecCs t|j}|dkrtd|S)z;Determine if the connection to the hypervisor is encrypted rXzvirConnectIsEncrypted() failed)rZvirConnectIsEncryptedrprrxrrr isEncrypted`s zvirConnect.isEncryptedcCs t|j}|dkrtd|S)zDetermine if the connection to the hypervisor is secure A connection will be classed as secure if it is either encrypted, or running over a channel which is not exposed to eavesdropping (eg a UNIX domain socket, or pipe) rXzvirConnectIsSecure() failed)rZvirConnectIsSecurerprrxrrrisSecuregs zvirConnect.isSecurecCs t|j}|durtd|S)zElist the defined domains, stores the pointers to the names in @names Nz%virConnectListDefinedDomains() failed)rZvirConnectListDefinedDomainsrprrxrrrlistDefinedDomainsvs zvirConnect.listDefinedDomainscCs t|j}|durtd|S)zHlist the defined interfaces, stores the pointers to the names in @names Nz(virConnectListDefinedInterfaces() failed)rZvirConnectListDefinedInterfacesrprrxrrrlistDefinedInterfaces}s z virConnect.listDefinedInterfacescCs t|j}|durtd|S)zFlist the defined networks, stores the pointers to the names in @names Nz&virConnectListDefinedNetworks() failed)rZvirConnectListDefinedNetworksrprrxrrrlistDefinedNetworkss zvirConnect.listDefinedNetworkscCs t|j}|durtd|S)zJlist the defined storage pool, stores the pointers to the names in @names Nz*virConnectListDefinedStoragePools() failed)rZ!virConnectListDefinedStoragePoolsrprrxrrrlistDefinedStoragePoolss z"virConnect.listDefinedStoragePoolscCs$t|j||}|dur td|S)zlist the node devices NzvirNodeListDevices() failed)rZvirNodeListDevicesrprrcapr;r>rrr listDevicesszvirConnect.listDevicescCs t|j}|durtd|S)zlist the networks, stores the pointers to the names in @names NzvirConnectListNetworks() failed)rZvirConnectListNetworksrprrxrrr listNetworkss zvirConnect.listNetworkscCs t|j}|durtd|S)zList the defined secret IDs NzvirConnectListSecrets() failed)rZvirConnectListSecretsrprrxrrr listSecretss zvirConnect.listSecretscCs t|j}|durtd|S)zClist the storage pools, stores the pointers to the names in @names Nz#virConnectListStoragePools() failed)rZvirConnectListStoragePoolsrprrxrrrlistStoragePoolss zvirConnect.listStoragePoolscCs.t|j|}|durtdt||d}|S)aPTry to find a domain based on the hypervisor ID number Note that this won't work for inactive domains which have an ID of -1, in that case a lookup based on the Name or UUID need to be done instead. virDomainFree should be used to free the resources after the domain object is no longer needed. NzvirDomainLookupByID() failedr<)rZvirDomainLookupByIDrprr)ridr>rrrr lookupByIDs  zvirConnect.lookupByIDcCs.t|j|}|durtdt||d}|S)zTry to lookup a domain on the given hypervisor based on its name. virDomainFree should be used to free the resources after the domain object is no longer needed. NzvirDomainLookupByName() failedr<)rZvirDomainLookupByNamerprrrrrr lookupByNames  zvirConnect.lookupByNamecCs.t|j|}|durtdt||d}|S)zBTry to lookup a domain on the given hypervisor based on its UUID. NzvirDomainLookupByUUID() failedr<)rZvirDomainLookupByUUIDrprrrrvr>rrrr lookupByUUIDs  zvirConnect.lookupByUUIDcCs.t|j|}|durtdt||d}|S)zTry to lookup a domain on the given hypervisor based on its UUID. virDomainFree should be used to free the resources after the domain object is no longer needed. Nz$virDomainLookupByUUIDString() failedr<)rZvirDomainLookupByUUIDStringrprrrrxr>rrrrlookupByUUIDStrings  zvirConnect.lookupByUUIDStringcCs.t|j|}|durtdt||d}|S)Create and start a new virtual network, based on an XML description similar to the one returned by virNetworkGetXMLDesc() virNetworkFree should be used to free the resources after the network object is no longer needed. NzvirNetworkCreateXML() failedr<)rZvirNetworkCreateXMLrprrorrr>rrrrnetworkCreateXMLs  zvirConnect.networkCreateXMLcCs0t|j||}|dur tdt||d}|S)rNz!virNetworkCreateXMLFlags() failedr<)rZvirNetworkCreateXMLFlagsrprrorrrrnetworkCreateXMLFlagss  z virConnect.networkCreateXMLFlagscCs.t|j|}|durtdt||d}|S)Define an inactive persistent virtual network or modify an existing persistent one from the XML description. virNetworkFree should be used to free the resources after the network object is no longer needed. NzvirNetworkDefineXML() failedr<)rZvirNetworkDefineXMLrprrorrrrnetworkDefineXML&s  zvirConnect.networkDefineXMLcCs0t|j||}|dur tdt||d}|S)rNz!virNetworkDefineXMLFlags() failedr<)rZvirNetworkDefineXMLFlagsrprrorrrrnetworkDefineXMLFlags2s  z virConnect.networkDefineXMLFlagscCs.t|j|}|durtdt||d}|S)zTry to lookup a network on the given hypervisor based on its name. virNetworkFree should be used to free the resources after the network object is no longer needed. NzvirNetworkLookupByName() failedr<)rZvirNetworkLookupByNamerprrorrrrnetworkLookupByName>s  zvirConnect.networkLookupByNamecCs.t|j|}|durtdt||d}|S)CTry to lookup a network on the given hypervisor based on its UUID. NzvirNetworkLookupByUUID() failedr<)rZvirNetworkLookupByUUIDrprrorrrrnetworkLookupByUUIDMs  zvirConnect.networkLookupByUUIDcCs.t|j|}|durtdt||d}|S)rNz%virNetworkLookupByUUIDString() failedr<)rZvirNetworkLookupByUUIDStringrprrorrrrnetworkLookupByUUIDStringYs  z$virConnect.networkLookupByUUIDStringcCs.t|j|}|durtdt||d}|S)a Creates a new stream object which can be used to perform streamed I/O with other public API function. When no longer needed, a stream object must be released with virStreamFree. If a data stream has been used, then the application must call virStreamFinish or virStreamAbort before free'ing to, in order to notify the driver of termination. If a non-blocking data stream is required passed VIR_STREAM_NONBLOCK for flags, otherwise pass 0. NzvirStreamNew() failedr<)rZ virStreamNewrpr virStream)rr;r>rrrr newStreames  zvirConnect.newStreamcCs0t|j||}|dur tdt||d}|S)zCreate a new device on the VM host machine, for example, virtual HBAs created using vport_create. virNodeDeviceFree should be used to free the resources after the node device object is no longer needed. NzvirNodeDeviceCreateXML() failedr<)rZvirNodeDeviceCreateXMLrpr virNodeDevicerrrrnodeDeviceCreateXML{s  zvirConnect.nodeDeviceCreateXMLcCs0t|j||}|dur tdt||d}|S)a0Define a new inactive persistent device or modify an existing persistent one from the XML description on the VM host machine, for example, a mediated device. virNodeDeviceFree should be used to free the resources after the node device object is no longer needed. NzvirNodeDeviceDefineXML() failedr<)rZvirNodeDeviceDefineXMLrprrrrrrnodeDeviceDefineXMLs  zvirConnect.nodeDeviceDefineXMLcCs.t|j|}|durtdt||d}|S)zLookup a node device by its name. virNodeDeviceFree should be used to free the resources after the node device object is no longer needed. Nz"virNodeDeviceLookupByName() failedr<)rZvirNodeDeviceLookupByNamerprrrrrrnodeDeviceLookupByNames  z!virConnect.nodeDeviceLookupByNamecCs2t|j|||}|dur"tdt||d}|S)zLookup SCSI Host which is capable with 'fc_host' by its WWNN and WWPN. virNodeDeviceFree should be used to free the resources after the node device object is no longer needed. Nz)virNodeDeviceLookupSCSIHostByWWN() failedr<)rZ virNodeDeviceLookupSCSIHostByWWNrprr)rZwwnnZwwpnr;r>rrrrnodeDeviceLookupSCSIHostByWWNs  z(virConnect.nodeDeviceLookupSCSIHostByWWNcCs t|j}|dkrtd|S)z5Provides the number of defined but inactive domains. rXz&virConnectNumOfDefinedDomains() failed)rZvirConnectNumOfDefinedDomainsrprrxrrrnumOfDefinedDomainss zvirConnect.numOfDefinedDomainscCs t|j}|dkrtd|S)zKProvides the number of defined (inactive) interfaces on the physical host. rXz)virConnectNumOfDefinedInterfaces() failed)rZ virConnectNumOfDefinedInterfacesrprrxrrrnumOfDefinedInterfacess z!virConnect.numOfDefinedInterfacescCs t|j}|dkrtd|S)z*Provides the number of inactive networks. rXz'virConnectNumOfDefinedNetworks() failed)rZvirConnectNumOfDefinedNetworksrprrxrrrnumOfDefinedNetworkss zvirConnect.numOfDefinedNetworkscCs t|j}|dkrtd|S)z.Provides the number of inactive storage pools rXz+virConnectNumOfDefinedStoragePools() failed)rZ"virConnectNumOfDefinedStoragePoolsrprrxrrrnumOfDefinedStoragePoolss z#virConnect.numOfDefinedStoragePoolscCs$t|j||}|dkr td|S)zProvides the number of node devices. If the optional 'cap' argument is non-None, then the count will be restricted to devices with the specified capability rXzvirNodeNumOfDevices() failed)rZvirNodeNumOfDevicesrprrrrr numOfDevicesszvirConnect.numOfDevicescCs t|j}|dkrtd|S)z'Provides the number of active domains. rXzvirConnectNumOfDomains() failed)rZvirConnectNumOfDomainsrprrxrrr numOfDomainss zvirConnect.numOfDomainscCs t|j}|dkrtd|S)z?Provides the number of active interfaces on the physical host. rXz"virConnectNumOfInterfaces() failed)rZvirConnectNumOfInterfacesrprrxrrrnumOfInterfacess zvirConnect.numOfInterfacescCs t|j}|dkrtd|S)z"Provides the number of nwfilters. rXz!virConnectNumOfNWFilters() failed)rZvirConnectNumOfNWFiltersrprrxrrrnumOfNWFilterss zvirConnect.numOfNWFilterscCs t|j}|dkrtd|S)z(Provides the number of active networks. rXz virConnectNumOfNetworks() failed)rZvirConnectNumOfNetworksrprrxrrr numOfNetworks s zvirConnect.numOfNetworkscCs t|j}|dkrtd|S)z+Fetch number of currently defined secrets. rXzvirConnectNumOfSecrets() failed)rZvirConnectNumOfSecretsrprrxrrr numOfSecretss zvirConnect.numOfSecretscCs t|j}|dkrtd|S)z,Provides the number of active storage pools rXz$virConnectNumOfStoragePools() failed)rZvirConnectNumOfStoragePoolsrprrxrrrnumOfStoragePoolss zvirConnect.numOfStoragePoolscCs0t|j||}|dur tdt||d}|S)aDefine a new network filter, based on an XML description similar to the one returned by virNWFilterGetXMLDesc(). This API may be used to associate a filter with a currently running guest that does not have a filter defined for a specific network port. Since the bindings are generally automatically managed by the hypervisor, using this command to define a filter for a network port and then starting the guest afterwards may prevent the guest from starting if it attempts to use the network port and finds a filter already defined. virNWFilterFree should be used to free the resources after the binding object is no longer needed. Nz$virNWFilterBindingCreateXML() failedr<)rZvirNWFilterBindingCreateXMLrprvirNWFilterBindingrrrrnwfilterBindingCreateXML*s  z#virConnect.nwfilterBindingCreateXMLcCs.t|j|}|durtdt||d}|S)zTry to lookup a network filter binding on the given hypervisor based on network port device name. virNWFilterBindingFree should be used to free the resources after the binding object is no longer needed. Nz*virNWFilterBindingLookupByPortDev() failedr<)rZ!virNWFilterBindingLookupByPortDevrprr)rZportdevr>rrrrnwfilterBindingLookupByPortDev=s  z)virConnect.nwfilterBindingLookupByPortDevcCs.t|j|}|durtdt||d}|S)Define a new network filter, based on an XML description similar to the one returned by virNWFilterGetXMLDesc() virNWFilterFree should be used to free the resources after the nwfilter object is no longer needed. NzvirNWFilterDefineXML() failedr<)rZvirNWFilterDefineXMLrpr virNWFilterrrrrnwfilterDefineXMLIs  zvirConnect.nwfilterDefineXMLcCs0t|j||}|dur tdt||d}|S)r Nz"virNWFilterDefineXMLFlags() failedr<)rZvirNWFilterDefineXMLFlagsrprr rrrrnwfilterDefineXMLFlagsUs  z!virConnect.nwfilterDefineXMLFlagscCs.t|j|}|durtdt||d}|S)zTry to lookup a network filter on the given hypervisor based on its name. virNWFilterFree should be used to free the resources after the nwfilter object is no longer needed. Nz virNWFilterLookupByName() failedr<)rZvirNWFilterLookupByNamerprr rrrrnwfilterLookupByNameas  zvirConnect.nwfilterLookupByNamecCs.t|j|}|durtdt||d}|S)zJTry to lookup a network filter on the given hypervisor based on its UUID. Nz virNWFilterLookupByUUID() failedr<)rZvirNWFilterLookupByUUIDrprr rrrrnwfilterLookupByUUIDps  zvirConnect.nwfilterLookupByUUIDcCs.t|j|}|durtdt||d}|S)zTry to lookup an nwfilter on the given hypervisor based on its UUID. virNWFilterFree should be used to free the resources after the nwfilter object is no longer needed. Nz&virNWFilterLookupByUUIDString() failedr<)rZvirNWFilterLookupByUUIDStringrprr rrrrnwfilterLookupByUUIDString|s  z%virConnect.nwfilterLookupByUUIDStringcCs"t|j|}|dkrtd|S)zThis method will restore a domain saved to disk by virDomainSave(). See virDomainRestoreFlags() for more control. rXzvirDomainRestore() failed)rZvirDomainRestorerpr)rfrmr>rrrrestoreszvirConnect.restorecCs&t|j|||}|dkr"td|S)aThis method will restore a domain saved to disk by virDomainSave(). If the hypervisor supports it, @dxml can be used to alter host-specific portions of the domain XML that will be used when restoring an image. For example, it is possible to alter the backing filename that is associated with a disk device, in order to prepare for file renaming done as part of backing up the disk device while the domain is stopped. If @flags includes VIR_DOMAIN_SAVE_BYPASS_CACHE, then libvirt will attempt to bypass the file system cache while restoring the file, or fail if it cannot do so for the given system; this can allow less pressure on file system cache, but also risks slowing restores from NFS. Normally, the saved state file will remember whether the domain was running or paused, and restore defaults to the same state. Specifying VIR_DOMAIN_SAVE_RUNNING or VIR_DOMAIN_SAVE_PAUSED in @flags will override the default read from the file. These two flags are mutually exclusive. If @flags includes VIR_DOMAIN_SAVE_RESET_NVRAM, then libvirt will discard any existing NVRAM file and re-initialize NVRAM from the pristine template. rXzvirDomainRestoreFlags() failed)rZvirDomainRestoreFlagsrpr)rrrr;r>rrr restoreFlagsszvirConnect.restoreFlagscCs$t|j||}|dkr td|S)z1This method will restore a domain saved to disk. rXzvirDomainRestoreParams() failed)rZvirDomainRestoreParamsrprrrrr restoreParamsszvirConnect.restoreParamscCs&t|j|||}|dkr"td|S)aThis updates the definition of a domain stored in a saved state file. @file must be a file created previously by virDomainSave() or virDomainSaveFlags(). @dxml can be used to alter host-specific portions of the domain XML that will be used when restoring an image. For example, it is possible to alter the backing filename that is associated with a disk device, to match renaming done as part of backing up the disk device while the domain is stopped. Normally, the saved state file will remember whether the domain was running or paused, and restore defaults to the same state. Specifying VIR_DOMAIN_SAVE_RUNNING or VIR_DOMAIN_SAVE_PAUSED in @flags will override the default saved into the file; omitting both leaves the file's default unchanged. These two flags are mutually exclusive. rXz$virDomainSaveImageDefineXML() failed)rZvirDomainSaveImageDefineXMLrpr)rfilerr;r>rrrsaveImageDefineXMLszvirConnect.saveImageDefineXMLcCs$t|j||}|dur td|S)aFThis method will extract the XML describing the domain at the time a saved state file was created. @file must be a file created previously by virDomainSave() or virDomainSaveFlags(). No security-sensitive data will be included unless @flags contains VIR_DOMAIN_SAVE_IMAGE_XML_SECURE. Nz%virDomainSaveImageGetXMLDesc() failed)rZvirDomainSaveImageGetXMLDescrpr)rrr;r>rrrsaveImageGetXMLDescszvirConnect.saveImageGetXMLDesccCs0t|j||}|dur tdt||d}|S)aIf XML specifies a UUID, locates the specified secret and replaces all attributes of the secret specified by UUID by attributes specified in xml (any attributes not specified in xml are discarded). Otherwise, creates a new secret with an automatically chosen UUID, and initializes its attributes from xml. virSecretFree should be used to free the resources after the secret object is no longer needed. NzvirSecretDefineXML() failedr<)rZvirSecretDefineXMLrpr virSecretrrrrsecretDefineXMLs  zvirConnect.secretDefineXMLcCs.t|j|}|durtdt||d}|S)zBTry to lookup a secret on the given hypervisor based on its UUID. NzvirSecretLookupByUUID() failedr<)rZvirSecretLookupByUUIDrprrrrrrsecretLookupByUUIDs  zvirConnect.secretLookupByUUIDcCs.t|j|}|durtdt||d}|S)zTry to lookup a secret on the given hypervisor based on its UUID. Uses the printable string value to describe the UUID virSecretFree should be used to free the resources after the secret object is no longer needed. Nz$virSecretLookupByUUIDString() failedr<)rZvirSecretLookupByUUIDStringrprrrrrrsecretLookupByUUIDStrings  z#virConnect.secretLookupByUUIDStringcCs0t|j||}|dur tdt||d}|S)aTry to lookup a secret on the given hypervisor based on its usage The usageID is unique within the set of secrets sharing the same usageType value. virSecretFree should be used to free the resources after the secret object is no longer needed. NzvirSecretLookupByUsage() failedr<)rZvirSecretLookupByUsagerprr)r usageTypeusageIDr>rrrrsecretLookupByUsages  zvirConnect.secretLookupByUsagecCs$t|j||}|dkr td|S)zJOverride the default identity information associated with the connection. rXzvirConnectSetIdentity() failed)rZvirConnectSetIdentityrprrrrr setIdentity#szvirConnect.setIdentitycCs$t|j||}|dkr td|S)aStart sending keepalive messages after @interval seconds of inactivity and consider the connection to be broken when no response is received after @count keepalive messages sent in a row. In other words, sending count + 1 keepalive message results in closing the connection. When @interval is <= 0, no keepalive messages will be sent. When @count is 0, the connection will be automatically closed after @interval seconds of inactivity without sending any keepalive messages. Note: The client has to implement and run an event loop with virEventRegisterImpl() or virEventRegisterDefaultImpl() to be able to use keepalive messages. Failure to do so may result in connections being closed unexpectedly. Note: This API function controls only keepalive messages sent by the client. If the server is configured to use keepalive you still need to run the event loop to respond to them, even if you disable keepalives by this function. rXzvirConnectSetKeepAlive() failed)rZvirConnectSetKeepAliverpr)rintervalcountr>rrr setKeepAlive*szvirConnect.setKeepAlivecCs$t|j||}|dkr td|S)z Change the node memory tunables rXz#virNodeSetMemoryParameters() failed)rZvirNodeSetMemoryParametersrprrrrrr;DszvirConnect.setMemoryParameterscCs0t|j||}|dur tdt||d}|S)a6Create a new storage based on its XML description. The pool is not persistent, so its definition will disappear when it is destroyed, or if the host is restarted virStoragePoolFree should be used to free the resources after the storage pool object is no longer needed. Nz virStoragePoolCreateXML() failedr<)rZvirStoragePoolCreateXMLrprrrrrrstoragePoolCreateXMLOs  zvirConnect.storagePoolCreateXMLcCs0t|j||}|dur tdt||d}|S)zDefine an inactive persistent storage pool or modify an existing persistent one from the XML description. virStoragePoolFree should be used to free the resources after the storage pool object is no longer needed. Nz virStoragePoolDefineXML() failedr<)rZvirStoragePoolDefineXMLrprrrrrrstoragePoolDefineXML\s  zvirConnect.storagePoolDefineXMLcCs.t|j|}|durtdt||d}|S)zFetch a storage pool based on its unique name virStoragePoolFree should be used to free the resources after the storage pool object is no longer needed. Nz#virStoragePoolLookupByName() failedr<)rZvirStoragePoolLookupByNamerprrrrrrstoragePoolLookupByNamehs  z"virConnect.storagePoolLookupByNamecCs.t|j|}|durtdt||d}|S)a,Fetch a storage pool which maps to a particular target directory. If more than one pool maps to the path, it is undefined which will be returned first. virStoragePoolFree should be used to free the resources after the storage pool object is no longer needed. Nz)virStoragePoolLookupByTargetPath() failedr<)rZ virStoragePoolLookupByTargetPathrprrrrr>rrrrstoragePoolLookupByTargetPathss  z(virConnect.storagePoolLookupByTargetPathcCs.t|j|}|durtdt||d}|S)Fetch a storage pool based on its globally unique id virStoragePoolFree should be used to free the resources after the storage pool object is no longer needed. Nz#virStoragePoolLookupByUUID() failedr<)rZvirStoragePoolLookupByUUIDrprrrrrrstoragePoolLookupByUUIDs  z"virConnect.storagePoolLookupByUUIDcCs.t|j|}|durtdt||d}|S)r'Nz)virStoragePoolLookupByUUIDString() failedr<)rZ virStoragePoolLookupByUUIDStringrprrrrrrstoragePoolLookupByUUIDStrings  z(virConnect.storagePoolLookupByUUIDStringcCs.t|j|}|durtdt||d}|S)zFetch a pointer to a storage volume based on its globally unique key virStorageVolFree should be used to free the resources after the storage volume object is no longer needed. Nz!virStorageVolLookupByKey() failedr<)rZvirStorageVolLookupByKeyrprr)rr>r>rrrrstorageVolLookupByKeys  z virConnect.storageVolLookupByKeycCs.t|j|}|durtdt||d}|S)zFetch a pointer to a storage volume based on its locally (host) unique path virStorageVolFree should be used to free the resources after the storage volume object is no longer needed. Nz"virStorageVolLookupByPath() failedr<)rZvirStorageVolLookupByPathrprrr%rrrstorageVolLookupByPaths  z!virConnect.storageVolLookupByPathcCs&t|j|||}|dkr"td|S)aAttempt to suspend the node (host machine) for the given duration of time in the specified state (Suspend-to-RAM, Suspend-to-Disk or Hybrid-Suspend). Schedule the node's Real-Time-Clock interrupt to resume the node after the duration is complete. rXz"virNodeSuspendForDuration() failed)rZvirNodeSuspendForDurationrprrrrrsuspendForDurationszvirConnect.suspendForDurationcCst|j}|S)aProvide a pointer to the last error caught on that connection This method is not protected against access from multiple threads. In a multi-threaded application, always use the global virGetLastError() API which is backed by thread local storage. If the connection object was discovered to be invalid by an API call, then the error will be reported against the global error object. Since 0.6.0, all errors reported in the per-connection object are also duplicated in the global error object. As such an application can always use virGetLastError(). This method remains for backwards compatibility. )rvirConnGetLastErrorrprxrrrr-s zvirConnect.virConnGetLastErrorcCst|jdS)zThe error object is kept in thread local storage, so separate threads can safely access this concurrently. Reset the last error caught on that connection N)rvirConnResetLastErrorrpr rrrr.sz virConnect.virConnResetLastErrorrcCsTz |j|`t|j|Wnty2Yn0|jdurJt|jd|_dSrH)domainEventCallbacksclearrvirConnectDomainEventDeregisterrpAttributeErrorrr rrrrss    zvirConnect.__del__cCs|SrHrr rrr __enter__szvirConnect.__enter__) exc_type_ exc_value_ traceback_rcCs |dSrH)r)rr4r5r6rrr__exit__szvirConnect.__exit__)rTrcCsTz<|j|=t|jdkr:|`t|j|}|dkr:tdWntyNYn0dS)zRemoves a Domain Event Callback. De-registering for a domain callback will disable delivery of this event type rrXz(virConnectDomainEventDeregister() failedN)r/lenrr1rprr2)rrTr>rrrdomainEventDeregisters  z virConnect.domainEventDeregister)rTrFrcCsNz||j|<Wn:tyH||i|_t|j|}|dkrDtdYn0dS)nAdds a Domain Event Callback. Registering for a domain callback will enable delivery of the events rXz&virConnectDomainEventRegister() failedN)r/r2rZvirConnectDomainEventRegisterrpr)rrTrFr>rrrdomainEventRegisters  zvirConnect.domainEventRegisterr)domrEdetailrcCsHz0|jD] \}}||t||d|||q WntyBYn0dS)z@Dispatches events to python user domain event callbacks r<N)r/itemsrr2)rr=rEr>rTrFrrr_dispatchDomainEventCallbackss  z(virConnect._dispatchDomainEventCallbacks)r=rEr>rRrcCs,|d}|d}||t||d|||dS)zJDispatches events to python user domain lifecycle event callbacks rTrFr<rr)rr=rEr>rRrTrFrrr%_dispatchDomainEventLifecycleCallbacksz0virConnect._dispatchDomainEventLifecycleCallback)r=rRrcCs(|d}|d}||t||d|dS)zHDispatches events to python user domain generic event callbacks rTrFr<rrA)rr=rRrTrFrrr#_dispatchDomainEventGenericCallbacksz.virConnect._dispatchDomainEventGenericCallback)r=rrRrcCs*|d}|d}||t||d||dS)zKDispatches events to python user domain RTC change event callbacks rTrFr<rrA)rr=rrRrTrFrrr%_dispatchDomainEventRTCChangeCallback"sz0virConnect._dispatchDomainEventRTCChangeCallback)r=r4rRrcCs*|d}|d}||t||d||dS)zIDispatches events to python user domain watchdog event callbacks rTrFr<rrA)rr=r4rRrTrFrrr$_dispatchDomainEventWatchdogCallback+sz/virConnect._dispatchDomainEventWatchdogCallback)r=srcPathdevAliasr4rRrcCs.|d}|d}||t||d||||dSzIDispatches events to python user domain IO error event callbacks rTrFr<rrA)rr=rFrGr4rRrTrFrrr#_dispatchDomainEventIOErrorCallback4sz.virConnect._dispatchDomainEventIOErrorCallback)r=rFrGr4reasonrRrc Cs0|d}|d}||t||d|||||dSrHrA) rr=rFrGr4rJrRrTrFrrr)_dispatchDomainEventIOErrorReasonCallback=s z4virConnect._dispatchDomainEventIOErrorReasonCallback)r=phase localAddr remoteAddr authSchemesubjectrRrc Cs2|d}|d} ||t||d|||||| dS)zIDispatches events to python user domain graphics event callbacks rTrFr<rrA) rr=rLrMrNrOrPrRrTrFrrr$_dispatchDomainEventGraphicsCallbackGs z/virConnect._dispatchDomainEventGraphicsCallback)r=rrostatusrRrcCsFz.|d}|d}||t||d||||Wnty@Yn0dS)zSDispatches events to python user domain blockJob/blockJob2 event callbacks rTrFr<N)rr2)rr=rrorRrRrTrFrrr$_dispatchDomainEventBlockJobCallbackQs  z/virConnect._dispatchDomainEventBlockJobCallback)r= oldSrcPath newSrcPathrGrJrRrc Cs0|d}|d}||t||d|||||dS)zJDispatches event to python user domain diskChange event callbacks rTrFr<rrA) rr=rTrUrGrJrRrTrFrrr&_dispatchDomainEventDiskChangeCallback\sz1virConnect._dispatchDomainEventDiskChangeCallback)r=rGrJrRrcCs,|d}|d}||t||d|||dS)zJDispatches event to python user domain trayChange event callbacks rTrFr<rrA)rr=rGrJrRrTrFrrr&_dispatchDomainEventTrayChangeCallbackesz1virConnect._dispatchDomainEventTrayChangeCallback)r=rJrRrcCs*|d}|d}||t||d||dS)zHDispatches event to python user domain pmwakeup event callbacks rTrFr<rrArr=rJrRrTrFrrr$_dispatchDomainEventPMWakeupCallbacknsz/virConnect._dispatchDomainEventPMWakeupCallbackcCs*|d}|d}||t||d||dS)zIDispatches event to python user domain pmsuspend event callbacks rTrFr<rrArXrrr%_dispatchDomainEventPMSuspendCallbackwsz0virConnect._dispatchDomainEventPMSuspendCallback)r=actualrRrcCs*|d}|d}||t||d||dS)zODispatches events to python user domain balloon change event callbacks rTrFr<rrA)rr=r[rRrTrFrrr)_dispatchDomainEventBalloonChangeCallbacksz4virConnect._dispatchDomainEventBalloonChangeCallbackcCs*|d}|d}||t||d||dS)zNDispatches event to python user domain pmsuspend-disk event callbacks rTrFr<rrArXrrr)_dispatchDomainEventPMSuspendDiskCallbacksz4virConnect._dispatchDomainEventPMSuspendDiskCallback)r=rGrRrcCs*|d}|d}||t||d||dS)zNDispatches event to python user domain device removed event callbacks rTrFr<rrArr=rGrRrTrFrrr)_dispatchDomainEventDeviceRemovedCallbacksz4virConnect._dispatchDomainEventDeviceRemovedCallback)r=rrRrcCs*|d}|d}||t||d||dS)zGDispatches event to python user domain tunable event callbacks rTrFr<rrArr=rrRrTrFrrr#_dispatchDomainEventTunableCallbacksz.virConnect._dispatchDomainEventTunableCallback)r=r/rJrRrcCs,|d}|d}||t||d|||dS)zNDispatches event to python user domain agent lifecycle event callback rTrFr<rrA)rr=r/rJrRrTrFrrr*_dispatchDomainEventAgentLifecycleCallbacksz5virConnect._dispatchDomainEventAgentLifecycleCallbackcCs*|d}|d}||t||d||dS)zLDispatches event to python user domain device added event callbacks rTrFr<rrAr^rrr'_dispatchDomainEventDeviceAddedCallbacksz2virConnect._dispatchDomainEventDeviceAddedCallback)r= iterationrRrcCs*|d}|d}||t||d||dS)zSDispatches event to python user domain migration iteration event callbacks rTrFr<rrA)rr=rdrRrTrFrrr._dispatchDomainEventMigrationIterationCallbacksz9virConnect._dispatchDomainEventMigrationIterationCallbackcCs*|d}|d}||t||d||dS)zGDispatches event to python user domain job completed callbacks rTrFr<rrAr`rrr(_dispatchDomainEventJobCompletedCallbacksz3virConnect._dispatchDomainEventJobCompletedCallbackcCs*|d}|d}||t||d||dS)zUDispatches event to python user domain device removal failed event callbacks rTrFr<rrAr^rrr/_dispatchDomainEventDeviceRemovalFailedCallbacksz:virConnect._dispatchDomainEventDeviceRemovalFailedCallback)r=mtypensurirRrcCs,|d}|d}||t||d|||dS)zODispatches event to python user domain metadata change event callbacks rTrFr<rrArr=rhrirRrTrFrrr*_dispatchDomainEventMetadataChangeCallbacksz5virConnect._dispatchDomainEventMetadataChangeCallback)r=r,rr-excessrRrc Cs0|d}|d}||t||d|||||dS)zVDispatches event to python user domain block device threshold event callbacks rTrFr<rrA) rr=r,rr-rlrRrTrFrrr*_dispatchDomainEventBlockThresholdCallbacksz5virConnect._dispatchDomainEventBlockThresholdCallback)r= recipientr4r;rRrcCs.|d}|d}||t||d||||dS)zNDispatches event to python user domain memory failure event callbacks rTrFr<rrA)rr=rnr4r;rRrTrFrrr)_dispatchDomainEventMemoryFailureCallbacksz4virConnect._dispatchDomainEventMemoryFailureCallback)r=rrrRrcCs,|d}|d}||t||d|||dS)zYDispatches event to python user domain memory device size change event callbacks rTrFr<rrA)rr=rrrRrTrFrrr2_dispatchDomainEventMemoryDeviceSizeChangeCallbacksz=virConnect._dispatchDomainEventMemoryDeviceSizeChangeCallback)r=roldMACnewMACrRrcCs.|d}|d}||t||d||||dS)zNDispatches event to python user domain NIC MAC change event callbacks rTrFr<rrA)rr=rrqrrrRrTrFrrr(_dispatchDomainEventNICMACChangeCallbacksz3virConnect._dispatchDomainEventNICMACChangeCallback) callbackIDrcCsBz*t|j|}|dkr td|j|=Wnty<Yn0dS)r8rXz+virConnectDomainEventDeregisterAny() failedN)rZ"virConnectDomainEventDeregisterAnyrprdomainEventCallbackIDr2rrtr>rrrdomainEventDeregisterAnys  z#virConnect.domainEventDeregisterAnyro)rrEr>rRrcCs,|d}|d}||t||d|||dS)zKDispatches events to python user network lifecycle event callbacks rTrFr<rro)rrrEr>rRrTrFrrr&_dispatchNetworkEventLifecycleCallback sz1virConnect._dispatchNetworkEventLifecycleCallbackcCs,|d}|d}||t||d|||dS)zPDispatches event to python user network metadata change event callbacks rTrFr<rrxrjrrr+_dispatchNetworkEventMetadataChangeCallbacksz6virConnect._dispatchNetworkEventMetadataChangeCallbackcCsBz*t|j|}|dkr td|j|=Wnty<Yn0dS)z{Removes a Network Event Callback. De-registering for a network callback will disable delivery of this event typerXz,virConnectNetworkEventDeregisterAny() failedN)rZ#virConnectNetworkEventDeregisterAnyrprnetworkEventCallbackIDr2rvrrrnetworkEventDeregisterAnys  z$virConnect.networkEventDeregisterAny)reventIDrTrFrcCsjt|dsi|_|||d}|dur8t|jd||}nt|j|j||}|dkr\td||j|<|S)zoAdds a Network Event Callback. Registering for a network callback will enable delivery of the eventsr{rTrrrFNrXz*virConnectNetworkEventRegisterAny() failed)hasattrr{rZ!virConnectNetworkEventRegisterAnyrpr)rrr}rTrFrRr>rrrnetworkEventRegisterAny's   z"virConnect.networkEventRegisterAny)r=r}rTrFrcCsjt|dsi|_|||d}|dur8t|jd||}nt|j|j||}|dkr\td||j|<|S)r;rur~NrXz)virConnectDomainEventRegisterAny() failed)rrurZ virConnectDomainEventRegisterAnyrpr)rr=r}rTrFrRr>rrrdomainEventRegisterAny6s   z!virConnect.domainEventRegisterAnyr)poolrEr>rRrcCs,|d}|d}||t||d|||dS)z[Dispatches events to python user storage pool lifecycle event callbacks rTrFr<rr)rrrEr>rRrTrFrrr*_dispatchStoragePoolEventLifecycleCallbackEsz5virConnect._dispatchStoragePoolEventLifecycleCallback)rrRrcCs(|d}|d}||t||d|dS)zYDispatches events to python user storage pool generic event callbacks rTrFr<rr)rrrRrTrFrrr(_dispatchStoragePoolEventGenericCallbackOsz3virConnect._dispatchStoragePoolEventGenericCallbackcCsBz*t|j|}|dkr td|j|=Wnty<Yn0dS)zRemoves a Storage Pool Event Callback. De-registering for a storage pool callback will disable delivery of this event typerXz0virConnectStoragePoolEventDeregisterAny() failedN)rZ'virConnectStoragePoolEventDeregisterAnyrprstoragePoolEventCallbackIDr2rvrrrstoragePoolEventDeregisterAnyYs  z(virConnect.storagePoolEventDeregisterAny)rr}rTrFrcCsjt|dsi|_|||d}|dur8t|jd||}nt|j|j||}|dkr\td||j|<|S)zyAdds a Storage Pool Event Callback. Registering for a storage pool callback will enable delivery of the eventsrr~NrXz.virConnectStoragePoolEventRegisterAny() failed)rrrZ%virConnectStoragePoolEventRegisterAnyrpr)rrr}rTrFrRr>rrrstoragePoolEventRegisterAnyds   z&virConnect.storagePoolEventRegisterAnyr)r,rEr>rRrcCs,|d}|d}||t||d|||dS)zZDispatches events to python user node device lifecycle event callbacks rTrFr<rr)rr,rEr>rRrTrFrrr)_dispatchNodeDeviceEventLifecycleCallbackssz4virConnect._dispatchNodeDeviceEventLifecycleCallback)r,rRrcCs(|d}|d}||t||d|dS)zXDispatches events to python user node device generic event callbacks rTrFr<rr)rr,rRrTrFrrr'_dispatchNodeDeviceEventGenericCallback}sz2virConnect._dispatchNodeDeviceEventGenericCallbackcCsBz*t|j|}|dkr td|j|=Wnty<Yn0dS)zRemoves a Node Device Event Callback. De-registering for a node device callback will disable delivery of this event typerXz/virConnectNodeDeviceEventDeregisterAny() failedN)rZ&virConnectNodeDeviceEventDeregisterAnyrprnodeDeviceEventCallbackIDr2rvrrrnodeDeviceEventDeregisterAnys  z'virConnect.nodeDeviceEventDeregisterAny)r,r}rTrFrcCsjt|dsi|_|||d}|dur8t|jd||}nt|j|j||}|dkr\td||j|<|S)zwAdds a Node Device Event Callback. Registering for a node device callback will enable delivery of the eventsrr~NrXz-virConnectNodeDeviceEventRegisterAny() failed)rrrZ$virConnectNodeDeviceEventRegisterAnyrpr)rr,r}rTrFrRr>rrrnodeDeviceEventRegisterAnys   z%virConnect.nodeDeviceEventRegisterAnyr)secretrEr>rRrcCs,|d}|d}||t||d|||dS)zJDispatches events to python user secret lifecycle event callbacks rTrFr<rr)rrrEr>rRrTrFrrr%_dispatchSecretEventLifecycleCallbacksz0virConnect._dispatchSecretEventLifecycleCallback)rrRrcCs(|d}|d}||t||d|dS)zHDispatches events to python user secret generic event callbacks rTrFr<rr)rrrRrTrFrrr#_dispatchSecretEventGenericCallbacksz.virConnect._dispatchSecretEventGenericCallbackcCsBz*t|j|}|dkr td|j|=Wnty<Yn0dS)zyRemoves a Secret Event Callback. De-registering for a secret callback will disable delivery of this event typerXz+virConnectSecretEventDeregisterAny() failedN)rZ"virConnectSecretEventDeregisterAnyrprsecretEventCallbackIDr2rvrrrsecretEventDeregisterAnys  z#virConnect.secretEventDeregisterAny)rr}rTrFrcCsjt|dsi|_|||d}|dur8t|jd||}nt|j|j||}|dkr\td||j|<|S)zmAdds a Secret Event Callback. Registering for a secret callback will enable delivery of the eventsrr~NrXz)virConnectSecretEventRegisterAny() failed)rrrZ virConnectSecretEventRegisterAnyrpr)rrr}rTrFrRr>rrrsecretEventRegisterAnys   z!virConnect.secretEventRegisterAnyr\cs0tj|}|durtdfdd|DS)z5List all domains and returns a list of domain objectsNz!virConnectListAllDomains() failedcsg|]}t|dqSr]rAr|r rrr`raz-virConnect.listAllDomains..)rZvirConnectListAllDomainsrprr}rr rlistAllDomainsszvirConnect.listAllDomainscs0tj|}|durtdfdd|DS)z&Returns a list of storage pool objectsNz&virConnectListAllStoragePools() failedcsg|]}t|dqSr]r)r_Zpoolptrr rrr`raz2virConnect.listAllStoragePools..)rZvirConnectListAllStoragePoolsrprr}rr rlistAllStoragePoolsszvirConnect.listAllStoragePoolscs0tj|}|durtdfdd|DS)z!Returns a list of network objectsNz"virConnectListAllNetworks() failedcsg|]}t|dqSr]rx)r_Znetptrr rrr`raz.virConnect.listAllNetworks..)rZvirConnectListAllNetworksrprr}rr rlistAllNetworksszvirConnect.listAllNetworksrcs0tj|}|durtdfdd|DS)z#Returns a list of interface objectsNz$virConnectListAllInterfaces() failedcsg|]}t|dqSr])r)r_Zifaceptrr rrr`raz0virConnect.listAllInterfaces..)rZvirConnectListAllInterfacesrprr}rr rlistAllInterfacesszvirConnect.listAllInterfacescs0tj|}|durtdfdd|DS)z*Returns a list of host node device objectsNz%virConnectListAllNodeDevices() failedcsg|]}t|dqSr]r)r_Zdevptrr rrr`raz-virConnect.listAllDevices..)rZvirConnectListAllNodeDevicesrprr}rr rlistAllDevicesszvirConnect.listAllDevicesr cs0tj|}|durtdfdd|DS)z(Returns a list of network filter objectsNz#virConnectListAllNWFilters() failedcsg|]}t|dqSr])r r_Z filter_ptrr rrr`raz/virConnect.listAllNWFilters..)rZvirConnectListAllNWFiltersrprr}rr rlistAllNWFiltersszvirConnect.listAllNWFiltersrcs0tj|}|durtdfdd|DS)z0Returns a list of network filter binding objectsNz*virConnectListAllNWFilterBindings() failedcsg|]}t|dqSr])rrr rrr`raz6virConnect.listAllNWFilterBindings..)rZ!virConnectListAllNWFilterBindingsrprr}rr rlistAllNWFilterBindingssz"virConnect.listAllNWFilterBindingscs0tj|}|durtdfdd|DS)z Returns a list of secret objectsNz!virConnectListAllSecrets() failedcsg|]}t|dqSr]r)r_Z secret_ptrr rrr` raz-virConnect.listAllSecrets..)rZvirConnectListAllSecretsrprr}rr rlistAllSecretsszvirConnect.listAllSecrets)rJrRrcCs |d}|d}||||dS)z/Dispatches events to python user close callbackrTrFrr)rrJrRrTrFrrr_dispatchCloseCallback s z!virConnect._dispatchCloseCallbackcCs t|j}|dkrtddS)zRemoves a close event callbackrXz*virConnectUnregisterCloseCallback() failedN)rZ!virConnectUnregisterCloseCallbackrprrxrrrunregisterCloseCallbacks z"virConnect.unregisterCloseCallbackcCs.|||d}t|j|}|dkr*td|S)z_Adds a close event callback, providing a notification when a connection fails / closesr~rXz(virConnectRegisterCloseCallback() failed)rZvirConnectRegisterCloseCallbackrpr)rrTrFrRr>rrrregisterCloseCallbacks  z virConnect.registerCloseCallback)rrer;rcCs2t|j|||}|dur"tdt||d}|S)a4Launch a new guest domain, based on an XML description similar to the one returned by virDomainGetXMLDesc() This function may require privileged access to the hypervisor. The domain is not persistent, so its definition will disappear when it is destroyed, or if the host is restarted (see virDomainDefineXML() to define persistent domains). @files provides an array of file descriptors which will be made available to the 'init' process of the guest. The file handles exposed to the guest will be renumbered to start from 3 (ie immediately following stderr). This is only supported for guests which use container based virtualization technology. If the VIR_DOMAIN_START_PAUSED flag is set, the guest domain will be started, but its CPUs will remain paused. The CPUs can later be manually started using virDomainResume. If the VIR_DOMAIN_START_AUTODESTROY flag is set, the guest domain will be automatically destroyed when the virConnectPtr object is finally released. This will also happen if the client application crashes / loses its connection to the libvirtd daemon. Any domains marked for auto destroy will block attempts at migration, save-to-file, or snapshots. Nz$virDomainCreateXMLWithFiles() failedr<)rZvirDomainCreateXMLWithFilesrprr)rrrer;r>rrrrcreateXMLWithFiles$s  zvirConnect.createXMLWithFiles)statsr;rcs2tj||}|dur tdfdd|DS)aQuery statistics for all domains on a given connection. Report statistics of various parameters for a running VM according to @stats field. The statistics are returned as an array of structures for each queried domain. The structure contains an array of typed parameters containing the individual statistics. The typed parameter name for each statistic field consists of a dot-separated string containing name of the requested group followed by a group specific description of the statistic value. The statistic groups are enabled using the @stats parameter which is a binary-OR of enum virDomainStatsTypes. The following groups are available (although not necessarily implemented for each hypervisor): VIR_DOMAIN_STATS_STATE: Return domain state and reason for entering that state. The typed parameter keys are in this format: "state.state" - state of the VM, returned as int from virDomainState enum "state.reason" - reason for entering given state, returned as int from virDomain*Reason enum corresponding to given state. Using 0 for @stats returns all stats groups supported by the given hypervisor. Specifying VIR_CONNECT_GET_ALL_DOMAINS_STATS_ENFORCE_STATS as @flags makes the function return error in case some of the stat types in @stats were not recognized by the daemon. Similarly to virConnectListAllDomains, @flags can contain various flags to filter the list of domains to provide stats for. VIR_CONNECT_GET_ALL_DOMAINS_STATS_ACTIVE selects online domains while VIR_CONNECT_GET_ALL_DOMAINS_STATS_INACTIVE selects offline ones. VIR_CONNECT_GET_ALL_DOMAINS_STATS_PERSISTENT and VIR_CONNECT_GET_ALL_DOMAINS_STATS_TRANSIENT allow to filter the list according to their persistence. To filter the list of VMs by domain state @flags can contain VIR_CONNECT_GET_ALL_DOMAINS_STATS_RUNNING, VIR_CONNECT_GET_ALL_DOMAINS_STATS_PAUSED, VIR_CONNECT_GET_ALL_DOMAINS_STATS_SHUTOFF and/or VIR_CONNECT_GET_ALL_DOMAINS_STATS_OTHER for all other states. Nz$virConnectGetAllDomainStats() failedcs$g|]}t|dd|dfqSrr<r"rAr_elemr rrr`qraz0virConnect.getAllDomainStats..)rZvirConnectGetAllDomainStatsrpr)rrr;r>rr rgetAllDomainStatsCs*zvirConnect.getAllDomainStats)domsrr;rcsbt}|D]"}t|ts td||jq tj|||}|durPtdfdd|DS)a" Query statistics for given domains. Report statistics of various parameters for a running VM according to @stats field. The statistics are returned as an array of structures for each queried domain. The structure contains an array of typed parameters containing the individual statistics. The typed parameter name for each statistic field consists of a dot-separated string containing name of the requested group followed by a group specific description of the statistic value. The statistic groups are enabled using the @stats parameter which is a binary-OR of enum virDomainStatsTypes. The following groups are available (although not necessarily implemented for each hypervisor): VIR_DOMAIN_STATS_STATE: Return domain state and reason for entering that state. The typed parameter keys are in this format: "state.state" - state of the VM, returned as int from virDomainState enum "state.reason" - reason for entering given state, returned as int from virDomain*Reason enum corresponding to given state. Using 0 for @stats returns all stats groups supported by the given hypervisor. Specifying VIR_CONNECT_GET_ALL_DOMAINS_STATS_ENFORCE_STATS as @flags makes the function return error in case some of the stat types in @stats were not recognized by the daemon. Get statistics about domains provided as a list in @doms. @stats is a bit field selecting requested statistics types.z(domain list contains non-domain elementsNzvirDomainListGetStats() failedcs$g|]}t|dd|dfqSrrArr rrr`raz1virConnect.domainListGetStats..)listrKrrappendrprZvirDomainListGetStats)rrrr;Zdomlistr=r>rr rdomainListGetStatsss zvirConnect.domainListGetStats)N)rrr)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)NNNNr)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)Nr)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)r)rr)rr)r1r2r3rrwrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrBrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr r r rrrrrrrrrrrrr!r;r"r#r$r&r(r)r*r+r,r-r.rsr3rr BaseExceptionrr7 _DomainCBr:r r<r5r@rr4rrBrCrDrErIrKrQrSrVrWrYrZr\r]r_rarbrcrerfrgrkrmrorprsrwryrzr|rrrrrrrrrrrrrrrrrrrrrrrrrrrrr rrrrrrrOsb                                                     !               $      " & ( * & ( $ " " " " " " $ " " * " $ ( & $ &  & &  " & "  "& "  "& "  "         "00c@seZdZd-ddZddZddZdd Zd.d d Zd dZd/ddZ ddZ d0ddZ ddZ ddZ ddZddZddZdd Zd!d"Zd#d$Zd%d&Zd'd(Zd1d)d*Zd2d+d,ZdS)3rNcCs.||_t|jdvr$tdt|||_dSrlrmrqrrrrszvirNodeDevice.__init__cCs |jdurt|jd|_dSrH)rprZvirNodeDeviceFreer rrrrss  zvirNodeDevice.__del__cCs|jSrHrtr rrrruszvirNodeDevice.connectcCs t|jSrv)rZvirNodeDevice_pointerrpr rrrrwszvirNodeDevice.c_pointerrcCs"t|j|}|durtd|S)zDFetch an XML document describing all aspects of the device. Nz virNodeDeviceGetXMLDesc() failed)rZvirNodeDeviceGetXMLDescrprr}rrrr~szvirNodeDevice.XMLDesccCs t|j}|dkrtd|S)z.Extract the autostart flag for a node device. rXz"virNodeDeviceGetAutostart() failed)rZvirNodeDeviceGetAutostartrprrxrrrrs zvirNodeDevice.autostartcCs"t|j|}|dkrtd|S)zStart a defined node device: rXzvirNodeDeviceCreate() failed)rZvirNodeDeviceCreaterprr}rrrrszvirNodeDevice.createcCs t|j}|dkrtd|S)zDestroy the device object. The virtual device (only works for vHBA currently) is removed from the host operating system. This function may require privileged access. rXzvirNodeDeviceDestroy() failed)rZvirNodeDeviceDestroyrprrxrrrrs zvirNodeDevice.destroycCs$t|j||}|dkr td|S)aNDetach the node device from the node itself so that it may be assigned to a guest domain. Depending on the hypervisor, this may involve operations such as unbinding any device drivers from the device, binding the device to a dummy device driver and resetting the device. Different backend drivers expect the device to be bound to different dummy devices. For example, QEMU's "kvm" backend driver (the default) expects the device to be bound to "pci-stub", but its "vfio" backend driver expects the device to be bound to "vfio-pci". If the device is currently in use by the node, this method may fail. Once the device is not assigned to any guest, it may be re-attached to the node using the virNodeDeviceReAttach() method. rXz!virNodeDeviceDetachFlags() failed)rZvirNodeDeviceDetachFlagsrpr)rZ driverNamer;r>rrr detachFlagsszvirNodeDevice.detachFlagscCs t|j}|dkrtd|S)a0Detach the node device from the node itself so that it may be assigned to a guest domain. Depending on the hypervisor, this may involve operations such as unbinding any device drivers from the device, binding the device to a dummy device driver and resetting the device. If the device is currently in use by the node, this method may fail. Once the device is not assigned to any guest, it may be re-attached to the node using the virNodeDeviceReattach() method. If the caller needs control over which backend driver will be used during PCI device assignment (to use something other than the default, for example VFIO), the newer virNodeDeviceDetachFlags() API should be used instead. rXzvirNodeDeviceDettach() failed)rZvirNodeDeviceDettachrprrxrrrdettachs zvirNodeDevice.dettachcCs t|j}|dkrtd|S)z1Determine if the node device is currently active rXzvirNodeDeviceIsActive() failed)rZvirNodeDeviceIsActiverprrxrrrrs zvirNodeDevice.isActivecCs t|j}|dkrtd|S)zxDetermine if the node device has a persistent configuration which means it will still exist after shutting down rXz"virNodeDeviceIsPersistent() failed)rZvirNodeDeviceIsPersistentrprrxrrrrs zvirNodeDevice.isPersistentcCs t|j}|durtd|S)z$list the node device's capabilities NzvirNodeDeviceListCaps() failed)rZvirNodeDeviceListCapsrprrxrrrlistCapss zvirNodeDevice.listCapscCst|j}|S)zJust return the device name )rZvirNodeDeviceGetNamerprxrrrr@&s zvirNodeDevice.namecCs t|j}|dkrtd|S)zAAccessor for the number of capabilities supported by the device. rXzvirNodeDeviceNumOfCaps() failed)rZvirNodeDeviceNumOfCapsrprrxrrr numOfCaps+s zvirNodeDevice.numOfCapscCst|j}|S)z&Accessor for the parent of the device )rZvirNodeDeviceGetParentrprxrrrparent2s zvirNodeDevice.parentcCs t|j}|dkrtd|S)aRe-attach a previously detached node device to the node so that it may be used by the node again. Depending on the hypervisor, this may involve operations such as resetting the device, unbinding it from a dummy device driver and binding it to its appropriate driver. If the device is currently in use by a guest, this method may fail. rXzvirNodeDeviceReAttach() failed)rZvirNodeDeviceReAttachrprrxrrrreAttach7s zvirNodeDevice.reAttachcCs t|j}|dkrtd|S)aReset a previously detached node device to the node before or after assigning it to a guest. The exact reset semantics depends on the hypervisor and device type but, for example, KVM will attempt to reset PCI devices with a Function Level Reset, Secondary Bus Reset or a Power Management D-State reset. If the reset will affect other devices which are currently in use, this function may fail. rXzvirNodeDeviceReset() failed)rZvirNodeDeviceResetrprrxrrrrEs zvirNodeDevice.resetcCs"t|j|}|dkrtd|S)zConfigure the node device to be automatically started when the host machine boots or the parent device becomes available. rXz"virNodeDeviceSetAutostart() failed)rZvirNodeDeviceSetAutostartrprr'rrrr(UszvirNodeDevice.setAutostartcCs"t|j|}|dkrtd|S)zUndefine the device object. The virtual device is removed from the host operating system. This function may require privileged access. rXzvirNodeDeviceUndefine() failed)rZvirNodeDeviceUndefinerprr}rrrrV]szvirNodeDevice.undefinecCs$t|j||}|dkr td|S)zUpdate the definition of an existing node device, either its live running configuration, its persistent configuration, or both. rXzvirNodeDeviceUpdate() failed)rZvirNodeDeviceUpdaterprrrrrr{eszvirNodeDevice.update)N)r)r)r)r)r)r1r2r3rrsrurwr~rrrrrrrrr@rrrrr(rVr{rrrrrs*       rc@steZdZdddZddZddZdd Zd d Zd d ZdddZ dddZ ddZ ddZ ddZ dddZdS)rNcCs.||_t|jdvr$tdt|||_dSrlrmrqrrrrnszvirSecret.__init__cCs |jdurt|jd|_dSrH)rprZ virSecretFreer rrrrsts  zvirSecret.__del__cCs|jSrHrtr rrrruyszvirSecret.connectcCs t|jSrv)rZvirSecret_pointerrpr rrrrw|szvirSecret.c_pointercCs t|j}|durtd|S)z0Extract the UUID unique Identifier of a secret. NzvirSecretGetUUID() failed)rZvirSecretGetUUIDrprrxrrrr{s zvirSecret.UUIDcCs t|j}|durtd|S)z4Fetch globally unique ID of the secret as a string. NzvirSecretGetUUIDString() failed)rZvirSecretGetUUIDStringrprrxrrrr|s zvirSecret.UUIDStringrcCs"t|j|}|durtd|S)z=Fetches an XML document describing attributes of the secret. NzvirSecretGetXMLDesc() failed)rZvirSecretGetXMLDescrprr}rrrr~szvirSecret.XMLDesccCs$t|j||}|dkr td|S)z"Associates a value with a secret. rXzvirSecretSetValue() failed)rZvirSecretSetValuerpr)rvaluer;r>rrrsetValueszvirSecret.setValuecCs t|j}|dkrtd|S)z^Deletes the specified secret. This does not free the associated virSecretPtr object. rXzvirSecretUndefine() failed)rZvirSecretUndefinerprrxrrrrVs zvirSecret.undefinecCst|j}|S)aGet the unique identifier of the object with which this secret is to be used. The format of the identifier is dependent on the usage type of the secret. For a secret with a usage type of VIR_SECRET_USAGE_TYPE_VOLUME the identifier will be a fully qualified path name. The identifiers are intended to be unique within the set of all secrets sharing the same usage type. ie, there shall only ever be one secret for each volume path. )rZvirSecretGetUsageIDrprxrrrrs zvirSecret.usageIDcCst|j}|S)a4Get the type of object which uses this secret. The returned value is one of the constants defined in the virSecretUsageType enumeration. More values may be added to this enumeration in the future, so callers should expect to see usage types they do not explicitly know about. )rZvirSecretGetUsageTyperprxrrrrs zvirSecret.usageTypecCs"t|j|}|durtd|S)z,Fetches the value associated with a secret. NzvirSecretGetValue() failed)rZvirSecretGetValuerprr}rrrrszvirSecret.value)N)r)r)r)r1r2r3rrsrurwr{r|r~rrVrrrrrrrrms    rc@sXeZdZdddZddZddZdd Zd d Zd d ZdddZ ddZ ddZ dS)r NcCs.||_t|jdvr$tdt|||_dSrlrmrqrrrrszvirNWFilter.__init__cCs |jdurt|jd|_dSrH)rprZvirNWFilterFreer rrrrss  zvirNWFilter.__del__cCs|jSrHrtr rrrruszvirNWFilter.connectcCs t|jSrv)rZvirNWFilter_pointerrpr rrrrwszvirNWFilter.c_pointercCs t|j}|durtd|S)z8Extract the UUID unique Identifier of a network filter. NzvirNWFilterGetUUID() failed)rZvirNWFilterGetUUIDrprrxrrrr{s zvirNWFilter.UUIDcCs t|j}|durtd|S)zrrreventUpdateCallbackqszvirStream.eventUpdateCallbackcCs t|j}|dkrtd|S)a,Indicate that there is no further data to be transmitted on the stream. For output streams this should be called once all data has been written. For input streams this should be called once virStreamRecv returns end-of-file. This method is a synchronization point for all asynchronous errors, so if this returns a success code the application can be sure that all data has been successfully processed. If the stream is non-blocking, any callback must be removed beforehand. rXzvirStreamFinish() failed)rZvirStreamFinishrprrxrrrfinish{s zvirStream.finishrcCsJz|jrt|jWnty(Yn0|jdur@t|jd|_dSrH)rTrrrpr2Z virStreamFreer rrrrss   zvirStream.__del__)rQrRrcCs |d}|d}||||dS)zK Dispatches events to python user's stream event callbacks rTrFrr)rrQrRrTrFrrr_dispatchStreamEventCallbacks z&virStream._dispatchStreamEventCallback)rQrTrFrcCs6||_|||d}t|j||}|dkr2tddS)N)rrTrFrXz"virStreamEventAddCallback() failed)rTrZvirStreamEventAddCallbackrpr)rrQrTrFrRr>rrreventAddCallbacks  zvirStream.eventAddCallback)handlerrFrc Cs|tj}|dkrtdt|dkr*qz.||||}t|trV|dkrVtd|Wqtyz | Wnt yYn0Yq0qdS)aReceive the entire data stream, sending the data to the requested data sink. This is simply a convenient alternative to virStreamRecv, for apps that do blocking-I/O. A hypothetical handler function looks like: def handler(stream, # virStream instance buf, # string containing received data opaque): # extra data passed to recvAll as opaque fd = opaque return os.write(fd, buf) z*cannot use recvAll with nonblocking streamrzrecvAll handler returned %dN) recvrrrr9rKr5 RuntimeErrorrrrrrrFgotr>rrrrecvAlls      zvirStream.recvAllc Csnz||tj|}Wn4tyFz |Wnty>Yn0Yn0|sNqj||}|dkrtdqdS)a Send the entire data stream, reading the data from the requested data source. This is simply a convenient alternative to virStreamSend, for apps that do blocking-I/O. A hypothetical handler function looks like: def handler(stream, # virStream instance nbytes, # int amt of data to read opaque): # extra data passed to recvAll as opaque fd = opaque return os.read(fd, nbytes) rz*cannot use sendAll with nonblocking streamN)rrrrrsendrrrrrsendAlls    zvirStream.sendAll)nbytesrcCs"t|j|}|durtd|S)aReads a series of bytes from the stream. This method may block the calling application for an arbitrary amount of time. Errors are not guaranteed to be reported synchronously with the call, but may instead be delayed until a subsequent call. On success, the received data is returned. On failure, an exception is raised. If the stream is a NONBLOCK stream and the request would block, integer -2 is returned. NzvirStreamRecv() failed)rZ virStreamRecvrpr)rrr>rrrrs zvirStream.recv)datarcCs"t|j|}|dkrtd|S)aWrite a series of bytes to the stream. This method may block the calling application for an arbitrary amount of time. Once an application has finished sending data it should call virStreamFinish to wait for successful confirmation from the driver, or detect any error This method may not be used if a stream source has been registered Errors are not guaranteed to be reported synchronously with the call, but may instead be delayed until a subsequent call. rXzvirStreamSend() failed)rZ virStreamSendrpr)rrr>rrrrszvirStream.sendrr\cCs"t|j|}|durtd|S)zThis method is used to determine the length in bytes of the empty space to be created in a stream's target file when uploading or downloading sparsely populated files. This is the counterpart to sendHole. NzvirStreamRecvHole() failed)rZvirStreamRecvHolerprr}rrrrecvHoleszvirStream.recvHole)rr;rcCs$t|j||}|dkr td|S)a"Rather than transmitting empty file space, this method directs the stream target to create length bytes of empty space. This method would be used when uploading or downloading sparsely populated files to avoid the needless copy of empty file space. rXzvirStreamSendHole() failed)rZvirStreamSendHolerpr)rrr;r>rrrsendHoleszvirStream.sendHole)rr;rcCs$t|j||}|dur td|S)a Reads a series of bytes from the stream. This method may block the calling application for an arbitrary amount of time. This is just like recv except it has flags argument. Errors are not guaranteed to be reported synchronously with the call, but may instead be delayed until a subsequent call. On success, the received data is returned. On failure, an exception is raised. If the stream is a NONBLOCK stream and the request would block, integer -2 is returned. NzvirStreamRecvFlags() failed)rZvirStreamRecvFlagsrpr)rrr;r>rrr recvFlags'szvirStream.recvFlags)r holeHandlerrFrc Cstj}||t}|dkr$tdn|dkr|}|durL|td||||}t|t r|dkr|td|qn*t|t rt |nt|t st t |t|dkrq||||}t|t r|dkr|td|qdS) a1Receive the entire data stream, sending the data to the requested data sink handler and calling the skip holeHandler to generate holes for sparse stream targets. This is simply a convenient alternative to recvFlags, for apps that do blocking-I/O and want to preserve sparseness. Hypothetical callbacks can look like this: def handler(stream, # virStream instance buf, # string containing received data opaque): # extra data passed to sparseRecvAll as opaque fd = opaque return os.write(fd, buf) def holeHandler(stream, # virStream instance length, # number of bytes to skip opaque): # extra data passed to sparseRecvAll as opaque fd = opaque cur = os.lseek(fd, length, os.SEEK_CUR) return os.ftruncate(fd, cur) # take this extra step to # actually allocate the hole rz0cannot use sparseRecvAll with nonblocking streamNzrecvHole handler failedrzholeHandler handler returned %dz!sparseRecvAll handler returned %d)rrrVIR_STREAM_RECV_STOP_AT_HOLErrrrrKr5 ValueErrorbytes TypeErrorror9) rrrrFwantrrZret_holeZret_datarrr sparseRecvAll:s0          zvirStream.sparseRecvAll)rr skipHandlerrFrc Cs|||\}}|sB|dkrB||dks8||||dkr|qtj}||krT|}||||}t|tr|dkr|td||sqt|tsJ||} | dkrt dqdS)a Send the entire data stream, reading the data from the requested data source. This is simply a convenient alternative to virStreamSend, for apps that do blocking-I/O and want to preserve sparseness. Hypothetical callbacks can look like this: def handler(stream, # virStream instance nbytes, # int amt of data to read opaque): # extra data passed to sparseSendAll as opaque fd = opaque return os.read(fd, nbytes) def holeHandler(stream, # virStream instance opaque): # extra data passed to sparseSendAll as opaque fd = opaque cur = os.lseek(fd, 0, os.SEEK_CUR) # ... find out current section and its boundaries # and set inData = True/False and sectionLen correspondingly os.lseek(fd, cur, os.SEEK_SET) return [inData, sectionLen] def skipHandler(stream, # virStream instance length, # number of bytes to skip opaque): # extra data passed to sparseSendAll as opaque fd = opaque return os.lseek(fd, length, os.SEEK_CUR) rz!sparseSendAll handler returned %drz0cannot use sparseSendAll with nonblocking streamN) rrrrrKr5rrrr) rrrrrFZinDataZ sectionLenrrr>rrr sparseSendAllns(    zvirStream.sparseSendAll)N)r)r)r)!r1r2r3rrurwrrrrrsr5rr4rrrr rrrrrrrrr rrrr boolrrrrrrIs&    "   <4rc@seZdZdddZddZddZdd Zd d Zd d dZddZ d!ddZ d"ddZ ddddZ ddddZ d#eeddddZdS)$rNcCs8||_||_t|jdvr.tdt|||_dSrl_domrurnror1rrprr=r=rrrrs  zvirDomainCheckpoint.__init__cCs |jdurt|jd|_dSrH)rprZvirDomainCheckpointFreer rrrrss  zvirDomainCheckpoint.__del__cCs|jSrHrtr rrrruszvirDomainCheckpoint.connectcCs|jSrHrr rrrdomainszvirDomainCheckpoint.domaincCs t|jSrv)rZvirDomainCheckpoint_pointerrpr rrrrwszvirDomainCheckpoint.c_pointerrcCs"t|j|}|dkrtd|S)aRemoves a checkpoint from the domain. When removing a checkpoint, the record of which portions of the disk were dirtied after the checkpoint will be merged into the record tracked by the parent checkpoint, if any. If @flags includes VIR_DOMAIN_CHECKPOINT_DELETE_CHILDREN, then any descendant checkpoints are also deleted. If @flags includes VIR_DOMAIN_CHECKPOINT_DELETE_CHILDREN_ONLY, then any descendant checkepoints are deleted, but this checkpoint remains. These two flags are mutually exclusive. If @flags includes VIR_DOMAIN_CHECKPOINT_DELETE_METADATA_ONLY, then any checkpoint metadata tracked by libvirt is removed while keeping the checkpoint contents intact; if a hypervisor does not require any libvirt metadata to track checkpoints, then this flag is silently ignored. rXz"virDomainCheckpointDelete() failed)rZvirDomainCheckpointDeleterprr}rrrrszvirDomainCheckpoint.deletecCs t|j}|durtd|S)z(Get the public name for that checkpoint Nz#virDomainCheckpointGetName() failed)rZvirDomainCheckpointGetNamerprrxrrrgetNames zvirDomainCheckpoint.getNamecCs0t|j|}|durtdt|j|d}|S)zGet the parent checkpoint for @checkpoint, if any. virDomainCheckpointFree should be used to free the resources after the checkpoint object is no longer needed. Nz%virDomainCheckpointGetParent() failedr<)rZvirDomainCheckpointGetParentrprrr)rr;r>Z_virDomainCheckpoint__tmprrr getParents zvirDomainCheckpoint.getParentcCs"t|j|}|durtd|S)aProvide an XML description of the domain checkpoint. No security-sensitive data will be included unless @flags contains VIR_DOMAIN_CHECKPOINT_XML_SECURE; this flag is rejected on read-only connections. Normally, the XML description includes an element giving a full description of the domain at the time the checkpoint was created; to reduce parsing time, it will be suppressed when @flags contains VIR_DOMAIN_CHECKPOINT_XML_NO_DOMAIN. By default, the XML description contains only static information that does not change over time. However, when @flags contains VIR_DOMAIN_CHECKPOINT_XML_SIZE, each listing adds an additional attribute that shows an estimate of the current size in bytes that have been dirtied between the time the checkpoint was created and the current point in time. Note that updating the size may be expensive and data will be inaccurate once guest OS writes to the disk. Also note that hypervisors may require that the domain associated with @checkpoint is running when VIR_DOMAIN_CHECKPOINT_XML_SIZE is used. Nz&virDomainCheckpointGetXMLDesc() failed)rZvirDomainCheckpointGetXMLDescrprr}rrr getXMLDescszvirDomainCheckpoint.getXMLDescrrcCs|S)zIGet the connection that owns the domain that a checkpoint was created forrur rrr getConnectszvirDomainCheckpoint.getConnectrcCs|S)z0Get the domain that a checkpoint was created forrr rrr getDomain szvirDomainCheckpoint.getDomainr\cs0tj|}|durtdfdd|DS)zCList all child checkpoints and returns a list of checkpoint objectsNz+virDomainCheckpointListAllChildren() failedcsg|]}t|dqSr])rrrcr rrr`raz7virDomainCheckpoint.listAllChildren..)rZ"virDomainCheckpointListAllChildrenrprr}rr rlistAllChildrensz#virDomainCheckpoint.listAllChildren)N)r)r)r)r)r1r2r3rrsrurrwrrrrrrr5rrrrrrrs   rc@seZdZd'ddZddZddZdd Zd d Zd(d dZddZ d)ddZ d*ddZ d+ddZ d,ddZ d-ddZd.ddZdddd Zd!dd"d#Zd/eedd$d%d&ZdS)0rNNcCs8||_||_t|jdvr.tdt|||_dSrlrrrrrrs  zvirDomainSnapshot.__init__cCs |jdurt|jd|_dSrH)rprZvirDomainSnapshotFreer rrrrss  zvirDomainSnapshot.__del__cCs|jSrHrtr rrrru$szvirDomainSnapshot.connectcCs|jSrHrr rrrr'szvirDomainSnapshot.domaincCs t|jSrv)rZvirDomainSnapshot_pointerrpr rrrrw*szvirDomainSnapshot.c_pointerrcCs"t|j|}|dkrtd|S)aDelete the snapshot. If @flags is 0, then just this snapshot is deleted, and changes from this snapshot are automatically merged into children snapshots. If @flags includes VIR_DOMAIN_SNAPSHOT_DELETE_CHILDREN, then this snapshot and any descendant snapshots are deleted. If @flags includes VIR_DOMAIN_SNAPSHOT_DELETE_CHILDREN_ONLY, then any descendant snapshots are deleted, but this snapshot remains. These two flags are mutually exclusive. If @flags includes VIR_DOMAIN_SNAPSHOT_DELETE_METADATA_ONLY, then any snapshot metadata tracked by libvirt is removed while keeping the snapshot contents intact; if a hypervisor does not require any libvirt metadata to track snapshots, then this flag is silently ignored. Since libvirt 9.0.0 deletion of external snapshots is supported for QEMU driver. Using @flags VIR_DOMAIN_SNAPSHOT_DELETE_CHILDREN and VIR_DOMAIN_SNAPSHOT_DELETE_CHILDREN_ONLY is not supported with external snapshots. In case that daemon process is terminated while the snapshot delete is in process the operation will be aborted when the daemon starts again. rXz virDomainSnapshotDelete() failed)rZvirDomainSnapshotDeleterprr}rrrr2szvirDomainSnapshot.deletecCs t|j}|durtd|S)z&Get the public name for that snapshot Nz!virDomainSnapshotGetName() failed)rZvirDomainSnapshotGetNamerprrxrrrrNs zvirDomainSnapshot.getNamecCs0t|j|}|durtdt|j|d}|S)zGet the parent snapshot for @snapshot, if any. virDomainSnapshotFree should be used to free the resources after the snapshot object is no longer needed. Nz#virDomainSnapshotGetParent() failedr<)rZvirDomainSnapshotGetParentrprrNr)rr;r>Z_virDomainSnapshot__tmprrrrUs zvirDomainSnapshot.getParentcCs"t|j|}|durtd|S)aProvide an XML description of the domain snapshot, with a top-level element of . No security-sensitive data will be included unless @flags contains VIR_DOMAIN_SNAPSHOT_XML_SECURE; this flag is rejected on read-only connections. Nz$virDomainSnapshotGetXMLDesc() failed)rZvirDomainSnapshotGetXMLDescrprr}rrrr`szvirDomainSnapshot.getXMLDesccCs"t|j|}|dkrtd|S)z{Determine if the given snapshot is associated with libvirt metadata that would prevent the deletion of the domain. rXz%virDomainSnapshotHasMetadata() failed)rZvirDomainSnapshotHasMetadatarprr}rrr hasMetadatalszvirDomainSnapshot.hasMetadatacCs"t|j|}|dkrtd|S)zsDetermine if the given snapshot is the domain's current snapshot. See also virDomainHasCurrentSnapshot(). rXz#virDomainSnapshotIsCurrent() failed)rZvirDomainSnapshotIsCurrentrprr}rrr isCurrenttszvirDomainSnapshot.isCurrentcCs"t|j|}|durtd|S)z@collect the list of child snapshot names for the given snapshot Nz+virDomainSnapshotListChildrenNames() failed)rZ"virDomainSnapshotListChildrenNamesrprr}rrrlistChildrenNamessz#virDomainSnapshot.listChildrenNamescCs"t|j|}|dkrtd|S)acProvides the number of child snapshots for this domain snapshot. This function will accept VIR_DOMAIN_SNAPSHOT_LIST_TOPOLOGICAL in @flags only if virDomainSnapshotListChildrenNames() can honor it, although the flag has no other effect here. By default, this command covers only direct children. It is also possible to expand things to cover all descendants, when @flags includes VIR_DOMAIN_SNAPSHOT_LIST_DESCENDANTS. Additional filters are provided via the same @flags values as documented in virDomainSnapshotListAllChildren(). rXz%virDomainSnapshotNumChildren() failed)rZvirDomainSnapshotNumChildrenrprr}rrr numChildrens zvirDomainSnapshot.numChildrenrrcCs|S)zGGet the connection that owns the domain that a snapshot was created forrr rrrrszvirDomainSnapshot.getConnectrcCs|S)z.Get the domain that a snapshot was created forrr rrrrszvirDomainSnapshot.getDomainr\cs0tj|}|durtdfdd|DS)z?List all child snapshots and returns a list of snapshot objectsNz)virDomainSnapshotListAllChildren() failedcsg|]}t|dqSr])rNrr^r rrr`raz5virDomainSnapshot.listAllChildren..)rZ virDomainSnapshotListAllChildrenrprr}rr rrsz!virDomainSnapshot.listAllChildren)N)r)r)r)r)r)r)r)r)r1r2r3rrsrurrwrrrrrrrrrrr5rrrrrrrNs     rNr"rr%r'r)r+rXr-r/  @i i@liiiii i@iiiiiii i@iir !"#$%&'()*+,-./0123456789:;<=>?ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqz group-namez process-idz process-timezsasl-user-namezselinux-contextz unix-group-idz unix-user-idz user-namezx509-distinguished-namezinbound.averagez inbound.burstz inbound.floorz inbound.peakzoutbound.averagezoutbound.burstz outbound.peakZdevice_read_bytes_secZdevice_read_iops_secZ device_weightZdevice_write_bytes_secZdevice_write_iops_secZweightrzbuf-sizeZ granularityZ group_nameZread_bytes_secZread_bytes_sec_maxZread_bytes_sec_max_lengthZ read_iops_secZread_iops_sec_maxZread_iops_sec_max_lengthZ size_iops_secZtotal_bytes_secZtotal_bytes_sec_maxZtotal_bytes_sec_max_lengthZtotal_iops_secZtotal_iops_sec_maxZtotal_iops_sec_max_lengthZwrite_bytes_secZwrite_bytes_sec_maxZwrite_bytes_sec_max_lengthZwrite_iops_secZwrite_iops_sec_maxZwrite_iops_sec_max_lengthZerrsZflush_operationsZflush_total_timesZrd_bytesZ rd_operationsZrd_total_timesZwr_bytesZ wr_operationsZwr_total_timesZcpu_timeZ system_timeZ user_timeZ vcpu_timez disk.countzdisk.z.aliasz.dependency.countz .dependency.z.namez .guest_aliasz .guest_busz .partitionz.serialzfs.countzfs.z .disk.countz.disk.z.devicez.fstypez .mountpointz .total-bytesz .used-bytesrzif.countzif.z .addr.countz.addr.z.addrz.prefixz.typez.hwaddrzload.15mzload.1mzload.5mzos.idzos.kernel-releasezos.kernel-versionz os.machinezos.namezos.pretty-namez os.variantz os.variant-idz os.versionz os.version-idz timezone.nameztimezone.offsetz user.countzuser.z.domainz .login-timeZ poll_growZ poll_max_nsZ poll_shrinkZthread_pool_maxZthread_pool_minZauto_converge_throttleZcompression_bytesZcompression_cacheZcompression_cache_missesZcompression_overflowZcompression_pagesZdata_processedZdata_remainingZ data_totalZdisk_bpsZdisk_processedZdisk_remainingZdisk_temp_totalZdisk_temp_usedZ disk_totalrZ downtime_neterrmsgZ memory_bpsZmemory_constantZmemory_dirty_rateZmemory_iterationZ memory_normalZmemory_normal_bytesZmemory_page_sizeZmemory_postcopy_requestsZmemory_processedZmemory_remainingZ memory_totalZ operationZ setup_timesuccessZ time_elapsedZtime_elapsed_netZtime_remainingZvfio_data_transferredz sev-api-majorz sev-api-minorz sev-build-idzsev-measurementz sev-policyz sev-secretzsev-secret-headerzsev-secret-set-addresszsev-snp-policyZ hard_limitZ min_guaranteeZ soft_limitZswap_hard_limitZ numa_modeZ numa_nodesetrrZ image_formatzparallel.channelsrZ cpu_sharesZemulator_periodZemulator_quotaZ global_periodZ global_quotaZiothread_periodZiothread_quotalimitZ reservationZsharesZ vcpu_periodZ vcpu_quotazballoon.availablezballoon.currentzballoon.disk_cacheszballoon.hugetlb_pgalloczballoon.hugetlb_pgfailzballoon.last-updatezballoon.major_faultzballoon.maximumzballoon.minor_faultz balloon.rsszballoon.swap_inzballoon.swap_outzballoon.unusedzballoon.usablez block.countzblock.z .allocationz .backingIndexz .capacityz.errorsz.fl.reqsz .fl.timesz.latency_histogram.flush.z.latency_histogram.read.z bin.countzbin.z.startz.valuez.latency_histogram.write.z.latency_histogram.zone_append.z.limits.discard_alignmentz.limits.discard_maxz.limits.iov_hw_maxz.limits.iov_maxz .limits.memory_alignment_minimalz .limits.memory_alignment_optimalz.limits.request_alignmentz.limits.transfer_hw_maxz.limits.transfer_maxz.limits.transfer_optimalz.limits.write_zeroes_alignmentz.limits.write_zeroes_maxz.pathz .physicalz .rd.bytesz.rd.reqsz .rd.timesz .thresholdz.timed_group.countz .timed_group.z.flush_latency_avgz.flush_latency_maxz.flush_latency_minz .intervalz.rd_latency_avgz.rd_latency_maxz.rd_latency_minz.rd_queue_depth_avgz.wr_latency_avgz.wr_latency_maxz.wr_latency_minz.wr_queue_depth_avgz.zone_append_latency_avgz.zone_append_latency_maxz.zone_append_latency_minz.zone_append_queue_depth_avgz .wr.bytesz.wr.reqsz .wr.timeszcpu.cache.monitor.countzcpu.cache.monitor.z .bank.countz.bank.z.bytesz.idz.vcpuszcpu.haltpoll.fail.timezcpu.haltpoll.success.timez cpu.systemzcpu.timezcpu.userz.curz.maxz.sumzdirtyrate.calc_modezdirtyrate.calc_periodzdirtyrate.calc_start_timezdirtyrate.calc_statuszdirtyrate.megabytes_per_secondzdirtyrate.vcpu.z.megabytes_per_secondziothread.countz iothread.z .poll-growz .poll-max-nsz .poll-shrinkzmemory.bandwidth.monitor.countzmemory.bandwidth.monitor.z .node.countz.node.z .bytes.localz .bytes.totalz net.countznet.z .rx.bytesz.rx.dropz.rx.errsz.rx.pktsz .tx.bytesz.tx.dropz.tx.errsz.tx.pktszperf.alignment_faultszperf.branch_instructionszperf.branch_misseszperf.bus_cycleszperf.cache_misseszperf.cache_referenceszperf.cmtzperf.context_switcheszperf.cpu_clockzperf.cpu_cycleszperf.cpu_migrationszperf.emulation_faultszperf.instructionsz perf.mbmlz perf.mbmtzperf.page_faultszperf.page_faults_majzperf.page_faults_minzperf.ref_cpu_cycleszperf.stalled_cycles_backendzperf.stalled_cycles_frontendzperf.task_clockz state.reasonz state.statez vcpu.currentz vcpu.maximumzvcpu.z.delayz.haltedz.statez.timez.waitzvm.zblkdeviotune.diskzblkdeviotune.group_namezblkdeviotune.read_bytes_seczblkdeviotune.read_bytes_sec_maxz&blkdeviotune.read_bytes_sec_max_lengthzblkdeviotune.read_iops_seczblkdeviotune.read_iops_sec_maxz%blkdeviotune.read_iops_sec_max_lengthzblkdeviotune.size_iops_seczblkdeviotune.total_bytes_secz blkdeviotune.total_bytes_sec_maxz'blkdeviotune.total_bytes_sec_max_lengthzblkdeviotune.total_iops_seczblkdeviotune.total_iops_sec_maxz&blkdeviotune.total_iops_sec_max_lengthzblkdeviotune.write_bytes_secz blkdeviotune.write_bytes_sec_maxz'blkdeviotune.write_bytes_sec_max_lengthzblkdeviotune.write_iops_seczblkdeviotune.write_iops_sec_maxz&blkdeviotune.write_iops_sec_max_lengthzcputune.cpu_shareszcputune.emulatorpinzcputune.emulator_periodzcputune.emulator_quotazcputune.global_periodzcputune.global_quotazcputune.iothreadpin%uzcputune.iothread_periodzcputune.iothread_quotazcputune.vcpupin%uzcputune.vcpu_periodzcputune.vcpu_quotazauto_converge.incrementzauto_converge.initialzbandwidth.avail.switchoverzbandwidth.postcopy compressionzcompression.mt.dthreadszcompression.mt.levelzcompression.mt.threadszcompression.xbzrle.cachezcompression.zlib.levelzcompression.zstd.levelZdestination_nameZdestination_xmlZ disks_portZ disks_uriZ graphics_uriZlisten_addressZ migrate_disksZmigrate_disks_detect_zeroeszparallel.connectionsZpersistent_xmlztls.destinationZ migrate_uriZguestZidleZintrZiowaitZkernelrZ utilizationZshm_full_scansZshm_merge_across_nodesZshm_pages_sharedZshm_pages_sharingZshm_pages_to_scanZshm_pages_unsharedZshm_pages_volatileZshm_sleep_millisecsZbufferscachedfreerZcbitposz cert-chainzcpu0-idz max-es-guestsz max-guestsZpdhzreduced-phys-bitsZalignment_faultsZbranch_instructionsZ branch_missesZ bus_cyclesZ cache_missesZcache_referencesZcmtZcontext_switchesZ cpu_clockZ cpu_cyclesZcpu_migrationsZemulation_faultsZ instructionsZmbmlZmbmtZ page_faultsZpage_faults_majZpage_faults_minZref_cpu_cyclesZstalled_cycles_backendZstalled_cycles_frontendZ task_clock)r)N)N)N)N)N)N)N(r ImportErrorZlib_eZ cygvirtmodZcyg_er4rrtypingrrrrrrr r r r r r5Z_EventCBZ_EventAddHandleFuncZ_EventUpdateHandleFuncZ_EventRemoveHandleFuncZ_TimerCBZ_EventAddTimeoutFuncZ_EventUpdateTimeoutFuncZ_EventRemoveTimeoutFuncrZ_BlkioParameterZ_MemoryParameterZ_SchedParameterZ_TypedParameterrrr8r?rBrJrPrUrVrYr[r\r]r^r_rarbrcrdrerfrrgrhrirjrkobjectrrorrrrrrrrr rrrrNZVIR_DOMAIN_BLKIO_PARAM_INTZVIR_DOMAIN_BLKIO_PARAM_UINTZVIR_DOMAIN_BLKIO_PARAM_LLONGZVIR_DOMAIN_BLKIO_PARAM_ULLONGZVIR_DOMAIN_BLKIO_PARAM_DOUBLEZVIR_DOMAIN_BLKIO_PARAM_BOOLEANZVIR_CPU_COMPARE_ERRORZVIR_CPU_COMPARE_INCOMPATIBLEZVIR_CPU_COMPARE_IDENTICALZVIR_CPU_COMPARE_SUPERSETZ(VIR_CONNECT_BASELINE_CPU_EXPAND_FEATURESZ#VIR_CONNECT_BASELINE_CPU_MIGRATABLEZ$VIR_CONNECT_BASELINE_CPU_IGNORE_HOSTZVIR_CONNECT_CLOSE_REASON_ERRORZVIR_CONNECT_CLOSE_REASON_EOFZ"VIR_CONNECT_CLOSE_REASON_KEEPALIVEZVIR_CONNECT_CLOSE_REASON_CLIENTZ)VIR_CONNECT_COMPARE_CPU_FAIL_INCOMPATIBLEZ$VIR_CONNECT_COMPARE_CPU_VALIDATE_XMLZVIR_CRED_USERNAMEZVIR_CRED_AUTHNAMEZVIR_CRED_LANGUAGEZVIR_CRED_CNONCEZVIR_CRED_PASSPHRASEZVIR_CRED_ECHOPROMPTZVIR_CRED_NOECHOPROMPTZVIR_CRED_REALMZVIR_CRED_EXTERNALZ7VIR_CONNECT_DOMAIN_EVENT_AGENT_LIFECYCLE_REASON_UNKNOWNZ>VIR_CONNECT_DOMAIN_EVENT_AGENT_LIFECYCLE_REASON_DOMAIN_STARTEDZ7VIR_CONNECT_DOMAIN_EVENT_AGENT_LIFECYCLE_REASON_CHANNELZ8VIR_CONNECT_DOMAIN_EVENT_AGENT_LIFECYCLE_STATE_CONNECTEDZ;VIR_CONNECT_DOMAIN_EVENT_AGENT_LIFECYCLE_STATE_DISCONNECTEDZVIR_DOMAIN_BLOCK_JOB_COMPLETEDZVIR_DOMAIN_BLOCK_JOB_FAILEDZVIR_DOMAIN_BLOCK_JOB_CANCELEDZVIR_DOMAIN_BLOCK_JOB_READYZ-VIR_DOMAIN_EVENT_DISK_CHANGE_MISSING_ON_STARTZ+VIR_DOMAIN_EVENT_DISK_DROP_MISSING_ON_STARTZVIR_CONNECT_ROZVIR_CONNECT_NO_ALIASESZ(VIR_CONNECT_GET_ALL_DOMAINS_STATS_ACTIVEZ*VIR_CONNECT_GET_ALL_DOMAINS_STATS_INACTIVEZ,VIR_CONNECT_GET_ALL_DOMAINS_STATS_PERSISTENTZ+VIR_CONNECT_GET_ALL_DOMAINS_STATS_TRANSIENTZ)VIR_CONNECT_GET_ALL_DOMAINS_STATS_RUNNINGZ(VIR_CONNECT_GET_ALL_DOMAINS_STATS_PAUSEDZ)VIR_CONNECT_GET_ALL_DOMAINS_STATS_SHUTOFFZ'VIR_CONNECT_GET_ALL_DOMAINS_STATS_OTHERZ(VIR_CONNECT_GET_ALL_DOMAINS_STATS_NOWAITZ)VIR_CONNECT_GET_ALL_DOMAINS_STATS_BACKINGZ/VIR_CONNECT_GET_ALL_DOMAINS_STATS_ENFORCE_STATSZ?VIR_CONNECT_GET_DOMAIN_CAPABILITIES_DISABLE_DEPRECATED_FEATURESZVIR_CONNECT_LIST_DOMAINS_ACTIVEZ!VIR_CONNECT_LIST_DOMAINS_INACTIVEZ#VIR_CONNECT_LIST_DOMAINS_PERSISTENTZ"VIR_CONNECT_LIST_DOMAINS_TRANSIENTZ VIR_CONNECT_LIST_DOMAINS_RUNNINGZVIR_CONNECT_LIST_DOMAINS_PAUSEDZ VIR_CONNECT_LIST_DOMAINS_SHUTOFFZVIR_CONNECT_LIST_DOMAINS_OTHERZ$VIR_CONNECT_LIST_DOMAINS_MANAGEDSAVEZ'VIR_CONNECT_LIST_DOMAINS_NO_MANAGEDSAVEZ"VIR_CONNECT_LIST_DOMAINS_AUTOSTARTZ%VIR_CONNECT_LIST_DOMAINS_NO_AUTOSTARTZ%VIR_CONNECT_LIST_DOMAINS_HAS_SNAPSHOTZ$VIR_CONNECT_LIST_DOMAINS_NO_SNAPSHOTZ'VIR_CONNECT_LIST_DOMAINS_HAS_CHECKPOINTZ&VIR_CONNECT_LIST_DOMAINS_NO_CHECKPOINTZ$VIR_CONNECT_LIST_INTERFACES_INACTIVEZ"VIR_CONNECT_LIST_INTERFACES_ACTIVEZ"VIR_CONNECT_LIST_NETWORKS_INACTIVEZ VIR_CONNECT_LIST_NETWORKS_ACTIVEZ$VIR_CONNECT_LIST_NETWORKS_PERSISTENTZ#VIR_CONNECT_LIST_NETWORKS_TRANSIENTZ#VIR_CONNECT_LIST_NETWORKS_AUTOSTARTZ&VIR_CONNECT_LIST_NETWORKS_NO_AUTOSTARTZ(VIR_CONNECT_LIST_NODE_DEVICES_CAP_SYSTEMZ)VIR_CONNECT_LIST_NODE_DEVICES_CAP_PCI_DEVZ)VIR_CONNECT_LIST_NODE_DEVICES_CAP_USB_DEVZ/VIR_CONNECT_LIST_NODE_DEVICES_CAP_USB_INTERFACEZ%VIR_CONNECT_LIST_NODE_DEVICES_CAP_NETZ+VIR_CONNECT_LIST_NODE_DEVICES_CAP_SCSI_HOSTZ-VIR_CONNECT_LIST_NODE_DEVICES_CAP_SCSI_TARGETZ&VIR_CONNECT_LIST_NODE_DEVICES_CAP_SCSIZ)VIR_CONNECT_LIST_NODE_DEVICES_CAP_STORAGEZ)VIR_CONNECT_LIST_NODE_DEVICES_CAP_FC_HOSTZ(VIR_CONNECT_LIST_NODE_DEVICES_CAP_VPORTSZ.VIR_CONNECT_LIST_NODE_DEVICES_CAP_SCSI_GENERICZ%VIR_CONNECT_LIST_NODE_DEVICES_CAP_DRMZ,VIR_CONNECT_LIST_NODE_DEVICES_CAP_MDEV_TYPESZ&VIR_CONNECT_LIST_NODE_DEVICES_CAP_MDEVZ)VIR_CONNECT_LIST_NODE_DEVICES_CAP_CCW_DEVZ)VIR_CONNECT_LIST_NODE_DEVICES_CAP_CSS_DEVZ&VIR_CONNECT_LIST_NODE_DEVICES_CAP_VDPAZ)VIR_CONNECT_LIST_NODE_DEVICES_CAP_AP_CARDZ*VIR_CONNECT_LIST_NODE_DEVICES_CAP_AP_QUEUEZ+VIR_CONNECT_LIST_NODE_DEVICES_CAP_AP_MATRIXZ%VIR_CONNECT_LIST_NODE_DEVICES_CAP_VPDZ.VIR_CONNECT_LIST_NODE_DEVICES_CAP_CCWGROUP_DEVZ1VIR_CONNECT_LIST_NODE_DEVICES_CAP_CCWGROUP_MEMBERZ(VIR_CONNECT_LIST_NODE_DEVICES_PERSISTENTZ'VIR_CONNECT_LIST_NODE_DEVICES_TRANSIENTZ&VIR_CONNECT_LIST_NODE_DEVICES_INACTIVEZ$VIR_CONNECT_LIST_NODE_DEVICES_ACTIVEZ"VIR_CONNECT_LIST_SECRETS_EPHEMERALZ%VIR_CONNECT_LIST_SECRETS_NO_EPHEMERALZ VIR_CONNECT_LIST_SECRETS_PRIVATEZ#VIR_CONNECT_LIST_SECRETS_NO_PRIVATEZ'VIR_CONNECT_LIST_STORAGE_POOLS_INACTIVEZ%VIR_CONNECT_LIST_STORAGE_POOLS_ACTIVEZ)VIR_CONNECT_LIST_STORAGE_POOLS_PERSISTENTZ(VIR_CONNECT_LIST_STORAGE_POOLS_TRANSIENTZ(VIR_CONNECT_LIST_STORAGE_POOLS_AUTOSTARTZ+VIR_CONNECT_LIST_STORAGE_POOLS_NO_AUTOSTARTZ"VIR_CONNECT_LIST_STORAGE_POOLS_DIRZ!VIR_CONNECT_LIST_STORAGE_POOLS_FSZ$VIR_CONNECT_LIST_STORAGE_POOLS_NETFSZ&VIR_CONNECT_LIST_STORAGE_POOLS_LOGICALZ#VIR_CONNECT_LIST_STORAGE_POOLS_DISKZ$VIR_CONNECT_LIST_STORAGE_POOLS_ISCSIZ#VIR_CONNECT_LIST_STORAGE_POOLS_SCSIZ$VIR_CONNECT_LIST_STORAGE_POOLS_MPATHZ"VIR_CONNECT_LIST_STORAGE_POOLS_RBDZ'VIR_CONNECT_LIST_STORAGE_POOLS_SHEEPDOGZ&VIR_CONNECT_LIST_STORAGE_POOLS_GLUSTERZ"VIR_CONNECT_LIST_STORAGE_POOLS_ZFSZ'VIR_CONNECT_LIST_STORAGE_POOLS_VSTORAGEZ+VIR_CONNECT_LIST_STORAGE_POOLS_ISCSI_DIRECTZVIR_DOMAIN_ABORT_JOB_POSTCOPYZ'VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_BLOCKZ)VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_DEFAULTZ(VIR_DOMAIN_AGENT_RESPONSE_TIMEOUT_NOWAITZ)VIR_DOMAIN_AUTHORIZED_SSH_KEYS_SET_APPENDZ)VIR_DOMAIN_AUTHORIZED_SSH_KEYS_SET_REMOVEZ&VIR_DOMAIN_BACKUP_BEGIN_REUSE_EXTERNALZ0VIR_DOMAIN_BACKUP_BEGIN_PRESERVE_SHUTDOWN_DOMAINZVIR_DOMAIN_BLOCK_COMMIT_SHALLOWZVIR_DOMAIN_BLOCK_COMMIT_DELETEZVIR_DOMAIN_BLOCK_COMMIT_ACTIVEZ VIR_DOMAIN_BLOCK_COMMIT_RELATIVEZ'VIR_DOMAIN_BLOCK_COMMIT_BANDWIDTH_BYTESZVIR_DOMAIN_BLOCK_COPY_SHALLOWZVIR_DOMAIN_BLOCK_COPY_REUSE_EXTZ#VIR_DOMAIN_BLOCK_COPY_TRANSIENT_JOBZ(VIR_DOMAIN_BLOCK_COPY_SYNCHRONOUS_WRITESZ VIR_DOMAIN_BLOCK_JOB_ABORT_ASYNCZ VIR_DOMAIN_BLOCK_JOB_ABORT_PIVOTZ)VIR_DOMAIN_BLOCK_JOB_INFO_BANDWIDTH_BYTESZ*VIR_DOMAIN_BLOCK_JOB_SPEED_BANDWIDTH_BYTESZ!VIR_DOMAIN_BLOCK_JOB_TYPE_UNKNOWNZVIR_DOMAIN_BLOCK_JOB_TYPE_PULLZVIR_DOMAIN_BLOCK_JOB_TYPE_COPYZ VIR_DOMAIN_BLOCK_JOB_TYPE_COMMITZ'VIR_DOMAIN_BLOCK_JOB_TYPE_ACTIVE_COMMITZ VIR_DOMAIN_BLOCK_JOB_TYPE_BACKUPZ%VIR_DOMAIN_BLOCK_PULL_BANDWIDTH_BYTESZVIR_DOMAIN_BLOCK_REBASE_SHALLOWZ!VIR_DOMAIN_BLOCK_REBASE_REUSE_EXTZ VIR_DOMAIN_BLOCK_REBASE_COPY_RAWZVIR_DOMAIN_BLOCK_REBASE_COPYZ VIR_DOMAIN_BLOCK_REBASE_RELATIVEZ VIR_DOMAIN_BLOCK_REBASE_COPY_DEVZ'VIR_DOMAIN_BLOCK_REBASE_BANDWIDTH_BYTESZVIR_DOMAIN_BLOCK_RESIZE_BYTESZ VIR_DOMAIN_BLOCK_RESIZE_CAPACITYZVIR_DOMAIN_BLOCKED_UNKNOWNZVIR_DOMAIN_CHANNEL_FORCEZ%VIR_DOMAIN_CHECKPOINT_CREATE_REDEFINEZ$VIR_DOMAIN_CHECKPOINT_CREATE_QUIESCEZ.VIR_DOMAIN_CHECKPOINT_CREATE_REDEFINE_VALIDATEZ%VIR_DOMAIN_CHECKPOINT_DELETE_CHILDRENZ*VIR_DOMAIN_CHECKPOINT_DELETE_METADATA_ONLYZ*VIR_DOMAIN_CHECKPOINT_DELETE_CHILDREN_ONLYZ&VIR_DOMAIN_CHECKPOINT_LIST_DESCENDANTSZ VIR_DOMAIN_CHECKPOINT_LIST_ROOTSZ&VIR_DOMAIN_CHECKPOINT_LIST_TOPOLOGICALZ!VIR_DOMAIN_CHECKPOINT_LIST_LEAVESZ$VIR_DOMAIN_CHECKPOINT_LIST_NO_LEAVESZ VIR_DOMAIN_CHECKPOINT_XML_SECUREZ#VIR_DOMAIN_CHECKPOINT_XML_NO_DOMAINZVIR_DOMAIN_CHECKPOINT_XML_SIZEZVIR_DOMAIN_CONSOLE_FORCEZVIR_DOMAIN_CONSOLE_SAFEZ$VIR_DOMAIN_CONTROL_ERROR_REASON_NONEZ'VIR_DOMAIN_CONTROL_ERROR_REASON_UNKNOWNZ'VIR_DOMAIN_CONTROL_ERROR_REASON_MONITORZ(VIR_DOMAIN_CONTROL_ERROR_REASON_INTERNALZVIR_DOMAIN_CONTROL_OKZVIR_DOMAIN_CONTROL_JOBZVIR_DOMAIN_CONTROL_OCCUPIEDZVIR_DOMAIN_CONTROL_ERRORZVIR_DUMP_CRASHZ VIR_DUMP_LIVEZVIR_DUMP_BYPASS_CACHEZVIR_DUMP_RESETZVIR_DUMP_MEMORY_ONLYZVIR_DOMAIN_CORE_DUMP_FORMAT_RAWZ&VIR_DOMAIN_CORE_DUMP_FORMAT_KDUMP_ZLIBZ%VIR_DOMAIN_CORE_DUMP_FORMAT_KDUMP_LZOZ(VIR_DOMAIN_CORE_DUMP_FORMAT_KDUMP_SNAPPYZ#VIR_DOMAIN_CORE_DUMP_FORMAT_WIN_DMPZVIR_DOMAIN_CRASHED_UNKNOWNZVIR_DOMAIN_CRASHED_PANICKEDZVIR_DOMAIN_NONEZVIR_DOMAIN_START_PAUSEDZVIR_DOMAIN_START_AUTODESTROYZVIR_DOMAIN_START_BYPASS_CACHEZVIR_DOMAIN_START_FORCE_BOOTZVIR_DOMAIN_START_VALIDATEZVIR_DOMAIN_START_RESET_NVRAMZVIR_DOMAIN_DEFINE_VALIDATEZVIR_DOMAIN_DESTROY_DEFAULTZVIR_DOMAIN_DESTROY_GRACEFULZVIR_DOMAIN_DESTROY_REMOVE_LOGSZ VIR_DOMAIN_DEVICE_MODIFY_CURRENTZVIR_DOMAIN_DEVICE_MODIFY_LIVEZVIR_DOMAIN_DEVICE_MODIFY_CONFIGZVIR_DOMAIN_DEVICE_MODIFY_FORCEZ'VIR_DOMAIN_DIRTYRATE_MODE_PAGE_SAMPLINGZ&VIR_DOMAIN_DIRTYRATE_MODE_DIRTY_BITMAPZ$VIR_DOMAIN_DIRTYRATE_MODE_DIRTY_RINGZVIR_DOMAIN_DIRTYRATE_UNSTARTEDZVIR_DOMAIN_DIRTYRATE_MEASURINGZVIR_DOMAIN_DIRTYRATE_MEASUREDZVIR_DOMAIN_DISK_ERROR_NONEZVIR_DOMAIN_DISK_ERROR_UNSPECZVIR_DOMAIN_DISK_ERROR_NO_SPACEZ!VIR_DOMAIN_EVENT_CRASHED_PANICKEDZ$VIR_DOMAIN_EVENT_CRASHED_CRASHLOADEDZVIR_DOMAIN_EVENT_DEFINED_ADDEDZ VIR_DOMAIN_EVENT_DEFINED_UPDATEDZ VIR_DOMAIN_EVENT_DEFINED_RENAMEDZ&VIR_DOMAIN_EVENT_DEFINED_FROM_SNAPSHOTZ&VIR_DOMAIN_EVENT_GRAPHICS_ADDRESS_IPV4Z&VIR_DOMAIN_EVENT_GRAPHICS_ADDRESS_IPV6Z&VIR_DOMAIN_EVENT_GRAPHICS_ADDRESS_UNIXZ!VIR_DOMAIN_EVENT_GRAPHICS_CONNECTZ$VIR_DOMAIN_EVENT_GRAPHICS_INITIALIZEZ$VIR_DOMAIN_EVENT_GRAPHICS_DISCONNECTZVIR_DOMAIN_EVENT_ID_LIFECYCLEZVIR_DOMAIN_EVENT_ID_REBOOTZVIR_DOMAIN_EVENT_ID_RTC_CHANGEZVIR_DOMAIN_EVENT_ID_WATCHDOGZVIR_DOMAIN_EVENT_ID_IO_ERRORZVIR_DOMAIN_EVENT_ID_GRAPHICSZ#VIR_DOMAIN_EVENT_ID_IO_ERROR_REASONZ!VIR_DOMAIN_EVENT_ID_CONTROL_ERRORZVIR_DOMAIN_EVENT_ID_BLOCK_JOBZVIR_DOMAIN_EVENT_ID_DISK_CHANGEZVIR_DOMAIN_EVENT_ID_TRAY_CHANGEZVIR_DOMAIN_EVENT_ID_PMWAKEUPZVIR_DOMAIN_EVENT_ID_PMSUSPENDZ"VIR_DOMAIN_EVENT_ID_BALLOON_CHANGEZ"VIR_DOMAIN_EVENT_ID_PMSUSPEND_DISKZ"VIR_DOMAIN_EVENT_ID_DEVICE_REMOVEDZVIR_DOMAIN_EVENT_ID_BLOCK_JOB_2ZVIR_DOMAIN_EVENT_ID_TUNABLEZ#VIR_DOMAIN_EVENT_ID_AGENT_LIFECYCLEZ VIR_DOMAIN_EVENT_ID_DEVICE_ADDEDZ'VIR_DOMAIN_EVENT_ID_MIGRATION_ITERATIONZ!VIR_DOMAIN_EVENT_ID_JOB_COMPLETEDZ)VIR_DOMAIN_EVENT_ID_DEVICE_REMOVAL_FAILEDZ#VIR_DOMAIN_EVENT_ID_METADATA_CHANGEZ#VIR_DOMAIN_EVENT_ID_BLOCK_THRESHOLDZ"VIR_DOMAIN_EVENT_ID_MEMORY_FAILUREZ-VIR_DOMAIN_EVENT_ID_MEMORY_DEVICE_SIZE_CHANGEZ"VIR_DOMAIN_EVENT_ID_NIC_MAC_CHANGEZVIR_DOMAIN_EVENT_IO_ERROR_NONEZVIR_DOMAIN_EVENT_IO_ERROR_PAUSEZ VIR_DOMAIN_EVENT_IO_ERROR_REPORTZ#VIR_DOMAIN_EVENT_PMSUSPENDED_MEMORYZ!VIR_DOMAIN_EVENT_PMSUSPENDED_DISKZ!VIR_DOMAIN_EVENT_RESUMED_UNPAUSEDZ!VIR_DOMAIN_EVENT_RESUMED_MIGRATEDZ&VIR_DOMAIN_EVENT_RESUMED_FROM_SNAPSHOTZ!VIR_DOMAIN_EVENT_RESUMED_POSTCOPYZ(VIR_DOMAIN_EVENT_RESUMED_POSTCOPY_FAILEDZ"VIR_DOMAIN_EVENT_SHUTDOWN_FINISHEDZVIR_DOMAIN_EVENT_SHUTDOWN_GUESTZVIR_DOMAIN_EVENT_SHUTDOWN_HOSTZVIR_DOMAIN_EVENT_STARTED_BOOTEDZ!VIR_DOMAIN_EVENT_STARTED_MIGRATEDZ!VIR_DOMAIN_EVENT_STARTED_RESTOREDZ&VIR_DOMAIN_EVENT_STARTED_FROM_SNAPSHOTZVIR_DOMAIN_EVENT_STARTED_WAKEUPZ"VIR_DOMAIN_EVENT_STARTED_RECREATEDZ!VIR_DOMAIN_EVENT_STOPPED_SHUTDOWNZ"VIR_DOMAIN_EVENT_STOPPED_DESTROYEDZ VIR_DOMAIN_EVENT_STOPPED_CRASHEDZ!VIR_DOMAIN_EVENT_STOPPED_MIGRATEDZVIR_DOMAIN_EVENT_STOPPED_SAVEDZVIR_DOMAIN_EVENT_STOPPED_FAILEDZ&VIR_DOMAIN_EVENT_STOPPED_FROM_SNAPSHOTZ"VIR_DOMAIN_EVENT_STOPPED_RECREATEDZ!VIR_DOMAIN_EVENT_SUSPENDED_PAUSEDZ#VIR_DOMAIN_EVENT_SUSPENDED_MIGRATEDZ"VIR_DOMAIN_EVENT_SUSPENDED_IOERRORZ#VIR_DOMAIN_EVENT_SUSPENDED_WATCHDOGZ#VIR_DOMAIN_EVENT_SUSPENDED_RESTOREDZ(VIR_DOMAIN_EVENT_SUSPENDED_FROM_SNAPSHOTZ$VIR_DOMAIN_EVENT_SUSPENDED_API_ERRORZ#VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPYZ*VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY_FAILEDZ)VIR_DOMAIN_EVENT_SUSPENDED_GUEST_SHUTDOWNZ!VIR_DOMAIN_EVENT_TRAY_CHANGE_OPENZ"VIR_DOMAIN_EVENT_TRAY_CHANGE_CLOSEZVIR_DOMAIN_EVENT_DEFINEDZVIR_DOMAIN_EVENT_UNDEFINEDZVIR_DOMAIN_EVENT_STARTEDZVIR_DOMAIN_EVENT_SUSPENDEDZVIR_DOMAIN_EVENT_RESUMEDZVIR_DOMAIN_EVENT_STOPPEDZVIR_DOMAIN_EVENT_SHUTDOWNZVIR_DOMAIN_EVENT_PMSUSPENDEDZVIR_DOMAIN_EVENT_CRASHEDZ"VIR_DOMAIN_EVENT_UNDEFINED_REMOVEDZ"VIR_DOMAIN_EVENT_UNDEFINED_RENAMEDZVIR_DOMAIN_EVENT_WATCHDOG_NONEZVIR_DOMAIN_EVENT_WATCHDOG_PAUSEZVIR_DOMAIN_EVENT_WATCHDOG_RESETZ"VIR_DOMAIN_EVENT_WATCHDOG_POWEROFFZ"VIR_DOMAIN_EVENT_WATCHDOG_SHUTDOWNZVIR_DOMAIN_EVENT_WATCHDOG_DEBUGZ#VIR_DOMAIN_EVENT_WATCHDOG_INJECTNMIZ(VIR_DOMAIN_FD_ASSOCIATE_SECLABEL_RESTOREZ)VIR_DOMAIN_FD_ASSOCIATE_SECLABEL_WRITABLEZVIR_DOMAIN_GET_HOSTNAME_LEASEZVIR_DOMAIN_GET_HOSTNAME_AGENTZVIR_DOMAIN_JOB_STATS_COMPLETEDZ#VIR_DOMAIN_JOB_STATS_KEEP_COMPLETEDZ#VIR_DOMAIN_GRAPHICS_RELOAD_TYPE_ANYZ#VIR_DOMAIN_GRAPHICS_RELOAD_TYPE_VNCZVIR_DOMAIN_GUEST_INFO_USERSZVIR_DOMAIN_GUEST_INFO_OSZVIR_DOMAIN_GUEST_INFO_TIMEZONEZVIR_DOMAIN_GUEST_INFO_HOSTNAMEZ VIR_DOMAIN_GUEST_INFO_FILESYSTEMZVIR_DOMAIN_GUEST_INFO_DISKSZ VIR_DOMAIN_GUEST_INFO_INTERFACESZVIR_DOMAIN_GUEST_INFO_LOADZ(VIR_DOMAIN_INTERFACE_ADDRESSES_SRC_LEASEZ(VIR_DOMAIN_INTERFACE_ADDRESSES_SRC_AGENTZ&VIR_DOMAIN_INTERFACE_ADDRESSES_SRC_ARPZ VIR_DOMAIN_JOB_OPERATION_UNKNOWNZVIR_DOMAIN_JOB_OPERATION_STARTZVIR_DOMAIN_JOB_OPERATION_SAVEZ VIR_DOMAIN_JOB_OPERATION_RESTOREZ%VIR_DOMAIN_JOB_OPERATION_MIGRATION_INZ&VIR_DOMAIN_JOB_OPERATION_MIGRATION_OUTZ!VIR_DOMAIN_JOB_OPERATION_SNAPSHOTZ(VIR_DOMAIN_JOB_OPERATION_SNAPSHOT_REVERTZVIR_DOMAIN_JOB_OPERATION_DUMPZVIR_DOMAIN_JOB_OPERATION_BACKUPZ(VIR_DOMAIN_JOB_OPERATION_SNAPSHOT_DELETEZVIR_DOMAIN_JOB_NONEZVIR_DOMAIN_JOB_BOUNDEDZVIR_DOMAIN_JOB_UNBOUNDEDZVIR_DOMAIN_JOB_COMPLETEDZVIR_DOMAIN_JOB_FAILEDZVIR_DOMAIN_JOB_CANCELLEDZVIR_DOMAIN_LIFECYCLE_POWEROFFZVIR_DOMAIN_LIFECYCLE_REBOOTZVIR_DOMAIN_LIFECYCLE_CRASHZ#VIR_DOMAIN_LIFECYCLE_ACTION_DESTROYZ#VIR_DOMAIN_LIFECYCLE_ACTION_RESTARTZ*VIR_DOMAIN_LIFECYCLE_ACTION_RESTART_RENAMEZ$VIR_DOMAIN_LIFECYCLE_ACTION_PRESERVEZ,VIR_DOMAIN_LIFECYCLE_ACTION_COREDUMP_DESTROYZ,VIR_DOMAIN_LIFECYCLE_ACTION_COREDUMP_RESTARTZ-VIR_DOMAIN_EVENT_MEMORY_FAILURE_ACTION_IGNOREZ-VIR_DOMAIN_EVENT_MEMORY_FAILURE_ACTION_INJECTZ,VIR_DOMAIN_EVENT_MEMORY_FAILURE_ACTION_FATALZ,VIR_DOMAIN_EVENT_MEMORY_FAILURE_ACTION_RESETZ)VIR_DOMAIN_MEMORY_FAILURE_ACTION_REQUIREDZ#VIR_DOMAIN_MEMORY_FAILURE_RECURSIVEZ4VIR_DOMAIN_EVENT_MEMORY_FAILURE_RECIPIENT_HYPERVISORZ/VIR_DOMAIN_EVENT_MEMORY_FAILURE_RECIPIENT_GUESTZVIR_MEMORY_VIRTUALZVIR_MEMORY_PHYSICALZVIR_DOMAIN_MEM_CURRENTZVIR_DOMAIN_MEM_LIVEZVIR_DOMAIN_MEM_CONFIGZVIR_DOMAIN_MEM_MAXIMUMZVIR_DOMAIN_MEMORY_STAT_SWAP_INZVIR_DOMAIN_MEMORY_STAT_SWAP_OUTZ"VIR_DOMAIN_MEMORY_STAT_MAJOR_FAULTZ"VIR_DOMAIN_MEMORY_STAT_MINOR_FAULTZVIR_DOMAIN_MEMORY_STAT_UNUSEDZ VIR_DOMAIN_MEMORY_STAT_AVAILABLEZ%VIR_DOMAIN_MEMORY_STAT_ACTUAL_BALLOONZVIR_DOMAIN_MEMORY_STAT_RSSZVIR_DOMAIN_MEMORY_STAT_USABLEZ"VIR_DOMAIN_MEMORY_STAT_LAST_UPDATEZ"VIR_DOMAIN_MEMORY_STAT_DISK_CACHESZ&VIR_DOMAIN_MEMORY_STAT_HUGETLB_PGALLOCZ%VIR_DOMAIN_MEMORY_STAT_HUGETLB_PGFAILZVIR_DOMAIN_MEMORY_STAT_LASTZVIR_DOMAIN_MEMORY_STAT_NRZVIR_DOMAIN_MESSAGE_DEPRECATIONZVIR_DOMAIN_MESSAGE_TAINTINGZVIR_DOMAIN_MESSAGE_IOERRORSZVIR_DOMAIN_METADATA_DESCRIPTIONZVIR_DOMAIN_METADATA_TITLEZVIR_DOMAIN_METADATA_ELEMENTZVIR_MIGRATE_LIVEZVIR_MIGRATE_PEER2PEERZVIR_MIGRATE_TUNNELLEDZVIR_MIGRATE_PERSIST_DESTZVIR_MIGRATE_UNDEFINE_SOURCEZVIR_MIGRATE_PAUSEDZVIR_MIGRATE_NON_SHARED_DISKZVIR_MIGRATE_NON_SHARED_INCZVIR_MIGRATE_CHANGE_PROTECTIONZVIR_MIGRATE_UNSAFEZVIR_MIGRATE_OFFLINEZVIR_MIGRATE_COMPRESSEDZVIR_MIGRATE_ABORT_ON_ERRORZVIR_MIGRATE_AUTO_CONVERGEZVIR_MIGRATE_RDMA_PIN_ALLZVIR_MIGRATE_POSTCOPYZVIR_MIGRATE_TLSZVIR_MIGRATE_PARALLELZ)VIR_MIGRATE_NON_SHARED_SYNCHRONOUS_WRITESZVIR_MIGRATE_POSTCOPY_RESUMEZVIR_MIGRATE_ZEROCOPYZ%VIR_DOMAIN_MIGRATE_MAX_SPEED_POSTCOPYZVIR_DOMAIN_AFFECT_CURRENTZVIR_DOMAIN_AFFECT_LIVEZVIR_DOMAIN_AFFECT_CONFIGZVIR_DOMAIN_NOSTATE_UNKNOWNZVIR_DOMAIN_NUMATUNE_MEM_STRICTZ!VIR_DOMAIN_NUMATUNE_MEM_PREFERREDZ"VIR_DOMAIN_NUMATUNE_MEM_INTERLEAVEZ#VIR_DOMAIN_NUMATUNE_MEM_RESTRICTIVEZ!VIR_DOMAIN_OPEN_GRAPHICS_SKIPAUTHZ#VIR_DOMAIN_PMSUSPENDED_DISK_UNKNOWNZVIR_DOMAIN_PMSUSPENDED_UNKNOWNZVIR_DOMAIN_PAUSED_UNKNOWNZVIR_DOMAIN_PAUSED_USERZVIR_DOMAIN_PAUSED_MIGRATIONZVIR_DOMAIN_PAUSED_SAVEZVIR_DOMAIN_PAUSED_DUMPZVIR_DOMAIN_PAUSED_IOERRORZVIR_DOMAIN_PAUSED_WATCHDOGZVIR_DOMAIN_PAUSED_FROM_SNAPSHOTZVIR_DOMAIN_PAUSED_SHUTTING_DOWNZVIR_DOMAIN_PAUSED_SNAPSHOTZVIR_DOMAIN_PAUSED_CRASHEDZVIR_DOMAIN_PAUSED_STARTING_UPZVIR_DOMAIN_PAUSED_POSTCOPYZ!VIR_DOMAIN_PAUSED_POSTCOPY_FAILEDZVIR_DOMAIN_PAUSED_API_ERRORZVIR_DOMAIN_PROCESS_SIGNAL_NOPZVIR_DOMAIN_PROCESS_SIGNAL_HUPZVIR_DOMAIN_PROCESS_SIGNAL_INTZVIR_DOMAIN_PROCESS_SIGNAL_QUITZVIR_DOMAIN_PROCESS_SIGNAL_ILLZVIR_DOMAIN_PROCESS_SIGNAL_TRAPZVIR_DOMAIN_PROCESS_SIGNAL_ABRTZVIR_DOMAIN_PROCESS_SIGNAL_BUSZVIR_DOMAIN_PROCESS_SIGNAL_FPEZVIR_DOMAIN_PROCESS_SIGNAL_KILLZVIR_DOMAIN_PROCESS_SIGNAL_USR1ZVIR_DOMAIN_PROCESS_SIGNAL_SEGVZVIR_DOMAIN_PROCESS_SIGNAL_USR2ZVIR_DOMAIN_PROCESS_SIGNAL_PIPEZVIR_DOMAIN_PROCESS_SIGNAL_ALRMZVIR_DOMAIN_PROCESS_SIGNAL_TERMZ VIR_DOMAIN_PROCESS_SIGNAL_STKFLTZVIR_DOMAIN_PROCESS_SIGNAL_CHLDZVIR_DOMAIN_PROCESS_SIGNAL_CONTZVIR_DOMAIN_PROCESS_SIGNAL_STOPZVIR_DOMAIN_PROCESS_SIGNAL_TSTPZVIR_DOMAIN_PROCESS_SIGNAL_TTINZVIR_DOMAIN_PROCESS_SIGNAL_TTOUZVIR_DOMAIN_PROCESS_SIGNAL_URGZVIR_DOMAIN_PROCESS_SIGNAL_XCPUZVIR_DOMAIN_PROCESS_SIGNAL_XFSZZ VIR_DOMAIN_PROCESS_SIGNAL_VTALRMZVIR_DOMAIN_PROCESS_SIGNAL_PROFZVIR_DOMAIN_PROCESS_SIGNAL_WINCHZVIR_DOMAIN_PROCESS_SIGNAL_POLLZVIR_DOMAIN_PROCESS_SIGNAL_PWRZVIR_DOMAIN_PROCESS_SIGNAL_SYSZVIR_DOMAIN_PROCESS_SIGNAL_RT0ZVIR_DOMAIN_PROCESS_SIGNAL_RT1ZVIR_DOMAIN_PROCESS_SIGNAL_RT2ZVIR_DOMAIN_PROCESS_SIGNAL_RT3ZVIR_DOMAIN_PROCESS_SIGNAL_RT4ZVIR_DOMAIN_PROCESS_SIGNAL_RT5ZVIR_DOMAIN_PROCESS_SIGNAL_RT6ZVIR_DOMAIN_PROCESS_SIGNAL_RT7ZVIR_DOMAIN_PROCESS_SIGNAL_RT8ZVIR_DOMAIN_PROCESS_SIGNAL_RT9ZVIR_DOMAIN_PROCESS_SIGNAL_RT10ZVIR_DOMAIN_PROCESS_SIGNAL_RT11ZVIR_DOMAIN_PROCESS_SIGNAL_RT12ZVIR_DOMAIN_PROCESS_SIGNAL_RT13ZVIR_DOMAIN_PROCESS_SIGNAL_RT14ZVIR_DOMAIN_PROCESS_SIGNAL_RT15ZVIR_DOMAIN_PROCESS_SIGNAL_RT16ZVIR_DOMAIN_PROCESS_SIGNAL_RT17ZVIR_DOMAIN_PROCESS_SIGNAL_RT18ZVIR_DOMAIN_PROCESS_SIGNAL_RT19ZVIR_DOMAIN_PROCESS_SIGNAL_RT20ZVIR_DOMAIN_PROCESS_SIGNAL_RT21ZVIR_DOMAIN_PROCESS_SIGNAL_RT22ZVIR_DOMAIN_PROCESS_SIGNAL_RT23ZVIR_DOMAIN_PROCESS_SIGNAL_RT24ZVIR_DOMAIN_PROCESS_SIGNAL_RT25ZVIR_DOMAIN_PROCESS_SIGNAL_RT26ZVIR_DOMAIN_PROCESS_SIGNAL_RT27ZVIR_DOMAIN_PROCESS_SIGNAL_RT28ZVIR_DOMAIN_PROCESS_SIGNAL_RT29ZVIR_DOMAIN_PROCESS_SIGNAL_RT30ZVIR_DOMAIN_PROCESS_SIGNAL_RT31ZVIR_DOMAIN_PROCESS_SIGNAL_RT32ZVIR_DOMAIN_REBOOT_DEFAULTZ VIR_DOMAIN_REBOOT_ACPI_POWER_BTNZVIR_DOMAIN_REBOOT_GUEST_AGENTZVIR_DOMAIN_REBOOT_INITCTLZVIR_DOMAIN_REBOOT_SIGNALZVIR_DOMAIN_REBOOT_PARAVIRTZVIR_DOMAIN_RUNNING_UNKNOWNZVIR_DOMAIN_RUNNING_BOOTEDZVIR_DOMAIN_RUNNING_MIGRATEDZVIR_DOMAIN_RUNNING_RESTOREDZ VIR_DOMAIN_RUNNING_FROM_SNAPSHOTZVIR_DOMAIN_RUNNING_UNPAUSEDZ%VIR_DOMAIN_RUNNING_MIGRATION_CANCELEDZ VIR_DOMAIN_RUNNING_SAVE_CANCELEDZVIR_DOMAIN_RUNNING_WAKEUPZVIR_DOMAIN_RUNNING_CRASHEDZVIR_DOMAIN_RUNNING_POSTCOPYZ"VIR_DOMAIN_RUNNING_POSTCOPY_FAILEDZ VIR_DOMAIN_SAVE_IMAGE_XML_SECUREZVIR_DOMAIN_SAVE_BYPASS_CACHEZVIR_DOMAIN_SAVE_RUNNINGZVIR_DOMAIN_SAVE_PAUSEDZVIR_DOMAIN_SAVE_RESET_NVRAMZVIR_DOMAIN_TIME_SYNCZVIR_DOMAIN_PASSWORD_ENCRYPTEDZVIR_DOMAIN_SHUTDOWN_DEFAULTZ"VIR_DOMAIN_SHUTDOWN_ACPI_POWER_BTNZVIR_DOMAIN_SHUTDOWN_GUEST_AGENTZVIR_DOMAIN_SHUTDOWN_INITCTLZVIR_DOMAIN_SHUTDOWN_SIGNALZVIR_DOMAIN_SHUTDOWN_PARAVIRTZVIR_DOMAIN_SHUTDOWN_UNKNOWNZVIR_DOMAIN_SHUTDOWN_USERZVIR_DOMAIN_SHUTOFF_UNKNOWNZVIR_DOMAIN_SHUTOFF_SHUTDOWNZVIR_DOMAIN_SHUTOFF_DESTROYEDZVIR_DOMAIN_SHUTOFF_CRASHEDZVIR_DOMAIN_SHUTOFF_MIGRATEDZVIR_DOMAIN_SHUTOFF_SAVEDZVIR_DOMAIN_SHUTOFF_FAILEDZ VIR_DOMAIN_SHUTOFF_FROM_SNAPSHOTZVIR_DOMAIN_SHUTOFF_DAEMONZ#VIR_DOMAIN_SNAPSHOT_CREATE_REDEFINEZ"VIR_DOMAIN_SNAPSHOT_CREATE_CURRENTZ&VIR_DOMAIN_SNAPSHOT_CREATE_NO_METADATAZVIR_DOMAIN_SNAPSHOT_CREATE_HALTZ$VIR_DOMAIN_SNAPSHOT_CREATE_DISK_ONLYZ$VIR_DOMAIN_SNAPSHOT_CREATE_REUSE_EXTZ"VIR_DOMAIN_SNAPSHOT_CREATE_QUIESCEZ!VIR_DOMAIN_SNAPSHOT_CREATE_ATOMICZVIR_DOMAIN_SNAPSHOT_CREATE_LIVEZ#VIR_DOMAIN_SNAPSHOT_CREATE_VALIDATEZ#VIR_DOMAIN_SNAPSHOT_DELETE_CHILDRENZ(VIR_DOMAIN_SNAPSHOT_DELETE_METADATA_ONLYZ(VIR_DOMAIN_SNAPSHOT_DELETE_CHILDREN_ONLYZ$VIR_DOMAIN_SNAPSHOT_LIST_DESCENDANTSZVIR_DOMAIN_SNAPSHOT_LIST_ROOTSZ!VIR_DOMAIN_SNAPSHOT_LIST_METADATAZVIR_DOMAIN_SNAPSHOT_LIST_LEAVESZ"VIR_DOMAIN_SNAPSHOT_LIST_NO_LEAVESZ$VIR_DOMAIN_SNAPSHOT_LIST_NO_METADATAZ!VIR_DOMAIN_SNAPSHOT_LIST_INACTIVEZVIR_DOMAIN_SNAPSHOT_LIST_ACTIVEZ"VIR_DOMAIN_SNAPSHOT_LIST_DISK_ONLYZ!VIR_DOMAIN_SNAPSHOT_LIST_INTERNALZ!VIR_DOMAIN_SNAPSHOT_LIST_EXTERNALZ$VIR_DOMAIN_SNAPSHOT_LIST_TOPOLOGICALZ"VIR_DOMAIN_SNAPSHOT_REVERT_RUNNINGZ!VIR_DOMAIN_SNAPSHOT_REVERT_PAUSEDZ VIR_DOMAIN_SNAPSHOT_REVERT_FORCEZ&VIR_DOMAIN_SNAPSHOT_REVERT_RESET_NVRAMZVIR_DOMAIN_SNAPSHOT_XML_SECUREZVIR_DOMAIN_NOSTATEZVIR_DOMAIN_RUNNINGZVIR_DOMAIN_BLOCKEDZVIR_DOMAIN_PAUSEDZVIR_DOMAIN_SHUTDOWNZVIR_DOMAIN_SHUTOFFZVIR_DOMAIN_CRASHEDZVIR_DOMAIN_PMSUSPENDEDZVIR_DOMAIN_STATS_STATEZVIR_DOMAIN_STATS_CPU_TOTALZVIR_DOMAIN_STATS_BALLOONZVIR_DOMAIN_STATS_VCPUZVIR_DOMAIN_STATS_INTERFACEZVIR_DOMAIN_STATS_BLOCKZVIR_DOMAIN_STATS_PERFZVIR_DOMAIN_STATS_IOTHREADZVIR_DOMAIN_STATS_MEMORYZVIR_DOMAIN_STATS_DIRTYRATEZVIR_DOMAIN_STATS_VMZ VIR_DOMAIN_UNDEFINE_MANAGED_SAVEZ&VIR_DOMAIN_UNDEFINE_SNAPSHOTS_METADATAZVIR_DOMAIN_UNDEFINE_NVRAMZVIR_DOMAIN_UNDEFINE_KEEP_NVRAMZ(VIR_DOMAIN_UNDEFINE_CHECKPOINTS_METADATAZVIR_DOMAIN_UNDEFINE_TPMZVIR_DOMAIN_UNDEFINE_KEEP_TPMZVIR_DOMAIN_VCPU_CURRENTZVIR_DOMAIN_VCPU_LIVEZVIR_DOMAIN_VCPU_CONFIGZVIR_DOMAIN_VCPU_MAXIMUMZVIR_DOMAIN_VCPU_GUESTZVIR_DOMAIN_VCPU_HOTPLUGGABLEZVIR_DOMAIN_XML_SECUREZVIR_DOMAIN_XML_INACTIVEZVIR_DOMAIN_XML_UPDATE_CPUZVIR_DOMAIN_XML_MIGRATABLEZ VIR_FROM_NONEZ VIR_FROM_XENZ VIR_FROM_XENDZVIR_FROM_XENSTOREZVIR_FROM_SEXPRZ VIR_FROM_XMLZ VIR_FROM_DOMZ VIR_FROM_RPCZVIR_FROM_PROXYZ VIR_FROM_CONFZ VIR_FROM_QEMUZ VIR_FROM_NETZ VIR_FROM_TESTZVIR_FROM_REMOTEZVIR_FROM_OPENVZZVIR_FROM_XENXMZVIR_FROM_STATS_LINUXZ VIR_FROM_LXCZVIR_FROM_STORAGEZVIR_FROM_NETWORKZVIR_FROM_DOMAINZ VIR_FROM_UMLZVIR_FROM_NODEDEVZVIR_FROM_XEN_INOTIFYZVIR_FROM_SECURITYZ VIR_FROM_VBOXZVIR_FROM_INTERFACEZ VIR_FROM_ONEZ VIR_FROM_ESXZ VIR_FROM_PHYPZVIR_FROM_SECRETZ VIR_FROM_CPUZVIR_FROM_XENAPIZVIR_FROM_NWFILTERZ VIR_FROM_HOOKZVIR_FROM_DOMAIN_SNAPSHOTZVIR_FROM_AUDITZVIR_FROM_SYSINFOZVIR_FROM_STREAMSZVIR_FROM_VMWAREZVIR_FROM_EVENTZVIR_FROM_LIBXLZVIR_FROM_LOCKINGZVIR_FROM_HYPERVZVIR_FROM_CAPABILITIESZ VIR_FROM_URIZ VIR_FROM_AUTHZ VIR_FROM_DBUSZVIR_FROM_PARALLELSZVIR_FROM_DEVICEZ VIR_FROM_SSHZVIR_FROM_LOCKSPACEZVIR_FROM_INITCTLZVIR_FROM_IDENTITYZVIR_FROM_CGROUPZVIR_FROM_ACCESSZVIR_FROM_SYSTEMDZVIR_FROM_BHYVEZVIR_FROM_CRYPTOZVIR_FROM_FIREWALLZVIR_FROM_POLKITZVIR_FROM_THREADZVIR_FROM_ADMINZVIR_FROM_LOGGINGZVIR_FROM_XENXLZ VIR_FROM_PERFZVIR_FROM_LIBSSHZVIR_FROM_RESCTRLZVIR_FROM_FIREWALLDZVIR_FROM_DOMAIN_CHECKPOINTZ VIR_FROM_TPMZ VIR_FROM_BPFZ VIR_FROM_CHZ VIR_ERR_NONEZVIR_ERR_WARNINGZ VIR_ERR_ERRORZ VIR_ERR_OKZVIR_ERR_INTERNAL_ERRORZVIR_ERR_NO_MEMORYZVIR_ERR_NO_SUPPORTZVIR_ERR_UNKNOWN_HOSTZVIR_ERR_NO_CONNECTZVIR_ERR_INVALID_CONNZVIR_ERR_INVALID_DOMAINZVIR_ERR_INVALID_ARGZVIR_ERR_OPERATION_FAILEDZVIR_ERR_GET_FAILEDZVIR_ERR_POST_FAILEDZVIR_ERR_HTTP_ERRORZVIR_ERR_SEXPR_SERIALZVIR_ERR_NO_XENZVIR_ERR_XEN_CALLZVIR_ERR_OS_TYPEZVIR_ERR_NO_KERNELZVIR_ERR_NO_ROOTZVIR_ERR_NO_SOURCEZVIR_ERR_NO_TARGETZVIR_ERR_NO_NAMEZ VIR_ERR_NO_OSZVIR_ERR_NO_DEVICEZVIR_ERR_NO_XENSTOREZVIR_ERR_DRIVER_FULLZVIR_ERR_CALL_FAILEDZVIR_ERR_XML_ERRORZVIR_ERR_DOM_EXISTZVIR_ERR_OPERATION_DENIEDZVIR_ERR_OPEN_FAILEDZVIR_ERR_READ_FAILEDZVIR_ERR_PARSE_FAILEDZVIR_ERR_CONF_SYNTAXZVIR_ERR_WRITE_FAILEDZVIR_ERR_XML_DETAILZVIR_ERR_INVALID_NETWORKZVIR_ERR_NETWORK_EXISTZVIR_ERR_SYSTEM_ERRORZ VIR_ERR_RPCZVIR_ERR_GNUTLS_ERRORZVIR_WAR_NO_NETWORKZVIR_ERR_NO_DOMAINZVIR_ERR_NO_NETWORKZVIR_ERR_INVALID_MACZVIR_ERR_AUTH_FAILEDZVIR_ERR_INVALID_STORAGE_POOLZVIR_ERR_INVALID_STORAGE_VOLZVIR_WAR_NO_STORAGEZVIR_ERR_NO_STORAGE_POOLZVIR_ERR_NO_STORAGE_VOLZVIR_WAR_NO_NODEZVIR_ERR_INVALID_NODE_DEVICEZVIR_ERR_NO_NODE_DEVICEZVIR_ERR_NO_SECURITY_MODELZVIR_ERR_OPERATION_INVALIDZVIR_WAR_NO_INTERFACEZVIR_ERR_NO_INTERFACEZVIR_ERR_INVALID_INTERFACEZVIR_ERR_MULTIPLE_INTERFACESZVIR_WAR_NO_NWFILTERZVIR_ERR_INVALID_NWFILTERZVIR_ERR_NO_NWFILTERZVIR_ERR_BUILD_FIREWALLZVIR_WAR_NO_SECRETZVIR_ERR_INVALID_SECRETZVIR_ERR_NO_SECRETZVIR_ERR_CONFIG_UNSUPPORTEDZVIR_ERR_OPERATION_TIMEOUTZVIR_ERR_MIGRATE_PERSIST_FAILEDZVIR_ERR_HOOK_SCRIPT_FAILEDZVIR_ERR_INVALID_DOMAIN_SNAPSHOTZVIR_ERR_NO_DOMAIN_SNAPSHOTZVIR_ERR_INVALID_STREAMZVIR_ERR_ARGUMENT_UNSUPPORTEDZVIR_ERR_STORAGE_PROBE_FAILEDZVIR_ERR_STORAGE_POOL_BUILTZVIR_ERR_SNAPSHOT_REVERT_RISKYZVIR_ERR_OPERATION_ABORTEDZVIR_ERR_AUTH_CANCELLEDZVIR_ERR_NO_DOMAIN_METADATAZVIR_ERR_MIGRATE_UNSAFEZVIR_ERR_OVERFLOWZVIR_ERR_BLOCK_COPY_ACTIVEZVIR_ERR_OPERATION_UNSUPPORTEDZ VIR_ERR_SSHZVIR_ERR_AGENT_UNRESPONSIVEZVIR_ERR_RESOURCE_BUSYZVIR_ERR_ACCESS_DENIEDZVIR_ERR_DBUS_SERVICEZVIR_ERR_STORAGE_VOL_EXISTZVIR_ERR_CPU_INCOMPATIBLEZVIR_ERR_XML_INVALID_SCHEMAZVIR_ERR_MIGRATE_FINISH_OKZVIR_ERR_AUTH_UNAVAILABLEZVIR_ERR_NO_SERVERZVIR_ERR_NO_CLIENTZVIR_ERR_AGENT_UNSYNCEDZVIR_ERR_LIBSSHZVIR_ERR_DEVICE_MISSINGZ VIR_ERR_INVALID_NWFILTER_BINDINGZVIR_ERR_NO_NWFILTER_BINDINGZ!VIR_ERR_INVALID_DOMAIN_CHECKPOINTZVIR_ERR_NO_DOMAIN_CHECKPOINTZVIR_ERR_NO_DOMAIN_BACKUPZVIR_ERR_INVALID_NETWORK_PORTZVIR_ERR_NETWORK_PORT_EXISTZVIR_ERR_NO_NETWORK_PORTZVIR_ERR_NO_HOSTNAMEZVIR_ERR_CHECKPOINT_INCONSISTENTZVIR_ERR_MULTIPLE_DOMAINSZVIR_ERR_NO_NETWORK_METADATAZVIR_ERR_AGENT_COMMAND_TIMEOUTZVIR_ERR_AGENT_COMMAND_FAILEDZVIR_EVENT_HANDLE_READABLEZVIR_EVENT_HANDLE_WRITABLEZVIR_EVENT_HANDLE_ERRORZVIR_EVENT_HANDLE_HANGUPZVIR_IP_ADDR_TYPE_IPV4ZVIR_IP_ADDR_TYPE_IPV6ZVIR_INTERFACE_DEFINE_VALIDATEZVIR_INTERFACE_XML_INACTIVEZVIR_KEYCODE_SET_LINUXZVIR_KEYCODE_SET_XTZVIR_KEYCODE_SET_ATSET1ZVIR_KEYCODE_SET_ATSET2ZVIR_KEYCODE_SET_ATSET3ZVIR_KEYCODE_SET_OSXZVIR_KEYCODE_SET_XT_KBDZVIR_KEYCODE_SET_USBZVIR_KEYCODE_SET_WIN32ZVIR_KEYCODE_SET_QNUMZVIR_DOMAIN_MEMORY_PARAM_INTZVIR_DOMAIN_MEMORY_PARAM_UINTZVIR_DOMAIN_MEMORY_PARAM_LLONGZVIR_DOMAIN_MEMORY_PARAM_ULLONGZVIR_DOMAIN_MEMORY_PARAM_DOUBLEZVIR_DOMAIN_MEMORY_PARAM_BOOLEANZ$VIR_NWFILTER_BINDING_CREATE_VALIDATEZVIR_NWFILTER_DEFINE_VALIDATEZVIR_NETWORK_CREATE_VALIDATEZVIR_NETWORK_DEFINE_VALIDATEZVIR_NETWORK_EVENT_ID_LIFECYCLEZ$VIR_NETWORK_EVENT_ID_METADATA_CHANGEZVIR_NETWORK_EVENT_DEFINEDZVIR_NETWORK_EVENT_UNDEFINEDZVIR_NETWORK_EVENT_STARTEDZVIR_NETWORK_EVENT_STOPPEDZ VIR_NETWORK_METADATA_DESCRIPTIONZVIR_NETWORK_METADATA_TITLEZVIR_NETWORK_METADATA_ELEMENTZVIR_NETWORK_PORT_CREATE_RECLAIMZ VIR_NETWORK_PORT_CREATE_VALIDATEZVIR_NETWORK_UPDATE_COMMAND_NONEZ!VIR_NETWORK_UPDATE_COMMAND_MODIFYZ!VIR_NETWORK_UPDATE_COMMAND_DELETEZ#VIR_NETWORK_UPDATE_COMMAND_ADD_LASTZ$VIR_NETWORK_UPDATE_COMMAND_ADD_FIRSTZ!VIR_NETWORK_UPDATE_AFFECT_CURRENTZVIR_NETWORK_UPDATE_AFFECT_LIVEZ VIR_NETWORK_UPDATE_AFFECT_CONFIGZVIR_NETWORK_SECTION_NONEZVIR_NETWORK_SECTION_BRIDGEZVIR_NETWORK_SECTION_DOMAINZVIR_NETWORK_SECTION_IPZ VIR_NETWORK_SECTION_IP_DHCP_HOSTZ!VIR_NETWORK_SECTION_IP_DHCP_RANGEZVIR_NETWORK_SECTION_FORWARDZ%VIR_NETWORK_SECTION_FORWARD_INTERFACEZVIR_NETWORK_SECTION_FORWARD_PFZVIR_NETWORK_SECTION_PORTGROUPZVIR_NETWORK_SECTION_DNS_HOSTZVIR_NETWORK_SECTION_DNS_TXTZVIR_NETWORK_SECTION_DNS_SRVZVIR_NETWORK_XML_INACTIVEZVIR_NODE_ALLOC_PAGES_ADDZVIR_NODE_ALLOC_PAGES_SETZ#VIR_NODE_DEVICE_CREATE_XML_VALIDATEZ#VIR_NODE_DEVICE_DEFINE_XML_VALIDATEZ"VIR_NODE_DEVICE_EVENT_ID_LIFECYCLEZVIR_NODE_DEVICE_EVENT_ID_UPDATEZVIR_NODE_DEVICE_EVENT_CREATEDZVIR_NODE_DEVICE_EVENT_DELETEDZVIR_NODE_DEVICE_EVENT_DEFINEDZVIR_NODE_DEVICE_EVENT_UNDEFINEDZ%VIR_NODE_DEVICE_UPDATE_AFFECT_CURRENTZ"VIR_NODE_DEVICE_UPDATE_AFFECT_LIVEZ$VIR_NODE_DEVICE_UPDATE_AFFECT_CONFIGZVIR_NODE_DEVICE_XML_INACTIVEZVIR_NODE_CPU_STATS_ALL_CPUSZVIR_NODE_MEMORY_STATS_ALL_CELLSZVIR_NODE_SUSPEND_TARGET_MEMZVIR_NODE_SUSPEND_TARGET_DISKZVIR_NODE_SUSPEND_TARGET_HYBRIDZVIR_DOMAIN_SCHED_FIELD_INTZVIR_DOMAIN_SCHED_FIELD_UINTZVIR_DOMAIN_SCHED_FIELD_LLONGZVIR_DOMAIN_SCHED_FIELD_ULLONGZVIR_DOMAIN_SCHED_FIELD_DOUBLEZVIR_DOMAIN_SCHED_FIELD_BOOLEANZVIR_SECRET_DEFINE_VALIDATEZVIR_SECRET_EVENT_ID_LIFECYCLEZ!VIR_SECRET_EVENT_ID_VALUE_CHANGEDZVIR_SECRET_EVENT_DEFINEDZVIR_SECRET_EVENT_UNDEFINEDZVIR_SECRET_USAGE_TYPE_NONEZVIR_SECRET_USAGE_TYPE_VOLUMEZVIR_SECRET_USAGE_TYPE_CEPHZVIR_SECRET_USAGE_TYPE_ISCSIZVIR_SECRET_USAGE_TYPE_TLSZVIR_SECRET_USAGE_TYPE_VTPMZVIR_STORAGE_POOL_BUILD_NEWZVIR_STORAGE_POOL_BUILD_REPAIRZVIR_STORAGE_POOL_BUILD_RESIZEZ#VIR_STORAGE_POOL_BUILD_NO_OVERWRITEZ VIR_STORAGE_POOL_BUILD_OVERWRITEZVIR_STORAGE_POOL_CREATE_NORMALZ"VIR_STORAGE_POOL_CREATE_WITH_BUILDZ,VIR_STORAGE_POOL_CREATE_WITH_BUILD_OVERWRITEZ/VIR_STORAGE_POOL_CREATE_WITH_BUILD_NO_OVERWRITEZ VIR_STORAGE_POOL_DEFINE_VALIDATEZVIR_STORAGE_POOL_DELETE_NORMALZVIR_STORAGE_POOL_DELETE_ZEROEDZ#VIR_STORAGE_POOL_EVENT_ID_LIFECYCLEZ!VIR_STORAGE_POOL_EVENT_ID_REFRESHZVIR_STORAGE_POOL_EVENT_DEFINEDZ VIR_STORAGE_POOL_EVENT_UNDEFINEDZVIR_STORAGE_POOL_EVENT_STARTEDZVIR_STORAGE_POOL_EVENT_STOPPEDZVIR_STORAGE_POOL_EVENT_CREATEDZVIR_STORAGE_POOL_EVENT_DELETEDZVIR_STORAGE_POOL_INACTIVEZVIR_STORAGE_POOL_BUILDINGZVIR_STORAGE_POOL_RUNNINGZVIR_STORAGE_POOL_DEGRADEDZVIR_STORAGE_POOL_INACCESSIBLEZ(VIR_STORAGE_VOL_CREATE_PREALLOC_METADATAZVIR_STORAGE_VOL_CREATE_REFLINKZVIR_STORAGE_VOL_CREATE_VALIDATEZVIR_STORAGE_VOL_DELETE_NORMALZVIR_STORAGE_VOL_DELETE_ZEROEDZ%VIR_STORAGE_VOL_DELETE_WITH_SNAPSHOTSZ&VIR_STORAGE_VOL_DOWNLOAD_SPARSE_STREAMZVIR_STORAGE_VOL_USE_ALLOCATIONZVIR_STORAGE_VOL_GET_PHYSICALZVIR_STORAGE_VOL_RESIZE_ALLOCATEZVIR_STORAGE_VOL_RESIZE_DELTAZVIR_STORAGE_VOL_RESIZE_SHRINKZVIR_STORAGE_VOL_FILEZVIR_STORAGE_VOL_BLOCKZVIR_STORAGE_VOL_DIRZVIR_STORAGE_VOL_NETWORKZVIR_STORAGE_VOL_NETDIRZVIR_STORAGE_VOL_PLOOPZ$VIR_STORAGE_VOL_UPLOAD_SPARSE_STREAMZVIR_STORAGE_VOL_WIPE_ALG_ZEROZVIR_STORAGE_VOL_WIPE_ALG_NNSAZVIR_STORAGE_VOL_WIPE_ALG_DODZVIR_STORAGE_VOL_WIPE_ALG_BSIZ VIR_STORAGE_VOL_WIPE_ALG_GUTMANNZ!VIR_STORAGE_VOL_WIPE_ALG_SCHNEIERZ"VIR_STORAGE_VOL_WIPE_ALG_PFITZNER7Z#VIR_STORAGE_VOL_WIPE_ALG_PFITZNER33ZVIR_STORAGE_VOL_WIPE_ALG_RANDOMZVIR_STORAGE_VOL_WIPE_ALG_TRIMZVIR_STORAGE_XML_INACTIVEZVIR_STREAM_EVENT_READABLEZVIR_STREAM_EVENT_WRITABLEZVIR_STREAM_EVENT_ERRORZVIR_STREAM_EVENT_HANGUPZVIR_STREAM_NONBLOCKrZVIR_TYPED_PARAM_STRING_OKAYZVIR_TYPED_PARAM_INTZVIR_TYPED_PARAM_UINTZVIR_TYPED_PARAM_LLONGZVIR_TYPED_PARAM_ULLONGZVIR_TYPED_PARAM_DOUBLEZVIR_TYPED_PARAM_BOOLEANZVIR_TYPED_PARAM_STRINGZVIR_VCPU_INFO_CPU_UNAVAILABLEZVIR_VCPU_INFO_CPU_OFFLINEZVIR_VCPU_OFFLINEZVIR_VCPU_RUNNINGZVIR_VCPU_BLOCKEDZVIR_CONNECT_IDENTITY_GROUP_NAMEZVIR_CONNECT_IDENTITY_PROCESS_IDZ!VIR_CONNECT_IDENTITY_PROCESS_TIMEZ#VIR_CONNECT_IDENTITY_SASL_USER_NAMEZ$VIR_CONNECT_IDENTITY_SELINUX_CONTEXTZ"VIR_CONNECT_IDENTITY_UNIX_GROUP_IDZ!VIR_CONNECT_IDENTITY_UNIX_USER_IDZVIR_CONNECT_IDENTITY_USER_NAMEZ,VIR_CONNECT_IDENTITY_X509_DISTINGUISHED_NAMEZVIR_DOMAIN_BANDWIDTH_IN_AVERAGEZVIR_DOMAIN_BANDWIDTH_IN_BURSTZVIR_DOMAIN_BANDWIDTH_IN_FLOORZVIR_DOMAIN_BANDWIDTH_IN_PEAKZ VIR_DOMAIN_BANDWIDTH_OUT_AVERAGEZVIR_DOMAIN_BANDWIDTH_OUT_BURSTZVIR_DOMAIN_BANDWIDTH_OUT_PEAKZ VIR_DOMAIN_BLKIO_DEVICE_READ_BPSZ!VIR_DOMAIN_BLKIO_DEVICE_READ_IOPSZVIR_DOMAIN_BLKIO_DEVICE_WEIGHTZ!VIR_DOMAIN_BLKIO_DEVICE_WRITE_BPSZ"VIR_DOMAIN_BLKIO_DEVICE_WRITE_IOPSZVIR_DOMAIN_BLKIO_WEIGHTZVIR_DOMAIN_BLOCK_COPY_BANDWIDTHZVIR_DOMAIN_BLOCK_COPY_BUF_SIZEZ!VIR_DOMAIN_BLOCK_COPY_GRANULARITYZ"VIR_DOMAIN_BLOCK_IOTUNE_GROUP_NAMEZ&VIR_DOMAIN_BLOCK_IOTUNE_READ_BYTES_SECZ*VIR_DOMAIN_BLOCK_IOTUNE_READ_BYTES_SEC_MAXZ1VIR_DOMAIN_BLOCK_IOTUNE_READ_BYTES_SEC_MAX_LENGTHZ%VIR_DOMAIN_BLOCK_IOTUNE_READ_IOPS_SECZ)VIR_DOMAIN_BLOCK_IOTUNE_READ_IOPS_SEC_MAXZ0VIR_DOMAIN_BLOCK_IOTUNE_READ_IOPS_SEC_MAX_LENGTHZ%VIR_DOMAIN_BLOCK_IOTUNE_SIZE_IOPS_SECZ'VIR_DOMAIN_BLOCK_IOTUNE_TOTAL_BYTES_SECZ+VIR_DOMAIN_BLOCK_IOTUNE_TOTAL_BYTES_SEC_MAXZ2VIR_DOMAIN_BLOCK_IOTUNE_TOTAL_BYTES_SEC_MAX_LENGTHZ&VIR_DOMAIN_BLOCK_IOTUNE_TOTAL_IOPS_SECZ*VIR_DOMAIN_BLOCK_IOTUNE_TOTAL_IOPS_SEC_MAXZ1VIR_DOMAIN_BLOCK_IOTUNE_TOTAL_IOPS_SEC_MAX_LENGTHZ'VIR_DOMAIN_BLOCK_IOTUNE_WRITE_BYTES_SECZ+VIR_DOMAIN_BLOCK_IOTUNE_WRITE_BYTES_SEC_MAXZ2VIR_DOMAIN_BLOCK_IOTUNE_WRITE_BYTES_SEC_MAX_LENGTHZ&VIR_DOMAIN_BLOCK_IOTUNE_WRITE_IOPS_SECZ*VIR_DOMAIN_BLOCK_IOTUNE_WRITE_IOPS_SEC_MAXZ1VIR_DOMAIN_BLOCK_IOTUNE_WRITE_IOPS_SEC_MAX_LENGTHZVIR_DOMAIN_BLOCK_STATS_ERRSZ VIR_DOMAIN_BLOCK_STATS_FLUSH_REQZ(VIR_DOMAIN_BLOCK_STATS_FLUSH_TOTAL_TIMESZ!VIR_DOMAIN_BLOCK_STATS_READ_BYTESZVIR_DOMAIN_BLOCK_STATS_READ_REQZ'VIR_DOMAIN_BLOCK_STATS_READ_TOTAL_TIMESZ"VIR_DOMAIN_BLOCK_STATS_WRITE_BYTESZ VIR_DOMAIN_BLOCK_STATS_WRITE_REQZ(VIR_DOMAIN_BLOCK_STATS_WRITE_TOTAL_TIMESZVIR_DOMAIN_CPU_STATS_CPUTIMEZVIR_DOMAIN_CPU_STATS_SYSTEMTIMEZVIR_DOMAIN_CPU_STATS_USERTIMEZVIR_DOMAIN_CPU_STATS_VCPUTIMEZ VIR_DOMAIN_GUEST_INFO_DISK_COUNTZ!VIR_DOMAIN_GUEST_INFO_DISK_PREFIXZ'VIR_DOMAIN_GUEST_INFO_DISK_SUFFIX_ALIASZ2VIR_DOMAIN_GUEST_INFO_DISK_SUFFIX_DEPENDENCY_COUNTZ3VIR_DOMAIN_GUEST_INFO_DISK_SUFFIX_DEPENDENCY_PREFIXZ8VIR_DOMAIN_GUEST_INFO_DISK_SUFFIX_DEPENDENCY_SUFFIX_NAMEZ-VIR_DOMAIN_GUEST_INFO_DISK_SUFFIX_GUEST_ALIASZ+VIR_DOMAIN_GUEST_INFO_DISK_SUFFIX_GUEST_BUSZ&VIR_DOMAIN_GUEST_INFO_DISK_SUFFIX_NAMEZ+VIR_DOMAIN_GUEST_INFO_DISK_SUFFIX_PARTITIONZ(VIR_DOMAIN_GUEST_INFO_DISK_SUFFIX_SERIALZVIR_DOMAIN_GUEST_INFO_FS_COUNTZVIR_DOMAIN_GUEST_INFO_FS_PREFIXZ*VIR_DOMAIN_GUEST_INFO_FS_SUFFIX_DISK_COUNTZ+VIR_DOMAIN_GUEST_INFO_FS_SUFFIX_DISK_PREFIXZ1VIR_DOMAIN_GUEST_INFO_FS_SUFFIX_DISK_SUFFIX_ALIASZ2VIR_DOMAIN_GUEST_INFO_FS_SUFFIX_DISK_SUFFIX_DEVICEZ2VIR_DOMAIN_GUEST_INFO_FS_SUFFIX_DISK_SUFFIX_SERIALZ&VIR_DOMAIN_GUEST_INFO_FS_SUFFIX_FSTYPEZ*VIR_DOMAIN_GUEST_INFO_FS_SUFFIX_MOUNTPOINTZ$VIR_DOMAIN_GUEST_INFO_FS_SUFFIX_NAMEZ+VIR_DOMAIN_GUEST_INFO_FS_SUFFIX_TOTAL_BYTESZ*VIR_DOMAIN_GUEST_INFO_FS_SUFFIX_USED_BYTESZ'VIR_DOMAIN_GUEST_INFO_HOSTNAME_HOSTNAMEZVIR_DOMAIN_GUEST_INFO_IF_COUNTZVIR_DOMAIN_GUEST_INFO_IF_PREFIXZ*VIR_DOMAIN_GUEST_INFO_IF_SUFFIX_ADDR_COUNTZ+VIR_DOMAIN_GUEST_INFO_IF_SUFFIX_ADDR_PREFIXZ0VIR_DOMAIN_GUEST_INFO_IF_SUFFIX_ADDR_SUFFIX_ADDRZ2VIR_DOMAIN_GUEST_INFO_IF_SUFFIX_ADDR_SUFFIX_PREFIXZ0VIR_DOMAIN_GUEST_INFO_IF_SUFFIX_ADDR_SUFFIX_TYPEZ&VIR_DOMAIN_GUEST_INFO_IF_SUFFIX_HWADDRZ$VIR_DOMAIN_GUEST_INFO_IF_SUFFIX_NAMEZVIR_DOMAIN_GUEST_INFO_LOAD_15MZVIR_DOMAIN_GUEST_INFO_LOAD_1MZVIR_DOMAIN_GUEST_INFO_LOAD_5MZVIR_DOMAIN_GUEST_INFO_OS_IDZ'VIR_DOMAIN_GUEST_INFO_OS_KERNEL_RELEASEZ'VIR_DOMAIN_GUEST_INFO_OS_KERNEL_VERSIONZ VIR_DOMAIN_GUEST_INFO_OS_MACHINEZVIR_DOMAIN_GUEST_INFO_OS_NAMEZ$VIR_DOMAIN_GUEST_INFO_OS_PRETTY_NAMEZ VIR_DOMAIN_GUEST_INFO_OS_VARIANTZ#VIR_DOMAIN_GUEST_INFO_OS_VARIANT_IDZ VIR_DOMAIN_GUEST_INFO_OS_VERSIONZ#VIR_DOMAIN_GUEST_INFO_OS_VERSION_IDZ#VIR_DOMAIN_GUEST_INFO_TIMEZONE_NAMEZ%VIR_DOMAIN_GUEST_INFO_TIMEZONE_OFFSETZ VIR_DOMAIN_GUEST_INFO_USER_COUNTZ!VIR_DOMAIN_GUEST_INFO_USER_PREFIXZ(VIR_DOMAIN_GUEST_INFO_USER_SUFFIX_DOMAINZ,VIR_DOMAIN_GUEST_INFO_USER_SUFFIX_LOGIN_TIMEZ&VIR_DOMAIN_GUEST_INFO_USER_SUFFIX_NAMEZVIR_DOMAIN_IOTHREAD_POLL_GROWZVIR_DOMAIN_IOTHREAD_POLL_MAX_NSZVIR_DOMAIN_IOTHREAD_POLL_SHRINKZ#VIR_DOMAIN_IOTHREAD_THREAD_POOL_MAXZ#VIR_DOMAIN_IOTHREAD_THREAD_POOL_MINZ%VIR_DOMAIN_JOB_AUTO_CONVERGE_THROTTLEZ VIR_DOMAIN_JOB_COMPRESSION_BYTESZ VIR_DOMAIN_JOB_COMPRESSION_CACHEZ'VIR_DOMAIN_JOB_COMPRESSION_CACHE_MISSESZ#VIR_DOMAIN_JOB_COMPRESSION_OVERFLOWZ VIR_DOMAIN_JOB_COMPRESSION_PAGESZVIR_DOMAIN_JOB_DATA_PROCESSEDZVIR_DOMAIN_JOB_DATA_REMAININGZVIR_DOMAIN_JOB_DATA_TOTALZVIR_DOMAIN_JOB_DISK_BPSZVIR_DOMAIN_JOB_DISK_PROCESSEDZVIR_DOMAIN_JOB_DISK_REMAININGZVIR_DOMAIN_JOB_DISK_TEMP_TOTALZVIR_DOMAIN_JOB_DISK_TEMP_USEDZVIR_DOMAIN_JOB_DISK_TOTALZVIR_DOMAIN_JOB_DOWNTIMEZVIR_DOMAIN_JOB_DOWNTIME_NETZVIR_DOMAIN_JOB_ERRMSGZVIR_DOMAIN_JOB_MEMORY_BPSZVIR_DOMAIN_JOB_MEMORY_CONSTANTZ VIR_DOMAIN_JOB_MEMORY_DIRTY_RATEZVIR_DOMAIN_JOB_MEMORY_ITERATIONZVIR_DOMAIN_JOB_MEMORY_NORMALZ"VIR_DOMAIN_JOB_MEMORY_NORMAL_BYTESZVIR_DOMAIN_JOB_MEMORY_PAGE_SIZEZ#VIR_DOMAIN_JOB_MEMORY_POSTCOPY_REQSZVIR_DOMAIN_JOB_MEMORY_PROCESSEDZVIR_DOMAIN_JOB_MEMORY_REMAININGZVIR_DOMAIN_JOB_MEMORY_TOTALZVIR_DOMAIN_JOB_OPERATIONZVIR_DOMAIN_JOB_SETUP_TIMEZVIR_DOMAIN_JOB_SUCCESSZVIR_DOMAIN_JOB_TIME_ELAPSEDZVIR_DOMAIN_JOB_TIME_ELAPSED_NETZVIR_DOMAIN_JOB_TIME_REMAININGZ$VIR_DOMAIN_JOB_VFIO_DATA_TRANSFERREDZ(VIR_DOMAIN_LAUNCH_SECURITY_SEV_API_MAJORZ(VIR_DOMAIN_LAUNCH_SECURITY_SEV_API_MINORZ'VIR_DOMAIN_LAUNCH_SECURITY_SEV_BUILD_IDZ*VIR_DOMAIN_LAUNCH_SECURITY_SEV_MEASUREMENTZ%VIR_DOMAIN_LAUNCH_SECURITY_SEV_POLICYZ%VIR_DOMAIN_LAUNCH_SECURITY_SEV_SECRETZ,VIR_DOMAIN_LAUNCH_SECURITY_SEV_SECRET_HEADERZ1VIR_DOMAIN_LAUNCH_SECURITY_SEV_SECRET_SET_ADDRESSZ)VIR_DOMAIN_LAUNCH_SECURITY_SEV_SNP_POLICYZVIR_DOMAIN_MEMORY_HARD_LIMITZVIR_DOMAIN_MEMORY_MIN_GUARANTEEZVIR_DOMAIN_MEMORY_SOFT_LIMITZ!VIR_DOMAIN_MEMORY_SWAP_HARD_LIMITZVIR_DOMAIN_NUMA_MODEZVIR_DOMAIN_NUMA_NODESETZVIR_DOMAIN_SAVE_PARAM_DXMLZVIR_DOMAIN_SAVE_PARAM_FILEZ"VIR_DOMAIN_SAVE_PARAM_IMAGE_FORMATZ'VIR_DOMAIN_SAVE_PARAM_PARALLEL_CHANNELSZVIR_DOMAIN_SCHEDULER_CAPZVIR_DOMAIN_SCHEDULER_CPU_SHARESZ$VIR_DOMAIN_SCHEDULER_EMULATOR_PERIODZ#VIR_DOMAIN_SCHEDULER_EMULATOR_QUOTAZ"VIR_DOMAIN_SCHEDULER_GLOBAL_PERIODZ!VIR_DOMAIN_SCHEDULER_GLOBAL_QUOTAZ$VIR_DOMAIN_SCHEDULER_IOTHREAD_PERIODZ#VIR_DOMAIN_SCHEDULER_IOTHREAD_QUOTAZVIR_DOMAIN_SCHEDULER_LIMITZ VIR_DOMAIN_SCHEDULER_RESERVATIONZVIR_DOMAIN_SCHEDULER_SHARESZ VIR_DOMAIN_SCHEDULER_VCPU_PERIODZVIR_DOMAIN_SCHEDULER_VCPU_QUOTAZVIR_DOMAIN_SCHEDULER_WEIGHTZ"VIR_DOMAIN_STATS_BALLOON_AVAILABLEZ VIR_DOMAIN_STATS_BALLOON_CURRENTZ$VIR_DOMAIN_STATS_BALLOON_DISK_CACHESZ(VIR_DOMAIN_STATS_BALLOON_HUGETLB_PGALLOCZ'VIR_DOMAIN_STATS_BALLOON_HUGETLB_PGFAILZ$VIR_DOMAIN_STATS_BALLOON_LAST_UPDATEZ$VIR_DOMAIN_STATS_BALLOON_MAJOR_FAULTZ VIR_DOMAIN_STATS_BALLOON_MAXIMUMZ$VIR_DOMAIN_STATS_BALLOON_MINOR_FAULTZVIR_DOMAIN_STATS_BALLOON_RSSZ VIR_DOMAIN_STATS_BALLOON_SWAP_INZ!VIR_DOMAIN_STATS_BALLOON_SWAP_OUTZVIR_DOMAIN_STATS_BALLOON_UNUSEDZVIR_DOMAIN_STATS_BALLOON_USABLEZVIR_DOMAIN_STATS_BLOCK_COUNTZVIR_DOMAIN_STATS_BLOCK_PREFIXZ(VIR_DOMAIN_STATS_BLOCK_SUFFIX_ALLOCATIONZ*VIR_DOMAIN_STATS_BLOCK_SUFFIX_BACKINGINDEXZ&VIR_DOMAIN_STATS_BLOCK_SUFFIX_CAPACITYZ$VIR_DOMAIN_STATS_BLOCK_SUFFIX_ERRORSZ%VIR_DOMAIN_STATS_BLOCK_SUFFIX_FL_REQSZ&VIR_DOMAIN_STATS_BLOCK_SUFFIX_FL_TIMESZ s    0 0    @&&0,     OkRgxh^Qg?6_q