** Description changed: Libvirt client network, breaks connection as poll calls are not re-entering. This causes libvirt connection die under a heavy load and doesn't work well with RTS that use signals. It was fixed upsteam by Peter Feiner <[email protected]>: http://libvirt.org/git/?p=libvirt.git;a=commit;h=bfa74ebe1f8a15872b7792480493515989130e34 ============================ SRU Justification: - Impact: if a kvm vm is placed into suspend over the monitor, and then resumed, libvirt will fail to see the resume event and continue reporting the VM as paused. - Development fix: libvirt is made to follow resume events. + Impact: libvirt connections can die under a heavy load + Development fix: libvirt is made to handle -EINTR. Stable fix: backported patch from upstream Test case: (To be filled in) - Regression potential: If there is a bug in the resume follower hook, then the case listed could cause a crash instead of having libvirt follow the VM. All qa-regression-tests passed with this fix. + Regression potential: Checks for -EINTR are added to existing checks for -EAGAIN. ============================
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092826 Title: libvirt client doesn't handle EINTR signal properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1092826/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
