On Mon, Dec 24, 2012 at 02:18:48PM +0100, Joop wrote:
Dan Kenigsberg wrote:
>Which version of libvirt is installed on your host?
>
libvirt-1.0.1-2.fc17.x86_64
libvirt-client-1.0.1-2.fc17.x86_64
libvirt-daemon-1.0.1-2.fc17.x86_64
libvirt-daemon-config-network-1.0.1-2.fc17.x86_64
libvirt-daemon-config-nwfilter-1.0.1-2.fc17.x86_64
libvirt-daemon-driver-interface-1.0.1-2.fc17.x86_64
libvirt-daemon-driver-lxc-1.0.1-2.fc17.x86_64
libvirt-daemon-driver-network-1.0.1-2.fc17.x86_64
libvirt-daemon-driver-nodedev-1.0.1-2.fc17.x86_64
libvirt-daemon-driver-nwfilter-1.0.1-2.fc17.x86_64
libvirt-daemon-driver-qemu-1.0.1-2.fc17.x86_64
libvirt-daemon-driver-secret-1.0.1-2.fc17.x86_64
libvirt-daemon-driver-storage-1.0.1-2.fc17.x86_64
libvirt-daemon-driver-uml-1.0.1-2.fc17.x86_64
libvirt-daemon-driver-xen-1.0.1-2.fc17.x86_64
libvirt-lock-sanlock-1.0.1-2.fc17.x86_64
libvirt-python-1.0.1-2.fc17.x86_64
From virt-preview repo
[fedora-virt-preview]
name=Virtualization packages from Rawhide built for latest Fedora
baseurl=http://fedorapeople.org/groups/virt/virt-preview/fedora-$releasev...
enabled=1
skip_if_unavailable=1
gpgcheck=0
>What is the output of the following python script on your machine? Mine
>says "1". Could it be that your libvirt says "0"?
>
>=============
>
>from vdsm import libvirtconnection
>
>conn = libvirtconnection.get()
>netXml = """<network>
> <name>test</name>
> <forward mode='passthrough'>
> <interface dev='em1'/>
> </forward>
></network>
>"""
>
>net = conn.networkDefineXML(netXml)
>net.create()
>print net.isPersistent()
>net.destroy()
>net.undefine()
>
>
0
libvir: Network Driver error : Network not found: no network with
matching uuid
Traceback (most recent call last):
File "test.py", line 16, in <module>
net.undefine()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2154, in
undefine
if ret == -1: raise libvirtError ('virNetworkUndefine() failed',
net=self)
libvirt.libvirtError: Network not found: no network with matching uuid
So '0' :-((
Suppose that error isn't good either.
Should I downgrade to an earlier version of libvirt?
Please try. My guess is that this is a libvirt bug added by
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=0211fd6e04cdc402da20...
in libvirt 1.0.1. More authoritative answer is expected by those added
to the CC line.