VirtualBox + VIMAGE

Mikolaj Golub to.my.trociny at gmail.com
Tue Jan 25 21:07:00 UTC 2011


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.

 >> 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
 >>

-- 
Mikolaj Golub
-------------- next part --------------
A non-text attachment was scrubbed...
Name: VirtualBox-3.2.12.VIMAGE.1.patch
Type: text/x-patch
Size: 5387 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-virtualization/attachments/20110125/f4d30792/VirtualBox-3.2.12.VIMAGE.1.bin


More information about the freebsd-virtualization mailing list