[Bug 484807] [NEW] module blacklisting not respected

[oger000]

Soren Hansen schrieb:
> On Wed, Nov 18, 2009 at 02:59:35PM -0000, oger000 wrote:
>> ad 1) ubuntu 9.10
>> ad 2) qemu-kvm 0.11.0-0ubuntu6.3
>> ad 3) The script /etc/init.d/qemu-kvm should respect the blacklisting system of modprobe (/etc/modprobe.d/blacklist-xxx.conf for example).
>> ad 4) The kvm modules are loaded even if blacklisted.
>> 
>> If you are interested why the issue arises: The kvm modules conflict
>> with virualbox and I dont want to modify the init scripts by hand
>> especally because there is infrastructure to handle this in another way.
> 
> I presume you need this because you're using qemu-kvm to emulate other
> architectures? Otherwise, why not just remove qemu-kvm instead of
> fiddling with blacklists?

Visualbox is in daily usage on my workstation. Also needed from other users who 
share my desktop one day a week when I am out. Virtualbox stops starting (with 
appropriate message) when kvm modules (kvm_intel) are loaded. This other users 
have no root access, I have. I have some rare cases where I need qemu-kvm, 
testing usb-stick images. So my idea was to disable (blacklist) the kvm-modules 
and do a manual "modprobe kvm_intel" when I need it.

The other way would be something like "update-rc.d -f kvm remove" (untested). 
But I think blacklisting is the "intended" way to configure that specific 
modules should not be loaded at boot time. So I'll try to improve my patch to go 
this route.


-- 
O(ettl) GER(hard)

-- 
module blacklisting not respected
https://bugs.launchpad.net/bugs/484807
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.