[Pkg-virtualbox-devel] Bug#577123: handling multiple modules contending for VT-x/AMD-V access

[James Nobis]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

The original ticket may be well over a year old but it is still
relevant.  I got bit by this after just upgrading to Squeeze this past
weekend.  This bug ticket was actually the only useful information I got
in about 2 pages of google results.

It seems that once a kernel module gets hold of the hardware
virtualization then it blocks other modules from sharing it.  In the
very least how about documentation for the relevant modules (kvm,
virtualbox-ose, and prob others) to give users information about the issue.

More thorough fixes would have to have a method of a default module and
then blacklist the other modules.  For that matter if the kvm module
isn't in use and someone launches a Virtual Box vm unload the kvm, then
unload the kvm module, reload the vboxdrv module, then launch the vm.

James
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCgAGBQJOZYR1AAoJEGUWgJyjXssuRZIP/2amEw01lHzDQx7xVKRwxST0
KpuLRZz4wtsmRQ/WINEJCUAtsTo6zjE8Qs3jNey+axUAdkfLngW/DmW8Wt+yq4fZ
2K7OcGe6isdVAwoQ4c7HmGkP747bTk58w2bMo503pXG7fHWfeTCE/n5eM2IDR0CY
d/PDfZ/AYScZOF3Fso5VFoFsFi9EUFy452seKJYsHcHQbKVjHWuQvOWuwSwqxOXx
MiPMbiDJ/cbIhXkI7jvZpH0drcLTTOswPDQXnB7Y76IfNTGnBMK2NChZ2A6Fs/iB
9eN7ZBaLUcpGVT55koXy1V7hLAyQOtEPLiwk98gRkuWPqPSaUerbyG0UXuqy1qVE
poA+ZAIN5d6Hwt3IINRDI8sc859zi77OIRjIQwsQ0cWw7niLCpkxXmX7Qyqwo+WL
p6Lz2VicqEZ05gs/SEFHjkGFwWtNgQdfVdi1XeFtQu772OA2PkJIGEJB9cyqq/Od
BkJ6oje3MeLWKWcAB5tx7y0DOehuBIgIl9ItOAuL47eXaEdzcclwAwQ8qywDMvFP
tevNKYo+PL/AqoxnUyCk4MnypHHYUeZH2zo2kFqylAWXf5jylgBREZDpEYTE8rc7
G4RjBYppoEYrckFwGfsyoX13WsdTo7cjeW5Azbvdd2VFq7UAH0JqK3RKk2EMBB5d
A6G0Lw1J7DtuSudpAQgY
=VGwu
-----END PGP SIGNATURE-----