Bug 961151

Summary:	Virtualbox+Tumbleweed+GNOME no boot "Failed to start LSB: VirtualBox Linux Additions kernel modules. See 'systemctl add vboxadd.service' for details."
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Forgotten User d8OdeRBJrK <forgotten_d8OdeRBJrK>
Component:	GNOME	Assignee:	E-mail List <gnome-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	dimstar, forgotten_d8OdeRBJrK
Version:	Current
Target Milestone:	---
Hardware:	VMWare
OS:	Windows 10
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	boot screen after install

Description Forgotten User d8OdeRBJrK 2016-01-08 13:24:05 UTC

Created attachment 661217 [details]
boot screen after install

Hello,

After installing Tumbleweed on Virtual KVM machine with GNOME Desktop it gets stuck on first boot.

It says "Failed to start LSB: VirtualBox Linux Additions kernel modules. See 'systemctl add vboxadd.service' for details."

the machine is set to OpenSuse 64bit setup, 2 cores on 1 socket, 4 GB RAM, 8 GB vdi device.

If I install it with KDE Desktop environment it is working without any issues.

I attach a screenshot of the point where it is stuck.

I downloaded the current iso from 
http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Current.iso

Regards,

Af0x

Comment 1 Dominique Leuenberger 2016-01-08 13:28:43 UTC

almost 100% a dup of bug 929697

*** This bug has been marked as a duplicate of bug 929697 ***

Comment 2 Dominique Leuenberger 2016-01-08 13:29:20 UTC

oh wait.. you said you installed in a KVM? not VirtualBox?

Comment 3 Dominique Leuenberger 2016-01-08 13:31:00 UTC

Please provide the output of the systemd journal (journalctl)

and also the X.org log file (either in /var/log or /var/lib/gdm/.local/share/xorg/xorg.0.log

Comment 4 Forgotten User d8OdeRBJrK 2016-01-08 13:36:37 UTC

hello, i run virtualbox on Windows 10 so i guess it´s virtualbox?

sorry for the duplicate. I tried to search this error in the bugtracker.

stupid question: how can I provide anything when it gets stuck on startup?

Regards,

Af0x

Comment 5 Dominique Leuenberger 2016-01-08 13:42:31 UTC

(In reply to Anon Ymous from comment #4)
> hello, i run virtualbox on Windows 10 so i guess it´s virtualbox?

ok, we're on virtualbox.. then it IS a duplicate of bug 929697

> sorry for the duplicate. I tried to search this error in the bugtracker.
> 
> stupid question: how can I provide anything when it gets stuck on startup?

Boot - let it hang, reset, boot to 1 user mode add a '1' to the boot parameters. The system will start without graphical interface and you can extract logs.

But in this case it's not needed... as we know it's a duplicate of the other bug

*** This bug has been marked as a duplicate of bug 929697 ***