From owner-freebsd-emulation@FreeBSD.ORG Sat Aug 8 16:52:24 2009 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6413F106566C for ; Sat, 8 Aug 2009 16:52:24 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id DE5308FC1D for ; Sat, 8 Aug 2009 16:52:23 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id E16201E0030B; Sat, 8 Aug 2009 18:52:22 +0200 (CEST) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.3/8.14.3) with ESMTP id n78GpEah004630; Sat, 8 Aug 2009 18:51:14 +0200 (CEST) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.3/8.14.3/Submit) id n78GpDjV004629; Sat, 8 Aug 2009 18:51:13 +0200 (CEST) (envelope-from nox) Date: Sat, 8 Aug 2009 18:51:13 +0200 (CEST) From: Juergen Lock Message-Id: <200908081651.n78GpDjV004629@triton8.kn-bremen.de> To: matheus@eternamente.info X-Newsgroups: local.list.freebsd.emulation In-Reply-To: References: Organization: home Cc: emulation@freebsd.org, Jeremy Messenger Subject: Re: VirtualBox NAT network works or not? X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Aug 2009 16:52:24 -0000 In article you write: >On Tue, July 28, 2009 00:39, Jeremy Messenger wrote: >> Hello, >> >> I have installed VirtualBox and very surpised about that it's very fast. >> Very nice! >> >> But I have a problem with NAT network and uses DHCP in guest. It does not >> work. The host is yesterday -CURRENT and very latest installed ports with >> libtool 2.2. I don't know how I can debug it. I have decided to install >> VirtualBox in Windows 7 and I have setup very same exactly how I do with >> guest of FreeBSD 6.4. It works perfect. The only difference is that >> VirtualBox version is 3.x in Windows and 2.x in -CURRENT. It is either bug >> or not ready? I have tried to disable VT-x and it makes no difference. I >> have tried all network adapter and no difference. > I've had nat mode problems too (guests randomly failing to dhcp on the first attempt, have to manually run `dhclient eth0' a second time in the guest), and the official vbox changelog, http://www.virtualbox.org/wiki/Changelog mentions NAT: fixed network communication corruptions (bugs #4499, #4540, #4591, #4604) for their 3.0.4 release too, so maybe we just need to wait for these fixes to reach the FreeBSD port... >I've been using Vbox 3 in FreeBSD for a bit more of a week now, and it is >doing what I want it to. > >the svn > >svn co >http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox > >I can use nat, but still trying to figure out how to reach the vm using >network. if anyone has any leads. so far, the best thing I think is to >make a reverse tunnel using ssh. > vbox' nat mode, like qemu's, can map individual guest ports to ones on the host (port forwarding), see here for details: http://www.virtualbox.org/manual/UserManual.html#networking-nat >matheus > >ps: I can't use my amd64 vm's if not from 7.2-STABLE. -CURRENT is no good >in here, tested three diff machines by now. I have problems parsing this, :) you mean amd64 guests stopped working on -current? Guess I should test that here... HTH, Juergen