From owner-freebsd-emulation Wed May 31 21:42:31 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 DBFEC37BA41 for ; Wed, 31 May 2000 21:42:27 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 AAA29835 for ; Thu, 1 Jun 2000 00:42:27 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id AAA46087; Thu, 1 Jun 2000 00:41:57 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 1 Jun 2000 00:41:57 -0400 (EDT) To: freebsd-emulation@freebsd.org Subject: VMware: plaindisk problem X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14645.58338.373097.99462@grasshopper.cs.duke.edu> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been trying to get VMware working with a plain scsi disk without much luck. I'm running into problems fairly late when I'm trying to get WNT (have tried W2K too) installed. The guest sees the plain disk and after it formats the partition I've given it, it claims the disk is corrupt & tells me to choose another. Can anybody offer any suggestions as to what I'm doing wrong? I'm running the latest vmware2 under 4.0-RELEASE. % grep da1 /var/run/dmesg.boot da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) % cat ~/.vmware/plain DRIVETYPE scsi CYLINDERS 1106 HEADS 255 SECTORS 63 ACCESS "/home/home1/gallatin/.vmware/disk.mbr" 0 63 ACCESS "/dev/rda1s1" 63 17767827 #RDONLY "/dev/null" 4192965 12305790 And the disks my vmware knows about: scsi0:0.present = TRUE scsi0:0.deviceType = "plainDisk" scsi0:0.fileName = "/home/home1/gallatin/.vmware/plain" scsi0.present = TRUE ide0:0.present = TRUE ide0:0.deviceType = "atapi-cdrom" ide0:0.fileName = "/dev/rcd0c" The disk in question looks like this: #fdisk /dev/rda1 ******* Working on device /dev/rda1 ******* parameters extracted from in-core disklabel are: cylinders=1106 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1106 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 17767827 (8675 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 1023/ sector 63/ head 254 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: Oddly enough, if I give it the slice, I see partitions: # fdisk /dev/rda1s1 ******* Working on device /dev/rda1s1 ******* parameters extracted from in-core disklabel are: cylinders=1105 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1105 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 105,(unknown) start 1869771365, size 168689522 (82367 Meg), flag ff beg: cyl 68/ sector 10/ head 13; end: cyl 288/ sector 43/ head 115 The data for partition 2 is: sysid 115,(unknown) start 1701519481, size 1869881465 (913028 Meg), flag 50 beg: cyl 371/ sector 37/ head 114; end: cyl 366/ sector 33/ head 32 The data for partition 3 is: sysid 116,(unknown) start 2573, size 0 (0 Meg), flag 20 beg: cyl 371/ sector 37/ head 114; end: cyl 372/ sector 50/ head 97 The data for partition 4 is: sysid 0,(unused) start 0, size 3435113472 (1677301 Meg), flag 0 beg: cyl 0/ sector 0/ head 0; end: cyl 0/ sector 0/ head 0 I'm trying to save memory by avoiding double caching of data in the guest and the host & I'd like to avoid going back to using a file.. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message