From owner-freebsd-emulation Sun Aug 6 4: 3:41 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from zmail6.easynet.fr (email.easynet.fr [195.114.64.207]) by hub.freebsd.org (Postfix) with SMTP id 5543237B77E for ; Sun, 6 Aug 2000 04:03:33 -0700 (PDT) (envelope-from fonvi@easynet.fr) Received: (qmail 78305 invoked from network); 6 Aug 2000 11:03:30 -0000 Received: from mailgate1.easynet.fr (192.168.1.2) by mailserver.easynet.fr with QMQP; 6 Aug 2000 11:03:30 -0000 Received: from adsl-92-1-170.pops.easynet.fr (HELO marduk.styx.org) (212.11.34.170) by mrelay1.easynet.fr with SMTP; 6 Aug 2000 11:03:30 -0000 Received: (from marc@localhost) by marduk.styx.org (8.9.3/8.9.3/ - 6/08/98) id NAA04651 for freebsd-emulation@FreeBSD.ORG; Sun, 6 Aug 2000 13:03:34 +0200 (CEST) (envelope-from marc) Date: Sun, 6 Aug 2000 13:03:34 +0200 From: Marc Fonvieille To: freebsd-emulation@FreeBSD.ORG Subject: Unknown format on /proc/cpuinfo with dosemu-1.0.1 Message-ID: <20000806130334.A4304@marduk.styx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i X-Useless-Header: Black Metal inc. X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm trying to play with dosemu-1.0.1 here's what i did: % mount -t linprocfs /proc /compat/linux/proc/ % /compat/linux/usr/bin/dos ERROR: Unknown format on /proc/cpuinfo The linprocfs mount run fine with vwmare2 Any advice? Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 4:31: 9 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 8B38D37B8E1 for ; Sun, 6 Aug 2000 04:31:06 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.255.96.148]) by mta02-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000806123014.EONB3760.mta02-svc.ntlworld.com@parish.my.domain>; Sun, 6 Aug 2000 12:30:14 +0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id MAA00684; Sun, 6 Aug 2000 12:30:55 +0100 (BST) (envelope-from mark) Date: Sun, 6 Aug 2000 12:30:54 +0100 From: Mark Ovens To: Marc Fonvieille Cc: freebsd-emulation@freebsd.org Subject: Re: Unknown format on /proc/cpuinfo with dosemu-1.0.1 Message-ID: <20000806123054.F257@parish> References: <20000806130334.A4304@marduk.styx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20000806130334.A4304@marduk.styx.org>; from fonvi@easynet.fr on Sun, Aug 06, 2000 at 01:03:34PM +0200 Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 01:03:34PM +0200, Marc Fonvieille wrote: > Hello, > > I'm trying to play with dosemu-1.0.1 > > here's what i did: > > % mount -t linprocfs /proc /compat/linux/proc/ > % /compat/linux/usr/bin/dos > ERROR: Unknown format on /proc/cpuinfo > > > The linprocfs mount run fine with vwmare2 Are you sure? That mount(8) line you are using appears to be mounting the FreeBSD procfs on /compat/linux/proc/. I use mount -t linprocfs linproc /compat/linux/proc but then vmware2 hangs my machine, so maybe I've got it wrong. > Any advice? > > Marc > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-emulation" in the body of the message -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 5:21:14 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from zmail6.easynet.fr (email.easynet.fr [195.114.64.207]) by hub.freebsd.org (Postfix) with SMTP id 1AC6637B5DA for ; Sun, 6 Aug 2000 05:21:10 -0700 (PDT) (envelope-from fonvi@easynet.fr) Received: (qmail 82039 invoked from network); 6 Aug 2000 12:21:07 -0000 Received: from mailgate3.easynet.fr (192.168.1.4) by mailserver.easynet.fr with QMQP; 6 Aug 2000 12:21:07 -0000 Received: from adsl-92-1-170.pops.easynet.fr (HELO marduk.styx.org) (212.11.34.170) by mrelay3.easynet.fr with SMTP; 6 Aug 2000 12:22:38 -0000 Received: (from marc@localhost) by marduk.styx.org (8.9.3/8.9.3/ - 6/08/98) id OAA06548; Sun, 6 Aug 2000 14:16:15 +0200 (CEST) (envelope-from marc) Date: Sun, 6 Aug 2000 14:16:14 +0200 From: Marc Fonvieille To: Mark Ovens Cc: freebsd-emulation@freebsd.org Subject: Re: Unknown format on /proc/cpuinfo with dosemu-1.0.1 Message-ID: <20000806141614.A6224@marduk.styx.org> References: <20000806130334.A4304@marduk.styx.org> <20000806123054.F257@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000806123054.F257@parish>; from marko@freebsd.org on Sun, Aug 06, 2000 at 12:30:54PM +0100 X-Useless-Header: Black Metal inc. X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 12:30:54PM +0100, Mark Ovens wrote: > > The linprocfs mount run fine with vwmare2 > > Are you sure? That mount(8) line you are using appears to be mounting > the FreeBSD procfs on /compat/linux/proc/. > > I use > > mount -t linprocfs linproc /compat/linux/proc > > but then vmware2 hangs my machine, so maybe I've got it wrong. > i use mount -t linprocfs /proc /compat/linux/proc/ without pb with vmware2 mount give me: linprocfs on /usr/compat/linux/proc (linprocfs, local) if i try mount -t linprocfs linproc /compat/linux/proc it runs fine too and mount give also: linprocfs on /usr/compat/linux/proc (linprocfs, local) So i think both syntax are good. Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 5:48:31 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id CA34837B5DA; Sun, 6 Aug 2000 05:48:27 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny4-45.ix.netcom.com [198.211.16.237]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id IAA01065; Sun, 6 Aug 2000 08:48:24 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id IAA00317; Sun, 6 Aug 2000 08:48:23 -0400 (EDT) (envelope-from vsilyaev) Date: Sun, 6 Aug 2000 08:48:22 -0400 From: "Vladimir N. Silyaev" To: Mark Ovens Cc: emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000806084822.A282@jupiter.delta.ny.us> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> <20000805150815.C254@parish> <200008052359.TAA00434@jupiter.delta.ny.us> <20000806014635.A255@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000806014635.A255@parish>; from marko@freebsd.org on Sun, Aug 06, 2000 at 01:46:35AM +0100 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 01:46:35AM +0100, Mark Ovens wrote: > > > > 2. Create new dummy configuration, without any hardware, and try it. It > > useless, but at least you should see a Phoenix BIOS logo. > > > > OK, I tried and it just rebooted again. This is the config file I was > using: > > Is the win95.nvram file supposed to exist? I haven't got one on my > system/ No, it's just a place in which nvram will be stored latter. > > If it doesn't help, that means you are have incompatible hardware > > (never heard before about that). > > It's a K6-233 (original K6, not a -2 or -3) I don't know. I personally don't have experience with new AMD's processors. Try to update BIOS on motherboard to latest one, and try to compile kernel without k6_mem.c file (just change it to dummy one with zero length). If you have another computer nearby, please use or external XServer or configure you FreeBSD box to use serial console. Purpose of that to know what exactly panic occurred (because when you are starting vmware, most likely , panic occurred, and it showing some information on your console, but you not able to seen that information, because you are in graphic mode). -- Regards, Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 6: 2:56 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 3ABBE37B607; Sun, 6 Aug 2000 06:02:54 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny4-45.ix.netcom.com [198.211.16.237]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id JAA20556; Sun, 6 Aug 2000 09:02:51 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id JAA00418; Sun, 6 Aug 2000 09:02:49 -0400 (EDT) (envelope-from vsilyaev) Date: Sun, 6 Aug 2000 09:02:49 -0400 From: "Vladimir N. Silyaev" To: Mark Ovens Cc: emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000806090249.A396@jupiter.delta.ny.us> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> <20000805150815.C254@parish> <200008052359.TAA00434@jupiter.delta.ny.us> <20000806012922.P254@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000806012922.P254@parish>; from marko@freebsd.org on Sun, Aug 06, 2000 at 01:29:22AM +0100 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 01:29:22AM +0100, Mark Ovens wrote: > > I don't have vmmon.ko, only vmmon_smp.ko and vmmon_up.ko. Is this > correct? Yep, for testing just remove smp one. > (I built vmware with Makefile rev 1.19) I hope that you are using not old Makefile, but all ports tree? -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 8:40:35 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from sentry.granch.com (sentry.granch.com [212.109.197.135]) by hub.freebsd.org (Postfix) with ESMTP id 3D47B37B52C for ; Sun, 6 Aug 2000 08:40:32 -0700 (PDT) (envelope-from shelton@sentry.granch.com) Received: (from shelton@localhost) by sentry.granch.com (8.9.3/8.9.3) id WAA35582 for freebsd-emulation@freebsd.org; Sun, 6 Aug 2000 22:43:24 +0700 (NOVST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 06 Aug 2000 22:43:24 +0700 (NOVST) Reply-To: "Rashid N. Achilov" Organization: Granch Ltd. From: "Rashid N. Achilov" To: freebsd-emulation@freebsd.org Subject: doscmd -rx? Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When I tried to run doscmd -rx, I have received message "mmap:Invalid argument". What does it mean and what I have to do for doscmd working with this option? -- With Best Regards. Rashid N. Achilov (RNA1-RIPE), Brainbench ID: 28514, Granch Ltd. lead engineer e-mail: achilov@granch.ru, tel (383-2) 24-2363 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 8:48:56 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by hub.freebsd.org (Postfix) with ESMTP id 7589837B62C for ; Sun, 6 Aug 2000 08:48:53 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.85.95]) by mta03-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000806154851.HBNI16423.mta03-svc.ntlworld.com@parish.my.domain>; Sun, 6 Aug 2000 16:48:51 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id QAA00470; Sun, 6 Aug 2000 16:48:39 +0100 (BST) (envelope-from mark) Date: Sun, 6 Aug 2000 16:48:38 +0100 From: Mark Ovens To: "Vladimir N. Silyaev" Cc: emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000806164837.A254@parish> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> <20000805150815.C254@parish> <200008052359.TAA00434@jupiter.delta.ny.us> <20000806014635.A255@parish> <20000806084822.A282@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20000806084822.A282@jupiter.delta.ny.us>; from vsilyaev@mindspring.com on Sun, Aug 06, 2000 at 08:48:22AM -0400 Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 08:48:22AM -0400, Vladimir N. Silyaev wrote: > On Sun, Aug 06, 2000 at 01:46:35AM +0100, Mark Ovens wrote: > > > > It's a K6-233 (original K6, not a -2 or -3) > > I don't know. I personally don't have experience with new AMD's processors. > Try to update BIOS on motherboard to latest one, and try to compile > kernel without k6_mem.c file (just change it to dummy one with zero length). > That was it! I built a new kernel and now vmware starts :) I am running my "real" Win95 and it goes through a lot of "New Hardware Detected" messages but hangs when it detects the PCI Bus. I can boot it in Safe Mode though. Thanks for your help Vladimir. -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 18:15:55 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 41BA237BCBF; Sun, 6 Aug 2000 18:15:53 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from morpheus.kfu.com (morpheus.kfu.com [205.178.90.230]) by quack.kfu.com (8.9.3/8.9.3) with ESMTP id SAA88144; Sun, 6 Aug 2000 18:15:52 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by morpheus.kfu.com with ESMTP (8.9.3//ident-1.0) id SAA34465; Sun, 6 Aug 2000 18:15:52 -0700 (PDT) Message-ID: <398E0DC8.745E02F9@quack.kfu.com> Date: Sun, 06 Aug 2000 18:15:52 -0700 From: Nick Sayer X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en-GB, en-US, en MIME-Version: 1.0 To: Robert Watson Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert Watson wrote: > > The following default-installed startup script is really, really scary: > > sysctl net.link.ether.bridge_refresh && bridge="_bridge" > kldload if_tap.ko > echo -n >/compat/linux/dev/vmnet1 > ifconfig vmnet1 $host_ip netmask $netmask > if [ _$bridge != _ ]; then > sysctl -w net.link.ether.bridge_refresh=1 > sysctl -w net.link.ether.bridge=1 > fi > > Un-announced, the vmware port enabled bridging between the ethernet > interfaces on my notebook, generated voluminous output for wi0, and broke > networking for ep0. This is a security risk, in that it automatically > enables bridging between previously un-connected LAN segments that may > have different security properties. This is against POLA in that it > breaks functionality (networking), bridges packets unto unexpected > segments (potentially breaking many other things, especially DHCP), etc. > Previously, use of networking support would create a virtual network > between the host and the guest OS, but not affect other networking > functionality. I think you're overreacting slightly. 1. You are probably the only person on the planet who has a machine with both bridging and vmware who (aparently) doesn't intend to bridge the guest onto the connected LAN. This means that you have an opportunity to customize the startup script rather than insist that everyone have it the way you like it. 2. In fact, you may be the only person on the planet who has a machine with bridging, vmware and more than one Ethernet interface active at the same time. 3. POLA in this case is the opposite of what you think it is. People who configure their kernels for bridging when they install vmware expect it to work when they fire up the guest. They would be astonished if it didn't. People bringing up vmware without bridging turned on would not see the behaviour you castigate. I believe that everyone running vmware is in one set or the other. Except you. Perhaps in a universe where subnetting was actually possible for Internet-connected networks the bridged configuration wouldn't be necessary. Perhaps when IPv6 is deployed, bridges can go away. No one would be happier than I. But until then, I don't see a problem with catering to the (vast) majority of users by default. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 18:23:10 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 1C7BA37BCC9; Sun, 6 Aug 2000 18:23:07 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.255.96.52]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000807012305.IBRL26680.mta01-svc.ntlworld.com@parish.my.domain>; Mon, 7 Aug 2000 02:23:05 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id CAA03731; Mon, 7 Aug 2000 02:23:00 +0100 (BST) (envelope-from mark) Date: Mon, 7 Aug 2000 02:23:00 +0100 From: Mark Ovens To: Nick Sayer Cc: Robert Watson , freebsd-emulation@freebsd.org Subject: Re: vmware changes result in nasty bridging mess Message-ID: <20000807022300.J254@parish> References: <398E0DC8.745E02F9@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <398E0DC8.745E02F9@quack.kfu.com>; from nsayer@quack.kfu.com on Sun, Aug 06, 2000 at 06:15:52PM -0700 Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 06:15:52PM -0700, Nick Sayer wrote: > 3. POLA in this case is the opposite of what you think it is. People who ^^^^ ???? -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 18:26:54 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 6D61A37BCBF for ; Sun, 6 Aug 2000 18:26:52 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.255.96.52]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000807012651.IBWZ26680.mta01-svc.ntlworld.com@parish.my.domain> for ; Mon, 7 Aug 2000 02:26:51 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id CAA03755 for emulation@freebsd.org; Mon, 7 Aug 2000 02:26:46 +0100 (BST) (envelope-from mark) Date: Mon, 7 Aug 2000 02:26:46 +0100 From: Mark Ovens To: emulation@freebsd.org Subject: VMware and Bochs Message-ID: <20000807022646.K254@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just got VMware running and I have a Bochs virtual disk setup with Win95 installed. Is it possible to have VMware use this? Ihaven't been able to make it work. Thanks -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 19:45:31 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id C875737B65B; Sun, 6 Aug 2000 19:45:28 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 56C7E1C5C; Sun, 6 Aug 2000 22:45:28 -0400 (EDT) Date: Sun, 6 Aug 2000 22:45:28 -0400 From: Bill Fumerola To: Nick Sayer Cc: Robert Watson , freebsd-emulation@FreeBSD.org Subject: Re: vmware changes result in nasty bridging mess Message-ID: <20000806224528.H95620@jade.chc-chimes.com> References: <398E0DC8.745E02F9@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <398E0DC8.745E02F9@quack.kfu.com>; from nsayer@quack.kfu.com on Sun, Aug 06, 2000 at 06:15:52PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 06:15:52PM -0700, Nick Sayer wrote: > I think you're overreacting slightly. I don't think he is. > 1. You are probably the only person on the planet who has a machine with both > bridging and vmware who (aparently) doesn't intend to bridge the guest > onto the connected LAN. This means that you have an opportunity to customize > the startup script rather than insist that everyone have it the way you like > it. That's nice. If I didn't turn bridging on, I don't want it on. I've been doing lots of recent ipfw testing recently and have compiled kernels with many different options that I have no intention of using just so I can test them as needed. I don't want some port turning them on by default. Lots of people just compile a kitchen sink kernel with all the firewalling options KNOWING that they can turn them on when they want them. > 3. POLA in this case is the opposite of what you think it is. People who > configure their kernels for bridging when they install vmware expect it to work > when they fire up the guest. They would be astonished if it didn't. People > bringing up vmware without bridging turned on would not see the behaviour you > castigate. I believe that everyone running vmware is in one set or the other. Except > you. I was astonished when I heard that vmware2 turned on bridgeing if it could find it. On a side note, if I was a {ports ,}security officer, I would have already either commented out the offending lines or marked the port FORBIDDEN. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 19:49:51 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id BE55A37B5B6; Sun, 6 Aug 2000 19:49:47 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id WAA92739; Sun, 6 Aug 2000 22:49:43 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 6 Aug 2000 22:49:43 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Nick Sayer Cc: freebsd-emulation@FreeBSD.ORG, security-officer@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess In-Reply-To: <398E0DC8.745E02F9@quack.kfu.com> 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 On Sun, 6 Aug 2000, Nick Sayer wrote: > I think you're overreacting slightly. Possibly; I'd like to think I'm reporting a serious set of bugs: one to do with correctness of a feature, and the other to do with potentially serious security implications of the feature, which may not have been fully thought out. I'm not opposed to supporting bridging with vmware, I'm pointing out that there are substantial problems with the current implementation, and I'd like it re-thought-out. In the mean time, I think it would be wise to disable the sysctl-munging in vmware.sh, while we fiture out how it should behave. The BRIDGE option in kernel was not intended to be used in such a hands-free way (i.e., it requires understanding of the topology, and can interact poorly with other networking features (IP forwarding/NAT) if not thought through carefully). We may need to extend the BRIDGE behavior, or tidy it up some, for it to be used in the way vmware currently attempts to use it. > 1. You are probably the only person on the planet who has a machine with > both > bridging and vmware who (aparently) doesn't intend to bridge the guest > onto > the connected LAN. This means that you have an opportunity to customize > the > startup script rather than insist that everyone have it the way you like > it. Possibly true, but I'm interested in POLA for many situations, not just the common case. :-) See below, however. > 2. In fact, you may be the only person on the planet who has a machine > with > bridging, vmware and more than one Ethernet interface active at the same > time. No, I'm worried about the following case: a machine with two interfaces, and vmware, who then tries out bridging for the purposes of using vmware. The result of that operation is not POLA, as the BRIDGE documentation clearly specifies that to turn on bridging, you set the sysctl, and that the option is passive until then. As the port is currently written, it enables BRIDGE at every boot, regardless of a guest running, and affects more than just the guest environment, bridging all interfaces. Also, I pointed out that enabling bridging with if_tap and two different ethernet devices results in extremely unfortunate behavior: failure of one to operate at all, and kernel-spewing (per-packet) in the other. > 3. POLA in this case is the opposite of what you think it is. People who > configure > their kernels for bridging when they install vmware expect it to work > when they > fire up the guest. They would be astonished if it didn't. People > bringing up > vmware without bridging turned on would not see the behaviour you > castigate. I > believe that everyone running vmware is in one set or the other. Except > you. That is incorrect. People enabling BRIDGE should see the documented behavior: nothing, until they enable the sysctl. POLA suggests that the documentation should match the functionality. :-) Not only that, users with multiple interfaces (not as uncommon as you'd like to think -- witness vmware on a box between a DSL modem and a home network) will find that suddenly the two networks carry each others traffic. > Perhaps in a universe where subnetting was actually possible for > Internet-connected > networks the bridged configuration wouldn't be necessary. Perhaps when > IPv6 is deployed, > bridges can go away. No one would be happier than I. But until then, I > don't see a > problem with catering to the (vast) majority of users by default. I'm not clear how bridging relates to IPv6. The bridging issue has to do with transparency, and throwing arbitrary IP routing into there won't help. Probably, approximations of the correct behavior should involve the following: During the install, the vmware user is asked what type of networking support they want. Responses can include bridged, or non-bridged. If bridged, they are instructed that they must enable the BRIDGE kernel option, and decide what bridging means to them. Probably, it means bridging a specific interface with the if_tap interface, rather than arbitrarily bridging all interfaces with the if_tap interface. If they have an existing bridge configured, then they need to decide if if_tap will be added to that bridge, or be part of a new bridge. All of this is configured using sysctls, and should probably be in /etc/sysctl.conf, possibly added/modified with a helper tool. POLA should mean not making a mess of an existing (potentially administered) network topology. Also, as I pointed out, this feature is broken for at least two different driver types -- this may be a function of the behavior of if_tap in combination with bridging: the vmnet driver used to (and may still) behave differently if used without a process attached to the user-land tap device. Clearly, this needs a bit more debugging, and is probably not ready for prime time. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 20:27:48 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 11D7637BD1E; Sun, 6 Aug 2000 20:27:41 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny9-43.ix.netcom.com [198.211.18.43]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA11379; Sun, 6 Aug 2000 23:27:25 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id XAA08941; Sun, 6 Aug 2000 23:27:23 -0400 (EDT) (envelope-from vsilyaev) Date: Sun, 6 Aug 2000 23:27:23 -0400 From: "Vladimir N. Silyaev" To: Mark Ovens Cc: emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000806232722.B3251@jupiter.delta.ny.us> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> <20000805150815.C254@parish> <200008052359.TAA00434@jupiter.delta.ny.us> <20000806014635.A255@parish> <20000806084822.A282@jupiter.delta.ny.us> <20000806164837.A254@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000806164837.A254@parish>; from marko@freebsd.org on Sun, Aug 06, 2000 at 04:48:38PM +0100 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 04:48:38PM +0100, Mark Ovens wrote: > > > It's a K6-233 (original K6, not a -2 or -3) > > > > I don't know. I personally don't have experience with new AMD's processors. > > Try to update BIOS on motherboard to latest one, and try to compile > > kernel without k6_mem.c file (just change it to dummy one with zero length). > > > > That was it! I built a new kernel and now vmware starts :) What's exactly? Kernel recompiling with fresh source code, or truncating k6_mem file? > I am > running my "real" Win95 and it goes through a lot of "New Hardware > Detected" messages but hangs when it detects the PCI Bus. I can boot > it in Safe Mode though. You should load in Safe Mode, and create new hardware profile. At other case you can easily broke you "real" configuration. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 23: 4:56 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 8157737BCE4; Sun, 6 Aug 2000 23:04:48 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.9.3/8.9.3) with ESMTP id XAA89631; Sun, 6 Aug 2000 23:04:47 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (ssmail@localhost) by medusa.kfu.com (8.9.3/8.8.8) with ESMTP id XAA15571; Sun, 6 Aug 2000 23:04:46 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) X-Authentication-Warning: medusa.kfu.com: ssmail owned process doing -bs Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.9.3//ident-1.0) id XAA00610; Sun, 6 Aug 2000 23:04:45 -0700 (PDT) Message-ID: <398E517D.A524966F@quack.kfu.com> Date: Sun, 06 Aug 2000 23:04:45 -0700 From: Nick Sayer X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Robert Watson Cc: freebsd-emulation@FreeBSD.ORG, security-officer@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert Watson wrote: > > On Sun, 6 Aug 2000, Nick Sayer wrote: > > > I think you're overreacting slightly. > > Possibly; I'd like to think I'm reporting a serious set of bugs: one to do > with correctness of a feature, and the other to do with potentially > serious security implications of the feature, which may not have been > fully thought out. I'm not opposed to supporting bridging with vmware, > I'm pointing out that there are substantial problems with the current > implementation, and I'd like it re-thought-out. > > In the mean time, I think it would be wise to disable the sysctl-munging > in vmware.sh, while we fiture out how it should behave. The BRIDGE option > in kernel was not intended to be used in such a hands-free way (i.e., it > requires understanding of the topology, and can interact poorly with other > networking features (IP forwarding/NAT) if not thought through carefully). > We may need to extend the BRIDGE behavior, or tidy it up some, for it to > be used in the way vmware currently attempts to use it. You act as though people are installing vmware largely on machines where complex network topographies exist. I would be more inclined to agree with your position if vmware was something that was part of the default installation. It is not. As such, having it be sure not to offend any possible user is an unnecessary hinderance. vmware does a ton of other things that are detremental from a purely security-conscious point of view. But a more pragmatic view balances that risk against the benefits gained. > > > 1. You are probably the only person on the planet who has a machine with > > both > > bridging and vmware who (aparently) doesn't intend to bridge the guest > > onto > > the connected LAN. This means that you have an opportunity to customize > > the > > startup script rather than insist that everyone have it the way you like > > it. > > Possibly true, but I'm interested in POLA for many situations, not just > the common case. :-) See below, however. But isn't that which astonishes least that which astonishes the least number of people?! > > > 2. In fact, you may be the only person on the planet who has a machine > > with > > bridging, vmware and more than one Ethernet interface active at the same > > time. > > No, I'm worried about the following case: a machine with two interfaces, > and vmware, who then tries out bridging for the purposes of using vmware. Everyone with this configuration, please raise their hands. Remember, to qualify the two interfaces must be run simultaneously. > The result of that operation is not POLA, as the BRIDGE documentation > clearly specifies that to turn on bridging, you set the sysctl, and that > the option is passive until then. As the port is currently written, it > enables BRIDGE at every boot, regardless of a guest running, and affects > more than just the guest environment, bridging all interfaces. And for both of you out there with two Ethernet cards and VMware running, you might want to add a bridge_cfg ioctl between the refresh and the enabling sysctl. > > Also, I pointed out that enabling bridging with if_tap and two different > ethernet devices results in extremely unfortunate behavior: failure of one > to operate at all, and kernel-spewing (per-packet) in the other. I have not been able to duplicate these results, though I have heard it said that wi is incapable of transmitting packets with other than its own Ethernet address, which would disqualify it as the host interface for a bridged vmware configuration. Perhaps that should be added to the hints file. > > > 3. POLA in this case is the opposite of what you think it is. People who > > configure > > their kernels for bridging when they install vmware expect it to work > > when they > > fire up the guest. They would be astonished if it didn't. People > > bringing up > > vmware without bridging turned on would not see the behaviour you > > castigate. I > > believe that everyone running vmware is in one set or the other. Except > > you. > > That is incorrect. People enabling BRIDGE should see the documented > behavior: nothing, until they enable the sysctl. POLA suggests that the > documentation should match the functionality. :-) > > Not only that, users with multiple interfaces (not as uncommon as you'd > like to think -- witness vmware on a box between a DSL modem and a home > network) will find that suddenly the two networks carry each others > traffic. If I had a gateway box like that, I don't think I'd be running vmware on it. I don't think I'm alone. > > > Perhaps in a universe where subnetting was actually possible for > > Internet-connected > > networks the bridged configuration wouldn't be necessary. Perhaps when > > IPv6 is deployed, > > bridges can go away. No one would be happier than I. But until then, I > > don't see a > > problem with catering to the (vast) majority of users by default. > > I'm not clear how bridging relates to IPv6. With IPv6 everyone will have enough subnets that bridging will not be nearly as necessary as it is now. > The bridging issue has to do > with transparency, and throwing arbitrary IP routing into there won't > help. Huh?! > > Probably, approximations of the correct behavior should involve the > following: > > During the install, the vmware user is asked what type of networking > support they want. Responses can include bridged, or non-bridged. If > bridged, they are instructed that they must enable the BRIDGE kernel > option, and decide what bridging means to them. Probably, it means > bridging a specific interface with the if_tap interface, rather than > arbitrarily bridging all interfaces with the if_tap interface. If they > have an existing bridge configured, then they need to decide if if_tap > will be added to that bridge, or be part of a new bridge. All of this is > configured using sysctls, and should probably be in /etc/sysctl.conf, > possibly added/modified with a helper tool. Patches are welcome. > > POLA should mean not making a mess of an existing (potentially > administered) network topology. Also, as I pointed out, this feature is > broken for at least two different driver types -- this may be a function > of the behavior of if_tap in combination with bridging: the vmnet driver > used to (and may still) behave differently if used without a process > attached to the user-land tap device. Clearly, this needs a bit more > debugging, and is probably not ready for prime time. Those of us to whom you complain have not been able to duplicate your failures. I have had no problems at all with or without vmware running. If it didn't work, I doubt those involved (myself included) would have committed it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 23: 9:53 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 1C7D137BE04; Sun, 6 Aug 2000 23:09:50 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.9.3/8.9.3) with ESMTP id XAA89667; Sun, 6 Aug 2000 23:09:48 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (ssmail@localhost) by medusa.kfu.com (8.9.3/8.8.8) with ESMTP id XAA15749; Sun, 6 Aug 2000 23:09:48 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) X-Authentication-Warning: medusa.kfu.com: ssmail owned process doing -bs Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.9.3//ident-1.0) id XAA00622; Sun, 6 Aug 2000 23:09:47 -0700 (PDT) Message-ID: <398E52AB.5CAA967B@quack.kfu.com> Date: Sun, 06 Aug 2000 23:09:47 -0700 From: Nick Sayer X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fumerola Cc: Robert Watson , freebsd-emulation@FreeBSD.org Subject: Re: vmware changes result in nasty bridging mess References: <398E0DC8.745E02F9@quack.kfu.com> <20000806224528.H95620@jade.chc-chimes.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Fumerola wrote: > > On Sun, Aug 06, 2000 at 06:15:52PM -0700, Nick Sayer wrote: > > > I think you're overreacting slightly. > > I don't think he is. > > > 1. You are probably the only person on the planet who has a machine with both > > bridging and vmware who (aparently) doesn't intend to bridge the guest > > onto the connected LAN. This means that you have an opportunity to customize > > the startup script rather than insist that everyone have it the way you like > > it. > > That's nice. If I didn't turn bridging on, I don't want it on. Then edit the script and turn it off rather than insisting that the whole world do it the way you like it. > > I've been doing lots of recent ipfw testing recently and have compiled kernels with > many different options that I have no intention of using just so I can test them > as needed. I don't want some port turning them on by default. Lots of people > just compile a kitchen sink kernel with all the firewalling options KNOWING that > they can turn them on when they want them. > > > 3. POLA in this case is the opposite of what you think it is. People who > > configure their kernels for bridging when they install vmware expect it to work > > when they fire up the guest. They would be astonished if it didn't. People > > bringing up vmware without bridging turned on would not see the behaviour you > > castigate. I believe that everyone running vmware is in one set or the other. Except > > you. > > I was astonished when I heard that vmware2 turned on bridgeing if it > could find it. I am astonished that it is causing you such mental trauma. > > On a side note, if I was a {ports ,}security officer, I would have already either > commented out the offending lines or marked the port FORBIDDEN. Then we have a difference of opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 23:20:11 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.14.126.45]) by hub.freebsd.org (Postfix) with ESMTP id 4322D37BA01 for ; Sun, 6 Aug 2000 23:20:09 -0700 (PDT) (envelope-from mdharnois@home.com) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.9.3/8.9.3) id BAA16264; Mon, 7 Aug 2000 01:20:08 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: freebsd-emulation@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess References: <398E0DC8.745E02F9@quack.kfu.com> <20000806224528.H95620@jade.chc-chimes.com> From: Michael Harnois Date: 07 Aug 2000 01:20:08 -0500 In-Reply-To: Bill Fumerola's message of "Sun, 6 Aug 2000 22:45:28 -0400" Message-ID: <864s4xy4mf.fsf@mharnois.workgroup.net> Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Carlsbad Caverns) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 6 Aug 2000 22:45:28 -0400, Bill Fumerola said: > I don't think he is. Nor do I. I have two Ethernet interfaces, one with a real IP address, and one with an internal-only address. Bridging them raises hell. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org Perish discretion when it interferes with duty. -- Hannah More To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Aug 6 23:26:18 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id F39B337BD03; Sun, 6 Aug 2000 23:26:15 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 9520D1C5C; Mon, 7 Aug 2000 02:26:15 -0400 (EDT) Date: Mon, 7 Aug 2000 02:26:15 -0400 From: Bill Fumerola To: Nick Sayer Cc: Robert Watson , freebsd-emulation@FreeBSD.org Subject: Re: vmware changes result in nasty bridging mess Message-ID: <20000807022615.K95620@jade.chc-chimes.com> References: <398E0DC8.745E02F9@quack.kfu.com> <20000806224528.H95620@jade.chc-chimes.com> <398E52AB.5CAA967B@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <398E52AB.5CAA967B@quack.kfu.com>; from nsayer@quack.kfu.com on Sun, Aug 06, 2000 at 11:09:47PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 11:09:47PM -0700, Nick Sayer wrote: > > That's nice. If I didn't turn bridging on, I don't want it on. > > Then edit the script and turn it off rather than insisting that the > whole world do it the way you like it. Luckily, security sanity is on my side, so the rest of the world is just going to have to deal with it. > > On a side note, if I was a {ports ,}security officer, I would have already either > > commented out the offending lines or marked the port FORBIDDEN. > > Then we have a difference of opinion. Yep. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 0:14:28 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from localhost.zbzoom.net (acs-24-154-5-187.zoominternet.net [24.154.5.187]) by hub.freebsd.org (Postfix) with ESMTP id BEBCB37B58E for ; Mon, 7 Aug 2000 00:14:25 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from localhost (localhost [127.0.0.1]) by topperwein.zbzoom.net (8.9.3/8.9.3) with ESMTP id RAA09288 for ; Sun, 6 Aug 2000 17:07:54 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Sun, 6 Aug 2000 17:07:54 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: freebsd-emulation@freebsd.org Subject: Re: Unknown format on /proc/cpuinfo with dosemu-1.0.1 In-Reply-To: <20000806123054.F257@parish> 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 On Sun, 6 Aug 2000, Mark Ovens wrote: > On Sun, Aug 06, 2000 at 01:03:34PM +0200, Marc Fonvieille wrote: > > Hello, > > > > I'm trying to play with dosemu-1.0.1 > > > > here's what i did: > > > > % mount -t linprocfs /proc /compat/linux/proc/ > > % /compat/linux/usr/bin/dos > > ERROR: Unknown format on /proc/cpuinfo > > > > > > The linprocfs mount run fine with vwmare2 > > Are you sure? That mount(8) line you are using appears to be mounting > the FreeBSD procfs on /compat/linux/proc/. > > I use > > mount -t linprocfs linproc /compat/linux/proc Put this in your /etc/fstab: linproc /compat/linux/proc linprocfs rw 0 0 and then mount /compat/linux/proc That works fine for my vmware2. -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 5: 1:12 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 9C39A37BD90; Mon, 7 Aug 2000 05:01:04 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny7-10.ix.netcom.com [198.211.17.138]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id IAA17708; Mon, 7 Aug 2000 08:01:01 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id IAA00335; Mon, 7 Aug 2000 08:00:59 -0400 (EDT) (envelope-from vsilyaev) Date: Sun, 6 Aug 2000 23:23:39 -0400 From: "Vladimir N. Silyaev" To: emulation@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess Message-ID: <20000806232339.A3251@jupiter.delta.ny.us> References: <200008032335.TAA01440@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="azLHFNyN32YCQGCU" X-Mailer: Mutt 1.0i X-Mailer: Mutt 1.0i In-Reply-To: ; from rwatson@FreeBSD.ORG on Sun, Aug 06, 2000 at 07:14:59PM -0400 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Ok, guys. See in the attachment fix, you should apply it to prevent current behavior. On Sun, Aug 06, 2000 at 07:14:59PM -0400, Robert Watson wrote: > On Thu, 3 Aug 2000, Vladimir N. Silyaev wrote: > > > >Bridging on by default may > > >have nasty side effects for multi-interface machines (especially security > > >side effects). > > It's several ways to work around about that: > > - compile kernel without bridging support. > > - remove bridge starting code vmware.sh file in rc.d directory. > > - create special bridge cluster with one real interface and with one emulated > > Actually, I was hoping that the vmware port wouldn't interfere with > existing configurations on the box :-). I compile in the BRIDGE code so > that I can test/develop with it, not so that ethernet support on the > notebook can be broken after I install the vmware port, or so that a port > can arbitrarily turn on bridging of all attached ethernet devices. > > > >I haven't read the code (I admit) but I finding the > > >current behavior both (a) irritating (messages) and (b) worrying > > >(unpredicted bridging with potential side effects). > > I don't know I never seen such effect. Could you to do more testing > > about that. > > The behavior with the wi0 ethernet driver seems to be continuous printing > of the output included in my previous message. > > With the ep0 driver, the results are actually much worse -- I'm unable to > use networking at all while the bridging sysctl is enabled (the default). > While the sysctl is enabled, dhclient fails for that interface, and any > attempt to manually configure and use it results in a route not found. > When I disable the sysctl, networking begins to work on the box. > > The following default-installed startup script is really, really scary: > > sysctl net.link.ether.bridge_refresh && bridge="_bridge" > kldload if_tap.ko > echo -n >/compat/linux/dev/vmnet1 > ifconfig vmnet1 $host_ip netmask $netmask > if [ _$bridge != _ ]; then > sysctl -w net.link.ether.bridge_refresh=1 > sysctl -w net.link.ether.bridge=1 > fi > > Un-announced, the vmware port enabled bridging between the ethernet > interfaces on my notebook, generated voluminous output for wi0, and broke > networking for ep0. This is a security risk, in that it automatically > enables bridging between previously un-connected LAN segments that may > have different security properties. This is against POLA in that it > breaks functionality (networking), bridges packets unto unexpected > segments (potentially breaking many other things, especially DHCP), etc. > Previously, use of networking support would create a virtual network > between the host and the guest OS, but not affect other networking > functionality. -- Vladimir --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="vmware.diff" Index: files/vmware.sh =================================================================== RCS file: /home/vns/cvs/vmware/vmware/vmmon-only/freebsd/port/files/vmware.sh,v retrieving revision 1.5 diff -u -r1.5 vmware.sh --- files/vmware.sh 2000/07/31 00:54:37 1.5 +++ files/vmware.sh 2000/08/07 03:16:16 @@ -8,6 +8,7 @@ networking=@@NETWORKING@@ host_ip=@@HOST_IP@@ netmask=@@NETMASK@@ +start_bridge=0 [ -x $vmware_dir/bin/vmware ] || exit @@ -19,17 +20,32 @@ exec >/dev/null + if [ $networking -eq 1 ]; then + if sysctl net.link.ether.bridge_refresh; then + if sysctl net.link.ether.bridge|grep 1; then + bridge="_bridge_on" + start_bridge=0 + else + if [ $start_bridge -eq 1 ]; then + bridge="_bridge" + else + bridge="_bridge_off" + fi + fi + fi + fi + case $1 in start) kldload ${vmware_dir}/lib/modules/vmmon_${suffix}.ko if [ $networking -eq 1 ]; then - sysctl net.link.ether.bridge_refresh && bridge="_bridge" kldload if_tap.ko echo -n >@@LINUX_DIR@@/dev/vmnet1 ifconfig vmnet1 $host_ip netmask $netmask + sysctl net.link.ether.bridge if [ _$bridge != _ ]; then sysctl -w net.link.ether.bridge_refresh=1 - sysctl -w net.link.ether.bridge=1 + [ $start_bridge -eq 1 ] && sysctl -w net.link.ether.bridge=1 fi fi echo -n " VMware${bridge}" >&2 @@ -40,7 +56,6 @@ if [ $networking -eq 1 ]; then ifconfig vmnet1 down ifconfig vmnet1 delete $host_ip - sysctl net.link.ether.bridge_refresh && bridge="_bridge" [ _$bridge != _ ] && sysctl -w net.link.ether.bridge_refresh=1 fi ;; --azLHFNyN32YCQGCU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 6:16:22 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from knock.econ.vt.edu (knock.econ.vt.edu [128.173.172.240]) by hub.freebsd.org (Postfix) with ESMTP id 03AEB37B78C for ; Mon, 7 Aug 2000 06:16:20 -0700 (PDT) (envelope-from rdmurphy@knock.econ.vt.edu) Received: (from rdmurphy@localhost) by knock.econ.vt.edu (8.9.3/8.9.3) id JAA09155; Mon, 7 Aug 2000 09:16:18 -0400 (EDT) (envelope-from rdmurphy) From: "Russell D. Murphy Jr." MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14734.46754.896118.510053@knock.econ.vt.edu> Date: Mon, 7 Aug 2000 09:16:18 -0400 (EDT) To: freebsd-emulation@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess In-Reply-To: <398E517D.A524966F@quack.kfu.com> References: <398E517D.A524966F@quack.kfu.com> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Reply-To: rdmurphy@vt.edu Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hand raised. According to Nick Sayer (August 6, 2000): | Everyone with this configuration, please raise their hands. | | Remember, to qualify the two interfaces must be run simultaneously. One of the nice things about FreeBSD is that it (and most ports) make few assumptions about "how everyone does" . . . whatever. Russ Murphy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 7:36:43 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ns2.destek.net (ns2.Destek.Net [192.156.97.61]) by hub.freebsd.org (Postfix) with ESMTP id 227F537B68B for ; Mon, 7 Aug 2000 07:36:39 -0700 (PDT) (envelope-from marc@destek.net) Received: from ns2.Destek.Net (ns2.Destek.Net [192.156.97.61]) by ns2.destek.net (8.10.0/8.10.0) with ESMTP id e77EWk534606; Mon, 7 Aug 2000 10:32:46 -0400 (EDT) Date: Mon, 7 Aug 2000 10:32:45 -0400 (EDT) From: Marc Evans To: Marcel Moolenaar Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: WebTrends on FreeBSD 4.1 (Linux Emulation) In-Reply-To: <3988B438.F4ADB5F7@cup.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1431494271-965658765=:12525" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1431494271-965658765=:12525 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello - I have embarked on implementing the missing syscall. I believe that I have code that is 95% complete. I am however not finding obvious information to place into the siginfo_t structure to return to the caller. Can anyone provide me with any pointers to code that I might reference, or anything that could help me with this last aspect? Also, any other general comments on this code is also appreciated. Thanks - Marc On Wed, 2 Aug 2000, Marcel Moolenaar wrote: > Marc Evans wrote: > > > > /kernel: linux: syscall rt_sigtimedwait is obsoleted or not implemented > > > > I have done some searches on the prior e-mail on the lists and I am not > > finding any discussion about 1) Is there a good workaround? 2) What was > > the basis of decision resulting in some syscalls not being implemented? > > 1) Implementing the syscall is the best "workaround" :-) > 2) This is not so much a decision. So far nothing depended > on the syscall. Implementation of syscalls is primarily > based on available time and how often Linux binaries > fail because it isnt implemented. > > > I am considering trying to implement the function, but if there is already > > a good workaround then please let me know. Also, if there is good reason > > not to bother trying to implement this, I would really appreciate > > knowing... > > I think that implementing the syscall is the best approach. > > -- > Marcel Moolenaar > mail: marcel@cup.hp.com / marcel@FreeBSD.org > tel: (408) 447-4222 > --0-1431494271-965658765=:12525 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="sig.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="sig.c" DQpzdGF0aWMgaW50DQpsaW51eF9kb19zaWd0aW1lZHdhaXQoc3RydWN0IHBy b2MgKnAsIGxpbnV4X3NpZ3NldF90ICptYXNrLA0KCXNpZ2luZm9fdCAqcHRy LCBzdHJ1Y3QgdGltZXZhbCAqdHYsIHNpemVfdCBzaWdzZXRzaXplKQ0Kew0K ICAgIHNpZ3NldF90IG9zZXQsIGJzZXQ7DQogICAgaW50IHJldCwgc2lnLCB0 aW1vOw0KDQogICAgLyogVmFsaWRhdGUgdGhlIGFyZ3VtZW50cyBwYXNzZWQg aW4gKi8NCiAgICBpZiAoc2lnc2V0c2l6ZSAhPSBzaXplb2YobGludXhfc2ln c2V0X3QpKQ0KCXJldHVybigtRUlOVkFMKTsNCg0KICAgIGlmICh0diAmJiAo dHYtPnR2X3VzZWMgPj0gMTAwMDAwMDAwMEwgfHwgdHYtPnR2X3VzZWMgPCAw IHx8DQoJICAgIHR2LT50dl9zZWMgPCAwIHx8IGl0aW1lcmZpeCh0dikpKQ0K CXJldHVybigtRUlOVkFMKTsNCg0KICAgIC8qIElmIHRoZXJlIGlzIGEgc2ln bmFsIHF1ZXVlZCwgaW1tZWRpYXRlbHkgY29tbXVuaWNhdGUgdGhhdCBiYWNr LiAqLw0KICAgIGxpbnV4X3RvX2JzZF9zaWdzZXQobWFzaywmYnNldCk7DQog ICAgU0lHU0VURVEob3NldCxwLT5wX3NpZ2xpc3QpOw0KICAgIFNJR1NFVEVR KHAtPnBfc2lnbGlzdCxic2V0KTsNCiAgICB0aW1vID0gdHYtPnR2X3NlYyA+ IDI0ICogNjAgKiA2MCA/IDI0ICogNjAgKiA2MCAqIGh6IDogdHZ0b2h6KHR2 KTsNCiAgICByZXQgPSB0c2xlZXAoJnNlbHdhaXQsIFBTT0NLIHwgUENBVENI LCAic2lndGltZWR3YWl0IiwgdGltbyk7DQogICAgc2lnID0gQ1VSU0lHKHAp Ow0KICAgIFNJR1NFVEVRKHAtPnBfc2lnbGlzdCxvc2V0KTsNCg0KICAgIGlm IChzaWcpIHsNCglyZXQgPSBzaWc7DQoJaWYgKHB0cikgew0KCSAgICBtZW1z ZXQocHRyLDAsc2l6ZW9mKCpwdHIpKTsNCgkgICAgcHRyLT5zaV9zaWdubyA9 IHNpZzsNCg0KLyoJCVRoZXNlIHJlYWxseSBuZWVkIHRvIGJlIGFjY3VyYXRl bHkgZmlsbGVkIGluIGZvciBwcm9wZXINCiAqCQliZWhhdmlvciBvZiB0aGUg YXBwbGljYXRpb24ocykuIEkgYW0gaGF2aW5nIHRyb3VibGUNCiAqCQlmaWd1 cmluZyBvdXQgd2hlcmUgdG8gZXh0cmFjdCB0aGUgaW5mb3JtYXRpb24gdGhv dWdoLi4uDQogKgkgICAgcHRyLT5zaV9lcnJubyA9IDA7DQogKgkgICAgcHRy LT5zaV9jb2RlID0gMDsNCiAqCSAgICBwdHItPnNpX3BpZCA9IDA7DQogKgkg ICAgcHRyLT5zaV91aWQgPSAwOw0KICovDQoJfQ0KI2lmZGVmIERFQlVHDQog ICAgICAgIHByaW50ZigiTGludXgtZW11bCglbGQpOiBzaWduYWwgcmVjZWl2 ZWQgKCVkKVxuIiwobG9uZylwLT5wX3BpZCxzaWcpOw0KI2VuZGlmDQogICAg fSBlbHNlIHsNCglpZiAocmV0ID09IEVXT1VMREJMT0NLKQ0KCSAgICByZXQg PSAtRUlOVFI7DQoJZWxzZQ0KCSAgICByZXQgPSAtcmV0Ow0KI2lmZGVmIERF QlVHDQogICAgICAgIHByaW50ZigiTGludXgtZW11bCglbGQpOiBubyBzaWdu YWwgKCVkKVxuIiwobG9uZylwLT5wX3BpZCxyZXQpOw0KI2VuZGlmDQogICAg fQ0KICAgIHJldHVybihyZXQpOw0KfQ0KDQoNCmludA0KbGludXhfcnRfc2ln dGltZWR3YWl0KHN0cnVjdCBwcm9jICpwLCBzdHJ1Y3QgbGludXhfcnRfc2ln dGltZWR3YWl0X2FyZ3MgKmFyZ3MpDQp7DQogICAgaW50IGVycm9yOw0KICAg IGxpbnV4X3NpZ3NldF90IG1hc2s7DQogICAgc3RydWN0IHRpbWV2YWwgdHM7 DQoNCiNpZmRlZiBERUJVRw0KICAgIHByaW50ZigiTGludXgtZW11bCglbGQp OiBydF9zaWd0aW1lZHdhaXQoJXAsICVwLCAlcCwgJWQpXG4iLA0KICAgICAg IChsb25nKXAtPnBfcGlkLCBhcmdzLT5tYXNrLCBhcmdzLT5wdHIsIGFyZ3Mt PnRpbWVvdXQsIGFyZ3MtPnNpZ3NldHNpemUpOw0KI2VuZGlmDQoNCiAgICBp ZiAoYXJncy0+c2lnc2V0c2l6ZSAhPSBzaXplb2YobGludXhfc2lnc2V0X3Qp KQ0KCXJldHVybigtRUlOVkFMKTsNCg0KICAgIGlmICgoZXJyb3IgPSBjb3B5 aW4oYXJncy0+bWFzaywgJm1hc2ssIHNpemVvZihtYXNrKSkpKQ0KCXJldHVy bigtZXJyb3IpOw0KDQogICAgaWYgKGFyZ3MtPnRpbWVvdXQpIHsNCglpZiAo KGVycm9yID0gY29weWluKGFyZ3MtPnRpbWVvdXQsICZ0cywgc2l6ZW9mKHRz KSkpKQ0KCSAgICByZXR1cm4oLWVycm9yKTsNCiNpZmRlZiBERUJVRw0KCXBy aW50ZigiTGludXgtZW11bCglbGQpOiBpbmNvbWluZyB0aW1lb3V0ICglbGQv JWxkKVxuIiwNCgkgICAgKGxvbmcpcC0+cF9waWQsIHRzLnR2X3NlYywgdHMu dHZfdXNlYyk7DQojZW5kaWYNCglpZiAoaXRpbWVyZml4KCZ0cykpIHsNCgkg ICAgLyogVGhlIHRpbWVvdXQgd2FzIGludmFsaWQuIENvbnZlcnQgaXQgdG8g c29tZXRoaW5nDQoJICAgICAqIHZhbGlkIHRoYXQgd2lsbCBhY3QgYXMgaXQg ZG9lcyB1bmRlciBMaW51eC4NCgkgICAgICovDQoJICAgIHRzLnR2X3NlYyAr PSB0cy50dl91c2VjIC8gMTAwMDAwMDsNCgkgICAgdHMudHZfdXNlYyAlPSAx MDAwMDAwOw0KCSAgICBpZiAodHMudHZfdXNlYyA8IDApIHsNCgkJdHMudHZf c2VjIC09IDE7DQoJCXRzLnR2X3VzZWMgKz0gMTAwMDAwMDsNCgkgICAgfQ0K CSAgICBpZiAodHMudHZfc2VjIDwgMCkNCgkJdGltZXZhbGNsZWFyKCZ0cyk7 DQojaWZkZWYgREVCVUcNCgkgICAgcHJpbnRmKCJMaW51eC1lbXVsKCVsZCk6 IGNvbnZlcnRlZCB0aW1lb3V0ICglbGQvJWxkKVxuIiwNCgkJKGxvbmcpcC0+ cF9waWQsIHRzLnR2X3NlYywgdHMudHZfdXNlYyk7DQojZW5kaWYNCgl9DQog ICAgfQ0KICAgIGVycm9yID0gbGludXhfZG9fc2lndGltZWR3YWl0KHAsJm1h c2ssYXJncy0+cHRyLA0KCWFyZ3MtPnRpbWVvdXQgPyAmdHMgOiBOVUxMLA0K CWFyZ3MtPnNpZ3NldHNpemUpOw0KDQojaWZkZWYgREVCVUcNCiAgICBwcmlu dGYoIkxpbnV4LWVtdWwoJWxkKTogcmV0dXJuaW5nICglZClcbiIsKGxvbmcp cC0+cF9waWQsZXJyb3IpOw0KI2VuZGlmDQoNCiAgICByZXR1cm4gZXJyb3I7 DQp9DQo= --0-1431494271-965658765=:12525-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 8: 1:46 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from scallop.baynetworks.com (ns5.baynetworks.com [194.133.90.101]) by hub.freebsd.org (Postfix) with ESMTP id 48A2E37B612; Mon, 7 Aug 2000 08:01:28 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by scallop.baynetworks.com (8.9.1/8.9.1) with ESMTP id RAA15458; Mon, 7 Aug 2000 17:06:22 +0200 (MET DST) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id LAA09741; Mon, 7 Aug 2000 11:01:04 -0400 (EDT) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id LAA09426; Mon, 7 Aug 2000 11:01:03 -0400 for Message-Id: <200008071501.LAA09426@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Ovens Cc: John Reynolds , emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? In-Reply-To: Message from Mark Ovens of "Sat, 05 Aug 2000 15:08:15 BST." <20000805150815.C254@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Aug 2000 11:01:04 -0400 From: Robert Withrow Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org marko@freebsd.org said: :- I originally built it with the latest port (Makefile rev 1.20) but in :- another thread here it implied/suggested that the previous Makefile :- (rev 1.19) may be better, so I grabbed that and tried it - no :- different. I'm guessing that 4.1-RC is not supported by *any* version of the VMWare port... But you'd need to check with the maintainer for sure. Comment: I know I sound like a broken record, but it would be much better if the VMWare port were configured so that all *released* versions of FBSD >= 4.0, at least, were supported. I'm not smart enough to do the work myself, but I can volunteer to test versions on 4.0 Rel. -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 8:23:33 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-5-187.zoominternet.net [24.154.5.187]) by hub.freebsd.org (Postfix) with ESMTP id CCBC237B69E; Mon, 7 Aug 2000 08:23:28 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.9.3/8.9.3) with ESMTP id LAA02627; Mon, 7 Aug 2000 11:23:39 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Mon, 7 Aug 2000 11:23:39 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: Robert Withrow Cc: Mark Ovens , John Reynolds , emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? In-Reply-To: <200008071501.LAA09426@pobox.engeast.BayNetworks.COM> 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 On Mon, 7 Aug 2000, Robert Withrow wrote: > > marko@freebsd.org said: > :- I originally built it with the latest port (Makefile rev 1.20) but in > :- another thread here it implied/suggested that the previous Makefile > :- (rev 1.19) may be better, so I grabbed that and tried it - no > :- different. > > I'm guessing that 4.1-RC is not supported by *any* version of the > VMWare port... But you'd need to check with the maintainer for sure. I'm running it quite successfully on 4.1-RC. Just FYI. -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 8:28:38 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from scallop.baynetworks.com (ns5.baynetworks.com [194.133.90.101]) by hub.freebsd.org (Postfix) with ESMTP id DDFD337B8F3; Mon, 7 Aug 2000 08:28:31 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by scallop.baynetworks.com (8.9.1/8.9.1) with ESMTP id RAA15829; Mon, 7 Aug 2000 17:33:32 +0200 (MET DST) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id LAA11001; Mon, 7 Aug 2000 11:28:15 -0400 (EDT) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id LAA12860; Mon, 7 Aug 2000 11:28:13 -0400 for Message-Id: <200008071528.LAA12860@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: behanna@zbzoom.net Cc: Mark Ovens , John Reynolds , emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? In-Reply-To: Message from Chris BeHanna of "Mon, 07 Aug 2000 11:23:39 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Aug 2000 11:28:14 -0400 From: Robert Withrow Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org behanna@zbzoom.net said: :- I'm running it quite successfully on 4.1-RC. Just FYI. With which version of the port? What I meant, but poorly stated, is that I don't think 4.1-RC is supported with any *currently available* version of the port. I'm running it fine on 4.0-REL, but I don't belive I could get it running now, with the current version of the port in the port tree. I don't know if I could get it working with any available version on the developers web-site. -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 9:59:49 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id C043E37BA4C for ; Mon, 7 Aug 2000 09:59:46 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.87.209]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000807165936.MVAT26680.mta01-svc.ntlworld.com@parish.my.domain>; Mon, 7 Aug 2000 17:59:36 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id RAA00882; Mon, 7 Aug 2000 17:59:18 +0100 (BST) (envelope-from mark) Date: Mon, 7 Aug 2000 17:59:17 +0100 From: Mark Ovens To: "Vladimir N. Silyaev" Cc: emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000807175917.A254@parish> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> <20000805150815.C254@parish> <200008052359.TAA00434@jupiter.delta.ny.us> <20000806014635.A255@parish> <20000806084822.A282@jupiter.delta.ny.us> <20000806164837.A254@parish> <20000806232722.B3251@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20000806232722.B3251@jupiter.delta.ny.us>; from vsilyaev@mindspring.com on Sun, Aug 06, 2000 at 11:27:23PM -0400 Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 11:27:23PM -0400, Vladimir N. Silyaev wrote: > On Sun, Aug 06, 2000 at 04:48:38PM +0100, Mark Ovens wrote: > > > > It's a K6-233 (original K6, not a -2 or -3) > > > > > > I don't know. I personally don't have experience with new AMD's processors. > > > Try to update BIOS on motherboard to latest one, and try to compile > > > kernel without k6_mem.c file (just change it to dummy one with zero length). > > > > > > > That was it! I built a new kernel and now vmware starts :) > What's exactly? Kernel recompiling with fresh source code, or truncating > k6_mem file? > Sorry, I meant truncating k6_mem.c. > > I am > > running my "real" Win95 and it goes through a lot of "New Hardware > > Detected" messages but hangs when it detects the PCI Bus. I can boot > > it in Safe Mode though. > You should load in Safe Mode, and create new hardware profile. At other > case you can easily broke you "real" configuration. > Yes, I found that out the hard way :) I had to re-install my video drivers when I booted W95 normally. > -- > Vladimir > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-emulation" in the body of the message -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 10: 6:57 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mother.ludd.luth.se (mother.ludd.luth.se [130.240.16.3]) by hub.freebsd.org (Postfix) with ESMTP id 8223437B9DC; Mon, 7 Aug 2000 10:06:47 -0700 (PDT) (envelope-from pantzer@ludd.luth.se) Received: from speedy.ludd.luth.se (speedy.ludd.luth.se [130.240.16.164]) by mother.ludd.luth.se (8.9.3+Sun/8.9.3) with ESMTP id TAA05733; Mon, 7 Aug 2000 19:05:38 +0200 (MEST) Message-Id: <200008071705.TAA05733@mother.ludd.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Sayer Cc: Robert Watson , freebsd-emulation@FreeBSD.ORG, security-officer@FreeBSD.ORG, pantzer@ludd.luth.se Subject: Re: vmware changes result in nasty bridging mess In-Reply-To: Message from Nick Sayer of "Sun, 06 Aug 2000 23:04:45 PDT." <398E517D.A524966F@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Aug 2000 19:05:38 +0200 From: Mattias Pantzare Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > 1. You are probably the only person on the planet who has a machine with > > > both > > > bridging and vmware who (aparently) doesn't intend to bridge the guest > > > onto > > > the connected LAN. This means that you have an opportunity to customize > > > the > > > startup script rather than insist that everyone have it the way you like > > > it. > > > > Possibly true, but I'm interested in POLA for many situations, not just > > the common case. :-) See below, however. > > But isn't that which astonishes least that which astonishes the least > number > of people?! On our campus network it is not uncommon to find peaople that has a gateway machine so that they can have several computers. Both the campus network and the private network is on ethernet. Guess what will hapen when they start to use vmware... Remember that it is usualy a normal workstation that is used for this. It may even be the fastest computer. If the network administrator sees packets from a diffrent IP-range on the network then the offendig computers is very likly to be disconnected. That will astonish the poor student... > > No, I'm worried about the following case: a machine with two interfaces, > > and vmware, who then tries out bridging for the purposes of using vmware. > > Everyone with this configuration, please raise their hands. > > Remember, to qualify the two interfaces must be run simultaneously. Do not assume that all networks look like the ones you have used. > > The result of that operation is not POLA, as the BRIDGE documentation > > clearly specifies that to turn on bridging, you set the sysctl, and that > > the option is passive until then. As the port is currently written, it > > enables BRIDGE at every boot, regardless of a guest running, and affects > > more than just the guest environment, bridging all interfaces. > > And for both of you out there with two Ethernet cards and VMware > running, > you might want to add a bridge_cfg ioctl between the refresh and the > enabling sysctl. The port shoud do that then. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 12:14: 1 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 8538037B792 for ; Mon, 7 Aug 2000 12:13:49 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.89.172]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000807191347.NVPP26680.mta01-svc.ntlworld.com@parish.my.domain>; Mon, 7 Aug 2000 20:13:47 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id UAA02953; Mon, 7 Aug 2000 20:13:33 +0100 (BST) (envelope-from mark) Date: Mon, 7 Aug 2000 20:13:33 +0100 From: Mark Ovens To: Robert Withrow Cc: John Reynolds , emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000807201333.L254@parish> References: <200008071501.LAA09426@pobox.engeast.BayNetworks.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200008071501.LAA09426@pobox.engeast.BayNetworks.COM>; from bwithrow@nortelnetworks.com on Mon, Aug 07, 2000 at 11:01:04AM -0400 Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Aug 07, 2000 at 11:01:04AM -0400, Robert Withrow wrote: > > marko@freebsd.org said: > :- I originally built it with the latest port (Makefile rev 1.20) but in > :- another thread here it implied/suggested that the previous Makefile > :- (rev 1.19) may be better, so I grabbed that and tried it - no > :- different. > > I'm guessing that 4.1-RC is not supported by *any* version of the > VMWare port... But you'd need to check with the maintainer for sure. > > Comment: I know I sound like a broken record, but it would be much > better if the VMWare port were configured so that all *released* versions > of FBSD >= 4.0, at least, were supported. I'm not smart enough to > do the work myself, but I can volunteer to test versions on 4.0 Rel. > Well, FWIW, I just re-installed it using the latest port (Makefile rev 1.20 and build 621 of vmware) on a 4.1-Stable build just after 4.1-R was made and it works just fine. FreeBSD parish 4.1-STABLE FreeBSD 4.1-STABLE #0: Sun Aug 6 14:32:43 BST 2000 root@parish:/usr/src/sys/compile/PARISH i386 > -- > Robert Withrow -- (+1 978 288 8256) > BWithrow@BayNetworks.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-emulation" in the body of the message -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 12:36:40 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from charon.khoral.com (charon.khoral.com [209.75.155.97]) by hub.freebsd.org (Postfix) with SMTP id 83A7437B672; Mon, 7 Aug 2000 12:36:29 -0700 (PDT) (envelope-from steve@khoral.com) Received: from zen.alb.khoral.com by charon.khoral.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 7 Aug 2000 19:36:29 UT Received: from benson (benson.alb.khoral.com [10.1.2.11]) by zen.alb.khoral.com (8.9.3/8.9.3) with ESMTP id NAA19443; Mon, 7 Aug 2000 13:36:23 -0600 (MDT) From: Steve Jorgensen Message-Id: <200008071936.NAA11161@benson> Subject: Re: FreeBSD/VMWare setup for dummies? To: marko@FreeBSD.ORG (Mark Ovens) Date: Mon, 7 Aug 2000 13:36:12 -0600 (MDT) Cc: bwithrow@nortelnetworks.com (Robert Withrow), jjreynold@home.com (John Reynolds), emulation@FreeBSD.ORG In-Reply-To: <20000805150815.C254@parish> from "Mark Ovens" at Aug 05, 2000 03:08:15 PM 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 I used to see the same behavior when I let vmware use /tmp on my small root partition, because there wasn't enough diskspace to hold its temporary file. My linux emulation system is under /usr/compat/linux which is a much larger disk partition, so when I created a tmp in that directory with the same permissions as /tmp, vmware worked just fine. Steve Mark Ovens wrote >> On Thu, Jul 27, 2000 at 08:42:30AM -0400, Robert Withrow wrote: >> > Thanks for the info. Actually, late last night I actually flopped in >> > the correct direction (probably accidentally). I'll note where your >> > stuff differs from mine: >> > >> > :- First off, is the NT/BSD boot disk an IDE disk? I hope so. Even VMware >> > :- themselves say booting a VM from scsi is at best experimental. I would >> > :- seriously doubt it would work under FreeBSD, but maybe >> > >> > It's scsi, and it seems to work. >> > >> >> I've been following this thread and learnt quite a bit from it, thanks >> guys, however I *still* can't get vmware to run :( >> >> It starts up but as soon as I click the Power On button the vmware >> window turns black and the whole machine locks solid (no keyboard or >> mouse response, and the desktop clock and xtimer stop) and after ~15 >> secs the machine spontaneously reboots (which is a PITA as it fsck's >> the disks every time). >> >> There is no clue in the vmware log, or /var/adm/messages, as to the >> cause. >> >> I've tried using a virtual disk and (currently) a plain disk (SCSI). >> I've set up with no CD-ROM and floppy (to minimize possible causes) >> but still it won't run. >> >> I originally built it with the latest port (Makefile rev 1.20) but in >> another thread here it implied/suggested that the previous Makefile >> (rev 1.19) may be better, so I grabbed that and tried it - no >> different. >> >> Can anyone shed any light on the cause of these crashes? Also, I have >> no .nvram file. Is it supposed to be created by hand? If so, what >> goes in it? >> >> # uname -a >> FreeBSD parish 4.1-RC FreeBSD 4.1-RC #0: Thu Jul 20 20:54:53 BST 2000 >> root@parish:/usr/obj/usr/src/sys/PARISH i386 >> >> # cat win95.{cfg,hba} >> #!/usr/local/lib/vmware/bin/vmware >> config.version = 2 >> >> # No cdrom installed >> >> >> # Disk Drive Info >> scsi0:0.present = TRUE >> scsi0:0.deviceType = "plainDisk" >> scsi0:0.fileName = "win95.hba" >> scsi0.present = TRUE >> >> # No floppy installed >> >> floppy0.present = FALSE >> >> # No networking installed >> >> # Memory size >> memsize = 32 >> >> # Nvram >> nvram = /usr/marko/.vmware/win95/win95.nvram >> >> # Log file >> log.fileName = /usr/marko/.vmware/win95/win95.log >> >> # Hints >> guestOS = win95 >> >> DRIVETYPE scsi >> CYLINDERS 527 >> HEADS 255 >> SECTORS 63 >> ACCESS "disk.mbr" 0 63 >> ACCESS "/dev/rda0s1" 63 1044162 >> ACCESS "/dev/null" 1044225 7422030 >> >> -- ----------------------------------------------------------- Steven Jorgensen steve@khoral.com steve@spukhaus.com ------------------------------+---------------------------- Khoral Research Inc. | PHONE: (505) 837-6500 6200 Uptown Blvd, Suite 200 | FAX: (505) 881-3842 Albuquerque, NM 87110 | URL: http://www.khoral.com/ ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 13:40:45 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 2375F37B9D2 for ; Mon, 7 Aug 2000 13:40:43 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id B435B5A7; Mon, 7 Aug 2000 13:40:42 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id NAA28638; Mon, 7 Aug 2000 13:40:42 -0700 (PDT) Message-ID: <398F1ECA.2A4CC223@cup.hp.com> Date: Mon, 07 Aug 2000 13:40:42 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Marc Evans Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: WebTrends on FreeBSD 4.1 (Linux Emulation) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marc Evans wrote: > > I have embarked on implementing the missing syscall. [snip] > > > > > > /kernel: linux: syscall rt_sigtimedwait is obsoleted or not implemented > > > Great! I'll take a look at it... -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 14:41:33 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from pegasus.kazrak.com (adsl-209-233-16-235.dsl.snfc21.pacbell.net [209.233.16.235]) by hub.freebsd.org (Postfix) with ESMTP id A1DAF37BAB3 for ; Mon, 7 Aug 2000 14:41:19 -0700 (PDT) (envelope-from brad@kazrak.com) Received: by pegasus.kazrak.com (Postfix, from userid 1001) id BA7FE435; Mon, 7 Aug 2000 14:41:07 -0700 (PDT) Date: Mon, 7 Aug 2000 14:41:07 -0700 From: Brad Jones To: Marc Fonvieille Cc: freebsd-emulation@freebsd.org Subject: Re: Unknown format on /proc/cpuinfo with dosemu-1.0.1 Message-ID: <20000807144107.A12629@pegasus.kazrak.com> References: <20000806130334.A4304@marduk.styx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000806130334.A4304@marduk.styx.org>; from fonvi@easynet.fr on Sun, Aug 06, 2000 at 01:03:34PM +0200 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 01:03:34PM +0200, Marc Fonvieille wrote: > I'm trying to play with dosemu-1.0.1 > > here's what i did: > > % mount -t linprocfs /proc /compat/linux/proc/ > % /compat/linux/usr/bin/dos > ERROR: Unknown format on /proc/cpuinfo > > > The linprocfs mount run fine with vwmare2 > Any advice? dosemu requires much more extensive /proc emulation than FreeBSD currently provides. I have submitted a patch that I believe should fix the cpuinfo problem, but there are so many other parts of /proc that dosemu wants that I gave up for the moment. (If you want the patch, it's in PR#20029.) BJ -- Brad Jones -- brad@kazrak.com "Computers are like Old Testament gods; lots of rules and no mercy." -- Joseph Campbell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 15:53:21 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 52A5D37B637 for ; Mon, 7 Aug 2000 15:53:19 -0700 (PDT) (envelope-from nsayer@sftw.com) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.9.3/8.9.3) with ESMTP id PAA77720; Mon, 7 Aug 2000 15:53:19 -0700 (PDT) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.9.3/8.9.3) with ESMTP id PAA77439; Mon, 7 Aug 2000 15:53:14 -0700 (PDT) (envelope-from nsayer@sftw.com) Message-ID: <398F3DDA.D7087E4F@sftw.com> Date: Mon, 07 Aug 2000 15:53:14 -0700 From: Nick Sayer Reply-To: nsayer@freebsd.org X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Robert Withrow , freebsd-emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? References: <200008071501.LAA09426@pobox.engeast.BayNetworks.COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert Withrow wrote: > marko@freebsd.org said: > :- I originally built it with the latest port (Makefile rev 1.20) but in > :- another thread here it implied/suggested that the previous Makefile > :- (rev 1.19) may be better, so I grabbed that and tried it - no > :- different. > > I'm guessing that 4.1-RC is not supported by *any* version of the > VMWare port... But you'd need to check with the maintainer for sure. > > Comment: I know I sound like a broken record, but it would be much > better if the VMWare port were configured so that all *released* versions > of FBSD >= 4.0, at least, were supported. I'm not smart enough to > do the work myself, but I can volunteer to test versions on 4.0 Rel. I know I sound like a broken record too, but you can run the current port on 4.1-RELEASE simply by adding the tap module. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 15:56:55 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id B934E37BBAD; Mon, 7 Aug 2000 15:56:53 -0700 (PDT) (envelope-from nsayer@sftw.com) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.9.3/8.9.3) with ESMTP id PAA77770; Mon, 7 Aug 2000 15:56:53 -0700 (PDT) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.9.3/8.9.3) with ESMTP id PAA77499; Mon, 7 Aug 2000 15:56:52 -0700 (PDT) (envelope-from nsayer@sftw.com) Message-ID: <398F3EB3.1E1F2B5B@sftw.com> Date: Mon, 07 Aug 2000 15:56:52 -0700 From: Nick Sayer X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Steve Jorgensen Cc: Mark Ovens , Robert Withrow , John Reynolds , emulation@FreeBSD.ORG Subject: Re: FreeBSD/VMWare setup for dummies? References: <200008071936.NAA11161@benson> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Steve Jorgensen wrote: > I used to see the same behavior when I let vmware use /tmp on my > small root partition, because there wasn't enough diskspace to > hold its temporary file. My linux emulation system is under > /usr/compat/linux which is a much larger disk partition, so when > I created a tmp in that directory with the same permissions as > /tmp, vmware worked just fine. > > Steve Be aware when you do this that it may have subtle, undesirable effects on other Linux apps. Most notably, if you print from Linux Netscape, the print job will go into /compat/linux/tmp, but lpr will look for it in /tmp/ and fail. This, and other helpful advice is available in the port's hints file, which if memory serves gets installed in share/doc/vmware/Hints.FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 16: 1:22 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 8D10B37B891 for ; Mon, 7 Aug 2000 16:01:12 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.84.147]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000807230109.PQEA26680.mta01-svc.ntlworld.com@parish.my.domain>; Tue, 8 Aug 2000 00:01:09 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id AAA03873; Tue, 8 Aug 2000 00:01:02 +0100 (BST) (envelope-from mark) Date: Tue, 8 Aug 2000 00:01:02 +0100 From: Mark Ovens To: Steve Jorgensen Cc: Robert Withrow , John Reynolds , emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000808000102.P254@parish> References: <20000805150815.C254@parish> <200008071936.NAA11161@benson> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200008071936.NAA11161@benson>; from steve@khoral.com on Mon, Aug 07, 2000 at 01:36:12PM -0600 Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Aug 07, 2000 at 01:36:12PM -0600, Steve Jorgensen wrote: > > I used to see the same behavior when I let vmware use /tmp on my > small root partition, because there wasn't enough diskspace to > hold its temporary file. My linux emulation system is under > /usr/compat/linux which is a much larger disk partition, so when > I created a tmp in that directory with the same permissions as > /tmp, vmware worked just fine. > My /tmp is symlinked to /usr/tmp. Turned out to be becuse I'm running a K6 CPU. Vladimir suggested making k6_mem.c an empty file and re-building my kernel; that fixed it. > Steve > > Mark Ovens wrote > >> On Thu, Jul 27, 2000 at 08:42:30AM -0400, Robert Withrow wrote: > >> > Thanks for the info. Actually, late last night I actually flopped in > >> > the correct direction (probably accidentally). I'll note where your > >> > stuff differs from mine: > >> > > >> > :- First off, is the NT/BSD boot disk an IDE disk? I hope so. Even VMware > >> > :- themselves say booting a VM from scsi is at best experimental. I would > >> > :- seriously doubt it would work under FreeBSD, but maybe > >> > > >> > It's scsi, and it seems to work. > >> > > >> > >> I've been following this thread and learnt quite a bit from it, thanks > >> guys, however I *still* can't get vmware to run :( > >> > >> It starts up but as soon as I click the Power On button the vmware > >> window turns black and the whole machine locks solid (no keyboard or > >> mouse response, and the desktop clock and xtimer stop) and after ~15 > >> secs the machine spontaneously reboots (which is a PITA as it fsck's > >> the disks every time). > >> > >> There is no clue in the vmware log, or /var/adm/messages, as to the > >> cause. > >> > >> I've tried using a virtual disk and (currently) a plain disk (SCSI). > >> I've set up with no CD-ROM and floppy (to minimize possible causes) > >> but still it won't run. > >> > >> I originally built it with the latest port (Makefile rev 1.20) but in > >> another thread here it implied/suggested that the previous Makefile > >> (rev 1.19) may be better, so I grabbed that and tried it - no > >> different. > >> > >> Can anyone shed any light on the cause of these crashes? Also, I have > >> no .nvram file. Is it supposed to be created by hand? If so, what > >> goes in it? > >> > >> # uname -a > >> FreeBSD parish 4.1-RC FreeBSD 4.1-RC #0: Thu Jul 20 20:54:53 BST 2000 > >> root@parish:/usr/obj/usr/src/sys/PARISH i386 > >> > >> # cat win95.{cfg,hba} > >> #!/usr/local/lib/vmware/bin/vmware > >> config.version = 2 > >> > >> # No cdrom installed > >> > >> > >> # Disk Drive Info > >> scsi0:0.present = TRUE > >> scsi0:0.deviceType = "plainDisk" > >> scsi0:0.fileName = "win95.hba" > >> scsi0.present = TRUE > >> > >> # No floppy installed > >> > >> floppy0.present = FALSE > >> > >> # No networking installed > >> > >> # Memory size > >> memsize = 32 > >> > >> # Nvram > >> nvram = /usr/marko/.vmware/win95/win95.nvram > >> > >> # Log file > >> log.fileName = /usr/marko/.vmware/win95/win95.log > >> > >> # Hints > >> guestOS = win95 > >> > >> DRIVETYPE scsi > >> CYLINDERS 527 > >> HEADS 255 > >> SECTORS 63 > >> ACCESS "disk.mbr" 0 63 > >> ACCESS "/dev/rda0s1" 63 1044162 > >> ACCESS "/dev/null" 1044225 7422030 > >> > >> > > > -- > ----------------------------------------------------------- > Steven Jorgensen steve@khoral.com steve@spukhaus.com > ------------------------------+---------------------------- > Khoral Research Inc. | PHONE: (505) 837-6500 > 6200 Uptown Blvd, Suite 200 | FAX: (505) 881-3842 > Albuquerque, NM 87110 | URL: http://www.khoral.com/ > ----------------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-emulation" in the body of the message -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 16:12: 5 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 8D7CE37BC06; Mon, 7 Aug 2000 16:12:02 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny8-37.ix.netcom.com [198.211.17.229]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id TAA28386; Mon, 7 Aug 2000 19:11:59 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id TAA00344; Mon, 7 Aug 2000 19:11:57 -0400 (EDT) (envelope-from vsilyaev) Date: Mon, 7 Aug 2000 19:11:57 -0400 From: "Vladimir N. Silyaev" To: Mark Ovens Cc: emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000807191157.A318@jupiter.delta.ny.us> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> <20000805150815.C254@parish> <200008052359.TAA00434@jupiter.delta.ny.us> <20000806014635.A255@parish> <20000806084822.A282@jupiter.delta.ny.us> <20000806164837.A254@parish> <20000806232722.B3251@jupiter.delta.ny.us> <20000807175917.A254@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000807175917.A254@parish>; from marko@freebsd.org on Mon, Aug 07, 2000 at 05:59:17PM +0100 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Aug 07, 2000 at 05:59:17PM +0100, Mark Ovens wrote: > > > > > It's a K6-233 (original K6, not a -2 or -3) > > > > > > > > I don't know. I personally don't have experience with new AMD's processors. > > > > Try to update BIOS on motherboard to latest one, and try to compile > > > > kernel without k6_mem.c file (just change it to dummy one with zero length). > > > > > > > > > > That was it! I built a new kernel and now vmware starts :) > > What's exactly? Kernel recompiling with fresh source code, or truncating > > k6_mem file? > > > > Sorry, I meant truncating k6_mem.c. Could I ask you to return back k6_mem.c file, recompile kernel and start again vmware. In the case if vmware will hang, that's mean pretty bad news, and it _should_ be included in readme file. Also if vmware will hang, I like to know what 'sysctl hw.model' said on your box. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 17:17:34 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id CE9E837B5C0 for ; Mon, 7 Aug 2000 17:17:25 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.88.83]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000808001723.PZDM26680.mta01-svc.ntlworld.com@parish.my.domain>; Tue, 8 Aug 2000 01:17:23 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id BAA00404; Tue, 8 Aug 2000 01:17:06 +0100 (BST) (envelope-from mark) Date: Tue, 8 Aug 2000 01:17:05 +0100 From: Mark Ovens To: "Vladimir N. Silyaev" Cc: emulation@freebsd.org Subject: Re: FreeBSD/VMWare setup for dummies? Message-ID: <20000808011705.A288@parish> References: <200007271242.IAA16126@pobox.engeast.BayNetworks.COM> <20000805150815.C254@parish> <200008052359.TAA00434@jupiter.delta.ny.us> <20000806014635.A255@parish> <20000806084822.A282@jupiter.delta.ny.us> <20000806164837.A254@parish> <20000806232722.B3251@jupiter.delta.ny.us> <20000807175917.A254@parish> <20000807191157.A318@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20000807191157.A318@jupiter.delta.ny.us>; from vsilyaev@mindspring.com on Mon, Aug 07, 2000 at 07:11:57PM -0400 Organization: Total lack of Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Aug 07, 2000 at 07:11:57PM -0400, Vladimir N. Silyaev wrote: > On Mon, Aug 07, 2000 at 05:59:17PM +0100, Mark Ovens wrote: > > > > > > It's a K6-233 (original K6, not a -2 or -3) > > > > > > > > > > I don't know. I personally don't have experience with new > > > > > AMD's processors. Try to update BIOS on motherboard to > > > > > latest one, and try to compile kernel without k6_mem.c file > > > > > (just change it to dummy one with zero length). > > > > > > > > > > > > > That was it! I built a new kernel and now vmware starts :) > > > What's exactly? Kernel recompiling with fresh source code, or truncating > > > k6_mem file? > > > > > > > Sorry, I meant truncating k6_mem.c. > Could I ask you to return back k6_mem.c file, recompile kernel and start > again vmware. In the case if vmware will hang, that's mean pretty bad news, > and it _should_ be included in readme file. Also if vmware will hang, I like > to know what 'sysctl hw.model' said on your box. > OK, I've copied back k6_mem.c and re-built my kernel and vmware works fine :) Strange! but I have cvsup'd since the kernel I was originally using (built July 20). Maybe something else has changed (in the kernel) that has fixed this. Anyway it does not really matter now, vmware works. # sysctl hw.model hw.model: AMD-K6tm w/ multimedia extensions > -- > Vladimir > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-emulation" in the body of the message -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Mon Aug 7 22:36:53 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 7A3FC37B72D; Mon, 7 Aug 2000 22:36:40 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-17.sugnm1.kt.home.ne.jp [203.165.77.17]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id OAA27125; Tue, 8 Aug 2000 14:36:36 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id OAA65922; Tue, 8 Aug 2000 14:36:04 +0900 (JST) Date: Tue, 08 Aug 2000 14:36:02 +0900 Message-ID: <86bsz4co1p.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: "Vladimir N. Silyaev" Cc: Robert Watson , freebsd-hackers@FreeBSD.ORG, security-officer@FreeBSD.ORG, emulation@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess In-Reply-To: In your message of "Sun, 6 Aug 2000 23:23:39 -0400" <20000806232339.A3251@jupiter.delta.ny.us> References: <200008032335.TAA01440@jupiter.delta.ny.us> <20000806232339.A3251@jupiter.delta.ny.us> User-Agent: Wanderlust/2.3.0 (Roam) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 11) (Carlsbad Caverns) (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 a quick glance, "start_bridge" doesn't seem to have chance to be 1, does it? And, what's the difference among those three values of "bridge"? > + bridge="_bridge_on" > + bridge="_bridge" > + bridge="_bridge_off" -- / /__ __ / ) ) ) ) / 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 Tue Aug 8 2:32:36 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id EB94037BFFF; Tue, 8 Aug 2000 02:32:24 -0700 (PDT) (envelope-from danny@cs.huji.ac.il) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13M5kB-0002Zk-00; Tue, 08 Aug 2000 12:32:19 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.03 #1) id 13M5kA-0001Zs-00; Tue, 08 Aug 2000 12:32:18 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: "Vladimir N. Silyaev" Cc: emulation@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: vmware ... In-reply-to: Your message of Sun, 6 Aug 2000 23:23:39 -0400 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Aug 2000 12:32:18 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi all, im trying to 'install' vmware, and im missing if_tap.ko, can someone point me in the right direction? danny PS: it's FreeBSD 4.1-RELEASE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 8 3:47:31 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 1EDC037B5DC for ; Tue, 8 Aug 2000 03:45:21 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id RAA38909 for ; Tue, 8 Aug 2000 17:45:07 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 8 Aug 2000 17:45:07 +0700 (NSS) From: Max Khon To: emulation@freebsd.org Subject: vmware full-screen 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 hi, there! has anyone got win9x running under vmware (full-screen)? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 8 4:15:58 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id E3F5637B60B; Tue, 8 Aug 2000 04:15:52 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny5-11.ix.netcom.com [198.211.17.11]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id HAA11918; Tue, 8 Aug 2000 07:15:49 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id HAA00414; Tue, 8 Aug 2000 07:15:47 -0400 (EDT) (envelope-from vsilyaev) Date: Tue, 8 Aug 2000 07:15:46 -0400 From: "Vladimir N. Silyaev" To: Akinori -Aki- MUSHA Cc: Robert Watson , freebsd-hackers@FreeBSD.ORG, security-officer@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess Message-ID: <20000808071546.C360@jupiter.delta.ny.us> References: <200008032335.TAA01440@jupiter.delta.ny.us> <20000806232339.A3251@jupiter.delta.ny.us> <86bsz4co1p.wl@localhost.local.idaemons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <86bsz4co1p.wl@localhost.local.idaemons.org>; from knu@idaemons.org on Tue, Aug 08, 2000 at 02:36:02PM +0900 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 08, 2000 at 02:36:02PM +0900, Akinori -Aki- MUSHA wrote: > At a quick glance, "start_bridge" doesn't seem to have chance to be 1, > does it? It's depend. I'm pretty tired that discussian about bridging. So if people want to use bridge let set start_bridge to 1, if not leave it in zero. Also it's possible to setup that value at configuration stage, whatever. > And, what's the difference among those three values of > "bridge"? To diagnostic current behaviour about bridging. > > > + bridge="_bridge_on" Startup script configured do not touch bridging and at the time when script starting, bridging was enabled. > > + bridge="_bridge_off" /.../ disabled. > > > + bridge="_bridge" Script configured to setup bridging and did successfully When bridge == "" its means that kernel compiled without bridging support, or outdated kernel. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 8 4:34:25 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from shrimp.baynetworks.com (ns4.BayNetworks.COM [192.32.253.7]) by hub.freebsd.org (Postfix) with ESMTP id 0237C37B838; Tue, 8 Aug 2000 04:34:22 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (ns4.baynetworks.com [132.245.135.84]) by shrimp.baynetworks.com (8.9.1/8.9.1) with ESMTP id HAA15766; Tue, 8 Aug 2000 07:27:18 -0400 (EDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id HAA11955; Tue, 8 Aug 2000 07:33:41 -0400 (EDT) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id HAA23521; Tue, 8 Aug 2000 07:33:41 -0400 for Message-Id: <200008081133.HAA23521@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Sayer Cc: Steve Jorgensen , Mark Ovens , John Reynolds , emulation@FreeBSD.ORG Subject: Re: FreeBSD/VMWare setup for dummies? In-Reply-To: Message from Nick Sayer of "Mon, 07 Aug 2000 15:56:52 PDT." <398F3EB3.1E1F2B5B@sftw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Aug 2000 07:33:41 -0400 From: Robert Withrow Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org nsayer@sftw.com said: :- Be aware when you do this that it may have subtle, undesirable effects :- on other Linux apps. Right. The standard way to deal with tmp space for VMWare is to modify the "vmware" script to set TMPDIR to some place with lots of fast space. Couldn't this become a standard part of the VMWare port, with the location being something that gets tweaked at install time, possibly via a dialog? -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 8 6: 0:39 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69]) by hub.freebsd.org (Postfix) with ESMTP id 68F1837B909; Tue, 8 Aug 2000 06:00:29 -0700 (PDT) (envelope-from myevmenkin@att.com) Received: from flf960r1.ems.att.com ([135.71.244.37]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id JAA22074; Tue, 8 Aug 2000 09:00:19 -0400 (EDT) Received: from mo3980bh3.ems.att.com by flf960r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id IAA13704; Tue, 8 Aug 2000 08:56:16 -0400 (EDT) Received: by mo3980bh3.ems.att.com with Internet Mail Service (5.5.2652.35) id ; Tue, 8 Aug 2000 08:00:18 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Danny Braniss'" , "Vladimir N. Silyaev" Cc: emulation@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: RE: vmware ... Date: Tue, 8 Aug 2000 08:00:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > im trying to 'install' vmware, and im missing > if_tap.ko, can someone > point me in the right direction? the tap (if_tap.ko) driver is part of -current and RELENG_4. it was not included in 4.1-RC. should you need to use it, please, download sources from -current or RELENG_4 and compile it. i hope it will be included in the next release. thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 8 8:35: 6 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id 1ACBE37B55D for ; Tue, 8 Aug 2000 08:35:04 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with ESMTP id PAA12223; Tue, 8 Aug 2000 15:32:48 GMT Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id IAA05378; Tue, 8 Aug 2000 08:33:17 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id LAA04659; Tue, 8 Aug 2000 11:33:17 -0400 (EDT) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14736.10301.62759.517414@hip186.ch.intel.com> Date: Tue, 8 Aug 2000 08:33:17 -0700 (MST) To: Max Khon Subject: Re: vmware full-screen In-Reply-To: References: X-Mailer: VM 6.75 under Emacs 20.6.3 Cc: emulation@freebsd.org Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ On Tuesday, August 8, Max Khon wrote: ] > hi, there! > > has anyone got win9x running under vmware (full-screen)? > > /fjoe > Yes, I've gotten win98 SE running full-screen under VMware when I was screwing with it. You must make sure that you are running "moused" (and thus pointing X at /dev/sysmouse) and change your mouse configuration from "auto" to "ps/2" explicitly inside the vmware configuration editor. Unless I did those things vmware would yell at me about my mouse and refuse to go into full-screen mode. If it's something other than that, then I'm out of clues :) -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 8 10:10:20 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id EF8FC37B5AB for ; Tue, 8 Aug 2000 10:09:42 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id AAA48944; Wed, 9 Aug 2000 00:08:13 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 9 Aug 2000 00:08:12 +0700 (NSS) From: Max Khon To: John Reynolds~ Cc: emulation@freebsd.org Subject: Re: vmware full-screen In-Reply-To: <14736.10301.62759.517414@hip186.ch.intel.com> 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 hi, there! On Tue, 8 Aug 2000, John Reynolds~ wrote: > > has anyone got win9x running under vmware (full-screen)? > > Yes, I've gotten win98 SE running full-screen under VMware when I was screwing > with it. > > You must make sure that you are running "moused" (and thus pointing X at > /dev/sysmouse) and change your mouse configuration from "auto" to "ps/2" > explicitly inside the vmware configuration editor. Unless I did those things > vmware would yell at me about my mouse and refuse to go into full-screen mode. been there, did that. thanks anyway > If it's something other than that, then I'm out of clues :) I have problems with vtys. I am running X at ttyvb. vmware tries to allocate /dev/tty13 for full-screen mode but I cannot imagine where /compat/linux/dev/tty13 should point to When it is symlinked to /dev/ttyvc vmware dumps core. /fjoe PS I heard that not all X drivers (I use 3.3.6) work correctly with vmware. which driver (and video card) do you have (mine is RIVA TNT 2)? I am runnign vmware under 4.1-STABLE (14 Aug) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Aug 8 16:39:26 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id E5A2537B85A for ; Tue, 8 Aug 2000 16:39:14 -0700 (PDT) (envelope-from vns@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny8-41.ix.netcom.com [198.211.17.233]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA10100; Tue, 8 Aug 2000 19:39:05 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id TAA00477; Tue, 8 Aug 2000 19:39:02 -0400 (EDT) (envelope-from vns) Date: Tue, 8 Aug 2000 19:39:02 -0400 (EDT) From: "Vladimir N.Silyaev" Message-Id: <200008082339.TAA00477@jupiter.delta.ny.us> To: beattie@beattie-home.net Cc: emulation@freebsd.org Subject: Re: vmware and vmnet devices In-Reply-To: References: Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In muc.lists.freebsd.hackers, you wrote: >running a very recent 4.x-STABLE and today's vmware2 port, when I power on >the virtual machine I get a pop-up with the message: > >could not open vmnet0, ethernet device 0 not configured > >and the virtual device does not power up. Is there a readme some where >that tells me how to create those nodes? What is the output of the following sequence: /usr/local/etc/rc.d/vmware.sh stop /usr/local/etc/rc.d/vmware.sh start kldstat Check that you are have vmnetxx nodes in /compat/linux/dev, and don't have it on /dev. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message