In general I think one would consider this sort of issue to be a problem with the containing VMM (i.e. KVM in this case) in the first instance.
i'll agree with you, but last week booting the _lenny_ xen dom0 kernel (2.6.26-2-xen-686 -> 2.6.26-21lenny3) booted until it ran into another issue.
however, it's also possible to treat each VMM as an architecture ;-) cheers pille -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
