Bug#983357: How are other distros handling this ?
Hi all,
in an effort to solve this bug the quickest way possible, I want to
share some pointers (and some time !).
First, it can affect not only "upstream" Debian but also Debian-based
distros. I personaly had the problem trying to use Kali as a HVM domU.
Although Chuck's fix worked on Kali, I dunno which distros may fail without.
But from memory, looking for solutions to the bug, I only found posts
about Debian.
From what I read, understood, and guessed :
- it appears to be a kernel+udev+Xen bug,
- it has nothing to do with Debian itself,
- all distros using Xen are also using upstream Xen virtual KB
So I'm wondering :
- how can this bug only affect Debian and Debian-based distros but not
others like Suse, fedora, etc ?
- If I'm right, how are other distros handling this bug ?
- How is the "Debian cloud installer" handling this bug ?
- If the problem can't be solved "at its roots", can't we just apply the
(harmless) workaround in the installer ?
We should really speed up the fix before the Full Freeze.
I can help for testing and reporting stuff, but I'm a noob in packaging.
Thanks all, have a nice day,
zithro / Cyril REBERT
PS: off-topic remarks.
I'm a regular Debian user since a dozen years, and Debian+Xen since 5
years, as dom0s and domUs. I recently joined the Debian Xen team.
I want to say this is one of the most critical and obscure bug -I-
encountered on a Debian stable installer.
It's obvious but I'll state it nonetheless : it's really not a good
"publicity" for Debian. Note I'm pointing no finger at anyone as I
really don't care for it, I only care for a resolution.
We don't really know how much users turned their backs on Debian because
of this bug : "Deb does not work, but distro X works, let's just use the
one that works OOTB".
But maybe this bug is only affecting a handful of users ?
Reply to: