Date: Sun, 6 Feb 2011 12:23:09 -0300 From: Mario Lobo <lobo@bsd.com.br> To: freebsd-questions@freebsd.org Cc: Eric Schuele <e.schuele@computer.org> Subject: Re: 8.2 prerelease, virtualbox, and windows guests that freeze... Message-ID: <201102061223.09545.lobo@bsd.com.br> In-Reply-To: <4D4DF58D.2040506@computer.org> References: <4D4DF58D.2040506@computer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 05 February 2011 22:12:45 Eric Schuele wrote: > All, > > I have a laptop running 8.2-prerelease GENERIC. I have virtualbox ose > 3.2.12 from ports (and kmod as well). > > I've only installed windows guests in vbox. I've installed windows 2008 > server 64, windows vista 64bit, and windows 7 32bit. I have the vbox > hdd images on an NTFS filesystem mounted using fuse. > > My box is a dual boot machine between FreeBSD and Windows. My desire is > to be able to utilize the same virtual machine in vbox on both my > Windows and FreeBSD installations. > > I can successfully utilize the virtuals in vbox (same version) in > Windows. However when I utilize any of the virtual machines in FreeBSD, > they run for several minutes and eventually "freeze". Freeze may not > necessarily be the correct term. All windows processes on the virtual > machine begin to die. First one process, then another, then all. Hard > to explain, which may not help my cause here. But, most important > fact... in Windows they work fine... under FreeBSD they run for a while > and then cease to run. When the VM is good and dead, it is always dead > with the little vbox virtual hard disk LED lit up (no idea if that is > important). > > Previously, they would run for a *very* short time. seconds? minutes? > and then die (sometimes I couldn't login). I disabled sound support and > now they run for 10-15 minutes. Had one run for an hour or two the > other day, but can't reproduce that. Usually 10-15 minutes max. > > Network works fine inside the virtual. > > I'm new to VirtualBox on FreeBSD. I've used it a bit on Windows with > good results. > > I did try a windows guest on a non fuse filesystem just to rule that > out, but had same issue. > > What else could I provide that might allow someone to point me in the > right direction here? > > Thanks. > > -- > Regards, > Eric Eric; My advice to you is that you change the file system on drive that holds the VMs files from NTFS to EXT2. 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. EXT on the other hand, is very stable in FreeBSD and has very good drivers for any version of 32/64 windows (Ext2IFS_1_11a) so you can access you vdi files. hope this helps. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] (99% winblows FREE)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201102061223.09545.lobo>