Date: Sat, 13 Mar 2010 08:48:39 +0100 From: Bernhard Froehlich <decke@bluelife.at> To: "Daisuke Aoyama" <aoyama@peach.ne.jp> Cc: freebsd-emulation@FreeBSD.org Subject: Re: Call for testers: VirtualBox 3.1.4 update Message-ID: <20100313084839.3c0ee0ee@bluelife.at> In-Reply-To: <4A980BD888314D5891D60C5C677B49BB@artemis> References: <b125726c2b23907bc4a2dc547ca8e091@bluelife.at> <4A980BD888314D5891D60C5C677B49BB@artemis>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 13 Mar 2010 15:19:55 +0900 "Daisuke Aoyama" <aoyama@peach.ne.jp> 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100313084839.3c0ee0ee>