From owner-freebsd-emulation@FreeBSD.ORG Thu Sep 30 08:29:51 2004 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0078616A4CF for ; Thu, 30 Sep 2004 08:29:51 +0000 (GMT) Received: from mta1.srv.hcvlny.cv.net (mta1.srv.hcvlny.cv.net [167.206.5.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB59F43D49 for ; Thu, 30 Sep 2004 08:29:50 +0000 (GMT) (envelope-from bsdfsse@optonline.net) Received: from [192.168.0.28] (ool-43532b7b.dyn.optonline.net [67.83.43.123]) by mta1.srv.hcvlny.cv.net (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0I4U00D1VI9PW6@mta1.srv.hcvlny.cv.net> for freebsd-emulation@freebsd.org; Thu, 30 Sep 2004 04:29:50 -0400 (EDT) Date: Thu, 30 Sep 2004 04:30:00 -0400 From: bsdfsse In-reply-to: <415B40E0.5030708@optonline.net> To: bsdfsse Message-id: <415BC408.8070200@optonline.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) References: <415B40E0.5030708@optonline.net> cc: freebsd-emulation@freebsd.org Subject: Re: Are there step-by-step VMWare instructions? X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 30 Sep 2004 08:29:51 -0000 I tried some more things I read about online, but it still locks up: I rebuilt my kernel with "HZ=1200", and that got rid of the "rtc: 100>kern.hz" messages. My /boot/loader.conf needed this: hw.ata.ata_dma="0" which changed this message: ad0: WARNING - WRITE_DMA no interrupt but good status to become this message: ad0: WARNING - WRITE_MUL no interrupt but good status The machine still hangs when I start the virtual machine. As soon as I hit the "Power on" button, FreeBSD nearly freezes. I can do a few things, but even after I "kill -9" vmware, the machine is still hosed. I really need to get VMWare to work, or else I have to reload Linux (or Windows). I own VMware 3.2 and 4.5 for both Windows and Linux. Each time my machine locks up, it starts running "fsck" in the background. Any suggestions? bsdfsse wrote: > > I am beginning to try and run the vmware3 port on FreeBSD-5.3beta6. > > First I "upgraded" the machine to 5.3-Stable by putting "RELENG_5" in my > stable-supfile. > > Next I went in to /usr/ports/emulators/vmware3 and ran: > make > make install > > I rebooted and ran "vmware &" in a command window, and then entered my > Linux licsense serial number. > > One of the first things it asked me, was what network device to bind to > "vmmonet" (I think), so I entered "fxp0" - which now I wonder if it > should have been "/dev/fxp0". > > After completing the install, I rebooted so it would run its start script. > > Next I used the wizard to make Win2000 Professional system, and copied > the Win2000 Pro ISO over to this machine. I configured the vm's cdrom to > be the Win2000 ISO file, so I could install it. > > When the VM machine boot, it couldn't find the mouse, so I selected (I > think) "/dev/mouse" and that error went away. Them it would not go past > this error: > > Cannot attach shared memory segment: Invalid argument. > Failed to initialize SVGA device. > > I looked up on Google and found this: > > http://lists.freebsd.org/pipermail/freebsd-emulation/2004-August/000526.html > > > "ake sure that you have sysctl > kern.ipc.shm_allow_removed set to 1" > > So I made the change he suggested, rebooted, and it did get past that > error. > > When it came up, it complained about not being able to bind vmnet, then > the machine locked up solid. > > Now I made a new virtual machine, and tried to install without > networking inside the vm, and it the machine 99% locked (the mouse > sometimes moves). > > I can't shell in using putty.exe either. > > It would really be nice if there was some step-by-step instructions, it > would make it easier for people to switch to FreeBSD (like I'm doing). I > am trying to document things as I go along, so if such doucments do not > exist, mine can be used by the next guy. > > The above link I found is an example of the knowledge being spread > around, maybe we can collect it in to one spot? > > I can post more detailed errors if this document does not exist, I > thought I would ask first in case it did. > > thx! > > > > > > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to > "freebsd-emulation-unsubscribe@freebsd.org" >