Can confirm it's still a problem with 20160218.4, but I have a couple workarounds.. Technically, the issue isn't that xenial fails to boot -- it's just that you can't see it (and neither can vagrant).
The issue is with 'console=ttyS0' on the grub command line. It's strange because my earlier vivid vagrant boxes also have this, but those never had a problem. Maybe some difference in other graphics stuff loaded in those vivid boxes... Anyway, on to the workarounds: 1 - edit xenial's grub.cfg to remove console=ttyS0. If your host is Linux, you should be able to mount the vmdk with 'kpartx -av /path/to/ubuntu-xenial-*.vmdk', then mount whatever loops kpartx spits back at you. If you're not comfortable with kpartx, you can launch virtualbox, edit a known working guest to add the xenial vmdk as another disk, boot that guest, and then 'sudo mount /dev/sdb1 /mnt'. At this point, you've got the xenial root disk mounted (i'm assuming at /mnt). Now edit /mnt/boot/grub/grub.cfg to remove the console=ttyS0 bits (i used sudo vi and a :w! for this since grub.cfg is mod 444). Now 'sudo umount /mnt'. If you did this with a known working guest through virtualbox, be sure to shutdown the guest, and remove the xenial vmdk from the guest's config so you don't unintentionally mount that again. Now 'vagrant up' your xenial machine, and it should proceed to a point you can 'vagrant ssh' to it (although you'll probably then hit bug 1538547). 2: add a serial port to your vagrant box I'm assuming here that you've run something like "vagrant box add xenialbox <url>" and adjusted your Vagrantfile to use xenialbox, and are sitting at a failed "vagrant up <your-xenial-guest>". That's perfect. Now open virtualbox and forcefully halt your xenial guest. Edit the guest by clicking Settings -> Ports -> Serial Ports -> Port 1. Click the "enable serial port" check box, leave the defaults alone for COM1, ensure Port Mode is "Disconnected" and click OK to save the settings. Now you can re-run 'vagrant up <your-xenial-guest>" and it ought to work.. (again, until you hit bug 1538547). Either of these worked for me to get 'vagrant ssh <my-xenial-guest>' working with virtualbox 5.0.14. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546108 Title: Latest Vagrant box for Ubuntu Xenial is failing to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1546108/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
