Vincent Danjean <vdanj...@debian.org> writes: > Package: linux-2.6 > Version: 2.6.32-16 > Severity: important
[..] > PS: the severity can be increased if lots of people experiments the same thing > or lowered if this is specific to my configuration. At first, I thought that the severity was appropriate as this bug doesn't break *all* systems, and the kernel is somewhat special in that most bugs will affect "the whole system". But I must admit that I was a bit surprised when 2.6.32-17 was uploaded without a fix for this problem. It makes me wonder if the severity shouldn't have been higher after all.... Just to be clear: This bug does break all KVM based systems, making them completely unbootable, and requiring console access to fix. I'm pretty sure there are plenty of KVM based hosting solutions around where this will be a severe problem. Is KVM a supported "hardware" platform i Debian? I would expect so. If it is, then please raise the severity of this bug high enough to reflect this. Thanks, Bjørn -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
