On 1/20/22 17:57, Mohamed Fathy wrote: > I don't know. > from internet im found way im try in my pc > starxmovo@penguin:~$ sudo systemctl start libvirtd > starxmovo@penguin:~$ sudo systemctl status libvirtd > ● libvirtd.service - Virtualization daemon > Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; > vendor preset: enabled) > Drop-In: /run/systemd/system/service.d > └─zzz-lxc-service.conf > Active: active (running) since Thu 2022-01-20 19:51:42 +03; 1min 0s ago > TriggeredBy: ● libvirtd-ro.socket > ● libvirtd.socket > ● libvirtd-admin.socket > Docs: man:libvirtd(8) > https://libvirt.org <https://libvirt.org> > Main PID: 129 (libvirtd) > Tasks: 19 (limit: 32768) > Memory: 47.3M > CGroup: /system.slice/libvirtd.service > └─129 /usr/sbin/libvirtd > > Jan 20 19:51:41 penguin systemd[1]: Starting Virtualization daemon... > Jan 20 19:51:42 penguin systemd[1]: Started Virtualization daemon. > Jan 20 19:51:45 penguin libvirtd[129]: libvirt version: 7.0.0, package: > 3 (Andrea Bolognani <eof@xxxxxxxxxx <mailto:eof@xxxxxxxxxx>>> Alright, this is fairly new. Anyway, the path that's in the error message points to a guest private directory: libvirt.libvirtError: Unable to set XATTR trusted.libvirt.security.dac on /var/lib/libvirt/qemu/domain-2-win2k/master-key.aes: Operation not permitted Therefore, I wonder what filesystem that is, because usually if underlying filesystem doesn't support XATTRs then ENOSUP is returned. Can you please share the output of: stat -f /var/lib/libvirt/qemu Maybe kernel doesn't have XATTRs enabled? I don't know what distro you are using, but based on the line above I assume it's debian. Could you perhaps do the following too then? grep -i xattr /boot/config-* Michal
