Date: Wed, 24 May 2000 22:18:55 -0700 (PDT) From: Frank Mayhar <frank@exit.com> To: Nick Sayer <nsayer@quack.kfu.com> Cc: freebsd-emulation@freebsd.org Subject: Re: VMware 2.0 problems. Message-ID: <200005250518.WAA10588@realtime.exit.com> In-Reply-To: <392CB310.A0A1AEAF@quack.kfu.com> from Nick Sayer at "May 24, 2000 09:58:56 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Nick Sayer wrote: > This should be > > ACCESS "/dev/da0s1" 63 6297417 Oops, fixed. Still no joy. > You may be screwed if the SCSI geometry that shows up in the guest > is not the same as the numbers you quote in the .hd file. If they're > not the same, Winblows type OSes for sure won't boot. > > Also, be sure that the disk.mbr file actually has the right contents. > You can make it with > > dd if=/dev/da0 bs=1b count=63 of=disk.mbr Did that. > The actual algorithm for doing this is to use FreeBSD's fdisk command to > find > out which block ranges the different raw slice devices occupy. You then > fill the rest of the space either with a local "mbr" file or with > /dev/null. > The idea is that you use the raw slice devices along with your own local > copy of the > mbr (usually the FreeBSD bootloader) to build the "plain disk" view. > Partitions that > you don't want to see can be substituted with /dev/null. I basically understand all this and have, as far as I can tell, set things up properly. The best I get is the BUG F(171):252 bugNr=3419 crash and coredump. This is incredibly frustrating; I have no idea what I'm doing wrong. For the record, the system is a P2B-DS, dual PII 400, 512MB, SCSI everything (no IDE or ATA). -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005250518.WAA10588>