FS#42367 - [virtualbox] VMs inoperable if started after host suspends to RAM

Attached to Project: Community Packages
Opened by Winslow Dalpe (winslow) - Monday, 13 October 2014, 22:22 GMT
Last edited by Sébastien Luttringer (seblu) - Friday, 07 November 2014, 09:40 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture x86_64
Severity Low
Priority Low
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

This issue has been confirmed by me to happen in 4.3.14, 4.3.16, and 4.3.18-1. I'm not sure how much farther is goes back because I just started using suspend to RAM recently.

After my machine wakes from being suspended to RAM, I find that none of my newly started virtualbox guests function correctly. The symptoms seem to vary. Most commonly, the guest machine will get past the GRUB selection menu, then display

tsc: Fast TSC calibration failed

And then just hang. The machine can be terminated, but at no point does it make any further progress in the booting process.

Rebooting my host machine resolves the issues, and the VMs continue working until my next Suspend. Nothing strange appears in the output of dmesg or journalctl before or after suspending and running virtualbox.

Attached is my VBox.log from my most recent incident. Nothing immediately stands out to me, with the exception of this final segment prior to me force shutting down the guest:

00:00:03.045861 Guest Log: BIOS: Booting from Hard Disk...
00:00:05.832522 Guest Log: BIOS: KBD: unsupported int 16h function 03
00:00:05.832522 Guest Log: BIOS: AX=0305 BX=0000 CX=0000 DX=0000
00:00:05.859190 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=81
00:00:05.859190 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=81
00:00:05.859190 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=82
00:00:05.859190 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=82
00:00:05.859190 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=83
00:00:05.859190 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=83
00:00:05.859190 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=84
00:00:05.859190 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=84
00:00:05.859190 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=85
00:00:05.859190 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=85
00:00:05.859190 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=86
00:00:05.859190 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=86
00:00:05.872523 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=87
00:00:05.872523 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=87
00:00:05.872523 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=88
00:00:05.872523 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=88
00:00:05.872523 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=89
00:00:05.872523 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=89
00:00:05.872523 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8a
00:00:05.872523 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8a
00:00:05.872523 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8b
00:00:05.872523 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8b
00:00:05.872523 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8c
00:00:05.872523 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8c
00:00:05.872523 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8d
00:00:05.872523 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8d
00:00:05.872523 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8e
00:00:05.872523 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8e
00:00:05.872523 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8f
00:00:05.872523 Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8f
00:00:06.165856 PIT: mode=2 count=0x4a9 (1193) - 1000.15 Hz (ch=0)
00:00:06.965856 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0)

I had created these forum posts (Arch and Virtualbox) regarding this topic. I was told that Arch's package of Virtualbox would not be supported on their forums, and so I am raising the issue here now.

https://bbs.archlinux.org/viewtopic.php?id=188147
https://forums.virtualbox.org/viewtopic.php?f=7&t=64126
   VBox.log (82.8 KiB)
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Friday, 07 November 2014, 09:40 GMT
Reason for closing:  Upstream
Comment by Sébastien Luttringer (seblu) - Saturday, 25 October 2014, 00:05 GMT
Are you able to reproduce with virtualbox-bin?
Comment by Winslow Dalpe (winslow) - Saturday, 25 October 2014, 05:12 GMT
Yes, I can reproduce with the AUR package virtualbox-bin version 4.3.18-1

The issue also continues with the latest arch packages as well.

Attached are logs from virtualbox-bin.
   VBox.PreSuspend.log (96.2 KiB)
   VBox.PostSuspend.log (95.3 KiB)
Comment by Sébastien Luttringer (seblu) - Saturday, 25 October 2014, 18:23 GMT
virtualbox-bin is a build provided by upstream, you can comment in the vbox forum thread that you tested with the ".run" version and you have the same issue.
I don't think we will be able to deal with this downstream. It works for me.

Loading...