Today I could not start my Win10 VM but cannot understand error message

In short I had to use my Win 10 VM for some work today and what used to work fine now will not start.
I have no idea what has changed but I have not touched the VM since I last used it.
The error I have is:-

Error starting domain: internal error: process exited while connecting to monitor: 2024-07-12T21:35:11.289494Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/home/alastair/applications/Windows_10/Win10_22H2_EnglishInternational_x64.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/home/alastair/applications/Windows_10/Win10_22H2_EnglishInternational_x64.iso': Permission denied

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 71, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 107, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
    ret = fn(self, *args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1425, in startup
    self._backend.create()
  File "/usr/lib64/python3.11/site-packages/libvirt.py", line 1379, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: process exited while connecting to monitor: 2024-07-12T21:35:11.289494Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/home/alastair/applications/Windows_10/Win10_22H2_EnglishInternational_x64.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/home/alastair/applications/Windows_10/Win10_22H2_EnglishInternational_x64.iso': Permission denied

I am reluctant to create a new VM from scratch as I have several apps installed and needed.
Please can somebody wiser than I help me fix the problem.
Budgeie2

I think you have to investigate why you receive a permission denied.
It seems you cannot access the iso image of Win10 : do you really need it in your Win10 VM?

1 Like

Entirely possible that the .ISO is mounted in the virtual machine, but it’s been deleted locally, I’ve done that to myself a number of times.

Pretty easy to remove it in virt-manager.

Hi and many thanks for both replies.
In my profound ignorance I have always left the CDROM iso from my home directory in the VM.
Now that you have told me and I have removed the connection from the VM, all is well. Just strange that it hasn’t happened before but all good now.
Thanks again,
Budgie2

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.