Changing disk QoS causes segfault with IO-Threads enabled (oVirt 4.3.0.4-1.el7)
We recently upgraded to 4.3.0 and have found that when changing disk QoS settings on VMs whilst IO-Threads is enabled causes them to segfault and the VM to reboot. We've been able to replicate this across several VMs. VMs with IO-Threads disabled/turned off do not segfault when changing the QoS. Mar 1 11:49:06 srvXX kernel: IO iothread1[30468]: segfault at fffffffffffffff8 ip 0000557649f2bd24 sp 00007f80de832f60 error 5 in qemu-kvm[5576498dd000+a03000] Mar 1 11:49:06 srvXX abrt-hook-ccpp: invalid number 'iothread1' Mar 1 11:49:11 srvXX libvirtd: 2019-03-01 00:49:11.116+0000: 13365: error : qemuMonitorIORead:609 : Unable to read from monitor: Connection reset by peer Happy to supply some more logs to someone if they'll help but just wondering whether anyone else has experienced this or knows of a current fix other than turning io-threads off. Cheers.
On 3 Mar 2019, at 23:39, jloh@squiz.net wrote:
We recently upgraded to 4.3.0 and have found that when changing disk QoS settings on VMs whilst IO-Threads is enabled causes them to segfault and the VM to reboot. We've been able to replicate this across several VMs. VMs with IO-Threads disabled/turned off do not segfault when changing the QoS.
Mar 1 11:49:06 srvXX kernel: IO iothread1[30468]: segfault at fffffffffffffff8 ip 0000557649f2bd24 sp 00007f80de832f60 error 5 in qemu-kvm[5576498dd000+a03000] Mar 1 11:49:06 srvXX abrt-hook-ccpp: invalid number 'iothread1' Mar 1 11:49:11 srvXX libvirtd: 2019-03-01 00:49:11.116+0000: 13365: error : qemuMonitorIORead:609 : Unable to read from monitor: Connection reset by peer
Happy to supply some more logs to someone if they'll help but just wondering whether anyone else has experienced this or knows of a current fix other than turning io-threads off.
would be best to open a bugzilla on that. It sounds like a real qemu problem. There were quite a few with iothreads in the past and QoS is relatively less frequent feature so it could still be buggy. Just make sure you include all the relevant versions of kernel,qemu,libvirt Thanks, michal
Cheers. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UEVUBKWDS7NHHE...
Today I was setting QoS for one of storage domains and I had same problem as you described here. Did you ever find a fix for that problem or did you maybe report it where? We still use oVirt 4.3.10 - we are planning to upgrade it this year. Thanks, Pavel
It seems that the problem occurs only if you change the storage QoS profile to Unlimited. Can anyone try this in newer versions of oVirt? Cheers. On 22. 04. 24 18:15, pavel.sipos@arnes.si wrote:
Today I was setting QoS for one of storage domains and I had same problem as you described here.
Did you ever find a fix for that problem or did you maybe report it where?
We still use oVirt 4.3.10 - we are planning to upgrade it this year.
Thanks, Pavel _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VBHLLXM5XKDIBZ...
participants (4)
-
jloh＠squiz.net -
Michal Skrivanek -
Pavel Šipoš -
pavel.sipos＠arnes.si