Date: Wed, 09 May 2001 08:50:43 -0400 From: Technical Information <tech_info@threespace.com> To: FreeBSD Chat <chat@freebsd.org> Subject: Re: vmware anyone? Message-ID: <4.3.2.7.2.20010509083937.017491f0@mail.threespace.com> In-Reply-To: <20010508184154.A29236@zerogravity.kawo2.rwth-aachen.d> References: <xzpoftjz69j.fsf@flood.ping.uio.no> <20010425202447.A441@darkstar.gte.net> <20010426124247.Z16200-100000@blues.jpj.net> <20010426193350.A16407@cichlids.cichlids.com> <xzpoftjz69j.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Incidentally, since I started this thread a week or so ago, I've had a chance to try VMWare. On a Red Hat Linux 7.1 host, it works pretty well with everything I've thrown at it so far--including Windows 98, Windows 2000, and FreeBSD 4.3-RELEASE (though the VMWare web site mentions support only up to 3.1 or so). In fact, setting up FreeBSD networking on the virtual hardware was even easier for me than on my real hardware...go figure. :-/ The one thing that hasn't worked so far is that the virtual system will crash the host OS (Linux) if you try to go full screen with more than a simple VGA display. I think this has something to do with XFree86 4.0+ incompatibilities, and I'm hoping VMWare will resolve that particular issue too through a patch or something. I haven't yet tried running it on a FreeBSD host via the Linux emulation, but I may try that one day if I ever get the disk space for it. I'm also curious to see the Windows 2000-hosted version, since that's what I'm running a lot of the time anyway. And it turns out that there's a substantial educational discount on the Workstation version if you're a student or member of an educational institution or something. Makes it much more palatable to the average joe. If you find yourself rebooting a lot between the OS you want and the OS you need (like me), then it's not a bad investment. --Chip Morton At 12:41 PM 5/8/2001, Alexander Langer wrote: >Thus spake Dag-Erling Smorgrav (des@ofug.org): > > > > Yes, but it still doesn't work. The kernel module is ok, but the > > > monitor-code from the plex86 folks does produce a fault in some > > > assembler code that is written by hand, and I'm not able to fix that. > > Do you have a trace and a listing of the code surrounding the fault? > >Hi! > >I tried it several times now. > >The kernel is hard-locked when that happens, i.e. it won't produce a >kernel dump. > >If I compile a kernel with DDB support, I can do "trace", but only >until an exit of a fork() call, so this doesn't help either. > >I have the assembler in-kernel code, that is executed right after a >fault, but manually initialing a kernel break at this point (e.g. by a >halt point) immediately reboots the kernel. >Note that the said fault is a plex86 specific fault, which happens >while monitoring the guest os, and not a FreeBSD kernel fault. > >Thus I'm unable to find the code surrounding the fault, I'm sorry. > >Alex >-- >cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20010509083937.017491f0>