Note: My comment (#34) above is in VirtualBox 6.1.8 and without the
Serial port redirection mentioned in comment #7. With the serial port
redirection everything seems to work properly for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Interestingly, using the VirtualBox GUI to boot a VM created from the
20200522.0.0 vagrant box causes the entire VirtualBox GUI to hang. The
only way out of it is to force quit the VM processes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Re #28
I have both problems using the 20200522.0.0 image on a Windows host.
Host specs: Lenovo Thinkpad P50, Intel Core i7-6700HQ, Windows 10 v1909,
tried with both VirtualBox 6.0.4 and 6.1.8.
Full details at https://askubuntu.com/questions/1243582/unable-to-boot-
official-vagrant-boxes-for-20-0
This doesn't sound like a good idea to me, given the prevalence of
running Ubuntu on virtual machines with less than 4GB of RAM. I'm
thinking specifically of hosting providers like Linode, AWS,
DigitalOcean, etc., as well as tools like Vagrant, all of which are
extremely popular right now. Using t
This appears to be a problem in certain daily builds only. I don't have
the exact dates of when it started and stopped working, but I was able
to reproduce several times in June, July, and August. After that, I was
unable to reproduce using a build made on August 20th, 2013, but then I
was able t
