Date: Sat, 8 Aug 2009 14:27:15 -0300 (BRT) From: "Nenhum_de_Nos" <matheus@eternamente.info> To: "Juergen Lock" <nox@jelal.kn-bremen.de> Cc: emulation@freebsd.org, Jeremy Messenger <mezz7@cox.net> Subject: Re: VirtualBox NAT network works or not? Message-ID: <fbbd44c07d1c28eef3f2022200e5ffa1.squirrel@10.1.1.10> In-Reply-To: <200908081651.n78GpDjV004629@triton8.kn-bremen.de> References: <op.uxrdsge29aq2h7@localhost> <200908081651.n78GpDjV004629@triton8.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, August 8, 2009 13:51, Juergen Lock wrote: > In article <f01e4302942811415e4533fd29d7818e.squirrel@10.1.1.10> 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 had problems in a work box where ssh portforwarding was not good. the box has no firewall at all. the same thing worked here at home ok. >>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 good to hear that, will read asap. thanks :) >>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... I have two machines (real ones) running FreeBSD 7.2-STABLE (one from late July, other mid June) and using vbox from this svn port ok. I have amd64 vm's (one each) and VT-x is enabled in both (if is really working I can't tell, but I can use both cores in the vm and folding at home performance is paired to the real native linux) and it is quite stable. I'd really like to do this in 8.0 (now in beta state), but I'm unable to do so as I get errors from vbox or machine crashes. so 7.2-STABLE is ok but the soon to be born 8.0 is not :( thanks, matheus > HTH, > Juergen > -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fbbd44c07d1c28eef3f2022200e5ffa1.squirrel>