o 3bB@shzddlZWn3ey9Zz'zddlZWney.Zzdeevr$eWYdZ[ndZ[wwWYdZ[ndZ[wwddlZddlmZm Z m Z dej dej dede de d ed e eefd e fd d Zdej de d dfddZd!dej dej dede ej ej ee e eejgdfdejde d e fddZddZddZddZdZdZdZdZdZdZd ZdZdZdS)"NzNo module named)AnyCallableDictconndomeventsecondsmicrosdetailscbDatareturnc Cs2|d}|d}||tj||d|||||dS)zBDispatches events to python user qemu monitor event callbacks cbopaque_objr)libvirt virDomain) rrrrr r r r rr./usr/lib/python3/dist-packages/libvirt_qemu.py!_dispatchQemuMonitorEventCallbacksr callbackIDcCsDzt|j|}|dkrtd|j|=WdSty!YdSw)ztRemoves a qemu monitor event callback. De-registering for a callback will disable delivery of this event typez3virConnectDomainQemuMonitorEventDeregister() failedN)libvirtmod_qemu*virConnectDomainQemuMonitorEventDeregister_or libvirtErrorqemuMonitorEventCallbackIDAttributeError)rrretrrrqemuMonitorEventDeregister)s  rr rflagscCspt|dsi|_|||d}|durt|jd|||}n t|j|j|||}|dkr1td||j|<|S)zpAdds a qemu monitor event callback. Registering for a monitor callback will enable delivery of the eventsr)r rrNrz1virConnectDomainQemuMonitorEventRegister() failed)hasattrrr(virConnectDomainQemuMonitorEventRegisterrrr)rrrr rr r rrrrqemuMonitorEventRegister5s    r#cCs(t|j|||}|durtd|S)z%Send a Guest Agent command to domain Nz"virDomainQemuAgentCommand() failed)rvirDomainQemuAgentCommandrrr)domaincmdtimeoutr rrrrqemuAgentCommandJs r(cCs4t|j||}|durtdtj||d}|S)aThis API is QEMU specific, so it will only work with hypervisor connections to the QEMU driver. This API will attach to an externally launched QEMU process identified by @pid. There are several requirements to successfully attach to an external QEMU process: - It must have been started with a monitor socket using the UNIX domain socket protocol. - No device hotplug/unplug, or other configuration changes can have been made via the monitor since it started. - The '-name' and '-uuid' arguments should have been set (not mandatory, but strongly recommended) To date, the only platforms we know of where pid_t is larger than unsigned int (64-bit Windows) also lack UNIX sockets, so the choice of @pid_value as an unsigned int should not present any difficulties. If successful, then the guest will appear in the list of running domains for this connection, and other APIs should operate normally (provided the above requirements were honored). NzvirDomainQemuAttach() failedr)rvirDomainQemuAttachrrrr)r pid_valuer r__tmprrr qemuAttachQs  r,cCs&t|j||}|durtd|S)zASend an arbitrary monitor command through qemu monitor of domain Nz$virDomainQemuMonitorCommand() failed)rvirDomainQemuMonitorCommandrrr)r%r&r rrrrqemuMonitorCommandms r.r<)r)r ImportErrorlib_ecygvirtmod_qemucyg_estrrtypingrrr virConnectrintrr_Tr#r(r,r.4VIR_CONNECT_DOMAIN_QEMU_MONITOR_EVENT_REGISTER_REGEX5VIR_CONNECT_DOMAIN_QEMU_MONITOR_EVENT_REGISTER_NOCASE#VIR_DOMAIN_QEMU_AGENT_COMMAND_BLOCK!VIR_DOMAIN_QEMU_AGENT_COMMAND_MIN%VIR_DOMAIN_QEMU_AGENT_COMMAND_DEFAULT$VIR_DOMAIN_QEMU_AGENT_COMMAND_NOWAIT&VIR_DOMAIN_QEMU_AGENT_COMMAND_SHUTDOWN'VIR_DOMAIN_QEMU_MONITOR_COMMAND_DEFAULT#VIR_DOMAIN_QEMU_MONITOR_COMMAND_HMPrrrrs<    6 J