From owner-freebsd-emulation Wed May 24 20:22: 9 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 512DE37B870 for ; Wed, 24 May 2000 20:22:06 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-40.sugnm1.kt.home.ne.jp [203.165.77.40]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id MAA03601; Thu, 25 May 2000 12:21:14 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id MAA05126; Thu, 25 May 2000 12:20:42 +0900 (JST) Date: Thu, 25 May 2000 12:20:41 +0900 Message-ID: <86hfbngvsm.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: frank@exit.com Cc: emulation@FreeBSD.ORG Subject: Re: VMware 2.0 problems. In-Reply-To: In your message of "Wed, 24 May 2000 17:57:33 -0700 (PDT)" <200005250057.RAA06561@realtime.exit.com> References: <200005250057.RAA06561@realtime.exit.com> User-Agent: Wanderlust/1.1.2 (Raspberry Beret) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, 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?? I think you should specify that slice by just /dev/da0s1, with no trailing disklabel. > RDONLY "/dev/null" 6297480 11614995 > ...which corresponds to the actual layout of my dual-boot disk. > I get "Can't open /dev/da0s1a for writing: Invalid argument." > > That's the _best_ I get. With other configurations I see vmware crashes. The message says it all. You got refused to commit write access on the device just because you didn't have write permission. You can obtain the permission by chmod'ing and/or chown'ing the device file as root, or configuring your /etc/fbtab suitably. (The latter is recommended for security reason) For details, read the manpage of each keyword. -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message