From owner-freebsd-emulation Thu Mar 8 21:54: 8 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by hub.freebsd.org (Postfix) with ESMTP id F354037B718 for ; Thu, 8 Mar 2001 21:54:04 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Fri, 9 Mar 2001 00:51:23 -0500 Message-ID: <3AA86FE5.92256526@babbleon.org> Date: Fri, 09 Mar 2001 00:53:41 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: mikko@dynas.se, Barry Lustig , emulation@freebsd.org Subject: Re: vmware networking References: <3AA456C7.A00F0358@babbleon.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, this is frustrating in the exteme, but although it worked once, I can't get it to work any more. One thing I noticed is that the network reverted from 192.168.0.1 the *second* time but not the first, but I've tried reconfiguring my guest to talk to that network without luck. I'm hoping that somebody has some ideas . . . I've beat myhead against it for a few days before appealing to you folks again, but I'm befuddled again. I've even re-done the deinstall/reinstall, but that didn't fix anything. I can go back to the complex firewall-like solution, but I was having trouble with that one, too . . . and that one time I rebooted & installed it all just worked so easily. I just wish I recapture that victory. A couple new questions, though, while I'm at it (both minor): 1. Is there any way to get the RTC device turned off by default? If it's on, vmware eats up all available CPU but I don't see a way to keep it off-by-default. 2. Is there a way to get rid of the annoying requester claiming that /dev/psm0 can't be opened and thus full-screen mode will fail? In actual point of fact, full-screen mode works just peachy (for graphics; I read the warnings about text mode and haven't even tried that). The Babbler wrote: > > As is frequently the case in such matters, the cause of my difficulty > was very simple. > > I did not have the latest port. The verison matched, but the port > *revision* did not match. > > With the truly latest port, it "just works," as suggested by so many > kind correspondents. > > Thank you one and all. > > Mikko Työläjärvi wrote: > > > > On Sun, 4 Mar 2001, The Babbler wrote: > > > > > Mikko Tyolajarvi wrote: > > > > > > > > In local.freebsd.emulation you write: > > > > > > > > >I'm trying to get networking going with vmware under FreeBSD. > > > > > > > > >I was going to set up host-only networking and use NATD to get to the > > > > >Great Wide World under vmware. This is kinda lucky since host-only is > > > > >apparently the only sort of networking that vmware supports under > > > > >FreeBSD. > > > > > > > > Last time I installed vmware, one had to have bridging support in the > > > > kernel, configure vmware for "host-only" networking, and then it Just > > > > Worked(tm) - full network access from vmware after giving the guest OS > > > > an IP address on the same subnet as the host OS. You can even use DHCP. > > > > > > > > The port has since been changed to use netgraph to do the bridging, > > > > which I assume should work without building a new kernel. So, it > > > > should work out-of-the box, without nat. > > > > > > Well, it doesn't. Any ideas on where to start? > > -- > "Brian, the man from babble-on" bts@babbleon.org > Brian T. Schellenberger http://www.babbleon.org > Support http://www.eff.org. Support decss defendents. > Support http://www.programming-freedom.org. Boycott amazon.com. -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message