MESSAGE
DATE | 2015-03-18 |
FROM | Ruben Safir
|
SUBJECT | Re: [NYLXS - HANGOUT] Apple crimes
|
On 03/18/2015 09:02 AM, Rick Moen wrote: > Quoting Ruben (ruben.safir-at-my.liu.edu): > >> I had a question, actually, about virtualization and kernel compilations. > Looking forward to it. It might be about the Software Freedom > Conservancy / Christoph Hellwig copyright infringement case against > VMware, Inc., nei? (There was some discussion of that suit on the ex-VA > Linux Systems mailing list, involving among other people Jeremy Allison, > who's on the Board of Directors of the Conservancy.) > >
No - it is about the technology. I'm compiling kernels after tinkering with the scheduler and other kernel internals. So I set up a virtualbox to do this. When I do, I followed the Manjaro instructions located here.
https://wiki.manjaro.org/index.php/Virtualbox ~~~~~~~~~~~~~~~~~~~~~~ No some of this I'm not understanding. Virtualization is built into the hardware, so why do I have to use these OS and Kernel specific packages.
It will then be necessary to select the appropriate *Virtualbox Host Module* to install, depending on the kernel version currently being run. Rather like installing a driver, doing so will ensure that Virtualbox is able to run properly. For example, where running kernel 3.7, the appropriate number would be entered to install the following module:
uname -r
You will have something like : /3.7.4-1-MANJARO/. It means that the kernel is /linux37/. Then install it with
sudo pacman -S linux/37/-virtualbox-host-modules
Once the installation has completed, it will then be necessary to add the /Virtualbox Module/ to your kernel. *The easy way is to simply reboot your system*. Otherwise, to start using Virtualbox immediately, enter the following command:
sudo modprobe vboxdrv
~~~~~~~~~~~~~~~~~~~~~~~~~
And more immediate to my problem, I'm HACKING the kernel. So if I make Kernel changes, will that break the virtualbox, regardless of any changes in the kernel.
I downloaded the latest kernel from kernel.org and did a compile and it won't boot, and I'm not sure why. So I need to eliminate this as a possible problem. I doubt it, but I don't know.
Ruben
|
|