On 06/09/2013 09:58 PM, Daniel Bareiro wrote:
> Ho, Eric.
>
>
> Still, I see the and 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?
>
These values are -1 printed a
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+: 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?
On 06/02/2013 01:25 PM, Daniel Bareiro wrote:
> 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+: 19289: info : libvirt version: 0.9.12
Relatively old...
> This have to do with a bug when u
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+: 19289: info : libvirt version: 0.9.12
>> 2013-06-02 01:05:29.709+: 19289: error : virStorageDefParsePerms:613 :
>> XML error: malformed owner eleme
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 t
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.
ss
