From owner-freebsd-emulation Wed May 24 20:35:35 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id B644A37BDEE for ; Wed, 24 May 2000 20:35:31 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id UAA56218; Wed, 24 May 2000 20:35:29 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id UAA08816; Wed, 24 May 2000 20:35:27 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200005250335.UAA08816@realtime.exit.com> Subject: Re: VMware 2.0 problems. In-Reply-To: <86hfbngvsm.wl@localhost.local.idaemons.org> from Akinori -Aki- MUSHA at "May 25, 2000 12:20:41 pm" To: Akinori -Aki- MUSHA Date: Wed, 24 May 2000 20:35:27 -0700 (PDT) Cc: emulation@FreeBSD.ORG Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Akinori -Aki- MUSHA wrote: > At Wed, 24 May 2000 17:57:33 -0700 (PDT), > Frank Mayhar wrote: > > Has anyone gotten VMware 2.0 to work on a 4.0-stable SCSI system? I've > > beaten my head against this wall again and again and I'm about to give > > up. I _really_ want to run this software, but this is ridiculous. > > > > My VMware configuration: > > > > No IDE. > > SCSI 0:0 Plain Disk, contents: > > DRIVETYPE scsi > > CYLINDERS 1115 > > HEADS 255 > > SECTORS 63 > > ACCESS "/home/frank/vmware/win98/disk.mbr" 0 63 > > ACCESS "/dev/da0s1a" 0 6297417 > > Are you sure you are going to give vmware your root filesystem?? My root is on /dev/da0s2a. That's what the RDONLY you elided covered. > I think you should specify that slice by just /dev/da0s1, with no > trailing disklabel. I've tried that. _That_ gives me: May 24 20:31:46: BUG F(171):252 bugNr=3419 May 24 20:31:46: MONITOR ERROR BUG F(171):252 bugNr=3419 May 24 20:31:46: Coredump with build $Name: build-476 $ May 24 20:31:46: Writing monitor corefile 'vmware-core' May 24 20:31:46: Msg_Post Error: msg.log.monpanic *** VMware internal monitor error *** BUG F(171):252 bugNr=3419 Please report this problem via the ``File an Incident'' link at http://www.vmware.com/support. Argh. > The message says it all. You got refused to commit write access on > the device just because you didn't have write permission. I'm not naive, I covered that. Got the above crash. I just want to know if anyone has gotten vmware working in a similar environment and if so, how. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message