http://bugzilla.novell.com/show_bug.cgi?id=545191 User jbeulich@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=545191#c11 --- Comment #11 from Jan Beulich <jbeulich@novell.com> 2009-10-16 09:56:35 MDT --- (In reply to comment #9)
valid, or just available?
Valid.
i use the stable/release kernel for 11.1, and the up-to-date, not-broken-like-3.3, 3.4.x hypervisor from OBS. that's been discussed -- perhaps even directly with you? -- previously in bugzilla.
If you mean power management being broken in 3.3, that certainly doesn't matter for this bug? We don't ship 3.4.x for 11.1, so we won't be able to help you with this combination either.
the only available clocksources are reported, @ Dom0, as
But I asked about Xen's clocksources, not Dom0's.
did you contact J Fitzhardinge @ your company? this seems to be something he's directly involved in ...
Who told you that Jeremy would work for Novell. He's at Citrix. (In reply to comment #10)
in issue https://bugzilla.novell.com/show_bug.cgi?id=530035, wherein you "suggest to simply be patient. After all, this is not some critical problem we're talking about", removing cpuidle breaks power mgmt.
It may break xenpm, but it certainly doesn't break power management.
apparently, on 10/1/2009, amd posted a patch, supposedl fixing those issues, that "has been submitted to xen-unstable but has not yet made it into the tree." ,,,
I saw that, and meanwhile it has been checked in. So once we'll have a product based on 3.5 or newer, this will work. Backporting such a change would require it to e.g. fix a severe issue, which isn't the case here. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.