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 Toolybird (Toolybird) - Sunday, 16 April 2023, 02:01 GMT
Opened by Tim Summerer (Summerer) - Sunday, 29 March 2020, 09:19 GMT
Last edited by Toolybird (Toolybird) - Sunday, 16 April 2023, 02:01 GMT
|
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
Closed by Toolybird (Toolybird)
Sunday, 16 April 2023, 02:01 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Sunday, 16 April 2023, 02:01 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
> 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.
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.