You are not logged in.
I am really stuck here and would be very disappointed if i have to use the arch default kernel from pacman to use virtualbox. Ths is my /var/log/vbox-install.log: http://pastebin.com/e63JFZx54. I compiled the Kernel on the linux kernel from [core] and did no modifications to the config i got from /proc/config.gz.
edit: I suppose this happens because I am missing the kernel headers right? Where do I put those, correspondig to my src folder beeing at ~/dev/kernel/linux
Last edited by chippoke (2012-06-12 19:24:14)
Offline
Why not build your kernel using ABS? That way, all the files will go where they should and pacman will own everything for easy FS management.
Offline
I did not see any adventage of that up to now but I will give it a try, who knows maybe its fixes my problem.
Offline
Advantages =
1) consistency
2) pacman owns and manages them
3) easy as hell rebuilds when upstream changes
Disadvantages =
...
Last edited by graysky (2012-06-12 20:05:57)
Offline
Nope, still doesnt work ![]()
Offline
Your link comes up as "Unknown paste ID" - try again.
Offline
Sorry for that, I reran vboxbuild with the kernel compiled with abs http://pastebin.com/pyTGg5nj
this is the output to stdout
:: Removing all old VirtualBox kernel modules [FAIL]
:: Removing all old VirtualBox kernel modules [FAIL]
:: Removing all old VirtualBox kernel modules [FAIL]
:: Removing all old VirtualBox kernel modules [FAIL]
:: Recompiling VirtualBox kernel modules (3.5.0-1-mainline) [BUSY] Look at /var/log/vbox-install.log to find out what went wrong
[FAIL]
[DONE]
Last edited by chippoke (2012-06-13 15:08:11)
Offline
Okay this seems to be an overall problem. Possible fix can be found right here: http://weltall.heliohost.org/wordpress/ … irtualbox/
Offline