1 |
On Thursday, February 18, 2016 10:06:25 AM Peter Humphrey wrote: |
2 |
> On Wednesday 17 February 2016 20:42:44 J. Roeleveld wrote: |
3 |
> > On Wednesday, February 17, 2016 05:01:51 PM Peter Humphrey wrote: |
4 |
> --->8 |
5 |
> |
6 |
> > > > I only have the following set: |
7 |
> > > > # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set |
8 |
> > > > CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y |
9 |
> > > > CONFIG_VIRT_TO_BUS=y |
10 |
> > > |
11 |
> > > Okay. I've tried that and I still get the pop-up notice "VBoxClient: the |
12 |
> > > VirtualBox kernel service is not running." This is with version 4.3.32. |
13 |
> > > I'll try later versions and see what happens. Thanks for the info. |
14 |
> > |
15 |
> > I actually run 4.3.28 myself at the moment. |
16 |
> |
17 |
> Right. |
18 |
> |
19 |
> --->8 |
20 |
> |
21 |
> > One other thing, are you in the "vboxusers" group? |
22 |
> |
23 |
> Of course. Also the vboxguest group recently. |
24 |
> |
25 |
> > My user is and I have the following devices: |
26 |
> > |
27 |
> > % ls -lsa /dev/vbox* |
28 |
> > 0 crw------- 1 root root 10, 56 Feb 7 13:16 /dev/vboxdrv |
29 |
> > 0 crw------- 1 root root 10, 55 Feb 7 13:16 /dev/vboxdrvu |
30 |
> > 0 crw------- 1 root root 10, 54 Feb 7 13:16 /dev/vboxnetctl |
31 |
> > |
32 |
> > /dev/vboxusb: |
33 |
> > total 0 |
34 |
> > 0 drwxr-x--- 3 root vboxusers 60 Feb 7 15:24 . |
35 |
> > 0 drwxr-xr-x 18 root root 6360 Feb 17 18:13 .. |
36 |
> > 0 drwxr-x--- 2 root vboxusers 100 Feb 17 18:13 001 |
37 |
> > |
38 |
> > What do you get for the following: |
39 |
> > |
40 |
> > % ls -lsa /dev/vbox* |
41 |
> > % lsmod | grep vbox |
42 |
> |
43 |
> # ls -lsa /dev/vbox* |
44 |
> 0 crw------- 1 root root 10, 58 Feb 17 16:54 /dev/vboxdrv |
45 |
> 0 crw------- 1 root root 10, 57 Feb 17 16:54 /dev/vboxdrvu |
46 |
> 0 crw------- 1 root root 10, 56 Feb 17 16:54 /dev/vboxnetctl |
47 |
> |
48 |
> /dev/vboxusb: |
49 |
> total 0 |
50 |
> 0 drwxr-x--- 3 root vboxusers 60 Feb 17 16:54 . |
51 |
> 0 drwxr-xr-x 19 root root 3.9K Feb 18 09:40 .. |
52 |
> 0 drwxr-x--- 2 root vboxusers 80 Feb 18 09:40 002 |
53 |
> |
54 |
> # ls -lsa /dev/vboxusb/002 |
55 |
> total 0 |
56 |
> 0 drwxr-x--- 2 root vboxusers 80 Feb 18 09:40 . |
57 |
> 0 drwxr-x--- 3 root vboxusers 60 Feb 17 16:54 .. |
58 |
> 0 crw-rw---- 1 root vboxusers 189, 130 Feb 17 16:54 003 |
59 |
> 0 crw-rw---- 1 root vboxusers 189, 133 Feb 18 09:40 006 |
60 |
> |
61 |
> # lsmod | grep vbox |
62 |
> vboxpci 13106 0 |
63 |
> vboxnetflt 16882 0 |
64 |
> vboxnetadp 17862 0 |
65 |
> vboxdrv 331090 3 vboxnetadp,vboxnetflt,vboxpci |
66 |
> |
67 |
> I still can't shake the idea that I don't have my kernel set up right. Do I |
68 |
> need anything particular in control groups, or name spaces, or anything? |
69 |
|
70 |
About the kernel: I don't have anything special. |
71 |
|
72 |
USE-flags: |
73 |
|
74 |
[I] app-emulation/virtualbox |
75 |
|
76 |
Installed versions: 4.3.32{tbz2}(03:46:09 PM 11/25/2015)(additions alsa |
77 |
extensions java opengl pam pulseaudio qt4 sdk udev -doc -headless -libressl - |
78 |
python -vboxwebsrv -vnc ELIBC="-FreeBSD" PYTHON_TARGETS="python2_7") |
79 |
|
80 |
|
81 |
What does " dmesg " have to say? |
82 |
|
83 |
For me: |
84 |
% dmesg | grep -i vbox |
85 |
[ 165.950507] vboxdrv: Found 8 processor cores. |
86 |
[ 165.950787] vboxdrv: fAsync=0 offMin=0x1fe offMax=0xa4f9 |
87 |
[ 165.950828] vboxdrv: TSC mode is 'synchronous', kernel timer mode is |
88 |
'normal'. |
89 |
[ 165.950829] vboxdrv: Successfully loaded version 4.3.32 (interface |
90 |
0x001a000b). |
91 |
[ 165.978641] vboxpci: pci-stub module not available, cannot detach PCI |
92 |
devices |
93 |
[ 165.978643] vboxpci: IOMMU found |
94 |
|
95 |
|
96 |
I actually updated to 4.3.32 yesterday. VMs are still starting. |
97 |
|
98 |
How exactly are you starting the VMs? |
99 |
|
100 |
I do it all with the GUI: /usr/bin/VirtualBox |
101 |
|
102 |
-- |
103 |
Joost |