Ubuntu guest aborting on saving state

[Tobiwan]

Hi,

I'm running an Ubuntu 17.10 guest on a Windows 10 Host with VirtualBox 5.1.30
When I try to save the machine state, the guest ends up in the "Aborted" state so I am unable to resume from the saved state
If I send a shut-down signal, it shuts down cleanly

Attached are the logs of a clean start followed by an attempt to save the machine state, and for convenience here's the last few lines.

Code: Select all

00:02:29.334109 VMMDev: Guest Additions capability report: (0x0 -> 0x1) seamless: yes, hostWindowMapping: no, graphics: no
00:02:29.334322 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:02:29.334349 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:02:29.334357 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:02:29.334361 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:02:34.502257 VMMDev: Guest Log: VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-54
00:02:34.502311 VMMDev: Guest Log: VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-54.
00:02:41.017557 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:02:41.081065 AIOMgr: Endpoint for file 'H:\dev\Ubuntu 17.10 Artful (64bit).vdi' (flags 000c0781) created successfully
00:02:41.119087 PDMR3Suspend: 101 482 226 ns run time
00:02:41.119115 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:02:41.119131 Console: Machine state changed to 'Paused'
00:02:45.077076 GUI: Request for close-action to save VM state.
00:02:45.077102 GUI: Passing request to save VM state from machine-logic to UI session.
00:02:45.077424 Console: Machine state changed to 'Saving'
00:02:45.078776 Changing the VM state from 'SUSPENDED' to 'SAVING'
00:02:45.085310 VUSB: Detached 'HidMouse' from port 1
00:02:45.099199 GUI: UIMediumEnumerator: Medium-enumeration finished!

Many thanks for any help you can offer!

Toby

[socratis]

VirtualBox VM 5.1.30 r118389 win.amd64 (Oct 16 2017 10:47:00) release log

Try to upgrade to 5.2.4.

00:00:04.579203 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x5 fAccess=0x2 \Device\HarddiskVolume2\Windows\System32\DriverStore\FileRepository\c0320995.inf_amd64_b17c65b77c4167f1\atikmdag.sys: 
00:00:04.581245 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: cached rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x2 fAccess=0x5 cHits=1 \Device\HarddiskVolume2\Windows\System32\DriverStore\FileRepository\c0320995.inf_amd64_b17c65b77c4167f1\atikmdag.sys

You get a couple of messages about your ATI graphics card. See if you can update or even re-install the drivers.

00:00:04.634914   NumCPUs           <integer> = 0x0000000000000004 (4)
00:00:05.166682 CPUM: Physical host cores: 4

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors, not logical ones. See: CPU Cores versus threads.

00:00:03.458597 File system of 'J:\dev\virtualBox\VBoxGuestAdditions.iso' (DVD) is ntfs
00:00:03.460186 File system of 'H:\dev\virtualBoxVM\Ubuntu 17.10\Snapshots' (snapshots) is ntfs

What's H:\? What's J:\? And always eject your Guest Additions (GAs) CD when you're done installing the GAs.

00:00:10.699991 IEM: rdmsr(0x140) -> #GP(0)
00:00:21.339186 IEM: rdmsr(0x619) -> #GP(0)

I don't particularly like those references (and some more), and I honestly don't know why they're there. Try to disable KVM in the VM Settings » System » Acceleration » set that to either Legacy or None.