From owner-freebsd-emulation@FreeBSD.ORG Fri Feb 26 15:42:35 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACD32106564A for ; Fri, 26 Feb 2010 15:42:35 +0000 (UTC) (envelope-from leslie@eskk.nu) Received: from mail.gelita.se (212-162-182-244.skbbip.com [212.162.182.244]) by mx1.freebsd.org (Postfix) with ESMTP id 6D5048FC18 for ; Fri, 26 Feb 2010 15:42:35 +0000 (UTC) Received: from mail.gelita.se (localhost.gelita.se [127.0.0.1]) by mail.gelita.se (Postfix) with ESMTP id 1377C10E77C for ; Fri, 26 Feb 2010 16:27:13 +0100 (CET) X-Virus-Scanned: amavisd-new at troback.com Received: from mail.gelita.se ([127.0.0.1]) by mail.gelita.se (mail.gelita.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTMPJut8P0qE for ; Fri, 26 Feb 2010 16:27:08 +0100 (CET) Received: from bljbsd01.no-ip.org (c-195-216-040-164.static.bjare.net [195.216.40.164]) by mail.gelita.se (Postfix) with ESMTP id 04F4810E50A for ; Fri, 26 Feb 2010 16:27:07 +0100 (CET) Message-ID: <4B87E7D8.1020905@eskk.nu> Date: Fri, 26 Feb 2010 16:25:12 +0100 From: Leslie Jensen User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; sv-SE; rv:1.9.1.8) Gecko/20100226 Thunderbird/3.0.2 MIME-Version: 1.0 To: freebsd-emulation@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Can't start vm after creating snapshot X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 26 Feb 2010 15:42:35 -0000 Hello I'm running a FreeBSD 8.0-RELEASE-p2 system with virtualbox-ose-3.1.2_1 and virtualbox-ose-kmod-3.1.2_1 installed. My Windows 7 guest will not start if I create a snapshot. It stops and a little red indicator says that the vm was aborted. If I remove the snapshot I'll have to start once in fail safe mode then I can start the vm normally again. Have I struck on a known bug or has anyone a suggestion on how to solve this issue? Thanks /Leslie