Ho, Eric.
On Tuesday, 04 June 2013 09:40:45 -0600,
Eric Blake wrote:
>>> This is what I see in libvirtd.log:
>>>
>>> 2013-06-02 01:05:29.709+0000: 19289: info : libvirt version: 0.9.12
Relatively old...
> 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
and since that thread discusses a fix that wasn't until commit
37a1012
(0.10.0), you are correct that your version of libvirtd has a bug, and
that upgrading would fix things for you.
Taking advantage of the new feature "multiarch" of Debian, I've migrated
the VMHost to amd64 architecture and after that, I did not have this
problem.
Still, I see the <owner> </owner> and <group> </group> in the
configuration file created after creating a pool once migrated to
libvirt-bin amd64, have values that do not seem to correspond with UID
and GID. This is normal?
<pool type='logical'>
<name>LVM</name>
<uuid>6f24dd66-565d-53fa-9b21-41f6b69de757</uuid>
<capacity unit='bytes'>979185434624</capacity>
<allocation unit='bytes'>431644213248</allocation>
<available unit='bytes'>547541221376</available>
<source>
<device path='/dev/md2'/>
<name>vms</name>
<format type='lvm2'/>
</source>
<target>
<path>/dev/vms</path>
<permissions>
<mode>0700</mode>
<owner>4294967295</owner>
<group>4294967295</group>
</permissions>
</target>
</pool>
Thanks for your reply.
Regards,
Daniel
--
Ing. Daniel Bareiro - GNU/Linux registered user #188.598
Proudly running Debian GNU/Linux with uptime:
16:43:32 up 25 days, 3:07, 12 users, load average: 0.00, 0.00, 0.00