S.Sakamoto wrote: >Hi, > >When I use virt-manager that is connected by xen, >the following error is given at every monitoring. > > libvir: Error : this function is not supported by the hypervisor: > virConnectNumOfNetworks > libvir: Error : this function is not supported by the hypervisor: > virConnectNumOfDefinedNetworks > >Therefore I have a question. > >Will virConnectNumOfNetworks and virConnectNumOfDefinedNetworks be >supported by Xen ? >When is it if supported ? Are you using libvirt from CVS when you see this? It's working for me, but I'll have another look. Perhaps there has been a regression somewhere ...

Hi, Rich Because log is pressed, I want to the breakage is revised if possible... If it will be revised, when is it ?

> > >Will virConnectNumOfNetworks and virConnectNumOfDefinedNetworks be > > >supported by Xen ? > > >When is it if supported ? > > > > Are you using libvirt from CVS when you see this? It's working for me, > > but I'll have another look. Perhaps there has been a regression > > somewhere ... > > Its broken in current CVS until you apply the patch I posted for review > yesterday. > > Dan.

Daniel Veillard wrote: >On Thu, Jul 05, 2007 at 02:21:02PM +0900, S.Sakamoto wrote: >>Hi, Rich >> >> >>Because log is pressed, >>I want to the breakage is revised if possible... >>If it will be revised, when is it ? > >Based on Dan's message: > > https://www.redhat.com/archives/libvir-list/2007-July/msg00012.html > >and the ChangeLog Actually it's not working at the moment unless you specify a qemu:///... URI. For example, with default / Xen URI: # ./mlvirsh net-list libvir: error : this function is not supported by the hypervisor: virConnectNumOfNetworks mlvirsh: libvirt: VIR_ERR_NO_SUPPORT: VIR_FROM_NONE: this function is not supported by the hypervisor: virConnectNumOfNetworks

On Thu, Jul 05, 2007 at 11:41:07AM +0100, Richard W.M. Jones wrote: > Daniel Veillard wrote: > >On Thu, Jul 05, 2007 at 02:21:02PM +0900, S.Sakamoto wrote: > >>Hi, Rich > >> > >> > >>Because log is pressed, > >>I want to the breakage is revised if possible... > >>If it will be revised, when is it ? > > > >Based on Dan's message: > > > > https://www.redhat.com/archives/libvir-list/2007-July/msg00012.html > > > >and the ChangeLog > > Actually it's not working at the moment unless you specify a qemu:///... > URI. For example, with default / Xen URI: > > # ./mlvirsh net-list > libvir: error : this function is not supported by the hypervisor: > virConnectNumOfNetworks > mlvirsh: libvirt: VIR_ERR_NO_SUPPORT: VIR_FROM_NONE: this function is > not supported by the hypervisor: virConnectNumOfNetworks A dumb typo - I had transcribed 'flags' and 'rflags' - its fixed now. The second issue was that the conversion of 'NULL' and 'xen' into a valid 'xen:///' URI was being done in the xen_unified.c driver. It needs to be done in the libvirt.c open function - the network drivers need a valid URI to parse. So I simply moved the 4 lines of code doing that conversion So with current checked in code: [root@celery libvirt]# ./src/virsh --connect xen:/// net-list --all Name State Autostart ----------------------------------------- default active yes [root@celery libvirt]# ./src/virsh --connect xen net-list --all Name State Autostart ----------------------------------------- default active yes [root@celery libvirt]# ./src/virsh net-list --all Name State Autostart ----------------------------------------- default active yes Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|