Hi all!
I'm trying virt-manager on Debian Wheezy and I noticed that it has
already defined a "default" pool. But if I run:
# /etc/init.d/libvirt-bin restart
I lose the definition of the pools. Actually, there are the definitions
of the pools; but these are not read after restarting libvirt.
ss01:/etc/libvirt/storage# ls -l
total 8
drwxr-xr-x 2 root root 4096 jun 1 09:36 autostart
-rw------- 1 root root 664 jun 1 13:46 default.xml
ss01:/etc/libvirt/storage/autostart# ls -l
total 0
lrwxrwxrwx 1 root root 32 may 24 07:24 default.xml ->
/etc/libvirt/storage/default.xml
After restart libvirt:
virsh # pool-list
Name State Autostart
-----------------------------------------
This is what I see in libvirtd.log:
2013-06-02 01:05:29.709+0000: 19289: info : libvirt version: 0.9.12
2013-06-02 01:05:29.709+0000: 19289: error : virStorageDefParsePerms:613 : XML
error: malformed owner element
2013-06-02 01:05:30.210+0000: 19289: error : virExecWithHook:424 : Cannot find
'pm-is-supported' in path: No existe el fichero o el directorio
2013-06-02 01:05:30.211+0000: 19289: warning : qemuCapsInit:949 : Failed to get
host power management capabilities
2013-06-02 01:05:33.014+0000: 19289: error : virExecWithHook:424 : Cannot find
'pm-is-supported' in path: No existe el fichero o el directorio
2013-06-02 01:05:33.014+0000: 19289: warning : lxcCapsInit:77 : Failed to get
host power management capabilities
2013-06-02 01:05:33.025+0000: 19289: error : virExecWithHook:424 : Cannot find
'pm-is-supported' in path: No existe el fichero o el directorio
2013-06-02 01:05:33.025+0000: 19289: warning : umlCapsInit:87 : Failed to get
host power management capabilities
could this be due to some type of error in the XML file that defines the
pool?
ss01:/etc/libvirt/storage# cat default.xml
<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made
using:
virsh pool-edit default
or other application using the libvirt API.
-->
<pool type='dir'>
<name>default</name>
<uuid>3174232f-3d63-3167-aa25-3949671bf4c2</uuid>
<capacity unit='bytes'>0</capacity>
<allocation unit='bytes'>0</allocation>
<available unit='bytes'>0</available>
<source>
</source>
<target>
<path>/var/lib/libvirt/images</path>
<permissions>
<mode>0700</mode>
<owner>4294967295</owner>
<group>4294967295</group>
</permissions>
</target>
</pool>
These are the versions of the packages I'm using:
libvirt-bin: 0.9.12-11 (Architecture: i386)
virt-manager: 0.9.1-4 (Architecture: all)
Thanks in advance for your reply.
Regards,
Daniel
--
Daniel Bareiro - GNU/Linux registered user #188.598
Proudly running Debian GNU/Linux with uptime:
21:50:39 up 17 days, 8:14, 12 users, load average: 0.00, 0.04, 0.00
On 06/01/2013 08:15 PM, Daniel Bareiro wrote:> Hi all! > > I'm trying virt-manager on Debian Wheezy and I noticed that it has > already defined a "default" pool. But if I run: > > # /etc/init.d/libvirt-bin restart > > I lose the definition of the pools. Actually, there are the definitions > of the pools; but these are not read after restarting libvirt. > > ss01:/etc/libvirt/storage# ls -l > total 8 > drwxr-xr-x 2 root root 4096 jun 1 09:36 autostart > -rw------- 1 root root 664 jun 1 13:46 default.xml > > > ss01:/etc/libvirt/storage/autostart# ls -l > total 0 > lrwxrwxrwx 1 root root 32 may 24 07:24 default.xml -> /etc/libvirt/storage/default.xml > > > After restart libvirt: > > virsh # pool-list > Name State Autostart > ----------------------------------------- > > > This is what I see in libvirtd.log: > > 2013-06-02 01:05:29.709+0000: 19289: info : libvirt version: 0.9.12 > 2013-06-02 01:05:29.709+0000: 19289: error : virStorageDefParsePerms:613 : XML error: malformed owner element"XML error: malformed owner element "> 2013-06-02 01:05:30.210+0000: 19289: error : virExecWithHook:424 : Cannot find 'pm-is-supported' in path: No existe el fichero o el directorio > 2013-06-02 01:05:30.211+0000: 19289: warning : qemuCapsInit:949 : Failed to get host power management capabilities > 2013-06-02 01:05:33.014+0000: 19289: error : virExecWithHook:424 : Cannot find 'pm-is-supported' in path: No existe el fichero o el directorio > 2013-06-02 01:05:33.014+0000: 19289: warning : lxcCapsInit:77 : Failed to get host power management capabilities > 2013-06-02 01:05:33.025+0000: 19289: error : virExecWithHook:424 : Cannot find 'pm-is-supported' in path: No existe el fichero o el directorio > 2013-06-02 01:05:33.025+0000: 19289: warning : umlCapsInit:87 : Failed to get host power management capabilities > > > could this be due to some type of error in the XML file that defines the > pool? > > ss01:/etc/libvirt/storage# cat default.xml > <!-- > WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE > OVERWRITTEN AND LOST. Changes to this xml configuration should be made > using: > virsh pool-edit default > or other application using the libvirt API. > --> > > <pool type='dir'> > <name>default</name> > <uuid>3174232f-3d63-3167-aa25-3949671bf4c2</uuid> > <capacity unit='bytes'>0</capacity> > <allocation unit='bytes'>0</allocation> > <available unit='bytes'>0</available> > <source> > </source> > <target> > <path>/var/lib/libvirt/images</path> > <permissions> > <mode>0700</mode> > <owner>4294967295</owner> > <group>4294967295</group>Owner and group should uid and gid of the images directory.> </permissions> > </target> > </pool> > > > These are the versions of the packages I'm using: > > libvirt-bin: 0.9.12-11 (Architecture: i386) > virt-manager: 0.9.1-4 (Architecture: all) > > > > > Thanks in advance for your reply. > > > Regards, > Daniel > > > _______________________________________________ > libvirt-users mailing list > libvirt-users@redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users
Hi, Colin. On Sunday, 02 June 2013 12:37:12 -0500, Colin Davis wrote:>> This is what I see in libvirtd.log: >> >> 2013-06-02 01:05:29.709+0000: 19289: info : libvirt version: 0.9.12 >> 2013-06-02 01:05:29.709+0000: 19289: error : virStorageDefParsePerms:613 : XML error: malformed owner element> "XML error: malformed owner element ">> 2013-06-02 01:05:30.210+0000: 19289: error : virExecWithHook:424 : Cannot find 'pm-is-supported' in path: No existe el fichero o el directorio >> 2013-06-02 01:05:30.211+0000: 19289: warning : qemuCapsInit:949 : Failed to get host power management capabilities >> 2013-06-02 01:05:33.014+0000: 19289: error : virExecWithHook:424 : Cannot find 'pm-is-supported' in path: No existe el fichero o el directorio >> 2013-06-02 01:05:33.014+0000: 19289: warning : lxcCapsInit:77 : Failed to get host power management capabilities >> 2013-06-02 01:05:33.025+0000: 19289: error : virExecWithHook:424 : Cannot find 'pm-is-supported' in path: No existe el fichero o el directorio >> 2013-06-02 01:05:33.025+0000: 19289: warning : umlCapsInit:87 : Failed to get host power management capabilities >> >> >> could this be due to some type of error in the XML file that defines the >> pool? >> >> ss01:/etc/libvirt/storage# cat default.xml >> <!-- >> WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE >> OVERWRITTEN AND LOST. Changes to this xml configuration should be made >> using: >> virsh pool-edit default >> or other application using the libvirt API. >> --> >> >> <pool type='dir'> >> <name>default</name> >> <uuid>3174232f-3d63-3167-aa25-3949671bf4c2</uuid> >> <capacity unit='bytes'>0</capacity> >> <allocation unit='bytes'>0</allocation> >> <available unit='bytes'>0</available> >> <source> >> </source> >> <target> >> <path>/var/lib/libvirt/images</path> >> <permissions> >> <mode>0700</mode> >> <owner>4294967295</owner> >> <group>4294967295</group>> Owner and group should uid and gid of the images directory.>> </permissions> >> </target> >> </pool>ss01:~# ls -ld /var/lib/libvirt/images drwx--x--x 2 root root 4096 may 27 11:03 /var/lib/libvirt/images So I adapted the permissions to this directory: <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group> </permissions> After restarting libvirt, the pool was recognized: virsh # pool-list Name State Autostart ----------------------------------------- default active yes Then I went back to create another pool: virsh # pool-define-as ISO dir - - - - "/space/isos" Pool ISO defined virsh # pool-start ISO Pool ISO started virsh # pool-autostart ISO Pool ISO marked as autostarted virsh # pool-list --all Name State Autostart ----------------------------------------- default active yes ISO active yes Files are created: ss01:/etc/libvirt/storage# ll total 12 drwxr-xr-x 2 root root 4096 jun 2 15:49 autostart -rw------- 1 root root 646 jun 2 15:05 default.xml -rw------- 1 root root 644 jun 2 15:48 ISO.xml ss01:/etc/libvirt/storage/autostart# ll total 0 lrwxrwxrwx 1 root root 32 may 24 07:24 default.xml -> /etc/libvirt/storage/default.xml lrwxrwxrwx 1 root root 28 jun 2 15:49 ISO.xml -> /etc/libvirt/storage/ISO.xml But it seems that the permissions are equally incorrect: ss01:/etc/libvirt/storage# cat ISO.xml <!-- WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE OVERWRITTEN AND LOST. Changes to this xml configuration should be made using: virsh pool-edit ISO or other application using the libvirt API. --> <pool type='dir'> <name>ISO</name> <uuid>3c7b9f44-c81a-13c7-47cc-f9f317e848a9</uuid> <capacity unit='bytes'>0</capacity> <allocation unit='bytes'>0</allocation> <available unit='bytes'>0</available> <source> </source> <target> <path>/space/isos</path> <permissions> <mode>0700</mode> <owner>4294967295</owner> <group>4294967295</group> </permissions> </target> </pool> This have to do with a bug when using libvirt on a 32-bit operating system? http://www.redhat.com/archives/libvir-list/2012-November/thread.html#01048 Thanks for your reply. Regards, Daniel -- Daniel Bareiro - GNU/Linux registered user #188.598 Proudly running Debian GNU/Linux with uptime: 15:25:28 up 18 days, 1:49, 12 users, load average: 0.34, 0.27, 0.19