Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#66014 - [virtualbox] VMs crash Virtualbox if guest is rebooted after saving VM state to disk

Attached to Project: Community Packages
Opened by Tim Summerer (Summerer) - Sunday, 29 March 2020, 09:19 GMT
Last edited by freswa (frederik) - Sunday, 29 March 2020, 14:09 GMT
Task Type Bug Report
Category Upstream Bugs
Status Assigned
Assigned To Christian Hesse (eworm)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

Description:
Virtual Machines such as Windows 10 or Ubuntu 20.04 (daily snapshot) boot into a black screen and the entire VirtualBox application freezes up (a system freeze/crash might also occur as this causes page fault that the kernel cannot handle).
I have observed this behavior for at least half a year. Therefore, this issue is most likely not a recent change in VirtualBox or the kernel.

NOTE to moderators: This is NOT an ArchLinux issue but since contributing to the bugreport upstream requires an Oracle account, I am reporting this here.


Additional info:
* package versions (not necessarily limited to these major versions):
VirtualBox 6
Linux 5.4
* config and/or log files etc.
attached dmesg output of page fault as file
* link to upstream bug report
https://www.virtualbox.org/ticket/19408

Steps to reproduce:
- Start Virtualbox
- Setup a VM e.g. an Ubuntu VM
- Suspend the VM to disk
- (maybe wait a while)
- start the VM
- trigger a reboot inside the VM
-> Virtualbox will trigger a kernel BUG and the application will become unusable or worse the system might freeze/crash.
This task depends upon

Comment by Christian Hesse (eworm) - Sunday, 29 March 2020, 18:46 GMT
Well the last comment to upstream report end with:

> However, the good news is, I cannot reproduce the problem anymore with the current Trunk bits, revision: r136516 So we need to figure out what changed.

Guess we just have to wait for the next release then.
Comment by Tim Summerer (Summerer) - Wednesday, 15 April 2020, 11:43 GMT
I tried to reproduce the issue on version 6.1.6 r137129 with a Windows 10, Ubuntu 18.04 and Manjaro VM.

I wasn't able to reproduce the behavior by trying once.

I have no idea if a fix regarding the issue was applied in 6.1.6 since the upstream bug report hasn't received an update in 4 weeks.

Loading...