Date: Thu, 27 Jul 2017 16:52:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 221050] emulators/virtualbox-ose: Bridged network doesn't work (11.1-RELEASE) Message-ID: <bug-221050-8075-o6J5zmtyZq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221050-8075@https.bugs.freebsd.org/bugzilla/> References: <bug-221050-8075@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221050 --- Comment #5 from steinex@nognu.de --- Some more details. This is from 2017Q3 packages: * I have no firewall or whatsoever in place on the host. * Attached is VBox.log when running an OpenBSD guest where bridged networki= ng does not work. It doesn't work for any guest though, no matter what OS as f= ar as I can tell. I can't spot obvious errors the log though. ** The interface to be bridged is em0 (Intel(R) 82579V Gigabit Network Devi= ce). ** Symptom is DHCP-requests just time out. * I don't know if its important but I thought it may be worth mentioning. W= hen doing "/usr/local/etc/rc.d/vboxnet onestop" to unload the modules again, dm= esg shows: "Warning: memory type iprtheap leaked memory on destroy (2 allocatio= ns, 128 bytes leaked)." * When trying to build virtualbox-ose from ports 2017Q3-branch (any depende= ncy but virtualbox-ose-kmod is already installed from packages at this point, including kBuild), build failure log is attached as virtualbox-ose-buildfailure.txt * When trying to build virtualbox-ose from ports 2017Q3-branch (any depende= ncy but virtualbox-ose-kmod and kBuild are already installed from packages at t= his point, build failure log is attached as kBuild-buildfailure.txt Please tell me if I can supply any more details. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221050-8075-o6J5zmtyZq>