<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Virtualbox on FreeBSD developer&#39;s notebook</title>
    <link>https://kernelnomicon.org/tags/virtualbox/</link>
    <description>Recent content in Virtualbox on FreeBSD developer&#39;s notebook</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 12 Jun 2016 18:31:32 +0000</lastBuildDate>
    <atom:link href="https://kernelnomicon.org/tags/virtualbox/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VirtualBox Shared Folders: One VOP at a Time</title>
      <link>https://kernelnomicon.org/posts/virtualbox-shared-folders-one-vop-at-a-time/</link>
      <pubDate>Sun, 12 Jun 2016 18:31:32 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/virtualbox-shared-folders-one-vop-at-a-time/</guid>
      <description>&lt;p&gt;Two months ago I tried to setup dev environment using FreeBSD Vagrant box just to find out that FreeBSD does not support VirtualBox shared folders. After some googling I found Li-Wen Hsu&amp;rsquo;s github &lt;a href=&#34;https://github.com/lwhsu/freebsd-vboxfs&#34;&gt;repository&lt;/a&gt; with some work in this area. Li-Wen and Will Andrews has already done major chunk of work: patches to VirtualBox build system, skeleton VFS driver, API to talk to hypervisor but hit a block with some implementation details in VirtualBox&amp;rsquo;s virtual-memory compatibility layer. Will provided &lt;a href=&#34;https://github.com/lwhsu/freebsd-vboxfs/blob/master/vboxvfs/vboxvfs_prov.c#L131&#34;&gt;very comprehensive analysis&lt;/a&gt; of the problem.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
