Publish 16.04 Boxes

[cheeseplus]

Leaving this as a placeholder so people can follow along and stop opening issues everywhere.

We are currently trying to build these but problems abound.

[cheeseplus]

Currently we can produce 3 boxes (one for each of the 3 hypervisors) that work under test-kitchen assuming you don't want shared folders.

updated
16.04 amd64 builds

• Parallels tools: packer finishes successfully but tools don't load
• VMware tools: packer finishes but shared folders don't seem to work
• VirtualBox: packer just hangs during tool install

[Maks3w]

This box works well without vagrant changes https://atlas.hashicorp.com/gbarbieru/boxes/xenial. Just it build the box with a kernel parameter for fix the interface name issue

https://github.com/ashantyk/vagrant-box-scripts/blob/master/make-ubuntu-16-xenial-xerus-box.sh#L66

[cheeseplus]

So we're well aware of that fix and that is not an issue with how we have chosen to resolve this - this is a two part issue as vagrant itself also has some bugs with relation to some 16.04 specific things.

geerlingguy/packer-boxes#1 (comment)
hashicorp/vagrant#4590
geerlingguy/packer-boxes#1 (comment)

And even then, shared folders aren't working for any of these that I've seen yet.

[legal90]

Parallels tools: failed to build, just dies hard

@cheeseplus Could you please describe what exactly goes wrong with Parallels Tools? (probably, in a separated issue).
I've just built and verified parallels box from template ubuntu-16.04-amd64.json and everything works fine there, including shared folders. (OS X 10.11, Parallels Desktop 11.1.3, Packer 0.9.0)

[cheeseplus]

@legal90 in short, in hangs upon installing the tools - not sure precisely what is freezing but it seems to hang indefinitely. Trying on alternate builders shortly.

[cheeseplus]

@legal90 are you using more RAM (> 512MB) by chance?

[cheeseplus]

@legal90 specifically

==> parallels-iso: Provisioning with shell script: scripts/common/vmtools.sh
    parallels-iso: + HOME_DIR=/home/vagrant
    parallels-iso: + mkdir -p /tmp/parallels
    parallels-iso: + mount -o loop /home/vagrant/prl-tools-lin.iso /tmp/parallels
    parallels-iso: mount: /dev/loop0 is write-protected, mounting read-only
    parallels-iso: + /tmp/parallels/install --install-unattended-with-deps
==> parallels-iso: Provisioning with shell script: scripts/ubuntu/cleanup.sh

==> default: Checking for Parallels Tools installed on the VM...
       ==> default: Parallels Tools were not detected on this VM! They are required
       ==> default: for shared folders, time sync and more. If shared folders are not
       ==> default: working on this machine, please install Parallels Tools within the
       ==> default: virtual machine and reload your VM.

Getting this on two different builders with Packer 0.10.0 and Parallels 11.1.3 and Ubuntu 16.04 amd64

[legal90]

are you using more RAM (> 512MB) by chance?

I've built it being on the clear state 2611d37, so there is a default RAM value, 512Mb.

[cheeseplus]

@legal90 so I may have mixed up about the hang - I get it to build but it definitely doesn't load the tools when Test-Kitchen starts up as seen above.

[legal90]

@cheeseplus /var/log/parallels-tools-install.log (in the box) should clarify what actually happened with Parallels Tools installation. Feel free to send it to me if needed.

[cheeseplus]

https://atlas.hashicorp.com/bento/boxes/ubuntu-16.04

@legal90 I'll open up a new issue today for investigating this further.

[legal90]

@cheeseplus FYI: I've just verified both of bento/ubuntu-16.04 and bento/ubuntu-16.04-i386 v2.2.6 from Atlas (for parallels provider), everything is fine there. There is Parallels Tools v11.1.3 installed inside, prltoolsd is running, prl_fs filesystem is available and /vagrant is mounted by Vagrant without any issues.