From owner-freebsd-emulation@freebsd.org Mon Sep 3 01:45:01 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 62428FCEFC0 for ; Mon, 3 Sep 2018 01:45:01 +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 EEA2970216 for ; Mon, 3 Sep 2018 01:45:00 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AD143FCEFBE; Mon, 3 Sep 2018 01:45:00 +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 8ACDAFCEFBD; Mon, 3 Sep 2018 01:45:00 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (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 1CD1B70215; Mon, 3 Sep 2018 01:45:00 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id f14-v6so13627474ita.4; Sun, 02 Sep 2018 18:45:00 -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=IV5R0PwNyiYW9lGRRDGgnayQOmid7pq36jqR/FhB+88=; b=lRXywGogcQiCW2LAecZ6ORYGNqdYlVTb/9ggitDutKtGBYcul6828S7yKap478pwI1 JBKsZM0EydesXXavePMySq8FNG2ZlHLPfGhQsUbt2zyx/sa0kEx3a1OLDTmSqA5EXQ8p 87qMmVKfXnteo17qWPstPRrQ8fNLh8N/+qpTncdGAgkSCeVmffOPI7docFOf0MQQZPec ygy7JwMus4KpTeh4am4zvlS2vBtIht6nu6hu4wmOus65DuSN9y6SCxM3MkI6vkCylnBM 9nPfeRdcbrkzKkNqGIynudFzDGuzNu0ybIfDqtO0jQWDj5Ef8ZGNQRpI4xkaV+YiQSwc 5eXw== 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=IV5R0PwNyiYW9lGRRDGgnayQOmid7pq36jqR/FhB+88=; b=uKRlwPkhNt8Bh4Cthc+Lf4GfsK7BrXG6Cb7Ikov6wHzi3FLmW4azEbQKu0XsmndudL d5d+IKWPeCFPblIY6821J0x45YSoakY6tlsVx3bUdzce2IiPxtq0qbaXRGzx1Ki4WWKi PHuXAhFOsCKcG6uUL8d5a9JSz5E9tZ1BB0uKQo09yaHL/LUpBdI1rr6wpaAHe3F0wW+2 9JCi2SWho0vK0+8+A9DD6WQEVYRfKAzeGfRTAF7a5y+lNA7eWMOMucd1d3xYfFJCsRff Q6r8Zi6xkscMp1jEfZjH/E9wpMpGtY53QCpxAig5BnlEuxXuKICju+htJoFizwBL9H2H D4Dw== X-Gm-Message-State: APzg51BZZglKX8EAZKStWOg4EJwKrQ9QGp0qGpGKD98NU1RlhmZjh4v2 0X3tAvytSABbLaEpVdYuOKRoWtY6FgNM7wcmLeg= X-Google-Smtp-Source: ANB0VdbqVSLdcLIgl3Zm5vGVmZKqjI4NHD0/PIXuPd7JXW5AXt7yIykaYYgw1yED4kqjM/aLnt3Ojc4NQODs5QwCytg= X-Received: by 2002:a02:98f4:: with SMTP id c49-v6mr18862795jak.114.1535939099382; Sun, 02 Sep 2018 18:44:59 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adam Date: Sun, 2 Sep 2018 20:44:47 -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 01:45:01 -0000 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