[libvirt-users] Duplicate reboot events

Innus, Martins minnus at buffalo.edu
Tue May 16 18:41:05 UTC 2017


Hi,

Running on:

$ cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)

And:

$ rpm -qa |grep libvirt
libvirt-daemon-2.0.0-10.el7_3.5.x86_64
libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64
libvirt-daemon-driver-secret-2.0.0-10.el7_3.5.x86_64
libvirt-client-2.0.0-10.el7_3.5.x86_64
libvirt-daemon-driver-network-2.0.0-10.el7_3.5.x86_64
libvirt-daemon-driver-storage-2.0.0-10.el7_3.5.x86_64
libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.5.x86_64
libvirt-daemon-config-network-2.0.0-10.el7_3.5.x86_64
libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.5.x86_64
libvirt-2.0.0-10.el7_3.5.x86_64
libvirt-python-2.0.0-2.el7.x86_64
libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.5.x86_64
libvirt-daemon-driver-lxc-2.0.0-10.el7_3.5.x86_64
libvirt-daemon-driver-interface-2.0.0-10.el7_3.5.x86_64

I’m seeing duplicated reboot events when using the python event api.  Use is simplified down to the simple test case attached.  Running with that results in:

$ sudo ./libvirt_events_single.py
Reboot: Domain i-06945b37(21)
1494958504.72
Reboot: Domain i-06945b37(21)
1494958504.74

This is reproducible 100% of the time by doing /sbin/reboot from within a VM started with qemu-kvm.  Any ideas on whats going on?

Let me know if any other information would be useful.

Thanks

Martins

-------------- next part --------------
A non-text attachment was scrubbed...
Name: libvirt_events_single.py
Type: text/x-python-script
Size: 459 bytes
Desc: libvirt_events_single.py
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20170516/45b1dc13/attachment.bin>


More information about the libvirt-users mailing list