I have learned that while this can be fixed using the above patch (actually, I had to increase my timeout to over nine minutes!) - the true cause of the issue is a bug in kvm-84.
kvm-85 will start even large VMs very quickly, obviating the need to increase the startup timeout in the first place. -- libvirtError: internal error unable to start guest https://bugs.launchpad.net/bugs/344400 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
