Hi, indeed your file is not accessible "crw------- 1 root root 10, 56 avril 27 13:44 /dev/vboxdrvu"
should really be "crw-rw-rw- 1 root root 10, 55 apr 19 16:08 /dev/vboxdrvu" so, a chmod 666 /dev/vboxdrvu might fix the issue (until reboot?) you might consider adding your user to vboxusers group. cheers, G. Il Mercoledì 27 Aprile 2016 16:21, Jean-Philippe MENGUAL <jpmeng...@hypra.fr> ha scritto: Hi, Sorry for lag, I had issues to explain to the user I'm helping. Le 21/04/2016 08:50, Gianfranco Costamagna a écrit : > Hi, > > can you please try to run > # ls -l /dev/vbox* > thanks! --------------- crw------- 1 root root 10, 57 avril 27 13:44 /dev/vboxdrv crw------- 1 root root 10, 56 avril 27 13:44 /dev/vboxdrvu crw------- 1 root root 10, 55 avril 27 13:44 /dev/vboxnetctl /dev/vboxusb: total 0 drwxr-x--- 2 root vboxusers 80 avril 27 13:44 002 Thanks for your help, Regards, > G. > > > > > Il Giovedì 21 Aprile 2016 0:00, Jean-Philippe MENGUAL <jpmeng...@hypra.fr> ha > scritto: > Hi, > > My kernel is purely a Debian kernel. I did nothing on it (not speificc > settings, etc). What should I do from the topic? Build a new kernel? It > seems to refer so bu,ld options, but I don't build my own kernel. I'm on > 3.16-4. > > For vboxnet0, it's because I set nic2 to host-only with host-only > adapter set to vboxnet0. But I may change this. > > Regards, > > > Le 20/04/2016 23:10, Gianfranco Costamagna a écrit : >> Hi, would be possible to check this? >> https://forums.virtualbox.org/viewtopic.php?f=7&t=60447 >> >> you might have some strange kernel configuration, according to the log you >> have an unaccessible virtualbox device. >> >> cheers, >> >> G. >> >> >> >> >> Il Mercoledì 20 Aprile 2016 21:22, Jean-Philippe MENGUAL >> <jpmeng...@hypra.fr> ha scritto: >> Oh strange! Sorry. Here's a new trial. >> >> Regards, >> >> >> >> Le 20/04/2016 20:21, Gianfranco Costamagna a écrit : >>> the log is empty... >>> I can't look at it! >>> >>> >>> >>> g. >>> >>> >>> >>> >>> Il Mercoledì 20 Aprile 2016 20:13, Jean-Philippe MENGUAL >>> <jpmeng...@hypra.fr> ha scritto: >>> Yes I have it and I updated it. I believed it was the problem, but... it >>> doesn't seem. >>> >>> Regards, >>> >>> >>> Le 20/04/2016 15:03, Gianfranco Costamagna a écrit : >>>> Hi, do you have the ext-pack installed? Did you update it? >>>> >>>> g. >>>> >>>> >>>> >>>> >>>> Il Mercoledì 20 Aprile 2016 15:00, Jean-Philippe MENGUAL >>>> <jpmeng...@hypra.fr> ha scritto: >>>> >>>> >>>> >>>> Package: virtualbox >>>> Version: 4.3.36-dfsg-1+deb8u1 >>>> Severity: important >>>> >>>> Dear Maintainer, >>>> >>>> *** Reporter, please consider answering these questions, where >>>> appropriate *** >>>> >>>> * What led up to the situation? >>>> >>>> Hi upgraded from 4.3.32 to 4.3.36. >>>> >>>> * What exactly did you do (or not do) that was effective (or >>>> ineffective)? >>>> >>>> After several failures, where I removed hdd (closemedium disk), >>>> re-attached and >>>> re-registered it, with vdi file, etc., I re-built a full new VM. Removed >>>> ~/.VirtualBox and ^ÃirtualBox VMs. Then: >>>> VBoxManage createvm --name xp --ostype WindowsXP --register >>>> VBoxManage modifyvm xp --memory "2000" --acpi on --boot1 dvd --boot2 >>>> disk --boot3 net --nic1 nat --nic2 hostonly --hostonlyadapter2 vboxnet0 >>>> --audio pulse >>>> >>>> VBoxManage storagectl xp --name ide --add ide >>>> VBoxManage storageattach xp --storagectl ide --port 0 --device 0 --type >>>> disk --medium ./xp2.vdi >>>> VBoxManage storageattach xp --storagectl ide --port 0 --device 0 --type >>>> hdd --medium ./xp2.vdi >>>> VBoxManage storageattach xp --storagectl sata --port 0 --device 1 --type >>>> dvddrive --medium host:/dev/sr0 >>>> >>>> VBoxManage storageattach xp --storagectl ide --port 0 --device 0 --type >>>> hdd --medium ./xp2.vdi >>>> VBoxManage storageattach xp --storagectl sata --port 0 --device 1 --type >>>> dvddrive --medium host:/dev/sr0 >>>> >>>> * What was the outcome of this action? >>>> >>>> Here's attached file cannot be closed because it is still attached to 1 >>>> virtual machines. Nonsense, since I've no >>>> other sessions, a single VM, a single disk. >>>> >>>> * What outcome did you expect instead? >>>> >>>> Should start VM. >>>> >>>> *** End of the template - remove these template lines *** >>>> >>>> Thanks for your help. I reproduce on 5.0 here, on testing. >>>> >>>> Ready to give you any needed info. >>>> >>>> Regards, >>>> >>>> >>>> -- System Information: >>>> Debian Release: 8.4 >>>> APT prefers stable-updates >>>> APT policy: (500, 'stable-updates'), (500, 'stable') >>>> Architecture: amd64 (x86_64) >>>> Foreign Architectures: i386 >>>> >>>> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) >>>> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) >>>> Shell: /bin/sh linked to /bin/dash >>>> Init: systemd (via /run/systemd/system) >>>> >>>> Versions of packages virtualbox depends on: >>>> ii adduser 3.113+nmu3 >>>> ii libc6 2.19-18+deb8u4 >>>> ii libcurl3-gnutls 7.38.0-4+deb8u3 >>>> ii libgcc1 1:4.9.2-10 >>>> ii libgsoap5 2.8.17-1 >>>> ii libpng12-0 1.2.50-2+deb8u2 >>>> ii libpython2.7 2.7.9-2 >>>> ii libsdl1.2debian 1.2.15-10+b1 >>>> ii libssl1.0.0 1.0.1k-3+deb8u4 >>>> >>>> ii libvncserver0 0.9.9+dfsg2-6.1+deb8u1 >>>> ii libvpx1 1.3.0-3 >>>> ii libx11-6 2:1.6.2-3 >>>> ii libxcursor1 1:1.1.14-1+b1 >>>> ii libxext6 2:1.3.3-1 >>>> ii libxml2 2.9.1+dfsg1-5+deb8u1 >>>> ii libxmu6 2:1.1.2-1 >>>> ii libxt6 1:1.1.4-1+b1 >>>> ii python 2.7.9-1 >>>> ii python2.7 2.7.9-2 >>>> pn python:any <none> >>>> ii virtualbox-dkms 4.3.36-dfsg-1+deb8u1 >>>> ii zlib1g 1:1.2.8.dfsg-2+b1 >>>> >>>> Versions of packages virtualbox recommends: >>>> ii libgl1-mesa-glx [libgl1] 10.3.2-1+deb8u1 >>>> ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 >>>> ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 >>>> ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 >>>> ii virtualbox-qt 4.3.36-dfsg-1+deb8u1 >>>> Versions of packages virtualbox suggests: >>>> pn vde2 <none> >>>> ii virtualbox-guest-additions-iso 4.3.18-3 >>>> >>>> -- no debconf information >>> >>>> >>> >> > -- Jean-Philippe MENGUAL HYPRA, progressons ensemble Tél.: 01 84 73 06 61 Mail: cont...@hypra.fr Site Web: http://hypra.fr
