Hi Alex, that issue back then didn't get a fix IIRC. It stayed not debuggable enough - you say you have many instances that encounter this on reboot.
I haven't seen it myself, but maybe this is a chance to track it down this time. Questions: 1. in case you can on your system - or if you have a comparable testbed - try newer libvirt/qemu stacks (if you do not want to upgrade the full system take a look at [1] If those would be good you could try to iterate to the fix. 2. btw are you also running through nova as the initial reporter or directly via libvirt/qemu? 3. since so many other people do not see the same and this is related to the virt-queue inuse getting "out of control" do you drive any kind of excessive I/O on that system that one could try to recreate? (a local repro would easen bisecting and similar tasks a lot). If you have any more info on steps to recreate please share. [1]: https://wiki.ubuntu.com/OpenStack/CloudArchive -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721167 Title: Guest stopped after "Virtqueue size exceeded error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1721167/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
