Date: Mon, 3 Sep 2018 09:28:24 -0500 From: Adam <amvandemore@gmail.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: "freebsd-emulation@freebsd.org" <emulation@freebsd.org>, FreeBSD X11 <freebsd-x11@freebsd.org> Subject: Re: VirtualBox W7 guest not resuming Message-ID: <CA%2BtpaK1SAGiJLBannw6J3wAQsxrUb%2BO4NSpRDWZ=_kA4Qp9oww@mail.gmail.com> In-Reply-To: <CAN6yY1tb4=j1rF6t5743Ndh1CZkYrWiyL3YiFAQu5naDDvs9Gw@mail.gmail.com> References: <CAN6yY1uRiG82zYsoaMHBWY=gZZLCeWc=2yrzpHgMr1okPD4FXA@mail.gmail.com> <CA%2BtpaK0m-y_S4yuoh=JnLi=eJGCNYsLbYbJPFwXRksnAoZu5Qg@mail.gmail.com> <CAN6yY1tb4=j1rF6t5743Ndh1CZkYrWiyL3YiFAQu5naDDvs9Gw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 3, 2018 at 1:36 AM Kevin Oberman <rkoberman@gmail.com> wrote:
> On Sun, Sep 2, 2018 at 6:45 PM Adam <amvandemore@gmail.com> wrote:
>
>> On Sun, Sep 2, 2018 at 8:30 PM Kevin Oberman <rkoberman@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK1SAGiJLBannw6J3wAQsxrUb%2BO4NSpRDWZ=_kA4Qp9oww>