Ubuntu 20.04 server guest suspended, resumed and Aborted

Discussions related to using VirtualBox on Linux hosts.
Post Reply
JDaus
Posts: 3
Joined: 24. Oct 2021, 10:51

Ubuntu 20.04 server guest suspended, resumed and Aborted

Post by JDaus »

Hi all,

I have a headless debian host with several debian guests and a win10 host as well, all running without issue.

The Ubuntu VM runs fine whilst i have its VM window open (even if this is started via xwindows forwarding to the windows VM). the issue is when i close the VM window and choose "Continue running in the background", the VM will often suspend>resume>Abort right away or within 30 minutes of closing the window.

I have followed information on disabling all ubuntu's suspend and hybernate features (can't find the url right now) and im using the server version of ubuntu rather than the desktop so i presume it should be setup to not suspend anyway i would think.

Code: Select all

00:00:11.995159 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007fd5f0000000 w=800 h=600 bpp=32 cbLine=0xC80 flags=0x1 origin=0,0
00:00:15.407153 VMMDev: Guest Additions information report: Version 6.1.34 r150636 '6.1.34_Ubuntu'
00:00:15.407211 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x00053100 (Linux >= 2.6, 64-bit)
00:00:15.407295 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:15.407355 VMMDev: vmmDevReqHandler_HeartbeatConfigure: No change (fHeartbeatActive=false)
00:00:15.407397 VMMDev: Heartbeat flatline timer set to trigger after 4 000 000 000 ns
00:00:15.407447 VMMDev: Guest Log: vgdrvHeartbeatInit: Setting up heartbeat to trigger every 2000 milliseconds
00:00:15.415617 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:15.417161 VMMDev: Guest Log: vboxguest: Successfully loaded version 6.1.34_Ubuntu r150636
00:00:15.417202 VMMDev: Guest Log: vboxguest: misc device minor 59, IRQ 20, I/O port d040, MMIO at 00000000f0400000 (size 0x400000)
00:00:15.723408 IEM: rdmsr(0x619) -> #GP(0)
00:00:15.997384 AC97: Reset
00:00:15.997439 AC97: Mixer reset (EAID=0x809, EACS=0x9)
00:00:15.997457 AC97: Record select to left=mic, right=mic
00:00:15.997925 AC97: Reset
00:00:15.997949 AC97: Mixer reset (EAID=0x809, EACS=0x9)
00:00:15.997958 AC97: Record select to left=mic, right=mic
00:00:16.001598 AC97: Record select to left=mic, right=mic
07:06:51.934219 VUSB: Disabled '00007fd6184126e0[proxy 0e8d:1806]' remote wakeup for configuration 0
07:06:51.935152 VUSB: Attached '00007fd6184126e0[proxy 0e8d:1806]' to port 2 on RootHub#1 (HighSpeed)
07:06:56.924277 Changing the VM state from 'RUNNING' to 'SUSPENDING'
07:06:56.929765 AIOMgr: Endpoint for file '/store/VMs/Ubuntu-20.04-arm/Ubuntu-20.04-arm.vdi' (flags 000c0781) created successfully
07:06:56.985841 PDMR3Suspend: 61 446 720 ns run time
07:06:56.985894 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
07:06:56.985915 Console: Machine state changed to 'Paused'
07:07:01.056383 Changing the VM state from 'SUSPENDED' to 'RESUMING'
07:07:01.056886 AIOMgr: Endpoint for file '/store/VMs/Ubuntu-20.04-arm/Ubuntu-20.04-arm.vdi' (flags 000c0723) created successfully
07:07:01.062693 Changing the VM state from 'RESUMING' to 'RUNNING'
07:07:01.062732 Console: Machine state changed to 'Running'
What isn't shown in the log files is that the state ends up as "Failed"

and another log from a different day

Code: Select all

00:00:16.673406 AC97: Record select to left=mic, right=mic
00:06:22.773190 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:06:22.780867 AIOMgr: Endpoint for file '/store/VMs/Ubuntu-20.04-arm/Ubuntu-20.04-arm.vdi' (flags 000c0781) created successfully
00:06:22.815900 PDMR3Suspend: 42 562 906 ns run time
00:06:22.815982 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:06:22.816004 Console: Machine state changed to 'Paused'
00:06:25.934282 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:06:25.934713 AIOMgr: Endpoint for file '/store/VMs/Ubuntu-20.04-arm/Ubuntu-20.04-arm.vdi' (flags 000c0723) created successfully
00:06:25.940447 Changing the VM state from 'RESUMING' to 'RUNNING'
00:06:25.940481 Console: Machine state changed to 'Running'
00:08:08.587822 VUSB: Disabled '00007f1640412690[proxy 0e8d:1806]' remote wakeup for configuration 0
00:08:08.588697 VUSB: Attached '00007f1640412690[proxy 0e8d:1806]' to port 2 on RootHub#1 (HighSpeed)
00:09:58.505848 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:09:58.512741 AIOMgr: Endpoint for file '/store/VMs/Ubuntu-20.04-arm/Ubuntu-20.04-arm.vdi' (flags 000c0781) created successfully
00:09:58.541574 PDMR3Suspend: 35 580 883 ns run time
00:09:58.541650 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:09:58.541677 Console: Machine state changed to 'Paused'
00:10:01.576652 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:10:01.577032 AIOMgr: Endpoint for file '/store/VMs/Ubuntu-20.04-arm/Ubuntu-20.04-arm.vdi' (flags 000c0723) created successfully
00:10:01.582710 Changing the VM state from 'RESUMING' to 'RUNNING'
00:10:01.582749 Console: Machine state changed to 'Running'
the server ends up in a "Failed" state and needs to be booted each time.

The USB device is likely the DVD writer, but i cannot work out how to figure this out.

ubuntu is running the Automatic Ripping Machine (ARM) software and has Guest Additions Version 6.1.34 r150636 '6.1.34_Ubuntu' installed.

if you need complete logs i am happy to provide.

anyone have any ideas??? its been anoying me for weeks.
JDaus
Posts: 3
Joined: 24. Oct 2021, 10:51

Re: Ubuntu 20.04 server guest suspended, resumed and Aborted

Post by JDaus »

found the info on disabling sleep and hibernation ...
https://linux-tips.us/how-to-disable-sl ... tu-server/
Post Reply