On 05/25/2012 08:53 PM, Luiz Capitulino wrote:
On Fri, 25 May 2012 13:01:37 +0100
Stefan Hajnoczi<stefanha@xxxxxxxxx> wrote:
I agree it would be nice to drop entirely but I don't feel happy doing
that to users who might have QEMU buried in scripts somewhere. One
day they upgrade packages and suddenly their stuff doesn't work
anymore.
This is very similar to kqemu and I don't think we regret having dropped it.
You couldn't imagine the number of complaints I got from users about dropping
kqemu. It caused me considerable pain. Complaints ranged from down right
hostile (I had to involve the Launchpad admins at one point because of a
particular user) to entirely sympathetic.
kqemu wasn't just a maintenance burden, it was preventing large guest memory
support in KVM guests. There was no simple way around it without breaking kqemu
ABI and making significant changes to the kqemu module.
Dropping features is only something that should be approached lightly and
certainly not something that should be done just because you don't like a
particular bit of code.
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
