From owner-freebsd-emulation Sun Feb 27 22:20:17 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by hub.freebsd.org (Postfix) with ESMTP id B638637B8D1 for ; Sun, 27 Feb 2000 22:20:13 -0800 (PST) (envelope-from nsayer@freebsd.org) Received: from medusa.kfu.com (medusa.kfu.com [170.1.70.5]) by quack.kfu.com (8.9.2/8.9.3) with ESMTP id WAA70843 for ; Sun, 27 Feb 2000 22:20:13 -0800 (PST) (envelope-from nsayer@freebsd.org) Received: from localhost (nsayer@localhost) by medusa.kfu.com (8.9.3/8.8.8) with ESMTP id WAA06277 for ; Sun, 27 Feb 2000 22:19:43 -0800 (PST) (envelope-from nsayer@freebsd.org) X-Authentication-Warning: medusa.kfu.com: nsayer owned process doing -bs Date: Sun, 27 Feb 2000 22:19:43 -0800 (PST) From: Nick Sayer X-Sender: nsayer@medusa.kfu.com Cc: freebsd-emulation@freebsd.org Subject: Re: vmware build 438 -> 468, raw disks fail. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oh, one more thing... Linux calls this BLKGETSIZE, and the IDE driver appears to return the number of blocks on the device. On Sun, 27 Feb 2000, Nick Sayer wrote: > > Duh. I don't know how I missed this... > For every crash, I get one of these: > > linux: 'ioctl' fd=12, cmd=1260 ('\^R',96) not implemented > > Updated linuxulator, anyone? :-) > > On Sat, 26 Feb 2000, Nick Sayer wrote: > > > > > I tried to move up to build 468 (release candidate 1) of vmware > > to see if it would get rid of some of the problems my office > > machine is having. Doing so breaks raw disks. The log shows this: > > > > Feb 26 12:19:15: RAWDISK: Linux's calculated capacity of /dev/hda is 16498755 se > > ctors > > RAWDISK: smaller than the actual size of the disk (16498755). > > RAWDISK: /dev/hda will therefore likely not work completelRAWDISK: correctly as > > a rawdisk with VMware. > > Feb 26 12:19:15: Caught signal 11 -- pid 2068 > > Feb 26 12:19:15: Dumping core... > > > > and the window disappears. > > > > The same thing happens if you have a configured raw disk and attempt to > > enter the configuration editor. > > > > It is still the case that the linuxulator appears to get block and char > > devices backwards. vmware complains that /dev/ad0 is not a raw device, > > when it actually is. Either vmware really wants a block device and is fibbing > > or the linuxulator is getting the two mixed up. > > > > I will try a virtual disk when I get home to see if that works ok. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-emulation" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-emulation" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message