VirtualBox
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Hey guys,
I managed to install VirtualBox but unfortunately I'm not able to start any virtual system so far. Whenever I try to start a system, which I moved to my new machine, I get the following error message:
"
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
"
When I try to execute the command '/etc/init.d/vboxdrv setup', this attempt results in the following: "sudo: /etc/init.d/vboxdrv: command not found".
I tried to follow all the steps listed here [1] but unfortunately that doesn't help either. My kernel version is the following: 3.8.10-gnu-1-generic. Any help is highly appreciated. :)
This sounds familiar, did you do a search before posting?
Actually yes but maybe there is somethin I have missed. Care to give me a hint?
This is probably what I meant https://trisquel.info/en/forum/intstalling-virtualbox-trisquel-6-howto-solved-if-you-need-it
If you'd use the trisquel's 3.2 version of linux this issue has been fixed.
@lembas: Thanks a lot but that's exactly the link I posted in my original post. Unfortunately that doesn't help...
@Sachin: You want me to downgrade to linux-3.2? Wouldn't that be a big step coming from linux-3.8?
This was the issue I filed a while ago
https://trisquel.info/en/issues/8166
I got to know about more from
http://www.phoronix.com/scan.php?page=news_item&px=OTk5M
On Thursday 01 August 2013 12:04 AM, name at domain wrote:
>
> @Sachin: You want me to downgrade to linux-3.2? Wouldn't that be a big
> step coming from linux-3.8?
>
Are you using Jxself's repo? I don't know if it has the same issue.
Thanks Sachin, I just updated the issue.
I'm not using Jxself's repo. What is special about this repo and where can I get it from?
Linux as you probably know has blobs, parts that are not free and their source code not available.
Linux-libre projects usually clean those out. Trisquel uses a linux-libre maintained by Ruben I believe, which is not always as much up to date as we would like.
jxself kernel is one kernel that is also linux-libre and is usually more up to date. So many people prefer to use it. There is also this other one
https://launchpad.net/~linux-libre/+archive/ppa
which is also a linux-libre kernel.
So, what is the difference? Well, you can read more about it here
https://trisquel.info/en/forum/better-libre-kernel-source-dns-ppa-or-jxself
But, the point is that some stuff might actually work in Trisquel kernel and not on jxself for example, or the other way around, because there are some differences.
I wonder, however, why does using one of those kernel's ppas leaves me with linux 3.8 instead of 3.10? -.^
mmm... this don't seem like a solution (at all)
@Sachin: You mentioned another command in the issue you linked to. Thus, I tried "sudo /etc/init.d/virtualbox start". But this only resulted in "No suitable module for running kernel found".
@GNUser: Thank you very much for your elaborations. However, I think I didn't manage yet to use the package from jxself.
I followed the instructions from here [1] but now I don't know the correct procedure to get rid of my old linux-libre package and using the new one from jxself.
On Thursday 01 August 2013 03:54 PM, name at domain wrote:
> @Sachin: You mentioned another command in the issue you linked to.
> Thus, I tried "sudo /etc/init.d/virtualbox start". But this only
> resulted in "No suitable module for running kernel found".
>
That happened because the kernel module does not exist with your version
of linux-libre.
you need to try other linux-libre repos
Isn't there a package for DKMS for VirtualBox? I know one exists for Parabola, and I use it because I use a custom linux-libre kernel.
Yes there is.
Looks like Virtualbox in Ubuntu quantal requires a non-free compiler.
If this doesn't change in the Ubuntu version the next Trisquel will be based on, Virtualbox will not be included.
Indeed, this is a serious issue. Virtualbox has also been removed from Parabola for the same reasons. For anyone wanting to get this fixed I've opened up a bug directly with VirtualBox's Trac here - https://www.virtualbox.org/ticket/12011
Until then we may have to use virt-manager and QEMU-KVM. :/
I installed jxself' repository but I don't really know how to proceed now. Which package(s) do I have to install?
Thanks a lot, Magic Banana.
Unfortunately I just get:
"Err http://jxself.org/repo/freesh/ freesh/main linux-image-3.10.4-gnu amd64 3:2.0
404 Not Found
Err http://jxself.org/repo/freesh/ freesh/main linux-libre64 amd64 3.10.4
404 Not Found
0% [Working]E: Failed to fetch http://jxself.org/repo/freesh/pool/main/l/linux-source-3.10.4-gnu/linux-image-3.10.4-gnu_2.0_amd64.deb: 404 Not Found
E: Failed to fetch http://jxself.org/repo/freesh/pool/main/l/linux-source-3.10.4-gnu/linux-image-3.10.4-gnu_2.0_amd64.deb: 404 Not Found
"
Is there something wrong with the repository?
On 05/08/13 18:41, gromobir wrote:
> Thanks a lot, Magic Banana. Unfortunately I just get:
>
> "Err http://jxself.org/repo/freesh/ freesh/main
> linux-image-3.10.4-gnu amd64 3:2.0 404 Not Found Err
> http://jxself.org/repo/freesh/ freesh/main linux-libre64 amd64
> 3.10.4 404 Not Found 0% [Working]E: Failed to fetch
> http://jxself.org/repo/freesh/pool/main/l/linux-source-3.10.4-gnu/linux-image-3.10.4-gnu_2.0_amd64.deb:
>
> 404 Not Found
>
> E: Failed to fetch
> http://jxself.org/repo/freesh/pool/main/l/linux-source-3.10.4-gnu/linux-image-3.10.4-gnu_2.0_amd64.deb:
>
> 404 Not Found "
>
> Is there something wrong with the repository?
Try doing sudo apt-get update, then try again.
Andrew.
Thank you very much, andrew. I managed to install the package now. Unfortunately, VirtualBox still isn't working for me. "uname -r" shows "3.10.5-gnu" now but "sudo /etc/init.d/vboxdrv setup" still gives me "sudo: /etc/init.d/vboxdrv: command not found". Any further hints?
On 06/08/13 19:12, gromobir wrote:
> Thank you very much, andrew. I managed to install the package now.
> Unfortunately, VirtualBox still isn't working for me. "uname -r"
> shows "3.10.5-gnu" now but "sudo /etc/init.d/vboxdrv setup" still
> gives me "sudo: /etc/init.d/vboxdrv: command not found". Any further
> hints?
I am currently having the same issue. Running
sudo /etc/init.d/virtualbox start
returns this:
* Starting VirtualBox kernel modules
* No suitable module for running kernel found
[fail]
I haven't had a lot of time to further investigate it, but if I find a
solution I will be sure to post it here.
Andrew.
On 06/08/13 19:12, gromobir wrote:
> Thank you very much, andrew. I managed to install the package now.
> Unfortunately, VirtualBox still isn't working for me. "uname -r"
> shows "3.10.5-gnu" now but "sudo /etc/init.d/vboxdrv setup" still
> gives me "sudo: /etc/init.d/vboxdrv: command not found". Any further
> hints?
I am currently having the same issue. Running
sudo /etc/init.d/virtualbox start
returns this:
* Starting VirtualBox kernel modules
* No suitable module for running kernel found
[fail]
I haven't had a lot of time to further investigate it, but if I find a
solution I will be sure to post it here.
Andrew.
Unfortunately the problem still persists. Even the latest kernel update didn't change anything.
-----BEGIN PGP MESSAGE-----
Charset: UTF-8
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
hQEMA4mdZH3jAkFlAQgAm2mQQqcjIzagK7EnIaIfrSoFFBkoRsM/LdGTkVefF5qW
ZL5cYvOHdnULJ7O2mjmxnsYRb1+75J79zKw0xXdM6sjgcsJoKw/LINTTCEXKYa/y
viP/zw2YVTq8TcHgDUQkgLFxfrrUhEE/hcy/6mEwhE7tLOV8hKRNwtdwGoGvtbl1
HBEog5Sbw+iwZcHiDv0n+hejNVIGPIMm1dEmyJfLu1eY5QUGYkWFiVHoHI9YRK0d
/3oFondjR3qZSVgrpKB/ErQJUYkhMZI455HSnPxTtmmGtblI1qeocfKkK/BvGXzn
iP36ex8iCn2RT2fW0okqH1RMkpM9gcQ6nhTeqRQFitLpAfpqonv7b98McXmm2Bny
sny4G5YkjkOaK0H+quW2oc/swGq0yYrIOyE4pZtlANmwYgyrP237CsUDR8XW2FNx
HmHNvnQ60330brxG37MvS73//k7Gswby9xC+R+oQAh09Jidz+xrD2qsuiMr9vSJN
K+8nGpFdOBJMm4JrdMgApxC5wQQB28LOsctpsV6OX2rDR46fzZ4307KJCjuA8SCY
0uWQSwfAkIh6F5Aa24UA8Mi34wdN/TsgxTGDzQ2MGWxnd2kEBNdk2zTR0xirHV8X
+OKsf27MiQ5OjX5Cu/STqdPPTgj1WejHRlk0odsWo4NCLGgGBequAN9zQks/HeNb
tj6+w/XQANlqhRLMmcaOeWPQXW+uDY2lR15bzmN8q3Z4LgL6ZS0XbyRiz+4qOjzq
ns+QFrOTmiqSrWDohXdj4E0M9wWHqbw8aCmBjn9JieM+PDtuPshSRDdYjVlAXKLM
2fPrGa3bTV4weO/2yQK/NLf/cOwlpu2TVzgBQoFJzqsRtz+kT2eWfrowelfpY+Jp
qRhdbyFyl2Olz7wYUDhMluxwsiQzlFBrtUzPTvegkrdmWQAztX24DrwAOqzgbysV
oDsHf4Wp1QOiicw26OsmIuwcX7EEShe05mXrxvb50WEayYoPWqxBVmyW1EAjgBAw
skrAsvzI0Q/Y78AcpALacQAB8g==
=ovRw
-----END PGP MESSAGE-----
On Wednesday 14 August 2013 06:31 PM, name at domain wrote:
> Unfortunately the problem still persists. Even the latest kernel update
> didn't change anything.
>
I just tried linux-libre 3.10 from jxself's repo, yes virtualbox
didn't work but if virtualbox is really necessary and downgrading to
linux-libre 3.2 is not a issue for you then you can have it working.
The other solution would be to install the packages "qemu, qemu-system
and qemu-launcher".
Here is a wiki-book
https://en.wikibooks.org/wiki/QEMU
If you are referring to the wiki-book substitute the command just
"qemu" with your hardware architecture based command like these
"qemu-system-i386" or "qemu-system-x86_64"
On 15/08/13 01:34, Sachin wrote:
> I just tried linux-libre 3.10 from jxself's repo, yes virtualbox
> didn't work but if virtualbox is really necessary and downgrading to
> linux-libre 3.2 is not a issue for you then you can have it working.
Kernel 3.2 works for me as well. So I changed by GRUB settings in
/etc/default/grub, with
GRUB_HIDDEN_TIMEOUT=
instead of
GRUB_HIDDEN_TIMEOUT=0
That gives me the GRUB menu each time, so I can choose between 3.2 and 3.10.
Andrew.
qemu can create virtualbox's vdi images and also run them
here's my virtualbox vdi running screenshot and the command that did it
"qemu-system-i386 -hda /path/to/trisquel6.vdi"
man, this hasn't to do with your version of kernel. A solution may be
sudo aptitude install linux-headers-`uname -r`-generic sudo dpkg-reconfigure virtualbox-dkms
...something else
check the GNUser discussions on this forum and beware!
On 04/09/13 23:23, brianyroush wrote:
> man, this hasn't to do with your version of kernel. A solution may
> be
>
> sudo aptitude install linux-headers-`uname -r`-generic sudo
> dpkg-reconfigure virtualbox-dkms
I have headers and dkms installed with my 3.10 kernel (from jxself's
repo) and I still get errors. The solution isn't so simple, unfortunately.
I also have 3.2 installed, which has always worked for me.
Also, if you have any fixes, it would be great if you could keep this
bug report updated: https://trisquel.info/en/issues/8166
Andrew.
Well, could I use my old virtual machines created with VirtualBox with QEMU? If not, that's not an option either. :-(
- Vous devez vous identifier ou créer un compte pour écrire des commentaires