incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wido den Hollander <w...@widodh.nl>
Subject Re: source pool conflict
Date Thu, 30 Aug 2012 11:49:44 GMT
On 08/30/2012 06:08 AM, Pranav Saxena wrote:
> Hi ,
>
> When  you create ( an account)  your first user VM , a router VM comes up too which is
named like r-4-VM. That is why you see two VM's listed when you run virsh list command  on
the hypervisor.  Regarding the libvirt error , it seems the libvert version 0.9.12 storage
driver  doesn't support duplicate underlying storage.
> I am not sure if it is supported for the later versions . You'll have to check that out
(http://libvirt.org/news.html )
>

The newer versions of libvirt indeed do not allow duplicate storage 
pools pointing to the same server / directory / mountpoint.

I think this is caused by the Secondary Storage pool which is not 
cleanly removed.

I haven't seen this behavior with the current master and libvirt 0.10.0. 
I think (can't remember) I fixed something regarding this, but I'm not 
sure though.

Wido

> https://bugzilla.redhat.com/show_bug.cgi?id=611823 .
>
> Regards,
> Pranav
>
>
>
> -----Original Message-----
> From: Gautam Sampathkumar [mailto:gsampathkumar@gmail.com]
> Sent: Thursday, August 30, 2012 3:48 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: source pool conflict
>
> Hi Everyone,
>               I'm running into a libvirt error on trying to instantiate a second user
VM. The first VM gets instantiated successfully, although for some reason I see 2 VMs started
up when I run 'virsh list' on the hypervisor, one with the name r-4-VM and the other with
the name 1-2-3-VM.
>
> Configuration:
> Running Cloudstack 3.0.2 release versions on both my hypervisor (centos
> 6.3) and my management server (ubuntu 10.04).
> libvirt 0.9.12
> libvirt-java 0.4.8
>
> The error I see in the libvirt logs :
>   error : virStoragePoolSourceFindDuplicate:1748 : operation failed: Storage source conflict
with pool: '85b9025f-b559-47e1-b02c-17aea4b95822'
>
>
> Any guidance would be appreciated.
>
> --Gautam
>


Mime
View raw message