After compiling libvirt, my existing VMs are not getting listed when i execute virsh list --all. Once I go back to the older version i can see those VMs.
These are VMs provisioned using openstack. So they are in the location /var/lib/nova/instances. Is it that only newly created VMs will be recognized by libvirt?
Is it possible to view already created Vms?

Regards
Ananth

On Mon, Jul 9, 2012 at 7:50 PM, Osier Yang <jyang@redhat.com> wrote:
On 2012年07月09日 18:04, Ananth wrote:
Hi,
Thanks for the inputs. I was able to resolve all dependencies and
compile libvirt-0.9.8 successfully. I am able to see the newly built
virsh tool inside /opt/libvirt/bin/virsh. But I am unable to start the
newly compiled service. My service is available in
/opt/libvirt/bin/libvirtd since i compiled with option ./configre
--with-netcf --prefix=/opt/libvirt.

I already had libvirt-0.9.4 installed in the system. So I stopped the
libvirtd service and started the service from
/opt/libvirt/sbin/libvirtd. I can see the below error message.

[root@CENTOS-BAY3 sbin]# ./libvirtd start
2012-07-09 09:48:12.576+0000: 12149: info : libvirt version: 0.9.8
2012-07-09 09:48:12.576+0000: 12149: error :
networkCheckRouteCollision:1655 : internal error Network is already in
use by interface virbr0

It should be caused by the default network is not destroyed.
And the bridge virbr0 is still working. (It's the right way
from my p.o,v, as you won't want to break the network of the
running guests even libvirtd is stopped). You can destroy the
default network before stopping libvirtd:

# virsh net-destroy default

Regards,
Osier



--
Regards
Ananth