On 22.02.2015 09:42, Guido Günther wrote: > On Sat, Feb 21, 2015 at 04:52:06PM +0100, Heinrich Schuchardt wrote: >> On 21.02.2015 16:22, Guido Günther wrote: >>> On Sat, Feb 21, 2015 at 04:05:59PM +0100, Heinrich Schuchardt wrote: >>>> Package: libvirt-daemon >>>> Version: 1.2.9-9 >>>> Severity: normal >>>> >>>> Dear Maintainer, >>>> >>>> /var/log/kern.log repeatedly shows errors like >>>> >>>> Feb 21 14:38:19 workstation libvirtd[1140]: libvirt version: 1.2.9, >>>> package: 9 (buildd 2015-02-06-16:39:25 binet) >>>> Feb 21 14:38:19 workstation libvirtd[1140]: internal error: unexpected >>>> storage mode for '/home/user/vm' >>> >>> Very likely not a bug but a permission problem on one of your storage >>> pools. >>> Cheers, >>> -- Guido >>> >> >> /etc/libvirt/storage/autostart has the following symlinks: >> default.xml -> /etc/libvirt/storage/default.xml >> Downloads.xml -> /etc/libvirt/storage/Downloads.xml >> tmp.xml -> /etc/libvirt/storage/tmp.xml >> >> The symlinked storage definitions have the following path information >> Downloads.xml:17: <path>/home/user/Downloads</path> >> default.xml:17: <path>/var/lib/libvirt/images</path> >> tmp.xml:17: <path>/tmp</path> > > Well the error is from the storage backend. You should look at the > running daemons configuration not the on disk files (using virsh). > Cheers, > -- Guido > Hello Guido,
as mentioned no guest is running. This is the output of virsh: $ sudo virsh list Id Name State ---------------------------------------------------- When starting the systems the pools are created via the xml files. Hence virsh can only show these pools: $ sudo virsh pool-list Name State Autostart ------------------------------------------- default active yes Downloads active yes tmp active yes So virsh does not show any hint what the problem is. Best regards Heinrich Schuchardt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org