[Pkg-virtualbox-devel] Bug#798527: virtualbox fails to work with systemd

[shirish शिरीष]

Reply in-line :-

On 9/10/15, Gianfranco Costamagna <costamagnagianfranco at yahoo.it> wrote:
> Hi Ritesh,

Hi Gianfranco,

Thank you for taking time and replying on the bug so fast.

<snipped>

> well, the user experience might be bad, bad graphics, 640x480 mode (or
> similar) and so on.
>
> Unfortunately when people play with custom kernels there is no guarantee
> that dkms will work,
> so I'm not sure forcing the dkms package is a good opinion

umm.... there seems to be a mis-understanding somewhere.

 I am not using any custom kernel, I am using the kernel provided by
debian itself.

[$] dpkg -l linux-image-4.1.0-2-amd64

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                           Version              Architecture
      Description
+++-==============================-====================-====================-=================================================================
ii  linux-image-4.1.0-2-amd64      4.1.6-1              amd64
      Linux 4.1 for 64-bit PCs

┌─[shirish at debian] - [~] - [4036]
└─[$] apt-cache policy linux-image-4.1.0-2-amd64
linux-image-4.1.0-2-amd64:
  Installed: 4.1.6-1
  Candidate: 4.1.6-1
  Version table:
 *** 4.1.6-1 600
        600 http://httpredir.debian.org/debian testing/main amd64 Packages
          1 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

 So I do not know where or in which context 'custom kernels'  have been used.

Secondly, I had used virtualbox  quite some time back, in the somewhat
g/olden days, all of the different parts of virtualbox used to pull in
all the other parts as well.

I am interested to know why that policy or way was changed. If for
nothing else, then simply to understand what use-case/reason lead to
the way it is now.

> (yes, people should know how to play with custom kernels, nevermind).
>
> So I have no opinion, either way some users might complain.
>
> But the answer should be "yes, virtualbox runs even without the vboxdrv
> driver"
> (at least IIRC)

As shared before, had used virtualbox before but not lot of time.

The last time I had used virtualbox I used the vboxdrv driver to get a
the status of the various modules. Something like :-

$sudo /etc/init.d/vboxdrv status

and it would give on the lines of :-

VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are loaded

and these are needed by some third-party apps.

Also if there is alternate way/command which also would tell/share
which modules are loaded, would be happy to know about that as well.

If Ritesh or you (Gianfranco) would be able to share some idea or
status about the vboxdrv then I would be in a position to know what
next steps I would have to take.

>
> cheers,
>
> Gianfranco

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8