Opened 6 years ago
Last modified 6 years ago
#18463 new defect
console boot hangs/highcpu without vbox serial & console=ttyS0 in grub
| Reported by: | busk | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.0.4 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
When using a cloud-init image like https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.ova , that uses grub console=ttyS0, boot hangs and high cpu occurs.
You can fix via workaround on cloud init image by removing console=ttyS0 from GRUB_CMD_LINUX_DEFAULT
`
sudo sed -i 's/ console=ttyS0g' /etc/default/grub.d/50-cloudimg-settings.cfg
sudo update-grub
`
but then virsh console my-kvm-qemu-vmnane on Linux doesn't return console information
Workaround is to add a serial port to vm via "raw with /dev/null"
It works fine in VMWare and other vms just not Virtualbox. This seems like it would be a Virtualbox issue thought there is a bug here https://bugs.launchpad.net/cloud-images/+bug/1573095
Replying to busk:
Are you using nested virtualization? Because the bug certainly talks about running the VM inside KVM, and nested virtualization is not supported, except under very specific conditions, one of them being VirtualBox running inside VirtualBox, and on an AMD CPU (for the moment).
BTW, it's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".