On 02/04/2020 12:42 PM, David C. Rankin wrote:
On 02/04/2020 04:18 AM, David C. Rankin wrote:
lAll,
After update to 5.5 kernel and rebuild of virtualbox from the 5.2.36 and the latest testcase build for 5.2.37 (all kernel modules build and load fine)
https://www.virtualbox.org/download/testcase/VirtualBox-5.2.37-135942-Linux_...
Arch guests fail to run on Arch host. network device enp0s3 not found, udev kernel rules fail, and the boot never complete.
All fine with the 5.4 kernel. I've posted to the vbox-users list, but if anyone here has additional information I would appreciate it.
This explains Virtualbox does not support the 5.5 kernel -- no fix yet:
Ticket #19145 (accepted defect) Opened 8 weeks ago linux: kernel 5.5-rc1/rc2 - we need changes https://www.virtualbox.org/ticket/19145
OK, Need help from the smart folks. Downgrading the kernel/kernel-headers to 5.4.15 and downgrading virtualbox to the version working on 5.14 [testcase 5.2.35 (135458)] does not allow guests to start as they did before the last update to linux 5.5. Starting the guest headless - reports it started. However, when I open the guest via-rdesktop monitor the boot, but the boot process would not complete and could not create the network interface enp0s3, the udev kernel device manager will not start, the boot process cannot flush the journal to persistent storage (??) and boot cannot create volatile files and directories (??) All modules build for each version of virtualbox. (5.2.35, 5.2.36 and testcase 5.2.37 (135942)). I have tried on the downgraded 5.4.15 and LTS. There is no combination that will start the virtualbox guests as before. There must be another package that was updated that comes into play (python?). Is anyone else experiencing problems with Virtualbox and has anyone else seen similar behavior? Any workarounds. I have a number of virtualbox guests I use. -- David C. Rankin, J.D.,P.E.