From owner-freebsd-emulation@freebsd.org Mon Sep 3 14:28:38 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 E6049FEB6A5 for ; Mon, 3 Sep 2018 14:28:37 +0000 (UTC) (envelope-from amvandemore@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 7C8DE86C22 for ; Mon, 3 Sep 2018 14:28:37 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 417E8FEB6A2; Mon, 3 Sep 2018 14:28:37 +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 1F568FEB6A1; Mon, 3 Sep 2018 14:28:37 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 A2EF886C21; Mon, 3 Sep 2018 14:28:36 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-io0-x232.google.com with SMTP id q5-v6so565001iop.3; Mon, 03 Sep 2018 07:28:36 -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=tS8LuE5XubniI/GPJ1IgJbV0yQR+8QMPk6Lexywgqbo=; b=IwPumoc5WBFcn4xsUqQh+FR3KL7VrTho1d0Lmy6ElIdePU30CldfgWiAjmXGFnelG2 YyxLVvztEei2FqswzjP2binPXzqB4gZHuyrY3by0Rtq8HMfvEYdFmiTS3F/c12Zororz yLRMpNzxeZgE4++p4G1s8O/utT5mqZfbDXfT2YjcRXSfKyjBiT8X/PYHeSupBWIYS8qx O/B2MgwZqN4eVonJJxBoM7D5kfDzxtJplBmeOukXMpKeCKr99xstRvRkKiyuCcZMMGcS Bokqg2M9rI6hRNuGKGQN22zptHT8XT5R2sddf5BnIx+S2oA2hmRp5H2IQdJ0955YCYG+ IAaQ== 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=tS8LuE5XubniI/GPJ1IgJbV0yQR+8QMPk6Lexywgqbo=; b=YsCvQ80butAAlYf0ebVdXp2U/0ILJYYoN/K6aUnwZMaU6KXF/FE+CCA/bsJYyauWKV MzEBOz2gZgNQ7MErPSaSMS1WLM3o6ZQFPWcMrPbvRQgP3G0rvOgn57UIWXCrgs4Gf5An lSC2caTtU1MVw446BZgRL9WGM6jEEjRguYwdYlUbp19iVXSMJjnBSbi/ALyB3fLB5Wy2 wfGxp83RbOGIPA904n/3giBKOEtr3ZEsBlWvcCjd00gCsgclHNaGl1lhHrH0hOLdPQy/ lGrD6tJFIO+YcBga7icSOguxyJldjTabqsdmSn7s9qOtAR2BV3Dhkgfmq+yhpQiQ89Nd L52w== X-Gm-Message-State: APzg51D54tkSWV251ehzl0IraepLH0qK/Wq3QPswIhLByJh5lyDeEND5 NMZFZwpPxK27SjkkGJEcjiyCWt5nUB3GeyfKvwgqcMjv X-Google-Smtp-Source: ANB0VdZQQ7iCVwKL+YTXBV1mPbq7St/pVeUO7wMS3x2cMeRjCT4qWD6YmBxXL684xGyGOilfGTEt9yf6Um9pteQneD8= X-Received: by 2002:a6b:a287:: with SMTP id l129-v6mr18761261ioe.26.1535984915952; Mon, 03 Sep 2018 07:28:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adam Date: Mon, 3 Sep 2018 09:28:24 -0500 Message-ID: Subject: Re: VirtualBox W7 guest not resuming To: Kevin Oberman Cc: "freebsd-emulation@freebsd.org" , FreeBSD X11 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 14:28:38 -0000 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