From owner-freebsd-emulation@FreeBSD.ORG Sat Mar 13 07:48:45 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 A47A7106566C for ; Sat, 13 Mar 2010 07:48:45 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail.itac.at (mail.itac.at [91.205.172.9]) by mx1.freebsd.org (Postfix) with ESMTP id 1BF5F8FC0A for ; Sat, 13 Mar 2010 07:48:45 +0000 (UTC) Received: from [78.142.74.81] (helo=localhost) by mail.itac.at with esmtpa (Exim 4.63) (envelope-from ) id 1NqM5R-00046Y-36; Sat, 13 Mar 2010 08:48:41 +0100 Date: Sat, 13 Mar 2010 08:48:39 +0100 From: Bernhard Froehlich To: "Daisuke Aoyama" Message-ID: <20100313084839.3c0ee0ee@bluelife.at> In-Reply-To: <4A980BD888314D5891D60C5C677B49BB@artemis> References: <4A980BD888314D5891D60C5C677B49BB@artemis> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.7; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.6 (/) X-Spam-Report: Spam detection software, running on the system "mail.itac.at", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Sat, 13 Mar 2010 15:19:55 +0900 "Daisuke Aoyama" wrote: > Hi, > > > Please report any functionality which was working with previous > > versions of VirtualBox and no longer working with 3.1.4 or any > > build failure. > > For fun, I build VirtualBox 3.1.4 with VNC patch + INT18 patch. > New Makefile is required of course. I attach new Makefile in this > mail. So far works perfectly with 32bit existing VMs. However, both of > existing Windows7 and fresh install of 64bit version are failed. > > Host: FreeNAS 0.7.1 based on FreeBSD 7.3-RC2 amd64 > Existing Guests: FreeNAS 0.7.1(64), Windows7(64/32), Server 2008(32), > 2003(32) > > (to iSCSI target via gPXE) > Succeeded fresh install: Windows7 x86 > Failed fresh install: Windows7 x64 > > When I created VM under 3.1.4 and installed in it, Windows installer > exited by some reason and rebooted the VM. I switched back to 3.1.2 > and deleted the HD, re-created empty HD, installed in it, Windows > installer finished everything without any issue. > Sorry, I have not been found the reason and the failure point yet. > I will check more. Does anyone confirm it? [...] Content analysis details: (0.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 3.4 FH_DATE_PAST_20XX The date is grossly in the future. -1.3 AWL AWL: From: address is in the auto white-list Cc: freebsd-emulation@FreeBSD.org Subject: Re: Call for testers: VirtualBox 3.1.4 update 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: Sat, 13 Mar 2010 07:48:45 -0000 On Sat, 13 Mar 2010 15:19:55 +0900 "Daisuke Aoyama" wrote: > Hi, > > > Please report any functionality which was working with previous > > versions of VirtualBox and no longer working with 3.1.4 or any > > build failure. > > For fun, I build VirtualBox 3.1.4 with VNC patch + INT18 patch. > New Makefile is required of course. I attach new Makefile in this > mail. So far works perfectly with 32bit existing VMs. However, both of > existing Windows7 and fresh install of 64bit version are failed. > > Host: FreeNAS 0.7.1 based on FreeBSD 7.3-RC2 amd64 > Existing Guests: FreeNAS 0.7.1(64), Windows7(64/32), Server 2008(32), > 2003(32) > > (to iSCSI target via gPXE) > Succeeded fresh install: Windows7 x86 > Failed fresh install: Windows7 x64 > > When I created VM under 3.1.4 and installed in it, Windows installer > exited by some reason and rebooted the VM. I switched back to 3.1.2 > and deleted the HD, re-created empty HD, installed in it, Windows > installer finished everything without any issue. > Sorry, I have not been found the reason and the failure point yet. > I will check more. Does anyone confirm it? Could you build 3.1.4 without additional patches but with debugging and attach the vbox.log file after such an vm crash? Thanks for testing, we really appreciate that because we cannot test every possible combination. -- Bernhard Froehlich http://www.bluelife.at/