From owner-freebsd-emulation  Thu Nov 30  6:59:47 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id CE29237B400
	for <freebsd-emulation@freebsd.org>; Thu, 30 Nov 2000 06:59:41 -0800 (PST)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA19266;
	Thu, 30 Nov 2000 09:59:41 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAUExfM02585;
	Thu, 30 Nov 2000 09:59:41 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 30 Nov 2000 09:59:41 -0500 (EST)
To: Peter Hornby <p.hornby@ned.dem.csiro.au>
Cc: freebsd-emulation@freebsd.org
Subject: Re: Vmware2 on 4.1-RELEASE
In-Reply-To: <3A266A7F.FB8B67BA@ned.dem.csiro.au>
References: <20001126180819.D19849@tmp.com.br>
	<4.2.0.58.20001127161355.009d1900@solo.ned.dem.csiro.au>
	<14882.33448.840576.154563@grasshopper.cs.duke.edu>
	<3A266A7F.FB8B67BA@ned.dem.csiro.au>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14886.27359.274083.576046@grasshopper.cs.duke.edu>
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Peter Hornby writes:
 > Andrew Gallatin wrote:
 > 
 > > Peter Hornby writes:
 > > <..>
 > >  > 1) Attempts to set all forms of physical/raw disk crash the vmware
 > >  > configuration editor. This crash generally occurs when filling in the
 > >  > <snip...>
 > >
 > > Have you tried reading /usr/local/share/doc/vmware/Hints.FreeBSD?
 > > Specifically, you should be using a "plain" disk.  See Hints.FreeBSD
 > > for more details.
 > > <snip..>
 > 
 > Thanx Drew. One more wrinkle. The following plain disk config
 > =========================
 > DRIVETYPE      ide
 > CYLINDERS  13410
 > HEADS         15
 > SECTORS       63
 > 
 > # Partition type: MBR
 > ACCESS "/home/truro1/peterho/vmware/hda/wd0.mbr" 0 63
 > 
 > # Partition type: Win95 FAT32
 > ACCESS "/dev/rwd0s1" 63 4096512
 > 
 > # Partition type: Win95 FAT32
 > ACCESS "/dev/rwd0s5" 4096575 4289292
 > 
 > # Partition type: Win95 FAT32
 > ACCESS "/dev/rwd0s6" 8385867 4273227
 > 
 > # Partition type: Padding
 > RDONLY "/dev/null" 12659094 13356
 > ==========================
 > 
 > Only links in the first partition into the device chain in the VM (ie. windows
 > only sees the first partition).
 > The workaround is ugly but obvious, define three plain disks. That works, so the
 > partitions are all OK etc..
 > Am I being stupid? or is this a bug?

I really don't know -- I've never used more than one windows
partition. 

Uhm..  Are rwd0s5 and rwd0s6 extended partitions?  Can FreeBSD even
see extended partitions?  Eg, can you mount -t msdos them?
If FreeBSD can't see them, then VMware running under FreeBSD can't see 
them.

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message