On Sun, 2010-11-28 at 13:39 +0300, Michael Tokarev wrote: > 28.11.2010 05:25, Ben Hutchings wrote: > > Please can you test whether this is fixed in 2.6.32-28? We backported a > > KVM feature (VCPU_EVENTS) which meant we needed an additional fix beyond > > the one which Michael Tokarev identified, and that was done in -28. > > Yes, with 2.6.32-28 686 kernel I can't reproduce the problem anymore, > kvm works as intended, while reverting back to -27 returns the issue. Excellent. > Reading #599507 again, together with this #604604 and also #604900, it > looks like all this stuff is the same thing. There's also #580652. Could be, but error code -22 (EINVAL) is not very specific. > Out of curiocity, why this feature (VCPU_EVENTS) were backported/applied > in the first place (it was in 2.6.32-12)? Isn't it somewhat too buggy > having in mind all the above? The svn changelog says: > r15572 | maks | 2010-04-27 17:36:34 +0100 (Tue, 27 Apr 2010) | 3 lines > > backport KVM: x86: Add KVM_GET/SET_VCPU_EVENTS > > is said to help with troubles on vmsave/restore. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part