Debian 10 VM in Windows 10 Host Blank Screen

[looqmaan]

Hi,

I have Debian 10 VM in Windows 10 Host. It was running just fine until this morning. I got an error this morning saying "Could not read memory value..." or something like that, and the VM went into an aborted state. When I tried to restart, I kept getting a blank screen. I have tried uninstalling/re-installing the VirtualBox, restoring from the backup (.ova) file, and creating a new OS from fresh Debian 10 iso. No luck. Could anyone please help take a look at the log files and let me know what I should do next?

Thanks.

VBox.zip

VBox Log File

(27.05 KiB) Downloaded 2 times

VBoxHardening.zip

VBoxHardening Log File

(27.69 KiB) Downloaded 3 times

[scottgus1]

Hyper-V is enabled and needs to be disabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)

Also, a spot of advice:

restoring from the backup (.ova) file,

Exporting != backup. Exporting and cloning aren't recommended for backing up a VM. Either process changes some guest settings, and a change in the guest means there's no way to confirm the backup. UUIDs get changed, which can up-end activation and grub loaders.

A simple file-copy of the fully-shut-down, not save-stated, guest's folder, with the guest .vbox file, Snapshots and Logs folders, and the guest virtual disk file(s), is the best way to copy a guest. The copy can be 'FC' file-compared on local backup media, or hashed for offsite media, to confirm the copies. Note that if the disk file is not in the guest folder next to the guest's .vbox file, the path to the drive file in the .vbox file is absolute, and the full path needs to be duplicated on the new host, or the .vbox file needs to be manually edited. (Not to mention Windows, Linux & Mac paths are not compatible with each other, and I would guess the same about Solaris hosts.) If the guest drive file is in the guest folder with the .vbox file, the path is relative, and the guest can be dropped onto any capable & properly-set-up host, any supported host OS. The guest folder can easily reside on any host drive. Virtualbox 6.0.x and later can easily move the guest folder to the host drive that the guest drive file is on, and then move the drive file into the guest folder so the guest is in optimum format.

[looqmaan]

Thank you for your kind help and your suggestions. I will give it a try and let you know the result.

[looqmaan]

Thanks again for your help and guidance. It works after disabling the VT-x.

Code: Select all

bcdedit /set hypervisorlaunchtype off

Regarding the backup/export of the VMs, is there a tutorial or a link/reference where I can learn more about it?

Best Regards.

[scottgus1]

The closest we have to a tutorial on backing up a VM is re-interpreting Moving a VM. And the paragraph I posted above.

disabling the VT-x.

Code: Select all

bcdedit /set hypervisorlaunchtype off

The bcdedit command doesn't disable VT-x, it disables Hyper-V. Disabling VT-x has to be done in the PC's BIOS and renders Virtualbox 6.1.x inoperable, and 6.0.x & earlier are severely restricted.

[looqmaan]

Thanks. Will look into that.