Am 04.02.2017 um 23:48 schrieb Tomasz Torcz:
On Sat, Feb 04, 2017 at 10:34:39PM +, gilesaj wrote:
The only reason I posted here is because that is what is in the text of the
error.
root@ns527415:~#journalctl -xn-- The start-up result is done.Feb 04 15:31:03
ns527415.ip-192-99-6.net
On Sat, Feb 04, 2017 at 10:34:39PM +, gilesaj wrote:
> The only reason I posted here is because that is what is in the text of the
> error.
>
> root@ns527415:~#journalctl -xn-- The start-up result is done.Feb 04 15:31:03
> ns527415.ip-192-99-6.net systemd[1]: Starting LSB: VirtualBox Linux
The only reason I posted here is because that is what is in the text of the
error.
root@ns527415:~#journalctl -xn-- The start-up result is done.Feb 04 15:31:03
ns527415.ip-192-99-6.net systemd[1]: Starting LSB: VirtualBox Linux kernel
module...-- Subject: Unit virtualbox.service has begun with
Am 04.02.2017 um 22:00 schrieb gilesaj:
During installation of VirtualBox I got this error. It seems to be a
problem with the way the OVH dedicated server displays the Linux Kernel
name as 3.14.32--grs-ipv6-64.
how is that a systemd problem at all?
contact OVH and/or Oracle
Hello
During installation of VirtualBox I got this error. It seems to be a problem
with the way the OVH dedicated server displays the Linux Kernel name as
3.14.32--grs-ipv6-64.
-
Loading new virtualbox-4.3.36 DKMS files...First
ok, thanks for input. Have managed to isolate it to a mismatch arising
from kernel update.
Thanks
Isla
On 3 February 2017 at 17:50, Lennart Poettering
wrote:
> On Fri, 03.02.17 09:23, Isla Finney (dr.isla.fin...@gmail.com) wrote:
>
> >
> > Feb 03 08:28:35 debian