Date: Tue, 25 Jan 2011 18:13:43 -0800 From: Julian Elischer <julian@freebsd.org> To: Mikolaj Golub <to.my.trociny@gmail.com> Cc: freebsd-emulation@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VirtualBox + VIMAGE Message-ID: <4D3F8357.2070005@freebsd.org> In-Reply-To: <86tygwy9p0.fsf@kopusha.home.net> References: <86oc77heqk.fsf@kopusha.home.net> <4D3D2DE9.2060004@freebsd.org> <86tygwy9p0.fsf@kopusha.home.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/25/11 1:06 PM, Mikolaj Golub wrote: > On Sun, 23 Jan 2011 23:44:41 -0800 Julian Elischer wrote: > > JE> On 1/23/11 6:33 AM, Mikolaj Golub wrote: > > >> As a quick fix I added in VBoxNetFlt-freebsd.c in all "problem" functions > >> CURVNET_SET_QUIET(vnet0) macro, which sets td->td_vnet to default vnet (see the > >> attached patch). This has fixed the issue for me and now I am happily running > >> both VNET jails and VirtualBox machines on my desktop. > >> > >> But the way I fixed the issue looks hackish for me. Could someone suggest a > >> better solution? > JE> this is probably at east partially the correct solution. > JE> Usually you should also set the value back to its previous value when > JE> you leave that code as well. > > Thank you for the comments. Actually the patch contained CURVNET_RESTORE() > too. I just did not mentioned it :-). So if it looks like right solution here > is an "improved" version of the patch: vnet to switch is taken from thread's > ucred (on interface initialization) or from ifp->if_vnet. yes I like it.. Now you just need a port person to patch the port :-) > >> In case someone is interested in trying this patch, below are the instructions > >> how to build "VIMAGE safe" vbox driver from ports: > >> > >> cd /usr/ports/emulators/virtualbox-ose-kmod > >> make patch > >> cd work > >> patch -p0< /path/to/VirtualBox-3.2.12.VIMAGE.patch > >> cd .. > >> VIMAGE=1 make > >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D3F8357.2070005>