| 1 |
On Sun, 27 Sep 2009 14:51:45 -0400, "Walter Dnes" <waltdnes@××××××××.org> |
| 2 |
wrote: |
| 3 |
> On Sun, Sep 27, 2009 at 09:28:03AM -0400, Walter Dnes wrote |
| 4 |
> |
| 5 |
> I apologize for wasting everybody's time. I didn't RTFM thoroughly |
| 6 |
> enough. Apparently, with the Sun install, and any time you build a new |
| 7 |
> kernel, you have to "/etc/init.d/vboxdrv setup". The result is... |
| 8 |
> |
| 9 |
> [d530][root][~] /etc/init.d/vboxdrv setup |
| 10 |
> * Stopping VirtualBox kernel module ... |
| 11 |
> * [ ok ] * Recompiling VirtualBox kernel module ... |
| 12 |
> * [ ok ] * Starting VirtualBox kernel module ... |
| 13 |
> |
| 14 |
> [d530][root][~] |
| 15 |
> |
| 16 |
> ...and on rebooting, I get... |
| 17 |
> |
| 18 |
> * Starting VirtualBox kernel module ... * [ ok ] |
| 19 |
> |
| 20 |
> While I'm at it, here's what I have in my .config regarding KVM. |
| 21 |
Since |
| 22 |
> I don't use KVM, can I turn off all the options here without affecting |
| 23 |
> virtualbox? |
| 24 |
> |
| 25 |
> # CONFIG_CRYPTO_HW is not set |
| 26 |
> CONFIG_HAVE_KVM=y |
| 27 |
> CONFIG_HAVE_KVM_IRQCHIP=y |
| 28 |
> CONFIG_VIRTUALIZATION=y |
| 29 |
> CONFIG_KVM=y |
| 30 |
> CONFIG_KVM_INTEL=y |
| 31 |
> # CONFIG_KVM_AMD is not set |
| 32 |
> # CONFIG_KVM_TRACE is not set |
| 33 |
> # CONFIG_LGUEST is not set |
| 34 |
> # CONFIG_VIRTIO_PCI is not set |
| 35 |
> # CONFIG_VIRTIO_BALLOON is not set |
| 36 |
> # CONFIG_BINARY_PRINTF is not set |
| 37 |
|
| 38 |
kvm and virtualbox are not related, you can turn those on if you don't |
| 39 |
need kvm. Virtualbox will continue working. |
| 40 |
-- |
| 41 |
Jesús Guerrero |
Archives