Import of existing zvol in Instances not working

Apps and Virtualization
,
1

Hello, I upgraded to TN Scale 25.04. and I am not able to import existing zvols from VMs to the new Instances tab. It does not matter if I select clone or move.

The following message will be shown:

File "/usr/lib/python3/dist-packages/middlewared/job.py", line 515, in run
await self.future
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 560, in __run_body
rv = await self.method(*args)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/api/base/decorator.py", line 93, in wrapped
result = await func(*args)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/virt/volume.py", line 230, in import_zvol
await self.middleware.call('virt.global.check_initialized')
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1000, in call
return await self._call(
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 715, in _call
return await methodobj(*prepared_call.args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/virt/global.py", line 255, in check_initialized
raise CallError('Virtualization not initialized.')
middlewared.service_exception.CallError: [EFAULT] Virtualization not initialized.

What does “Virtualization not initialized” and how can this be fixed?

2

My advice, go to the System / Boot menu and make the 24.10 boot environment active and reboot - hopefully your VMs will burst back into life.

Then go to the same UI page and delete the 25.04 boot environments.

Finally wait until 25.04.2 is available later this month and has been tried by a goodly number of people with VMs and upgrade directly to that - 25.04.2 will support existing VMs whilst 25.04.0 & 25.04.1 don’t.

3

OK thanks for your advice.
At the moment it looks good, all VMs are back.
Will wait till 25.04.2 is available and testet from the community.