I have a consistent issue with a VB instance running on my laptop, I have the same version running on my desktop with no issue.
The symptom is an SHA1 BAD Digest error during install or update.
If I install from an ISO I get it during install, if I use vagrant, it's during update.
Which makes me think it's an issue writing to disk or possibly caching, and possibly an issue with a driver on the laptop, which is a Lenovo X1, running windows 10 and minimal other apps.
I have attached the VB log and the linux log
----------------------------------------------------------------------------
Linux Guests fail during update
-
SilvaCloud
- Posts: 1
- Joined: 20. Jul 2020, 10:32
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Linux Guests fail during update
Your log contains these lines:
You might notice in the guest window's Status Bar the green turtle:
The choice of animal is appropriate: Your guest is running, just really slow. Or it might guru-meditate. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.
If VirtualBox is running without Hyper-V enabled, and nothing else is interfering with hardware virtualization (VT-x / AMD-V), then the usual virtualization icon (
) will be seen in the Status Bar.
To turn Hyper-V off completely, do this:
1. Shut down all programs. You will have to reboot your host.
2. See I have a 64bit host, but can't install 64bit guests. This tutorial has a couple more things to look for in step 2. Be sure these are all turned off.
3. Find the Command Prompt icon, right click it and choose Run As Administrator.
4. Enter this command:
If your Virtualbox does not start successfully, zip and post another vbox.log. For further info, see https://www.tenforums.com/tutorials/139 ... puter.html
{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
{timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...You might notice in the guest window's Status Bar the green turtle:
The choice of animal is appropriate: Your guest is running, just really slow. Or it might guru-meditate. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.If VirtualBox is running without Hyper-V enabled, and nothing else is interfering with hardware virtualization (VT-x / AMD-V), then the usual virtualization icon (
) will be seen in the Status Bar.To turn Hyper-V off completely, do this:
1. Shut down all programs. You will have to reboot your host.
2. See I have a 64bit host, but can't install 64bit guests. This tutorial has a couple more things to look for in step 2. Be sure these are all turned off.
3. Find the Command Prompt icon, right click it and choose Run As Administrator.
4. Enter this command:
bcdedit /set hypervisorlaunchtype off
5. Enter this command: shutdown -s -t 2
6. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10. If your Virtualbox does not start successfully, zip and post another vbox.log. For further info, see https://www.tenforums.com/tutorials/139 ... puter.html