Still see the problems with 'ubuntu/xenial64' (v20160527.0.0)
Switching from the user vagrant and ssh key authentication to user ubuntu and password authentication lets things progress a little further but run into hostname problem.
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
/sbin/ifdown eth1 2> /dev/null
Stdout from the command:
Stderr from the command:
sudo: unable to resolve host ubuntu-xenial
mesg: ttyname failed: Inappropriate ioctl for device
Still see the problems with 'ubuntu/xenial64' (v20160527.0.0)
Switching from the user vagrant and ssh key authentication to user ubuntu and password authentication lets things progress a little further but run into hostname problem.
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
/sbin/ifdown eth1 2> /dev/null
Stdout from the command:
Stderr from the command:
sudo: unable to resolve host ubuntu-xenial
mesg: ttyname failed: Inappropriate ioctl for device
Which looks like this is tracked in:
https:/ /bugs.launchpad .net/ubuntu/ +source/ livecd- rootfs/ +bug/1561250