On Thursday, February 18, 2016 10:06:25 AM Peter Humphrey wrote:
> On Wednesday 17 February 2016 20:42:44 J. Roeleveld wrote:
> > On Wednesday, February 17, 2016 05:01:51 PM Peter Humphrey wrote:
> --->8
>
> > > > I only have the following set:
> > > > # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
> > > > CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
> > > > CONFIG_VIRT_TO_BUS=y
> > >
> > > Okay. I've tried that and I still get the pop-up notice "VBoxClient: the
> > > VirtualBox kernel service is not running." This is with version 4.3.32.
> > > I'll try later versions and see what happens. Thanks for the info.
> >
> > I actually run 4.3.28 myself at the moment.
>
> Right.
>
> --->8
>
> > One other thing, are you in the "vboxusers" group?
>
> Of course. Also the vboxguest group recently.
>
> > My user is and I have the following devices:
> >
> > % ls -lsa /dev/vbox*
> > 0 crw------- 1 root root 10, 56 Feb 7 13:16 /dev/vboxdrv
> > 0 crw------- 1 root root 10, 55 Feb 7 13:16 /dev/vboxdrvu
> > 0 crw------- 1 root root 10, 54 Feb 7 13:16 /dev/vboxnetctl
> >
> > /dev/vboxusb:
> > total 0
> > 0 drwxr-x--- 3 root vboxusers 60 Feb 7 15:24 .
> > 0 drwxr-xr-x 18 root root 6360 Feb 17 18:13 ..
> > 0 drwxr-x--- 2 root vboxusers 100 Feb 17 18:13 001
> >
> > What do you get for the following:
> >
> > % ls -lsa /dev/vbox*
> > % lsmod | grep vbox
>
> # ls -lsa /dev/vbox*
> 0 crw------- 1 root root 10, 58 Feb 17 16:54 /dev/vboxdrv
> 0 crw------- 1 root root 10, 57 Feb 17 16:54 /dev/vboxdrvu
> 0 crw------- 1 root root 10, 56 Feb 17 16:54 /dev/vboxnetctl
>
> /dev/vboxusb:
> total 0
> 0 drwxr-x--- 3 root vboxusers 60 Feb 17 16:54 .
> 0 drwxr-xr-x 19 root root 3.9K Feb 18 09:40 ..
> 0 drwxr-x--- 2 root vboxusers 80 Feb 18 09:40 002
>
> # ls -lsa /dev/vboxusb/002
> total 0
> 0 drwxr-x--- 2 root vboxusers 80 Feb 18 09:40 .
> 0 drwxr-x--- 3 root vboxusers 60 Feb 17 16:54 ..
> 0 crw-rw---- 1 root vboxusers 189, 130 Feb 17 16:54 003
> 0 crw-rw---- 1 root vboxusers 189, 133 Feb 18 09:40 006
>
> # lsmod | grep vbox
> vboxpci 13106 0
> vboxnetflt 16882 0
> vboxnetadp 17862 0
> vboxdrv 331090 3 vboxnetadp,vboxnetflt,vboxpci
>
> I still can't shake the idea that I don't have my kernel set up right. Do I
> need anything particular in control groups, or name spaces, or anything?
About the kernel: I don't have anything special.
USE-flags:
[I] app-emulation/virtualbox
Installed versions: 4.3.32{tbz2}(03:46:09 PM 11/25/2015)(additions alsa
extensions java opengl pam pulseaudio qt4 sdk udev -doc -headless -libressl -
python -vboxwebsrv -vnc ELIBC="-FreeBSD" PYTHON_TARGETS="python2_7")
What does " dmesg " have to say?
For me:
% dmesg | grep -i vbox
[ 165.950507] vboxdrv: Found 8 processor cores.
[ 165.950787] vboxdrv: fAsync=0 offMin=0x1fe offMax=0xa4f9
[ 165.950828] vboxdrv: TSC mode is 'synchronous', kernel timer mode is
'normal'.
[ 165.950829] vboxdrv: Successfully loaded version 4.3.32 (interface
0x001a000b).
[ 165.978641] vboxpci: pci-stub module not available, cannot detach PCI
devices
[ 165.978643] vboxpci: IOMMU found
I actually updated to 4.3.32 yesterday. VMs are still starting.
How exactly are you starting the VMs?
I do it all with the GUI: /usr/bin/VirtualBox
--
Joost
