[Libvir] [Q]Will virConnectNumOfNetworks and virConnectNumOfDefinedNetworks be supported by Xen ?
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 ? Thanks, Shigeki Sakamoto.
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 ... Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
On Thu, Jun 28, 2007 at 10:21:17AM +0100, Richard W.M. Jones wrote:
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 ...
Its broken in current CVS until you apply the patch I posted for review yesterday. 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 -=|
Hi, Rich Because log is pressed, I want to the breakage is revised if possible... If it will be revised, when is it ? Thanks, Shigeki Sakamoto.
On Thu, Jun 28, 2007 at 10:21:17AM +0100, Richard W.M. Jones wrote:
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 ...
Its broken in current CVS until you apply the patch I posted for review yesterday.
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 -=|
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 Mon Jul 2 09:35:00 EST 2007 Daniel P. Berrange <berrange@redhat.com> * src/qemu_driver.c: Change 'qemu' to 'QEMU' to get compatability with previous releases reporting of driver type. Allow QEMU to handle qemu:///session for root users too. Fix network lookup functions to use networkPrivateData instead of privateData * src/remote_internal.c: Add auto-spawn of daemons for networking. Make network activate for Xen / Test drivers. Make the network functions use networkPrivateData instead of privateData I would expect the fix to be in CVS since Monday,
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 -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
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 with qemu URI: # ./mlvirsh -c qemu:///system net-list default This is one for Dan to comment on. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
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 -=|
Daniel P. Berrange wrote:
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
Confirmed here also. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Hi, Dan Thank you for revising it !! An error every monitoring is not given in virt-manager. Thanks, Shigeki Sakamoto.
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 -=|
participants (4)
-
Daniel P. Berrange -
Daniel Veillard -
Richard W.M. Jones -
S.Sakamoto