Luis Henriques wrote:
Ok, I am not sure but there is a possibility of having the vboxdrv driver
loaded. _But_ I was not using, i.e., I do not use VirtualBox. In my
attempts to reproduce the issue, I tried to load this module but, unfortunatly,
my distro has this package broken ATM (err... in fact, the problem is not the
distro but me - I am using an unstable version).
vboxdrv could be a problem if I was using it, but I believe it shouldn't cause
this if it is not being used... but it's just a guess.
Let's keep an eye open on it. If it reproduces, be sure to note what
drivers are loaded. Meanwhile, I don't recommend having different
virtualization modules loaded concurrently.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
