#778904 libvirtd: internal error: unexpected storage mode for '/home/user/vm'

Package:
libvirt-daemon
Source:
libvirt
Description:
Virtualization daemon
Submitter:
Heinrich Schuchardt
Date:
2015-02-23 18:57:05 UTC
Severity:
normal
#778904#5
Date:
2015-02-21 15:05:59 UTC
From:
To:
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'

No virtual machine was running.

File /home/user/vm does not exist.

Best regards

Heinrich Schuchardt
#778904#10
Date:
2015-02-21 15:22:59 UTC
From:
To:
Very likely not a bug but a permission problem on one of your storage
pools.
Cheers,
 -- Guido
#778904#15
Date:
2015-02-21 15:52:06 UTC
From:
To:
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>

sudo grep -GHrn user/vm /etc
finds no matching line.

So why should libvirt try to open /home/user/vm?

Best regards

Heinrich
#778904#20
Date:
2015-02-22 08:42:52 UTC
From:
To:
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
#778904#25
Date:
2015-02-23 18:49:36 UTC
From:
To:
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
#778904#30
Date:
2015-02-23 18:54:47 UTC
From:
To:
virsh pool-dumpxml just gives the same information that is in the config
files.

No evidence of the path causing the trouble

$ sudo virsh pool-dumpxml default


<pool type='dir'>


  <name>default</name>
  <uuid>c5b82cc9-38da-4fbf-bda5-c7c038e6bee8</uuid>
  <capacity unit='bytes'>98291167232</capacity>
  <allocation unit='bytes'>46136434688</allocation>
  <available unit='bytes'>52154732544</available>
  <source>
  </source>
  <target>
    <path>/var/lib/libvirt/images</path>
    <permissions>
      <mode>0755</mode>
      <owner>-1</owner>
      <group>-1</group>
    </permissions>
  </target>
</pool>

$ sudo virsh pool-dumpxml Downloads
<pool type='dir'>
  <name>Downloads</name>
  <uuid>2538fa03-7d19-426f-9b53-57cfbd032ad1</uuid>
  <capacity unit='bytes'>196722913280</capacity>
  <allocation unit='bytes'>88080920576</allocation>
  <available unit='bytes'>108641992704</available>
  <source>
  </source>
  <target>
    <path>/home/user/Downloads</path>
    <permissions>
      <mode>0755</mode>
      <owner>-1</owner>
      <group>-1</group>
    </permissions>
  </target>
</pool>

$ sudo virsh pool-dumpxml tmp
<pool type='dir'>
  <name>tmp</name>
  <uuid>e6ded047-e6cb-42d7-9532-a9b5c289037e</uuid>
  <capacity unit='bytes'>98291167232</capacity>
  <allocation unit='bytes'>46136434688</allocation>
  <available unit='bytes'>52154732544</available>
  <source>
  </source>
  <target>
    <path>/tmp</path>
    <permissions>
      <mode>0755</mode>
      <owner>-1</owner>
      <group>-1</group>
    </permissions>
  </target>
</pool>