Comment 12 for bug 589163
Revision history for this message
| Nathan Lutchansky (nathan-launchpad) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I'll echo James Hogarth's concerns here that whatever QA happened with this update, if any, obviously didn't include any QEMU/KVM testing. After updating to 2.6.32-22.35, I was unable to get qemu-kvm to run at all, regardless of which options I used. Didn't anybody try running KVM on the new kernel after applying a KVM-related patch?
My VM host was down for an hour this afternoon as a result of applying what was supposed to be a "long-term stable" update. I was bit last year by a KVM update with an obvious data loss bug (see bug #404394), so after today's bug, I'm regretting my choice of Ubuntu for my VM hosts.