[libvirt-users] Duplicate reboot events

[Innus, Martins]

> On May 16, 2017, at 3:49 PM, Martin Kletzander <mkletzan at redhat.com> wrote:
> 
> On Tue, May 16, 2017 at 06:41:05PM +0000, Innus, Martins wrote:
>> 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
>> 
> 
> Can you try with newer libvirt?

I’m not sure.  I will have to see if I can build it, unless there is a repo somewhere with centos7 rpms.  I assume by this you mean that you don’t see this with current libvirt?

> Does this happen with 'virsh event
> --loop --event lifecycle’?

“lifecycle” shows no output, but with “reboot” or “all”:

$ sudo virsh event --loop --all
event 'reboot' for domain i-06945b37
event 'reboot' for domain i-06945b37

> 
> Is there anything fishy going on when looking at the console (VN/spice)
> during that reboot?


Don’t see anything unusual.  I can send you the full console output if you want, but I don’t see anything strange.

Thanks

Martins

> 
>> 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
>> 
> 
>> #!/usr/bin/env python
>> 
>> import libvirt
>> import time
>> 
>> def RBcallback(conn, dom, opaque):
>>   print "Reboot: Domain %s(%s)" % (dom.name(), dom.ID())
>>   print time.time()
>> 
>> if __name__ == '__main__':
>> 
>>   libvirt.virEventRegisterDefaultImpl()
>> 
>>   conn = libvirt.openReadOnly('qemu:///system')
>> 
>>   conn.domainEventRegisterAny(None, libvirt.VIR_DOMAIN_EVENT_ID_REBOOT, RBcallback, None)
>> 
>>   while True:
>>       libvirt.virEventRunDefaultImpl()
> 
>> _______________________________________________
>> libvirt-users mailing list
>> libvirt-users at redhat.com
>> https://www.redhat.com/mailman/listinfo/libvirt-users