VirtualBox W7 guest not resuming

Kevin Oberman rkoberman at gmail.com
Mon Sep 3 17:02:26 UTC 2018


On Mon, Sep 3, 2018 at 7:28 AM Adam <amvandemore at gmail.com> wrote:

> On Mon, Sep 3, 2018 at 1:36 AM Kevin Oberman <rkoberman at gmail.com> wrote:
>
>> On Sun, Sep 2, 2018 at 6:45 PM Adam <amvandemore at gmail.com> wrote:
>>
>>> On Sun, Sep 2, 2018 at 8:30 PM Kevin Oberman <rkoberman at gmail.com>
>>> wrote:
>>>
>>>> I can no longer sresume my Windows 7 virtual system. I get the error:
>>>> Failed to open a session for the virtual machine Win7.
>>>>
>>>> Failed to load unit 'vga' (VERR_SSM_LOADED_TOO_MUCH).
>>>>
>>>> Result Code: NS_ERROR_FAILURE (0x80004005)
>>>> Component: ConsoleWrap
>>>> Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
>>>>
>>>> I suspect this may be tied to my upgrade to drm-stabe-kmod-g20180822
>>>> back
>>>> on Aug. 23. I have not booted my system since then, so my boot last
>>>> night
>>>> loaded the kernel module for the first time.
>>>>
>>>> I have no idea I m guessing that this is a drm kernel issue, but I am
>>>> not
>>>> at all sure, so am sending this to both lists.
>>>> 11.2-STABLE r337832 All ports are current.
>>>>
>>>
>>> I'm not sure this is related to the drm module but maybe.  Does the
>>> guest log contain any clues?
>>>
>>> --
>>> Adam
>>>
>>
>> Rolling back drm-stable-kmod to the last version (*477762*
>> <https://svnweb.freebsd.org/ports?view=revision&revision=477762>) fixed
>> the problem.
>>
>> While it is possible that something that the vbox port was doing
>> something wrong that the prior versions were allowing, I think that is
>> quite unlikely. It is almost certainly the drm module that is the culprit.
>>
>> Where can I find the guest log? O have searched the C: disk for vbox.log
>> files and find none.
>>
>> Tomorrow I will
>>
>
> The guest Vbox logs are on the host-side, for me they reside at:
>
> ~/VirtualBox\ VMs/Windows/Logs/
>
> My windows 7 works fine with the latest drm, but I don't ever try to
> resume either.  I always cold boot, and do my snapshots from ZFS.
>
> --
> Adam
>

I have nothing in my VirtualBox VMs directory other then my vdi file for
the Windows7 VM. A bit of searching led me to an Oracle article that
pointed me to ~/.VirtualBox/Machines/VM_NAME/Logs and there they were.

The failure is when the guest extensions load.
00:00:15.003600 VMMDev: Guest Additions information report: Interface =
0x00010004 osType = 0x00037000 (Windows 7, 32-bit)
00:00:15.003777 AssertLogRel
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.18/src/VBox/VMM/VMMR3/SSM.cpp(6140)
int ssmR3DataReadRecHdrV2(PSSMHANDLE): !pSSM->u.Read.fEndOfData
00:00:15.003789 SSM: LoadExec failed for 'vga' instance #0 (version 19,
pass 0xffffffff): VERR_SSM_LOADED_TOO_MUCH
00:00:15.003803 SSM: Unit at 0x6c64f270, current position: offUnit=0x1ab4
offUnitUser=0x2731
00:00:15.003811 VMSetError:
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.18/src/VBox/VMM/VMMR3/SSM.cpp(8707)
int ssmR3LoadExecV2(PVM, PSSMHANDLE); rc=VERR_SSM_LOADED_TOO_MUCH
00:00:15.003815 VMSetError: Failed to load unit 'vga'

The problem goes away when I downgrade the drm kernel modules. I will now
try shutting down the VM and restarting wit the latest kernel modules.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


More information about the freebsd-emulation mailing list