System rundown
Under a Windows 10 Pro 64-bit host I run VirtualBox Version 6.1.14 r140239 (Qt5.6.2), 64-bit. I have the current Guest Additions installed on the client VM. My trouble as described below has occurred for a number of months, so at least with the prior two versions of VB.
I have a VM guest of the latest 64-bit Linux Mint Cinnamon, dubbed Linux Mint 20 Ulyana. It is completely up-to-date (see below).
Physical RAM on the host is 8 GB. Disks are GPT under UEFI. The BIOS is updated to the current version dated 6/16/2020. Chipset is Intel. The host Windows OS version is 10.0.19041 (Build 19041) and is fully updated. SFC /scannow runs error-free. The disks have been checked for health.
The Linux guest is set to use 1792 MB of base memory. Video memory is set to 24 MB. The guest is accessed via a SATA controller in the VB app. It is stored as a VDI dynamically allocated storage device.
I have tried to solve my problem by trying different network configurations in VB. The current setting is Bridged Adapter, Realtek PCIe GbE Family Controller. The problem persists. The original setting of NAT had the same problems. Most other settings are the defaults from having set up the client.
The VM log file is attached.
Issue
Starting months ago, the Linux guest errors out on update operations. It generally happens when trying to read the ubuntu_dists_focal-updates_main packages. I suspect a network bug or issue in the VirtualBox for Windows client application. I will attach a screenshot of the last terminal screenful from running
Code: Select all
apt updatehttps://www.cluesforhumans.com/pub/vbf/VMprob.jpg
I have never been able to run updates successfully in this guest under this Windows host. I have tried installing new guests from the same current build of Linux Mint. I tried different ISOs. They all fail with the same problem. I could not complete the original installation of the guest from the ISO for this reason. The install always failed at some point (but not the exact same point) while trying to update.
However, to get around the failed builds, I built this guest from a different Windows 10 host machine several months ago. I did not have any trouble. I used my same network and router. I exported the machine. And I imported it into the VM client app on this host machine under Windows in order to create this guest. That worked without errors.
I had a Linux Mint guest on this same system for half-a-year before this trouble started. It always updated fine until one day this trouble began. I trashed that guest trying to repair the failed update downloads. That's when I tried building a new guest and found I could not complete the normal installation from ISO. (Checksums were also compared on the ISOs. I tried several times, including trying another variant from the Linux Mint family instead of Cinnamon. The installation always failed on this host.)
It so happens that this computer is set up as a dual-boot machine. I can boot it to Linux Mint 20 instead of Windows. So I installed the VB client application under that host on this same hardware. I imported the same VM there. It updates fine!
What I have been doing for three months now is, I boot to Linux, update the VM Linux guest there, reboot to Windows, and run the very same Linux guest successfully. Everything works so long as I do not try to update the packages under the Windows host.
Help getting this host to succeed at letting my Linux guest update would be most appreciated!
/spamless
