From owner-freebsd-emulation Sun May 21 3:29:19 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (Postfix) with ESMTP id 3E59137B831
for <emulation@freebsd.org>; Sun, 21 May 2000 03:29:11 -0700 (PDT)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id MAA16922
for emulation@freebsd.org; Sun, 21 May 2000 12:29:07 +0200 (CEST)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (Postfix, from userid 101)
id 6DC91885A; Sun, 21 May 2000 12:28:22 +0200 (CEST)
Date: Sun, 21 May 2000 12:28:22 +0200
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: emulation@freebsd.org
Subject: Linux ldconfig halts the system
Message-ID: <20000521122822.A90933@keltia.freenix.fr>
Mail-Followup-To: emulation@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.11i
X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Has anyone seen this ?
After upgrading my laptop to the latest CURRENT (yesterday), everytime the
system tries to run "/compat/linux/sbin/ldconfig" as part of rc.i386, the
kernel halts. Not a panic but a "normal" stop with the two messages 'Waiting
(60 seconds) for bufdaemon to stop'.
The ldconfig binary comes from linux_base-5.2 and has been brandelf'd Linux.
-rwxr-xr-x 1 root wheel 110368 May 21 12:18 ldconfig
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 4.0-CURRENT #78: Sun Feb 27 15:32:39 CET 2000
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
From owner-freebsd-emulation Sun May 21 7:52: 1 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from bachue.usc.unal.edu.co (bachue.usc.unal.edu.co [168.176.3.20])
by hub.freebsd.org (Postfix) with ESMTP id 67CDB37B803
for <freebsd-emulation@FreeBSD.org>; Sun, 21 May 2000 07:51:52 -0700 (PDT)
(envelope-from giffunip@asme.org)
Received: from asme.org ([216.252.136.128]) by bachue.usc.unal.edu.co
(Netscape Messaging Server 3.6) with ESMTP id AAA1C7B
for <freebsd-emulation@FreeBSD.org>;
Sun, 21 May 2000 09:50:21 -0400
Message-ID: <3927747F.2FDF8A0B@asme.org>
Date: Sun, 21 May 2000 00:30:39 -0500
From: "Pedro F. Giffuni" <giffunip@asme.org>
Organization: Universidad Nacional de Colombia
X-Mailer: Mozilla 4.5 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: freebsd-emulation@FreeBSD.org
Subject: doscmd reports itself as a 286
References: <38EF7A76.1ED12607@asme.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I always wondered about the posibility of running Minix 386 under a vm86
session. Today I tried to run Minix 386 with doscmd using FreeBSD-3.4R.
While the monitor went well at first, when I tried to load Minix the
following message appeared:
Loading Minix 2.0.0
You can't run a 386 kernel on this 80286
AFAIK, a vm86 session is not restricted to 286 instructions and
shouldn't report this lie. Furthermore, Minix 386 runs well on protected
mode. I'll investigate if the Microsoft Diagnostics report the same and
I'll file a PR.
The doscmd session continued well until I exited the monitor:
fd0>exit
________________________________________
Signal 4 from DOS program
ax=8600 bx=fe50 cx=f5eb dx=3f65
si=6457 di=0000 sp=91c9 bp=91ee
cs=91ca ss=96e0 ds=96e0 es=1af6
ip=acdd eflags=b0a92
ff ff ff 00 88 00 00 ff ff ff ff 00 8c 00 00 ff
(bad)
91ca:acdd Illegal instruction
________________________________________
When ESC, ls and finally exit is given:
________________________________________
(missed) OUTSB -> 0x647b
(missed) OUTSW -> 0x647b
ax=ff00 bx=22ca cx=ff22 dx=649d
si=6456 di=0000 sp=91cc bp=91ee
cs=2032 ss=96e0 ds=96e0 es=fffb
ip=ffff eflags=b0202
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
addb %al,(%bx+%si)
unsupported instruction
________________________________________
cheers,
Pedro.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
From owner-freebsd-emulation Sun May 21 16:47:14 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by hub.freebsd.org (Postfix) with ESMTP id 5FC1237B7DB
for <emulation@FreeBSD.ORG>; Sun, 21 May 2000 16:47:05 -0700 (PDT)
(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.3/8.9.0) id JAA77055;
Mon, 22 May 2000 09:16:07 +0930 (CST)
Date: Mon, 22 May 2000 09:16:07 +0930
From: Greg Lehey <grog@lemis.com>
To: Ollivier Robert <roberto@keltia.freenix.fr>
Cc: emulation@FreeBSD.ORG
Subject: HEADS UP missing? (was: Linux ldconfig halts the system)
Message-ID: <20000522091607.B76524@freebie.lemis.com>
References: <20000521122822.A90933@keltia.freenix.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <20000521122822.A90933@keltia.freenix.fr>
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-418-838-708
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Sunday, 21 May 2000 at 12:28:22 +0200, Ollivier Robert wrote:
> Has anyone seen this ?
>
> After upgrading my laptop to the latest CURRENT (yesterday), everytime the
> system tries to run "/compat/linux/sbin/ldconfig" as part of rc.i386, the
> kernel halts. Not a panic but a "normal" stop with the two messages 'Waiting
> (60 seconds) for bufdaemon to stop'.
Yes. There was something in UPDATING about this, which I think is
worth a HEADS UP:
20000417:
The method that we brand ELF binaries has changed to be more
acceptible to the binutils maintainers. You will need to
rebrand your ELF binaries that aren't native. One problem
binary is the Linux ldconfig. After your make world, but
before you reboot, you'll neeed to issue:
brandelf -t Linux /compat/linux/sbin/ldconfig
if you have Linux compatibility enabled on your machine.
> The ldconfig binary comes from linux_base-5.2 and has been brandelf'd Linux.
>
> -rwxr-xr-x 1 root wheel 110368 May 21 12:18 ldconfig
Possibly before 17 April?
Greg
--
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
From owner-freebsd-emulation Mon May 22 12:52:42 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from green.wl.vg (green.wl.vg [204.200.26.138])
by hub.freebsd.org (Postfix) with ESMTP id 4582137BABE
for <freebsd-emulation@freebsd.org>; Mon, 22 May 2000 12:52:39 -0700 (PDT)
(envelope-from patrick@whetstonelogic.com)
Received: from whetstonelogic.com (patrick [205.252.46.171])
by green.wl.vg (8.9.3/8.9.3) with ESMTP id MAA73421
for <freebsd-emulation@freebsd.org>; Mon, 22 May 2000 12:52:11 -0700 (PDT)
(envelope-from patrick@whetstonelogic.com)
Message-ID: <39298FE3.9FE381ED@whetstonelogic.com>
Date: Mon, 22 May 2000 15:52:03 -0400
From: Patrick Gardella <patrick@whetstonelogic.com>
Organization: Whetstone Logic, Inc.
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-emulation@freebsd.org
Subject: VMWare and routing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I'm trying to figure out how to make networking work on VMWare. I've
read through the mailing list archives, but I'm still stumped. I think
I could make it work if it wasn't using 192.168.254.x.
But here it is:
The vmnet1 is set up to be 192.168.254.3
Windows 98 is set up to be 192.168.254.2
I can ping both from Windows, as well as the real IP of my box. On my
box, I can ping both vmnet1 and Windows.
What routing should I use get it to talk to the rest of the network?
(IP forwarding is enabled.)
Feel free to call me a moron, but tell me what to do first!
Patrick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
From owner-freebsd-emulation Mon May 22 17:35:54 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from oxygen.yy.ics.keio.ac.jp (oxygen.yy.ics.keio.ac.jp [131.113.47.3])
by hub.freebsd.org (Postfix) with ESMTP
id AF48A37B6FC; Mon, 22 May 2000 17:35:44 -0700 (PDT)
(envelope-from sanpei@sanpei.org)
Received: from lavender.yy.cs.keio.ac.jp (ppp143.dialup.st.keio.ac.jp [131.113.27.143])
by oxygen.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id JAA21058;
Tue, 23 May 2000 09:35:41 +0900 (JST)
(envelope-from sanpei@sanpei.org)
Received: (from sanpei@localhost)
by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id JAA03312;
Tue, 23 May 2000 09:35:41 +0900 (JST)
Date: Tue, 23 May 2000 09:35:41 +0900 (JST)
Message-Id: <200005230035.JAA03312@lavender.yy.cs.keio.ac.jp>
To: ports@FreeBSD.ORG, freebsd-emulation@FreeBSD.ORG
Subject: Re: Exec format error: vmware2-2.0.476 and -CURRENT
In-Reply-To: Your message of "Sun, 14 May 2000 22:13:10 JST".
<200005141313.WAA06769@lavender.yy.cs.keio.ac.jp>
From: sanpei@sanpei.org (MIHIRA Yoshiro)
X-Mailer: mnews [version 1.21] 1997-12/23(Tue)
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>> kuriyama@FreeBSD.ORG wrote:
>>
>> >> At 11 May 2000 14:42:37 GMT,
>> >> Kentaro Inagaki <inagaki@tg.rim.or.jp> wrote:
>> >> > Not in post-extract, it is in post-patch.
>> >> > Please use the following patches.
>> >>
>> >> Fixed on my box! Thanks!
>>
>> I also fixed this problem, Thanks!
By the way, does someone have any plan to commit Inagaki-san's
patch for emulators/vmware2?
I think we need that patch under 5-current.
Cheers.
MIHIRA Yoshiro
Yokohama, Japan.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
From owner-freebsd-emulation Mon May 22 22:55: 6 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (Postfix) with ESMTP id 4FBC137B5F3
for <emulation@FreeBSD.ORG>; Mon, 22 May 2000 22:55:03 -0700 (PDT)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id HAA08806
for emulation@FreeBSD.ORG; Tue, 23 May 2000 07:55:01 +0200 (CEST)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (Postfix, from userid 101)
id 2729A885A; Tue, 23 May 2000 00:45:35 +0200 (CEST)
Date: Tue, 23 May 2000 00:45:35 +0200
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: emulation@FreeBSD.ORG
Subject: Re: HEADS UP missing? (was: Linux ldconfig halts the system)
Message-ID: <20000523004535.A3706@keltia.freenix.fr>
Mail-Followup-To: emulation@FreeBSD.ORG
References: <20000521122822.A90933@keltia.freenix.fr> <20000522091607.B76524@freebie.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.11i
In-Reply-To: <20000522091607.B76524@freebie.lemis.com>; from grog@lemis.com on Mon, May 22, 2000 at 09:16:07AM +0930
X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
According to Greg Lehey:
> Yes. There was something in UPDATING about this, which I think is
> worth a HEADS UP:
I've read UPDATING and the ldconfig binary was re-branded before I
rebooted. What I find surprising is that the system doesn't even panic (which
it shouldn't anyway) but shutdown itself w/o asking.
A ldconfig binary from another Linux system doesn't do this.
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 4.0-CURRENT #78: Sun Feb 27 15:32:39 CET 2000
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
From owner-freebsd-emulation Wed May 24 9:55:43 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170])
by hub.freebsd.org (Postfix) with ESMTP
id B9AD437BCFC; Wed, 24 May 2000 09:55:39 -0700 (PDT)
(envelope-from brian@Awfulhak.org)
Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12])
by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id RAA49431;
Wed, 24 May 2000 17:55:36 +0100 (BST)
(envelope-from brian@Awfulhak.org)
Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1])
by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id RAA88694;
Wed, 24 May 2000 17:55:32 +0100 (BST)
(envelope-from brian@Awfulhak.org)
Message-Id: <200005241655.RAA88694@hak.lan.Awfulhak.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: jake@FreeBSD.org
Cc: phk@FreeBSD.org, mdodd@FreeBSD.org,
freebsd-emulation@FreeBSD.org, Brian Somers <brian@Awfulhak.org>
Subject: queue.h mods
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <88686.959187329.1@hak.lan.Awfulhak.org>
Date: Wed, 24 May 2000 17:55:32 +0100
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Hi,
I think your queue.h modifications have broken the
emulators/vmware2 port. Are there any plans to fix it or shall I ?
cc -O -pipe -I/usr/ports/emulators/vmware2/work/vmware-distrib/vmnet-only/freebsd -I/sys -DCDEV_MAJOR_=201 -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/ports/emulators/vmware2/work/vmware-distrib/vmnet-only/freebsd -I/sys -I. -I@ -I@/../include -I/usr/include -mpreferred-stack-boundary=2 -c vmnet.c
vmnet.c:70: syntax error before `vmnet_softc'
vmnet.c:87: syntax error before `vmnet_softc'
......
$ cd /usr/ports/emulators/vmware2/work/vmware-distrib/vmnet-only/freebsd
$ sed -n 65,75p vmnet.c
#define DEB(x)
#define DLog(level, fmt, args...)
#endif /* DEBUG */
struct vmnet_softc {
SLIST_ENTRY(vmnet_softc) list;
dev_t dev; /* Back reference to device */
struct {
struct arpcom arpcom; /* interface info */
} iface;
--
Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org>
<http://www.Awfulhak.org> <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
From owner-freebsd-emulation Wed May 24 17:57:41 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196])
by hub.freebsd.org (Postfix) with ESMTP id 6EEEE37B557
for <emulation@freebsd.org>; Wed, 24 May 2000 17:57:36 -0700 (PDT)
(envelope-from frank@exit.com)
Received: from realtime.exit.com (realtime.exit.com [206.223.0.5])
by tinker.exit.com (8.9.3/8.9.3) with ESMTP id RAA55219
for <emulation@freebsd.org>; Wed, 24 May 2000 17:57:34 -0700 (PDT)
(envelope-from frank@exit.com)
Received: (from frank@localhost)
by realtime.exit.com (8.9.3/8.9.3) id RAA06561
for emulation@freebsd.org; Wed, 24 May 2000 17:57:33 -0700 (PDT)
(envelope-from frank)
From: Frank Mayhar <frank@exit.com>
Message-Id: <200005250057.RAA06561@realtime.exit.com>
Subject: VMware 2.0 problems.
To: emulation@freebsd.org
Date: Wed, 24 May 2000 17:57:33 -0700 (PDT)
Reply-To: frank@exit.com
Organization: Exit Consulting
X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved.
X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only.
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
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
RDONLY "/dev/null" 6297480 11614995
...which corresponds to the actual layout of my dual-boot disk.
SCSI 0:4 CD-ROM
Device Type CD-ROM
Name /dev/cdrom symlink from /compat/linux/dev to /dev/cd1c.
Floppy Drive
Type File
Path /dev/fd0
Ethernet Adapters Host-only
No serial, no parallel.
Mouse autodetect.
No sound.
Memory 64MB (host memory is 512MB).
Guest OS Windows 98
I get "Can't open /dev/da0s1a for writing: Invalid argument."
That's the _best_ I get. With other configurations I see vmware crashes.
Help!
--
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
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 <emulation@FreeBSD.ORG>; 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" <knu@idaemons.org>
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 <frank@exit.com> 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
From owner-freebsd-emulation Wed May 24 20:35:35 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196])
by hub.freebsd.org (Postfix) with ESMTP id B644A37BDEE
for <emulation@FreeBSD.ORG>; Wed, 24 May 2000 20:35:31 -0700 (PDT)
(envelope-from frank@exit.com)
Received: from realtime.exit.com (realtime.exit.com [206.223.0.5])
by tinker.exit.com (8.9.3/8.9.3) with ESMTP id UAA56218;
Wed, 24 May 2000 20:35:29 -0700 (PDT)
(envelope-from frank@exit.com)
Received: (from frank@localhost)
by realtime.exit.com (8.9.3/8.9.3) id UAA08816;
Wed, 24 May 2000 20:35:27 -0700 (PDT)
(envelope-from frank)
From: Frank Mayhar <frank@exit.com>
Message-Id: <200005250335.UAA08816@realtime.exit.com>
Subject: Re: VMware 2.0 problems.
In-Reply-To: <86hfbngvsm.wl@localhost.local.idaemons.org> from Akinori -Aki-
MUSHA at "May 25, 2000 12:20:41 pm"
To: Akinori -Aki- MUSHA <knu@idaemons.org>
Date: Wed, 24 May 2000 20:35:27 -0700 (PDT)
Cc: emulation@FreeBSD.ORG
Reply-To: frank@exit.com
Organization: Exit Consulting
X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved.
X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only.
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Akinori -Aki- MUSHA wrote:
> At Wed, 24 May 2000 17:57:33 -0700 (PDT),
> Frank Mayhar <frank@exit.com> 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??
My root is on /dev/da0s2a. That's what the RDONLY you elided covered.
> I think you should specify that slice by just /dev/da0s1, with no
> trailing disklabel.
I've tried that. _That_ gives me:
May 24 20:31:46: BUG F(171):252 bugNr=3419
May 24 20:31:46: MONITOR ERROR BUG F(171):252 bugNr=3419
May 24 20:31:46: Coredump with build $Name: build-476 $
May 24 20:31:46: Writing monitor corefile 'vmware-core'
May 24 20:31:46: Msg_Post Error: msg.log.monpanic
*** VMware internal monitor error ***
BUG F(171):252 bugNr=3419
Please report this problem via the ``File an Incident'' link
at http://www.vmware.com/support.
Argh.
> The message says it all. You got refused to commit write access on
> the device just because you didn't have write permission.
I'm not naive, I covered that. Got the above crash. I just want to know
if anyone has gotten vmware working in a similar environment and if so,
how.
--
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
From owner-freebsd-emulation Wed May 24 21:59: 3 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 4504D37B731
for <freebsd-emulation@freebsd.org>; Wed, 24 May 2000 21:58:59 -0700 (PDT)
(envelope-from nsayer@quack.kfu.com)
Received: from icarus.kfu.com (icarus.kfu.com [170.1.70.37])
by quack.kfu.com (8.9.2/8.9.3) with ESMTP id VAA90021;
Wed, 24 May 2000 21:58:57 -0700 (PDT)
(envelope-from nsayer@quack.kfu.com)
Received: from quack.kfu.com by icarus.kfu.com with ESMTP
(8.9.3//ident-1.0) id VAA12401; Wed, 24 May 2000 21:58:56 -0700 (PDT)
Message-ID: <392CB310.A0A1AEAF@quack.kfu.com>
Date: Wed, 24 May 2000 21:58:56 -0700
From: Nick Sayer <nsayer@quack.kfu.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: frank@exit.com, freebsd-emulation@freebsd.org
Subject: Re: VMware 2.0 problems.
References: <200005250057.RAA06561@realtime.exit.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
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
This should be
ACCESS "/dev/da0s1" 63 6297417
The two numbers are start and length.
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
The mbr is actually only the first sector, but on my disk the first
partition,
which is the space covered by the /dev/da0s1 device, started at 63
blocks in.
Your mileage may vary.
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.
> RDONLY "/dev/null" 6297480 11614995
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
From owner-freebsd-emulation Wed May 24 22:19: 3 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196])
by hub.freebsd.org (Postfix) with ESMTP id 71CCF37BDEF
for <freebsd-emulation@freebsd.org>; Wed, 24 May 2000 22:18:58 -0700 (PDT)
(envelope-from frank@exit.com)
Received: from realtime.exit.com (realtime.exit.com [206.223.0.5])
by tinker.exit.com (8.9.3/8.9.3) with ESMTP id WAA56843;
Wed, 24 May 2000 22:18:56 -0700 (PDT)
(envelope-from frank@exit.com)
Received: (from frank@localhost)
by realtime.exit.com (8.9.3/8.9.3) id WAA10588;
Wed, 24 May 2000 22:18:55 -0700 (PDT)
(envelope-from frank)
From: Frank Mayhar <frank@exit.com>
Message-Id: <200005250518.WAA10588@realtime.exit.com>
Subject: Re: VMware 2.0 problems.
In-Reply-To: <392CB310.A0A1AEAF@quack.kfu.com> from Nick Sayer at "May 24, 2000
09:58:56 pm"
To: Nick Sayer <nsayer@quack.kfu.com>
Date: Wed, 24 May 2000 22:18:55 -0700 (PDT)
Cc: freebsd-emulation@freebsd.org
Reply-To: frank@exit.com
Organization: Exit Consulting
X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved.
X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only.
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
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
From owner-freebsd-emulation Wed May 24 22:41:58 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 2000037B72F
for <emulation@FreeBSD.ORG>; Wed, 24 May 2000 22:41:53 -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 OAA23561;
Thu, 25 May 2000 14:41:16 +0900 (JST)
Received: by daemon.local.idaemons.org (8.9.3/3.7W) id OAA06513; Thu, 25 May 2000 14:40:45 +0900 (JST)
Date: Thu, 25 May 2000 14:40:44 +0900
Message-ID: <86g0r7gpb7.wl@localhost.local.idaemons.org>
From: "Akinori -Aki- MUSHA" <knu@idaemons.org>
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 20:35:27 -0700 (PDT)"
<200005250335.UAA08816@realtime.exit.com>
References: <86hfbngvsm.wl@localhost.local.idaemons.org>
<200005250335.UAA08816@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
At Wed, 24 May 2000 20:35:27 -0700 (PDT),
Frank Mayhar <frank@exit.com> wrote:
> My root is on /dev/da0s2a. That's what the RDONLY you elided covered.
Specifying a non-root partition by "a" would be improper anyway.
> > I think you should specify that slice by just /dev/da0s1, with no
> > trailing disklabel.
>
> I've tried that. _That_ gives me:
(snip)
Then, how about using a raw slice "/dev/rda0s1" ?
> > The message says it all. You got refused to commit write access on
> > the device just because you didn't have write permission.
>
> I'm not naive, I covered that. Got the above crash. I just want to know
> if anyone has gotten vmware working in a similar environment and if so,
> how.
Nick have the knack of it. It was him who wrote "setting up a plain
disk as a workaround for the broken raw disks" section of
Hints.FreeBSD.
--
/
/__ __
/ ) ) ) ) /
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
From owner-freebsd-emulation Wed May 24 22:43:53 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196])
by hub.freebsd.org (Postfix) with ESMTP id 34CFF37B9B8
for <emulation@FreeBSD.ORG>; Wed, 24 May 2000 22:43:51 -0700 (PDT)
(envelope-from frank@exit.com)
Received: from realtime.exit.com (realtime.exit.com [206.223.0.5])
by tinker.exit.com (8.9.3/8.9.3) with ESMTP id WAA56999;
Wed, 24 May 2000 22:43:50 -0700 (PDT)
(envelope-from frank@exit.com)
Received: (from frank@localhost)
by realtime.exit.com (8.9.3/8.9.3) id WAA10973;
Wed, 24 May 2000 22:43:50 -0700 (PDT)
(envelope-from frank)
From: Frank Mayhar <frank@exit.com>
Message-Id: <200005250543.WAA10973@realtime.exit.com>
Subject: Re: VMware 2.0 problems.
In-Reply-To: <86g0r7gpb7.wl@localhost.local.idaemons.org> from Akinori -Aki-
MUSHA at "May 25, 2000 02:40:44 pm"
To: Akinori -Aki- MUSHA <knu@idaemons.org>
Date: Wed, 24 May 2000 22:43:50 -0700 (PDT)
Cc: emulation@FreeBSD.ORG
Reply-To: frank@exit.com
Organization: Exit Consulting
X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved.
X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only.
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Akinori -Aki- MUSHA wrote:
> Then, how about using a raw slice "/dev/rda0s1" ?
Same thing (they're the same device in 4.0).
--
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
From owner-freebsd-emulation Sat May 27 6:35:24 2000
Delivered-To: freebsd-emulation@freebsd.org
Received: from gaea.uk.clara.net (gaea.uk.clara.net [195.8.69.101])
by hub.freebsd.org (Postfix) with ESMTP id 1030337B51F
for <freebsd-emulation@freebsd.org>; Sat, 27 May 2000 06:35:07 -0700 (PDT)
(envelope-from mark@NOSPAM.newpower.org)
Received: from du-023-0202.claranet.co.uk ([212.126.133.202] helo=NOSPAM.newpower.org)
by gaea.uk.clara.net with esmtp (Exim 3.11 #4)
id 12vgk5-000NYD-00
for freebsd-emulation@FreeBSD.ORG; Sat, 27 May 2000 14:35:06 +0100
Message-ID: <392FCF1B.77880148@NOSPAM.newpower.org>
Date: Sat, 27 May 2000 14:35:23 +0100
From: GraWlfanG <mark@NOSPAM.newpower.org>
Organization: None
X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-emulation@FreeBSD.ORG
Subject: vmware2 forcing reboot
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-RBL-Warning: (dul.maps.vix.com) See <URL:http://mail-abuse.org/dul/>
Sender: owner-freebsd-emulation@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I've take a look through this list and now found anything that really
helps with the problem I have.
I am running 4.0-STABLE on an AMD K6-2 450 with 128MB of main memory,
and installed vmware via ports when the vmware v2 beta was available.
This ran okay.
I've since updated to the vmware2 port (and added linux_procfs and rtc)
and now whenever I run vmware and "power up" an OS the system freezes
and then reboots after about 15 seconds.
Anyone has this and/or cured it ?
--
Mark W J Redding
Chaos reigns within. Reflect, repent and reboot. Order shall return.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message