When attempting to install a Linux O/S (Kali, Debian based), during the package installation phase it would fail. The apt logs showed that the hashes were wrong on various packages (despite the .iso being valid). A screenshot is included of this failure scenario. The packages are loaded from the mounted disk (no network mirror). Each re-install attempt would reveal different packages having the wrong hashes (but correct filesize).
Eventually I was able to install a smaller distribution of Debian and I can trigger the same issue while the guest O/S is running.
Doing a wget on the guest, downloading the same file from the Internet four times in succession will result in different file hashes. The file sizes are all the same:
user@debian:~$ md5sum nmap-7.80.tgz 05bb63c890ed67c33fd4b78ca15c1951 nmap-7.80.tgz user@debian:~$ md5sum nmap-7.80.tgz.1 96673f23b3165bf8341f37027b3ed285 nmap-7.80.tgz.1 user@debian:~$ md5sum nmap-7.80.tgz.2 c76e5aab92d51745ae89eeb9d2c529f0 nmap-7.80.tgz.2 user@debian:~$ md5sum nmap-7.80.tgz.3 7d14935704815ed83e220d0f73db0fab nmap-7.80.tgz.3Same file-sizes.
user@debian:~$ ls -l nmap-7.80.tgz* -rw-r--r-- 1 user user 13132692 Aug 10 2019 nmap-7.80.tgz -rw-r--r-- 1 user user 13132692 Aug 10 2019 nmap-7.80.tgz.1 -rw-r--r-- 1 user user 13132692 Aug 10 2019 nmap-7.80.tgz.2 -rw-r--r-- 1 user user 13132692 Aug 10 2019 nmap-7.80.tgz.3What debug related logs would be useful to attempt to identify the source of this strange issue?
Note I have tried both dynamic and fixed size disks and the issue occurs on both. I can't help but suspect there is an issue here possibly related to I/O related drivers.
Thank you.