Bug 1188189 - After an update to kernel 5.13.0, VirtualBox guest does not start
Summary: After an update to kernel 5.13.0, VirtualBox guest does not start
Status: RESOLVED DUPLICATE of bug 1188105
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Virtualization:Other (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Larry Finger
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-10 19:34 UTC by James Moe
Modified: 2021-07-13 15:00 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
VBox log of failed start (219.33 KB, text/x-log)
2021-07-10 19:34 UTC, James Moe 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Moe 2021-07-10 19:34:11 UTC 
Created attachment 850903 [details]
VBox log of failed start

tumbleweed 20210708

----[ from zypper ]----
The following 4 NEW packages are going to be installed:
  kernel-default-5.13.0-1.2 libtss2-rc0 systemd-rpm-macros virtualbox-kmp-default-6.1.22_k5.13.0_1-3.8
----[ end ]----

After the above updates, a VirtualBox v6.1.22 guest does not start. It fails with a "critical error." VBox.log is attached.
Comment 1 Larry Finger 2021-07-13 15:00:42 UTC 
This is a duplicate of #1188105.

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