I've confirmed that the latest Vagrant box published has the fix. I've also confirmed that users can overwrite the default passing of the serial console to a File::NULL and write to a different file.
For everyone affected, run a `vagrant box update` on Focal boxes. This will grab the latest box. If you cannot update your base, using the workaround of attaching a NULL handler will work. This is documented in the code attached to this MP, as well as below
```
config.vm.provider "virtualbox" do |vb|
vb.customize [ "modifyvm", :id, "--uart1", "0x3F8", "4" ]
# Create a NULL serial port to skip console logging by default
vb.customize [ "modifyvm", :id, "--uartmode1", "file", File::NULL ]
end
```
I've confirmed that the latest Vagrant box published has the fix. I've also confirmed that users can overwrite the default passing of the serial console to a File::NULL and write to a different file.
For everyone affected, run a `vagrant box update` on Focal boxes. This will grab the latest box. If you cannot update your base, using the workaround of attaching a NULL handler will work. This is documented in the code attached to this MP, as well as below
Vagrant cloud link to latest:
https:/ /app.vagrantup. com/ubuntu/ boxes/focal64/ versions/ 20201012. 0.0
configuring a NULL file handler
``` vm.provider "virtualbox" do |vb|
config.
vb.customize [ "modifyvm", :id, "--uart1", "0x3F8", "4" ]
# Create a NULL serial port to skip console logging by default
vb.customize [ "modifyvm", :id, "--uartmode1", "file", File::NULL ]
end
```