Reproducable with current upstream (3.2 in development) Note that on newer versions with full virtlogd there also is a similar message from that: virtlogd[19517]: End of file while reading data: Input/output error
There is some side effect that makes this slightly less straight forward. If the virReportError call is missing later on it reports "Error while processing monitor IO". I guess the report sets err and makes virGetLastError return something later on (what we still see is the generic catch all error message). It is like it is insisting on an error :-) If I don't get any from above I set the generic one down here. Yet just skipping those might have side effects I currently can't see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582990 Title: internal error: End of file from monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1582990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
