Hi I'm trying to implement virConnectListInterfaces for the ESX driver (actually the esx_interface driver) but the python generator does not write the code for this function

in generator.py this function is in a special table called: skip_impl and there is a comment saying: # Class methods which are written by hand in libvir.c but the Python-level # code is still automatically generated (so they are not in skip_function()) I'm not sure what does it mean

should I implement in libvir.c?

and I'm done?

OK, Thanks How about listing interfaces for a VM(virDomainListInterfaces ) will you accept such an API?

understood so, is that a bug? virsh # list Id Name State ---------------------------------- 16 rh53 running 256 smallLinux running 336 diskless linux running virsh # dominfo 16 Id: 16 Name: rh53 UUID: 564dea41-bf37-44d6-2c9e-c6009be71aa6 OS Type: hvm State: running CPU(s): 1 Max memory: 393216 kB Used memory: 393216 kB virsh # virsh # dumpxml 16 error: internal error Datastore URL '' has unexpected prefix, expecting '/vmfs/volumes/' prefix

Ah, the not responding NFS datastores may have an empty URL. I'll make the code more robust in this situation by changing the error to a warning. Because I iterate over all datastore of the server to find a matching one, and if a datastore with a problem comes first in the list it'll hinder the driver to find a possible matching one. Had this kind of problem before with virtual machines where a broken virtual machine caused the problem. I'll review the rest of the code for this kind of problem, because I suspect there will be more functions with this problem. Matthias 2009/9/16 Shahar Klein <shaharklein(a)yahoo.com&gt;: > It's my ESX4i testing server > with 3 datastores > one local and 2 over NFS mounts that are not responding > Plus this ESX4i server is quite messed up with cloning tests > I made before discovering the OVA-templates > I'll clean and try again and will make a mental note > to test NFS datastore diconnections > Thanks > Shahar > ________________________________ > From: Matthias Bolte <matthias.bolte(a)googlemail.com&gt; > To: Shahar Klein <shaharklein(a)yahoo.com&gt; > Cc: Daniel P. Berrange <berrange(a)redhat.com>; veillard(a)redhat.com; > libvir-list(a)redhat.com > Sent: Tuesday, September 15, 2009 7:56:43 PM > Subject: Re: [libvirt] Python binding to virConnectListInterfaces > > 2009/9/15 Shahar Klein <shaharklein(a)yahoo.com&gt;: >> understood >> so, is that a bug? >> virsh # list >>  Id Name                 State >> ---------------------------------- >>  16 rh53                 running >> 256 smallLinux           running >> 336 diskless linux       running >> virsh # dominfo 16 >> Id:             16 >> Name:           rh53 >> UUID:           564dea41-bf37-44d6-2c9e-c6009be71aa6 >> OS Type:        hvm >> State:          running >> CPU(s):         1 >> Max memory:     393216 kB >> Used memory:    393216 kB >> virsh # >> virsh # dumpxml 16 >> error: internal error Datastore URL '' has unexpected prefix, expecting >> '/vmfs/volumes/' prefix >> > > This message indicates that your ESX server has a datastore with URL > set to an empty string. This is unexpected. > > Goto https://<your-esx-server>/mob then goto content -> rootFolder -> > childEntity -> datastore. For each datastore element check the > info.url property, if one of them is an empty string or unset then > this is the cause for this error message. > > If this is really the case for you, the question is: Is an empty URL > valid, or is this a configuration issue with you ESX server? > > Matthias > >