On 02/24/2020 04:29 AM, David C. Rankin wrote: > On 02/23/2020 01:57 AM, Frank Batschulat wrote: >> you are trying a Virtualbox version 5.2.37 (135942), >> that does not support the 5.5 kernel. for more details see: >> >> Ticket #19145 (closed defect: fixed) >> Opened 2 months ago >> Last modified 2 days ago >> linux: kernel 5.5-rc1/rc2 - we need changes -> fixed in 6.1.4 >> https://www.virtualbox.org/ticket/19145 > > I was, 5.2.38 fixed the guest addition issue (confirmed) -- though it took > more than 50 minutes to find out due to > https://www.virtualbox.org/ticket/19311 that is still giving me fits. > > Thank you for your help. > >
Note, all my issues with 5.5 are resolved and all bugs closed. The delay issue was due to a disk in the RAID1 array holding the VB guest images developing high io_wait times though no errors were generated by mdadm or in the journal and smartctl gave the disk an overall pass. So https://www.virtualbox.org/ticket/19311 was not a VB bug and closed not a bug. Lesson, raid disks can be in pre-fail and if the guest is hosted on that array, performance becomes unuably slow. Bad drive removed from array, fresh 3T installed and array rebuilt and VB works like at champ on 5.5, headless and over the network. -- David C. Rankin, J.D.,P.E. _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
