The same bug has been reported in Red Hat: https://bugzilla.redhat.com/show_bug.cgi?id=487013
A patch has been posted that fixes it: http://www.redhat.com/archives /libvir-list/2009-March/msg00195.html "In the QEMu driver, the qemudDomainSetVcpus() entry point is calling into another entry point qemudDomainGetMaxVcpus(), this causes a deadlock due to recursive mutex locking. The qemudDomainSetVcpus() method should in fact be calling the internal method qemudGetMaxVCPUs(). This patch makes it do that, thus avoiding the recursive mutex locking." I'm assuming that means this bug should be pretty easy to fix. Or is it more complicated than just fixing the code and building a new package? ** Bug watch added: Red Hat Bugzilla #487013 https://bugzilla.redhat.com/show_bug.cgi?id=487013 -- virt-manager freezes when applying hardware change https://bugs.launchpad.net/bugs/367137 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
