new windows guest always aborts

[r144]

context
I have a windows guest that is running fine on a bullseye linux machine and virtualbox 6.1.
However, it has a vhd harddisk, and I want to replace that by a vdi harddisk.

I have cloned the vhd and created a vdi file; the size went down from 78 Gb to 37 Gb.

Before switching disks on the original guest, I decided to try out the vdi disk first. I did that by creating a new machine with another name (w2) and attaching the cloned vdi (attach existing disk).

the problem
If I start that new machine, it always fails with

Failed to open a session for the virtual machine w2.

and in the details virtualbox says

Code: Select all

The VM session was aborted.

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
SessionMachine
Interface: 
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

from the command line

Code: Select all

ggon@NL008-L0014Z vboxmanage startvm w2
Waiting for VM "w2" to power on...     
VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession
[1]    480833 exit 1     vboxmanage startvm w2
on@NL008-L0014Z vboxmanage startvm w2 
Waiting for VM "w2" to power on...     
VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession
[1]    480833 exit 1     vboxmanage startvm w2

Afterwards, the state is aborted. The logfile does not contain something alarming.
I tried different settings of virtualisation, including hyper-v , default and kvm, which all fail in the same way.
I tried removing the aborted attribute in the vbox file, but that made no difference either.

What can I do to revive the machine and test the validity of the cloned vdi? What causes this error?

thanks in advance, Ruud

[fth0]

The VBox.log file indicates that a version mismatch between VirtualBox and the VirtualBox Extension Pack led to the abort. Install matching versions to solve this problem.

[r144]

hi Th0,

thanks for this insight. Indeed, you are right. I completely missed that detail. The log files says

Code: Select all

00:00:01.041458 VirtualBox VM 6.1.40 r154048 linux.amd64 (Oct 11 2022 15:40:53) release log

and further on

Code: Select all

00:00:01.051139   Oracle VM VirtualBox Extension Pack (Version: 6.1.32 r149290; VRDE Module: VBoxVRDP)

...which is clearly a version mismatch. Didn't realise the consequence though.
I have installed the proper version and indeed this solves this problem! Thanks again.

Ruud