From owner-freebsd-questions@FreeBSD.ORG Sun Feb 6 21:38:09 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE00C106566B for ; Sun, 6 Feb 2011 21:38:08 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 74BCC8FC17 for ; Sun, 6 Feb 2011 21:38:08 +0000 (UTC) Received: by yie19 with SMTP id 19so1599419yie.13 for ; Sun, 06 Feb 2011 13:38:07 -0800 (PST) Received: by 10.90.83.5 with SMTP id g5mr5292210agb.59.1297028286913; Sun, 06 Feb 2011 13:38:06 -0800 (PST) Received: from papi.localnet ([187.113.166.194]) by mx.google.com with ESMTPS id 7sm391962yhl.45.2011.02.06.13.38.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 06 Feb 2011 13:38:06 -0800 (PST) From: Mario Lobo To: Eric Schuele Date: Sun, 6 Feb 2011 18:37:37 -0300 User-Agent: KMail/1.13.5 (FreeBSD/8.2-PRERELEASE; KDE/4.5.2; amd64; ; ) References: <4D4DF58D.2040506@computer.org> <201102061223.09545.lobo@bsd.com.br> <4D4EC7CB.7010200@computer.org> In-Reply-To: <4D4EC7CB.7010200@computer.org> X-KMail-Markup: true MIME-Version: 1.0 Message-Id: <201102061837.37675.lobo@bsd.com.br> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: 8.2 prerelease, virtualbox, and windows guests that freeze... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Feb 2011 21:38:09 -0000 On Sunday 06 February 2011 13:09:47 Eric Schuele wrote: > > Thanks for the suggestion, however, I've already tried this (sorta). > From my original post... > > >> I did try a windows guest on a non fuse filesystem just to rule that > >> out, but had same issue. > > I suppose it may have been a little less than clear. By "non fuse > filesystem" I actually meant UFS. The problem still persisted. > > > NTFS file systems on FreeBSD or even Linux are OK only for doing small > > r/w stuff. I use the ntfs-3g which is really good but don't trust NTFS > > for heavy usage under those OSs. Sometimes it's not even trustable under > > windows itself. > My bad!. Sorry!. But it seems that you're right. Looks like the issue is not the FS then. If you're building from the ports, try the svn version from: https://svn.bluelife.at/index.cgi/blueports It's already version 4.0.2 there. > I realize NTFS on fBSD has been shaky in the past, but had heard it had > come a long way these days. It does seem to work well for all my > purposes, except these VMs. Had hoped NTFS was not the issue. > > I've not tried the EXT IFS for windows yet, nor had I heard much > regarding their success or failure. If your willing to go out on a limb > and say "very good drivers for any version of 32/64 windows"... I'll > give it a try, and post my results. :) > Forgive me if it sounded "on a limb". Didn't mean to look like that. The only reason I mentioned it is because it's exactly the way I've been using. I have triple boot system. BSD AMD64, XP32 and Win7 64 and the IFS driver works flawlessly on both windows, and all 3 Vboxes accessing the same VDIs. Because of that, I believe I may have got carried away by saying "any win version". regards, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] (99% winblows FREE)