[Bug 1615579] Re: Vagrant fails to bring up xenial64 instance on VirtualBox
Is this bug still relevant? I have tried the latest ubuntu/xenial64 (v20201104.0.0) and it boots without any problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615579 Title: Vagrant fails to bring up xenial64 instance on VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1615579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615579] Re: Vagrant fails to bring up xenial64 instance on VirtualBox
I used to us this box without problem. But I faced the same problem when I updated the box. I spent time trying to figure out which version of the box still works. I found that the last version that works fine is 20160715.0.0 Another thing I noticed is that the file /etc/resolv.conf is empty on all the versions that don't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615579 Title: Vagrant fails to bring up xenial64 instance on VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1615579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615579] Re: Vagrant fails to bring up xenial64 instance on VirtualBox
** Changed in: vagrant (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615579 Title: Vagrant fails to bring up xenial64 instance on VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1615579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615579] Re: Vagrant fails to bring up xenial64 instance on VirtualBox
I spent hours trying to find out what was wrong with my Vagrantfile -- but it was the box which is messed up. The clues are: 1) the username is "ubuntu" but it should be "vagrant". 2) the nameserver is not hooked up, so no DNS names are translated. I tested this morning with the latest everything, on OS-x El Capitan and Ubuntu Make 16.04 host machines. The first two of these work, the last one does not: > $ vagrant box list > cbednarski/ubuntu-1604 (virtualbox, 0.1.0) > ubuntu/trusty64 (virtualbox, 20160830.0.0) > ubuntu/xenial64 (virtualbox, 20160909.0.0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615579 Title: Vagrant fails to bring up xenial64 instance on VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1615579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615579] Re: Vagrant fails to bring up xenial64 instance on VirtualBox
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: vagrant (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615579 Title: Vagrant fails to bring up xenial64 instance on VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1615579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615579] Re: Vagrant fails to bring up xenial64 instance on VirtualBox
I can't reproduce this on either of my Ubuntu machines, both of which are running the same version of Vagrant and the Linux kernel. What happens if you run 'vagrant box update' in the same directory as the Vagrantfile? It could be that you are running an older box which doesn't have this issue fixed (the official Vagrant boxes are updated every few days). For reference, the commands I ran were: cd /tmp vagrant init ubuntu/xenial64 vagrant up I didn't have the ubuntu/xenial64 box installed, so it fetched the latest version automatically the first time I ran vagrant up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615579 Title: Vagrant fails to bring up xenial64 instance on VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1615579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
