<br><br>On Tuesday, 20 September 2016, François Cami <<a href="javascript:_e(%7B%7D,'cvml','fcami@fedoraproject.org');" target="_blank">fcami@fedoraproject.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Sep 19, 2016 at 7:50 PM, Michael Vermaes <<a>mvermaes@gmail.com</a>> wrote:<br>
> On Tuesday, 20 September 2016, Laurentiu Pancescu <<a>lpancescu@gmail.com</a>><br>
> wrote:<br>
>><br>
>> On 17/09/16 21:52, Nico Kadel-Garcia wrote:<br>
>><br>
>>> Can you use the much more recent gcc in the dev-toolset-4<br>
>>> repositories, which is in turn enabled by the the centos-release-scl<br>
>>> and centos-release-scl-rh packages? It would mean using a customized<br>
>>> koji or mock setup and activating a BuildRequires<br>
>><br>
>><br>
>> No, we have to use the same compiler used for building the kernel. [1] The<br>
>> only way is to get the patch from the gcc 4.9 branch backported (it seems<br>
>> small in the diff, but I don't know how much different were the code bases<br>
>> of 4.8 and 4.9 by that time). Even then, having kernels older than 3.11 is<br>
>> likely to remain a problem, if we insist on choosing this route to the Guest<br>
>> Additions.<br>
>><br>
>> I spent almost the entire last week investigating this, reading VirtualBox<br>
>> code and trying different things - probably a few days more in total, since<br>
>> I started. I started reading Packer's intro Thursday evening, and the<br>
>> missing bits about its "virtualbox-iso" builder and the "vagrant"<br>
>> postprocessor the next morning. [2] By the end of the day, I already had an<br>
>> automated, repeatable way of building Vagrant images for CentOS 6 and 7,<br>
>> based on our official kickstarts and our Netinstall ISOs, with the<br>
>> VirtualBox Guest Additions preinstalled and fully working. I'm much more<br>
>> inclined to go this way. I'm not sure if it would be possible to use CBS,<br>
>> but I could use Jenkins to generate the images, by allocating a node to run<br>
>> VirtualBox and Packer natively. Would this be acceptable from others'<br>
>> perspective?<br>
>><br>
>> Would the SCL SIG be willing to also provide Packer, besides Vagrant?<br>
>> Right now, I'm downloading the Packer binary directly from upstream; for<br>
>> production purposes, I'd feel more comfortable with getting it from SCL.<br>
>><br>
>> Best regards,<br>
>> Laurențiu<br>
>><br>
>> [1]<br>
>> <a href="https://www.virtualbox.org/manual/ch12.html#ts_linux-kernelmodule-fails-to-load" target="_blank">https://www.virtualbox.org/man<wbr>ual/ch12.html#ts_linux-kernelm<wbr>odule-fails-to-load</a><br>
>> [2] <a href="https://en.wikipedia.org/wiki/Law_of_holes" target="_blank">https://en.wikipedia.org/wiki/<wbr>Law_of_holes</a><br>
>> ______________________________<wbr>_________________<br>
>> CentOS-devel mailing list<br>
>> <a>CentOS-devel@centos.org</a><br>
>> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" target="_blank">https://lists.centos.org/mailm<wbr>an/listinfo/centos-devel</a><br>
><br>
><br>
> For what it's worth, we had been using Packer to build CentOS Vagrant boxes<br>
> from the templates provided at <a href="https://github.com/chef/bento" target="_blank">https://github.com/chef/bento</a> until recently,<br>
> as there wasn't an 'official' CentOS box for the VMware provider. Since I am<br>
> currently working on using Packer's vmware-vmx builder to repackage your new<br>
> VMware box to include the VMware Tools (the VMware equivalent to the<br>
> Virtualbox guest additions), I would be interested to know if you would<br>
> pursue a similar approach (using Packer) for VMware?<br>
<br>
CentOS 7 ships open-vm-tools, so enabling the vmtoolsd unit should be enough.<br>
Or am I missing anything?<br>
<br>
> I realise this is a bit off-topic for your current issue with Virtualbox,<br>
> but it would be great to have the official CentOS Vagrant boxes well<br>
> supported under both Virtualbox and VMware.<br>
><br>
> Let me know what I can do to assist in this.<br>
><br>
> ______________________________<wbr>_________________<br>
> CentOS-devel mailing list<br>
> <a>CentOS-devel@centos.org</a><br>
> <a href="https://lists.centos.org/mailman/listinfo/centos-devel" target="_blank">https://lists.centos.org/mailm<wbr>an/listinfo/centos-devel</a><br>
><br>
______________________________<wbr>_________________<br>
CentOS-devel mailing list<br>
<a>CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" target="_blank">https://lists.centos.org/mailm<wbr>an/listinfo/centos-devel</a><br>
</blockquote><div><br></div><div>Including open-vm-tools in the box would be a necessary first step, but my experience is that it's still necessary to load the vmhgfs driver as well, in order to get shared folder support working. As discussed at <a href="https://kb.vmware.com/kb/2073804" target="_blank">https://kb.vmware.com/kb/<wbr>2073804</a>:</div><div><i><br></i></div><div><div><font size="2"><span style="background-color:rgba(255,255,255,0)"><i>- Why does an operating system release not include the <code style="padding:2px 4px;border-top-left-radius:4px;border-top-right-radius:4px;border-bottom-right-radius:4px;border-bottom-left-radius:4px">vmhgfs</code> driver?</i></span></font></div><div><span style="background-color:rgba(255,255,255,0);font-size:small"><i><br></i></span></div><div><i><font size="2"><span style="background-color:rgba(255,255,255,0)"></span></font><span style="background-color:rgba(255,255,255,0);font-size:small"><span></span>The </span><code style="padding:2px 4px;border-top-left-radius:4px;border-top-right-radius:4px;border-bottom-right-radius:4px;border-bottom-left-radius:4px">vmhgfs</code><span style="background-color:rgba(255,255,255,0);font-size:small"> driver has not been contributed upstream. To work around this situation, install VMware Tools bundled with the Workstation or Fusion products, which will install the missing </span><code style="padding:2px 4px;border-top-left-radius:4px;border-top-right-radius:4px;border-bottom-right-radius:4px;border-bottom-left-radius:4px">vmhgfs</code><span style="background-color:rgba(255,255,255,0);font-size:small">drivers. The VMware Tools installer will not disturb inbox VMware drivers included in the OS.</span></i></div></div>