After longer investigations, this error was a known bug related to memory management. Under certain circumstances, if memory was growing short, libvirtd tried to allocate more memory, but didn't react on errors if there wasn't enough, trying to dereference the null pointer given back in such cases. This error was fixed in one of the newer versions.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/916095 Title: Starting various VM via libvirt-bin, crashes libvirtd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/916095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
