From owner-freebsd-emulation@freebsd.org Mon Sep 3 19:00:58 2018 Return-Path: Delivered-To: freebsd-emulation@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E6B8FF238E for ; Mon, 3 Sep 2018 19:00:58 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B10CE70E84 for ; Mon, 3 Sep 2018 19:00:57 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6DBFEFF2386; Mon, 3 Sep 2018 19:00:57 +0000 (UTC) Delivered-To: emulation@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 214FAFF2385; Mon, 3 Sep 2018 19:00:57 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD78270E81; Mon, 3 Sep 2018 19:00:56 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-oi0-x233.google.com with SMTP id p84-v6so2492709oic.4; Mon, 03 Sep 2018 12:00:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jQvtTSGaeUjczoLipLltH37gnSpfdmTDkfK/1+4mu6I=; b=lMMP9tj3+ZBTCbXSKrQZ4au7oBviJ71plk/LZYjHU9bUwP1ASg3bidaj+LauwoAm7H Mpiv3TgSeRxGyK97ZRM8QL1RBNDQ09x+lad/eQJqqjzFzwgeb6fGcCnb6t/Z+ABw/LiZ mMVMv/d9nN+JU/O+2XaDrdFmqpkDNYaTK4y4c73DKJtmZYEr4LnamdTskYQWPTQKZnkR EMHJYLnOP/Av+xK9rOHjOVEB/CdGnouA79tTxzij/wQPugquXOQcGNYq41oAgFOkokyo BudM3tI/zJPUMas26jJJaUqCX/2ljQLyN+41tCqpDw9rr7iHFBOst/WqCLpnW+1VsTxq 9Wbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jQvtTSGaeUjczoLipLltH37gnSpfdmTDkfK/1+4mu6I=; b=NzbCt7lPGyZca5U5I3B3cMPRFxr2b9t1+YadGVDAuE+ZFNHHOhNv4GvDPGS7BRc1cd aSSRzarJGGaAXBK5j/5uITXNJMmKSEHQ1EyEeuekYseOfXfTnsGh+RwceZPjeYxs5VCv Ddz3CrAvkH8CUGU4THRlWwCBG7X8liO84KPooSZjBDixqmb5ChviOtEinlWy4fTFlji7 wxh358xFnASb942dlmGsb0zs6mpMOlfAJxhYH1VDEi6SSo2/8pWdMKl3q2v1QU2ratvT K6MdktkjPW0oVOLoMCGTtjvvpF0MJzGHdwbI/b4zlO/FWKfeORAAanlhNpROWSS3AskB mg7g== X-Gm-Message-State: APzg51D9wntoVzHptXRa5ik67faQyyGyR/BkzmwwwGd8Pf9KSDE1tcMy NRf71KZlH3MabEATbtkDwNtVP1q/0bbdhOW1+YA= X-Google-Smtp-Source: ANB0VdZzZ7DUuXkn7ws4QMGU6R2Pp+ijiA64cJPZ6FyahNT68Qh8B0WWP4Acn8SMNcCkAGWaSBxvTCoIK8OtkFRF4sE= X-Received: by 2002:aca:f0d4:: with SMTP id o203-v6mr19861942oih.21.1536001255854; Mon, 03 Sep 2018 12:00:55 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Mon, 3 Sep 2018 12:00:39 -0700 Message-ID: Subject: Re: VirtualBox W7 guest not resuming To: Adam Vande More Cc: "freebsd-emulation@freebsd.org" , "freebsd-x11@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Sep 2018 19:00:58 -0000 On Mon, Sep 3, 2018 at 10:02 AM Kevin Oberman wrote: > On Mon, Sep 3, 2018 at 7:28 AM Adam wrote: > >> On Mon, Sep 3, 2018 at 1:36 AM Kevin Oberman wrote: >> >>> On Sun, Sep 2, 2018 at 6:45 PM Adam wrote: >>> >>>> On Sun, Sep 2, 2018 at 8:30 PM Kevin Oberman >>>> 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* >>> ) 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. > After several reboots under varying conditions it looks like this only happens if the VM is paused when the new drm is instantiated. If it is shutdown, everything works fine. If you take the paused system, resume under the old DRM, shutdown, boot with the latest DRM, everything is fine and pause and resume work as expected from that point on. Why this could happen baffles me. but the issues is resolved for me. I have always shutdown VMs before updating versions of VBox, but, of course, not for other port upgrades. So this looks like a really weird corner case. I seriously doubt that it is worth the effort of tracking it down. BTW, the Oracle article listing the location as .VirtualBox/Machines is dated June of last year, so it's not really all that old. I am running 5.2.18 with the 5.2.18 Guest Additions. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683