Vagrant in a cloud-based host cannot ssh to boot2docker

[tooda02]

An OpenStack cloud-based host with Vagrant 1.7.4 and VirtualBox 5.0 (on Ubuntu 14.04) cannot ssh to a boot2docker container (these are the latest releases of both, but the issue can be reproduced with other releases). Using the sample Vagrantfile on vagrantcloud changed only to uncomment the forwarded-port line, vagrant up fails with a connection timeout:

Bringing machine 'boot2docker' up with 'virtualbox' provider...
==> boot2docker: Checking if box 'yungsang/boot2docker' is up to date...
==> boot2docker: Fixed port collision for 2375 => 2375. Now on port 2200.
==> boot2docker: Fixed port collision for 22 => 2222. Now on port 2201.
==> boot2docker: Clearing any previously set network interfaces...
==> boot2docker: Preparing network interfaces based on configuration...
boot2docker: Adapter 1: nat
==> boot2docker: Forwarding ports...
boot2docker: 2375 => 2200 (adapter 1)
boot2docker: 8080 => 8080 (adapter 1)
boot2docker: 22 => 2201 (adapter 1)
==> boot2docker: Running 'pre-boot' VM customizations...
==> boot2docker: Booting VM...
==> boot2docker: Waiting for machine to boot. This may take a few minutes...
boot2docker: SSH address: 127.0.0.1:2201
boot2docker: SSH username: docker
boot2docker: SSH auth method: private key
boot2docker: Warning: Connection timeout. Retrying...
--- 18 repetitions of line above line omitted for brevity ---
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

vagrant status shows the machine is running:

$vagrant status
Current machine states:
boot2docker running (virtualbox)

If the Vagrantfile is updated to change the vm.box to hashicorp/precise32, then the ssh connection is successful.