https://bugzilla.novell.com/show_bug.cgi?id=851338
https://bugzilla.novell.com/show_bug.cgi?id=851338#c31
--- Comment #31 from Jan Beulich
That seems like a poor choice - I've been waiting for this bug to be fixed to replace my openSuSE 12.1 VMs with openSuSE 13.1. When is 13.2 due out? Hopefully it won't suffer from the same bug?
As it stands right now it will. The problem is that so far no-one has come up with a workable replacement scheme for determining the desired compatibility level, and hence we're going to stick to the "compatible with the previous openSUSE release" one. Schemes looked at but not considered workable/reasonable: - compatible with everything (i.e. back to 3.0.2) - compatible with an ad hoc set of host distros A scheme that I would personally consider workable, but that wouldn't help you here would be to tie compatibility to versions being actively maintained by xen.org - 4.1.x has been out of support for quite a while... The main requirements for a scheme to be workable are - not vendor centric - not locking us into compatibility with an old version indefinitely - clear up front determination of when the compatibility level can be raised (this in particular means independence of other vendors' release schedules) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.