Error starting domain: internal error: process exited while connecting to monitor:

[anukulsharma]

Error starting domain: internal error: process exited while connecting to monitor: 2023-04-22T15:07:33.733713Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/home/parasetu/Downloads/Win10_20H2_v2_English_x64.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/home/parasetu/Downloads/Win10_20H2_v2_English_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 1402, in startup
    self._backend.create()
  File "/usr/lib/python3.10/site-packages/libvirt.py", line 1373, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: process exited while connecting to monitor: 2023-04-22T15:07:33.733713Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/home/parasetu/Downloads/Win10_20H2_v2_English_x64.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/home/parasetu/Downloads/Win10_20H2_v2_English_x64.iso': Permission denied

[anon11595408]

@anukulsharma

Error starting domain: internal error: process exited while connecting to monitor: 2023-04-22T15:07:33.733713Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/home/parasetu/Downloads/Win10_20H2_v2_English_x64.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/home/parasetu/Downloads/Win10_20H2_v2_English_x64.iso': Permission denied

…points to missing rights. Are you root? If not, try running the program from a root-shell, or via sudo. If that’s not an option, you can chown the file like this:

sudo chown parasetu /home/parasetu/Downloads/Win10_20H2_v2_English_x64.iso

[anukulsharma]

I did run your command but it didn’t work

[pebcak]

Run this: find $HOME ! -user $USER in a terminal.
It shouldn’t output anything. If it does, you have some ownership issue in your home directory.

[anon11595408]

@anukulsharma

I did run your command but it didn’t work

Is the file actually there, in that folder?
/home/parasetu/Downloads/Win10_20H2_v2_English_x64.iso

[anukulsharma]

Yes it actually exists

[anukulsharma]

@pebcak

find $HOME ! -user $USER

It did display now please help me to also resolve this, thanks

 find $HOME ! -user $USER
find: ‘/home/parasetu/doxygen-clang/pkg’: Permission denied
/home/parasetu/Downloads/Win10_20H2_v2_English_x64.iso
/home/parasetu/Downloads/virtio-win-0.1.208.iso
find: ‘/home/parasetu/websocketpp-git/pkg’: Permission denied
find: ‘/home/parasetu/cmocka-git/pkg’: Permission denied

[anon11595408]

This shows, @pebcak was right… your user isn’t owner of everything in your $HOME folder.

There are files that have shared rights with $ROOT within $HOME, therefore it is not a one-size-fits-all solution to chown all files within the user’s home-folder, afaict. Although in your situation, it might just suffice, to do:

sudo chown -R parasetu /home/parasetu/*

But I’m pretty sure that some folks here know a way around that?!

[anukulsharma]

Idk how an -R worked here , what did you remove , but it has worked for me thanks for helping me out

[pebcak]

chown --help
man chown