Arch linux guest crash after windows 10 host resume from sleep

[lindeshun]

My arch linux guest has 1G ram, with no X installed. Everytime my windows host goes to sleep and resume, this guest is PAUSED. When I try to resume it, the whole virtualbox interface just freeze, and I have to use windows task manager to kill the virtualbox process.

However, if I pause the guest manually before the windows host goes to sleep, after the host resume, the guest can be resumed successfully!

I also have a windows 10 guest and a ubuntu 16.04 guest, neither of them have this problem. So I guess my arch guest is not set correctly?But I tried to search arch linux wiki and this forum, with no avail.

Below is part of the log file, which I think might be helpful(the log just end there). the whole log files are also uploaded.

Code: Select all

00:12:52.179417 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:12:52.179432 Console: Machine state changed to 'Paused'
00:12:52.184240 Audio: Device configuration of driver 'DSoundAudio' has changed
00:13:11.803838 Resuming VM execution, reason 'host resume'
00:13:11.804352 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:13:11.805062 AIOMgr: Endpoint for file 'C:\Users\lindeshun\VirtualBox VMs\archlinux\Snapshots/{98511e59-f1fc-4a0a-a9bd-ef106ee50085}.vdi' (flags 000c0723) created successfully

Not a native English speaker, sorry for the wrong grammar.

[lindeshun]

I did some tests, and found an interesting result!

If I start the arch linux guest, pause it manually and resume it right away, the problem is gone! After did this, whenever I resume my windows host from sleep, the guest just keep running without error. So, I guess this might be a bug of virtualbox?

[scottgus1]

I don't see anything weird in the log. Could be a bug. Try a report on the Bugtracker, with a link back to this topic and a zipped vbox.log of the VM when you can get it to crash, and another log where you can get it to stay on.

[lindeshun]

I don't see anything weird in the log. Could be a bug. Try a report on the Bugtracker, with a link back to this topic and a zipped vbox.log of the VM when you can get it to crash, and another log where you can get it to stay on.

Thanks for your advice, I just report the bug.