Jan, On Friday, October 21, 2011 9:20 AM, "Jan Beulich" <[email protected]> wrote: > > Something to do with "microcode"? I didn't have this problem a few days > > ago, prior to the latest upgrade on this hardware. So maybe close? > > Yes, upstream c/s 23871:503ee256fecf (which got backported both > by us and upstream to 4.0.x and 4.1.x) introduced this. You need > to back-rev either microcode_ctl or xen for the time being.
We're too hooked on the general stability of the Xen version we use from you folks. Really don't want to drop back to another version, if I understand what you mean. Not even sure where I'd GET an older version. Sounds like I can monkey with microcode_ctl version instead? What version of that safe or recommended? Or should I just rm it or turn off the microcode svc? Thanks a lot. Garrett -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
