My virtual machine doesn't start anymore

[Attila23]

Hi, after last Manjaro system update, my virtual machine (Qemu/KVM and Virtual Machine Manager) doesn’t start anymore; here’s the message of error:

“Errore nell’avvio del dominio: internal error: process exited while connecting to monitor: 2022-03-15T06:43:12.573758Z qemu-system-x86_64: -blockdev {“driver”:“file”,“filename”:”/home/attila23/Virtual Machines/Win10_21H2_Italian_x64.iso",“node-name”:“libvirt-2-storage”,“auto-read-only”:true,“discard”:“unmap”}: Could not open ‘/home/attila23/Virtual Machines/Win10_21H2_Italian_x64.iso’: Permission denied

Traceback (most recent call last):
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 72, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 108, 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 1384, in startup
self._backend.create()
File “/usr/lib/python3.10/site-packages/libvirt.py”, line 1353, in create
raise libvirtError(‘virDomainCreate() failed’)
libvirt.libvirtError: internal error: process exited while connecting to monitor: 2022-03-15T06:43:12.573758Z qemu-system-x86_64: -blockdev {“driver”:“file”,“filename”:"/home/attila23/Virtual Machines/Win10_21H2_Italian_x64.iso",“node-name”:“libvirt-2-storage”,“auto-read-only”:true,“discard”:“unmap”}: Could not open ‘/home/attila23/Virtual Machines/Win10_21H2_Italian_x64.iso’: Permission denied"

What can I do?
Thank you very much for the help.
Attilio.

[anon89812132]

Hello,

@Attila23

Could not open ‘/home/attila23/Virtual Machines/Win10_21H2_Italian_x64.iso’: Permission denied

Permission denied in your home directory is a sign of ownership issues … probably you started, at some point, your VM with sudo … don’t do that! Fix the ownership on your home directory.

[Attila23]

Thank you very much, can you tell me how to do it?
I never started my VM with sudo, never started it via terminal, I don’t know how this was possible.

[anon89812132]

@Attila23

can you tell me how to do it?

Tos fix permissions of your user in your home directory, some like this

Any command leads to "command not found" in text console (CTRL+ALT+F(n))

You have another post where you mention you can’t login … That and this one leads me to speculate you have ownership issues on files and folders in your home directory. Please fix that first. sudo chown $USER:$USER $HOME Reboot your system just in case.

But according to

@Attila23

Traceback (most recent call last):
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 72, in cb_wrapper
callback(asyncjob, *args, **kwargs)

I found this discussion
https://www.reddit.com/r/VFIO/comments/sewiph/virtmanager_giving_spice_gl_error/

Might want to recheck the configs for the VM.

[ishaan2479]

@Attila23

Machines/Win10_21H2_Italian_x64.iso’: Permission denied"

[Stable Update] 2022-03-14 - Kernels, KDE, LibreOffice, Kodi, Qt5, Mozilla, NetworkManager, Pipewire

Found a solution ( a proper one?) Edit file /etc/libvirt/qemu.conf after line 504 # The user for QEMU processes run by the system instance. It can be # specified as a user name or as a user id. The qemu driver will try to # parse this value first as a name and then, if the name doesn't exist, # as a user id. # # Since a sequence of digits is a valid user name, a leading plus sign # can be used to ensure that a user id will not be interpreted as a user # name. # # Some examples of valid values…

[kinghat]

im having the same issue after latest stable update. my home dir is owned by my user kinghat:kinghat. its for a manjaro vm.

edit:
used these to solve it:

[Stable Update] 2022-03-14 - Kernels, KDE, LibreOffice, Kodi, Qt5, Mozilla, NetworkManager, Pipewire

Found a solution ( a proper one?) Edit file /etc/libvirt/qemu.conf after line 504 # The user for QEMU processes run by the system instance. It can be # specified as a user name or as a user id. The qemu driver will try to # parse this value first as a name and then, if the name doesn't exist, # as a user id. # # Since a sequence of digits is a valid user name, a leading plus sign # can be used to ensure that a user id will not be interpreted as a user # name. # # Some examples of valid values…

which is basically method one from this article:

[Solved] Cannot access storage file, Permission denied Error in KVM Libvirt -...

[Attila23]

Thank you very much, kinghat!
I solved it but it was the second method for me.
Very grateful to you!
Attilio.

[fumantsu]

I have exactly the same issue and it was working just before the upgrade, so the upgrade something change from something which as “norm” before.
Example for myself. Default installation of Virtual machine manager (I was already using vmware or virtualbox) because I don’t know about virt/qemu and image file in a directory inside home directory. owner of this me, and the file was readable/writeable only by nobody because this is how before was working. So… ?