Are those directories in /media/anon/8TB all different storage pools and can you share the output of "ls -l /media/anon/ssd"?
/media/anon/ssdAre those directories in /media/anon/8TB all different storage pools and can you share the output of "ls -l /media/anon/ssd"?
That directory is owned by anon, since the vm on your system is most likely running as a qemu user too I would try changing the permission of that to either "root:kvm" or "libvirt-qemu:kvm" If that doesn't work if may be useful to check what user is running the process when one a working vm boots.drwxrwxrwx 5 anon kvm 4096 Apr 5 10:52 language-models
ps -o user= -p (followed by pid)
I gave up on this, I am in the middle of installing said software on my hostmachineOn my system the vm's run as the qemu user so the qemu user needs to be able to write to the qcow2 images. Looking at your output.
That directory is owned by anon, since the vm on your system is most likely running as a qemu user too I would try changing the permission of that to either "root:kvm" or "libvirt-qemu:kvm" If that doesn't work if may be useful to check what user is running the process when one a working vm boots.
Code:ps -o user= -p (followed by pid) [CODE]
Linux Mint Cinnamon 21.1What distribution I are you running, I will try to see if I can replicate it within a virtual system?
maybe it's relevant maybe not. But my HDD is encrypted and I mount it manually via:What distribution I are you running, I will try to see if I can replicate it within a virtual system?
sudo cryptsetup luksOpen /dev/sda crypt
sudo mount /dev/mapper/crypt /media/anon/8TB/
Don't know if it's permitted here, but
"bump"
It's not relevant since you are just mounting a decrypted filesystem on a local mount location.maybe it's relevant maybe not. But my HDD is encrypted and I mount it manually via:
Code:sudo cryptsetup luksOpen /dev/sda crypt sudo mount /dev/mapper/crypt /media/anon/8TB/
I haven't had the time until now to try it myself. I installed qemu within a vm and every single path change and where I placed my vm started without any issues. Then I noticed this in the output your shared earlier.Don't know if it's permitted here, but
"bump"
I changed that directory to root:root as well and then I got the same error as you. Can you share the output of the following commands?anon@navi [11:38:31] [~]
-> % ls -ll /media/
insgesamt 4
drwxr-x---+ 7 root root 4096 Mär 20 19:39 anon
ls -l / | grep media
getfacl /media/anon
sureIt's not relevant since you are just mounting a decrypted filesystem on a local mount location.
I haven't had the time until now to try it myself. I installed qemu within a vm and every single path change and where I placed my vm started without any issues. Then I noticed this in the output your shared earlier.
I changed that directory to root:root as well and then I got the same error as you. Can you share the output of the following commands?
Code:ls -l / | grep media getfacl /media/anon
anon@navi [19:40:44] [~]
-> % ls -l / | grep media
drwxr-xr-x 3 root root 4096 Mär 11 17:41 media
anon@navi [19:40:46] [~]
-> % getfacl /media/anon
getfacl: Entferne führende '/' von absoluten Pfadnamen
# file: media/anon
# owner: root
# group: root
user::rwx
user:anon:r-x
group::---
mask::r-x
other::---
sudo setfacl -m u:libvirt-qemu:rx /media/anon
This did the trick. what exactly did this command do?Run the following command.
Your vm should then be able to start without getting a permission error.Code:sudo setfacl -m u:libvirt-qemu:rx /media/anon
The last command I asked you to share the output was the following.This did the trick. what exactly did this command do?
anon@navi [19:40:46] [~]
-> % getfacl /media/anon
getfacl: Entferne führende '/' von absoluten Pfadnamen
# file: media/anon
# owner: root
# group: root
user::rwx
user:anon:r-x
group::---
mask::r-x
other::---
anon@navi [11:38:31] [~]
-> % ls -ll /media/
insgesamt 4
drwxr-x---+ 7 root root 4096 Mär 20 19:39 anon