Forum › Forums › Official Releases › antiX-21/22 “Grup Yorum” › [SOLVED] VirtualBox 6.1 troubles
- This topic has 1 reply, 1 voice, and was last updated Jan 4-10:57 am by sybok.
-
AuthorPosts
-
December 8, 2022 at 2:46 pm #95161Member
sybok
Hi, recently (approximately two weeks ago) VirtualBox (VB) got messed up on my antiX-stable (based on antiX-19.2, upgraded) 64-bit.
1) No VM runs reliably anymore, Win10 sometimes boots but sadly not in most of the cases and it often reboots without a significant input from me, Android 9 suddenly reboots, antiX-21 got messed up as well.
2) Newly installed antiX-22 often reports troubles with SHA256 hash mismatch when attempting to download packages.Did/Does anyone experience that as well?
If yes, is there any known fix for item no. 1)?I removed and reinstalled VB and related packages; did not help.
I tested running from alternate Linux (Fedora-37) that is used in dual boot; same issue 1) there.Regarding 2), I have tried to change antiX/Debian repositories (followed by ‘apt clean’), alter the connected via NAT (and cable-connected) to bridged adapter.
None of that solves the problem.I searched the interweb and similar issue was fixed in 6.1.18 and someone pointed out Windows-host Hyper-V may cause such an issue by modifying packets.
‘apt-cache policy virtualbox’ outputs version: 6.1.22-dfsg-2~mx21+1
Repositories and other info can be found in the attachment.
I did check MX-Linux forum few days ago but found nothing (apart from discussing VB version 7 working in Slackware [?]).I consider exploring HW/disc health (using ‘smartctl’).
Nevertheless, the system runs normally, apart from the troublesome VB, thus I am not inclined to believe this is the cause.References:
https://lovelinux.medium.com/virtualbox-windows-10-and-hashes-863fb1908e27
https://forums.kali.org/showthread.php?48822-Kali-2020-2-OVA-VIRTUALBOX-HASH-SUM-MISMATCH -> contains a fix/workaround that did help in the case of antiX-22 guest.- This topic was modified 4 months ago by BobC.
Attachments:
January 4, 2023 at 10:57 am #96732Member
sybok
::Solved by upgrading to Virtualbox 7.0.4 (available in antiX/bullseye since December 2022).
Perhaps, some updates phased out several programs of sufficient compatibility with the version 6.1.22. -
AuthorPosts
- You must be logged in to reply to this topic.