On 02/05/2020 02:48 AM, David C. Rankin wrote:
>   This occurs both when the guests are started headless, or when run from the
> VirtualBox GUI.
> 
>   This now occurs with builds:
> 
> testcase 5.2.35 (135458)
> 5.2.36
> testcase 5.2.37 (135942)
> 
>   It occurs on the 5.4 kernel and on the 4.19 LTS kernel on Archlinux. So
> apparently there are changes to another package (python?) I'm still trying to
> sort this out.
> 
>   Have you heard of any other issue surrounding package updates impacting
> virtualbox?

Frank, (or any smart dev)

  I have attached the dmesg output and strace of the communications from the
Archlinux guest that hopefully captures what the problem is after package
updates on 1/27/20 left my 5.2 install unable to talk to each other in any
reasonable way. It takes 10 minutes to boot a simple Archlinux guest to a
basic text console.

  I am not great at interpreting the strace output, but the fact that ever
simple communication between host and guest appears to take 12-18 seconds to
complete -- corroborates with what I am seeing trying to run the guests. Both
files are in the attached tar.xz file to save bandwidth (it's only 22k)

  Let me know if anything stands out or if there is something else I can try
and grab.

  The vbox install I am using is from the AUR package I build for Arch
(https://aur.archlinux.org/packages/virtualbox-bin-5). I have built all
versions listed above as well as default 5.2.36 - same behavior on each. After
all the system downgrade tests -- I'm really stuck at this point.

-- 
David C. Rankin, J.D.,P.E.

Attachment: dmesg+strace_vbox-5.2.tar.xz
Description: application/xz

_______________________________________________
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

Reply via email to