** Description changed:
I use virt-manager with Ubuntu 25.04 VM. Sometimes I did external snapshots.
After upgrading VM to Ubuntu 25.10 I also saved snapshot. I can start any
snapshot except last one. When I start last one (with 25.10) I have this log.
Looks like this is apparmor false positive.
```
Error running snapshot 'init_25.10': internal error: process exited while
connecting to monitor: 2026-01-13T09:09:26.823084Z qemu-system-x86_64:
-blockdev
{"driver":"file","filename":"/home/a/mystorage/libvirt_pool/ubuntu.1757917759","node-name":"libvirt-4-storage","auto-read-only":true,"discard":"unmap"}:
Could not open '/home/a/mystorage/libvirt_pool/ubuntu.1757917759': Permission
denied
Traceback (most recent call last):
- File "/usr/share/virt-manager/virtManager/asyncjob.py", line 67, in
cb_wrapper
- callback(asyncjob, *args, **kwargs)
- ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
- File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, 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 1219, in
revert_to_snapshot
- self._backend.revertToSnapshot(snap.get_backend())
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
- File "/usr/lib/python3/dist-packages/libvirt.py", line 2456, in
revertToSnapshot
- raise libvirtError('virDomainRevertToSnapshot() failed')
+ File "/usr/share/virt-manager/virtManager/asyncjob.py", line 67, in
cb_wrapper
+ callback(asyncjob, *args, **kwargs)
+ ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
+ File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, 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 1219, in
revert_to_snapshot
+ self._backend.revertToSnapshot(snap.get_backend())
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
+ File "/usr/lib/python3/dist-packages/libvirt.py", line 2456, in
revertToSnapshot
+ raise libvirtError('virDomainRevertToSnapshot() failed')
libvirt.libvirtError: internal error: process exited while connecting to
monitor: 2026-01-13T09:09:26.823084Z qemu-system-x86_64: -blockdev
{"driver":"file","filename":"/home/a/mystorage/libvirt_pool/ubuntu.1757917759","node-name":"libvirt-4-storage","auto-read-only":true,"discard":"unmap"}:
Could not open '/home/a/mystorage/libvirt_pool/ubuntu.1757917759': Permission
denied
```
+ I think to cause such bug user should work in one snapshot and then switch to
another one without PowerOff VM.
To fix such problem I can use hack
```
sudo sh -c 'cat <<EOF >> "/etc/apparmor.d/abstractions/libvirt-qemu"
- # fix from
https://unix.stackexchange.com/questions/719408/failed-starting-vm-with-libvirt-qemu-permission-denied
- /home/$SUDO_USER/mystorage/libvirt_pool/ubuntu.1757917759 rwk,
+ # fix from
https://unix.stackexchange.com/questions/719408/failed-starting-vm-with-libvirt-qemu-permission-denied
+ /home/$SUDO_USER/mystorage/libvirt_pool/ubuntu.1757917759 rwk,
EOF'
```
Is it a bug? Error in default apparmor profile?
Bug was detected here:
https://unix.stackexchange.com/questions/719408/failed-starting-vm-with-libvirt-qemu-permission-denied
https://askubuntu.com/questions/1562823/libvirt-manager-could-not-open-permission-denied/1562844#1562844
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: apparmor 5.0.0~alpha1-0ubuntu8.3
ProcVersionSignature: Ubuntu 6.17.0-8.8-generic 6.17.2
Uname: Linux 6.17.0-8-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 14 12:46:57 2026
InstallationDate: Installed on 2024-08-19 (513 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
- LANG=en_US.UTF-8
- PATH=(custom, no user)
- SHELL=/bin/bash
- TERM=xterm-256color
- XDG_RUNTIME_DIR=<set>
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ TERM=xterm-256color
+ XDG_RUNTIME_DIR=<set>
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.17.0-8-generic
root=UUID=653a2212-f324-4b5f-bd9f-01f590dcf876 ro
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: apparmor
UpgradeStatus: Upgraded to questing on 2025-11-19 (56 days ago)
** Description changed:
I use virt-manager with Ubuntu 25.04 VM. Sometimes I did external snapshots.
After upgrading VM to Ubuntu 25.10 I also saved snapshot. I can start any
snapshot except last one. When I start last one (with 25.10) I have this log.
Looks like this is apparmor false positive.
```
Error running snapshot 'init_25.10': internal error: process exited while
connecting to monitor: 2026-01-13T09:09:26.823084Z qemu-system-x86_64:
-blockdev
{"driver":"file","filename":"/home/a/mystorage/libvirt_pool/ubuntu.1757917759","node-name":"libvirt-4-storage","auto-read-only":true,"discard":"unmap"}:
Could not open '/home/a/mystorage/libvirt_pool/ubuntu.1757917759': Permission
denied
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 67, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, 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 1219, in
revert_to_snapshot
self._backend.revertToSnapshot(snap.get_backend())
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/libvirt.py", line 2456, in
revertToSnapshot
raise libvirtError('virDomainRevertToSnapshot() failed')
libvirt.libvirtError: internal error: process exited while connecting to
monitor: 2026-01-13T09:09:26.823084Z qemu-system-x86_64: -blockdev
{"driver":"file","filename":"/home/a/mystorage/libvirt_pool/ubuntu.1757917759","node-name":"libvirt-4-storage","auto-read-only":true,"discard":"unmap"}:
Could not open '/home/a/mystorage/libvirt_pool/ubuntu.1757917759': Permission
denied
```
- I think to cause such bug user should work in one snapshot and then switch to
another one without PowerOff VM.
+ I think to cause such bug user should work in one snapshot and then switch to
another one without PowerOff VM. To do it in virt-manager I just double click
to another snapshot.
To fix such problem I can use hack
```
sudo sh -c 'cat <<EOF >> "/etc/apparmor.d/abstractions/libvirt-qemu"
# fix from
https://unix.stackexchange.com/questions/719408/failed-starting-vm-with-libvirt-qemu-permission-denied
/home/$SUDO_USER/mystorage/libvirt_pool/ubuntu.1757917759 rwk,
EOF'
```
Is it a bug? Error in default apparmor profile?
Bug was detected here:
https://unix.stackexchange.com/questions/719408/failed-starting-vm-with-libvirt-qemu-permission-denied
https://askubuntu.com/questions/1562823/libvirt-manager-could-not-open-permission-denied/1562844#1562844
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: apparmor 5.0.0~alpha1-0ubuntu8.3
ProcVersionSignature: Ubuntu 6.17.0-8.8-generic 6.17.2
Uname: Linux 6.17.0-8-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 14 12:46:57 2026
InstallationDate: Installed on 2024-08-19 (513 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.17.0-8-generic
root=UUID=653a2212-f324-4b5f-bd9f-01f590dcf876 ro
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: apparmor
UpgradeStatus: Upgraded to questing on 2025-11-19 (56 days ago)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2138353
Title:
virt-manager external snapshot become unavailable after time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2138353/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
