Hi, all. When I executing virsh to connect to openvz I get the following: [root@localhost ~]# virsh -c openvz:///system libvir: QEMU error : cannot create bridge 'virbr0' : File exists Failed to autostart network 'default': cannot create bridge 'virbr0' : File existsWelcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # ... But I didn't want to connect to QEMU... Anton
On Fri, Feb 22, 2008 at 01:47:44PM +0300, Anton Protopopov wrote:
When I executing virsh to connect to openvz I get the following: [root@localhost ~]# virsh -c openvz:///system libvir: QEMU error : cannot create bridge 'virbr0' : File exists Failed to autostart network 'default': cannot create bridge 'virbr0' : File existsWelcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # ... But I didn't want to connect to QEMU...
For reasons of history the qemu driver contains the network driver. When libvirt connects to the hypervisor it actually makes two connections -- one (which may be local, not an actual socket) to the hypervisor you requested, and another (usually over a Unix socket) to libvirtd for virNetwork* operations. The network connection is entirely optional[1], which is why you get the error above but your connection succeeds. Rich. [1] Optional unless you want to make virNetwork* calls of course. -- 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
Thanks. 2008/2/22, Richard W.M. Jones <rjones@redhat.com>:
On Fri, Feb 22, 2008 at 01:47:44PM +0300, Anton Protopopov wrote:
When I executing virsh to connect to openvz I get the following: [root@localhost ~]# virsh -c openvz:///system libvir: QEMU error : cannot create bridge 'virbr0' : File exists Failed to autostart network 'default': cannot create bridge 'virbr0' : File existsWelcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # ... But I didn't want to connect to QEMU...
For reasons of history the qemu driver contains the network driver.
When libvirt connects to the hypervisor it actually makes two connections -- one (which may be local, not an actual socket) to the hypervisor you requested, and another (usually over a Unix socket) to libvirtd for virNetwork* operations.
The network connection is entirely optional[1], which is why you get the error above but your connection succeeds.
Rich.
[1] Optional unless you want to make virNetwork* calls of course.
-- 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 Fri, Feb 22, 2008 at 2:13 PM, Richard W.M. Jones wrote:
On Fri, Feb 22, 2008 at 01:47:44PM +0300, Anton Protopopov wrote:
When I executing virsh to connect to openvz I get the following: [root@localhost ~]# virsh -c openvz:///system libvir: QEMU error : cannot create bridge 'virbr0' : File exists Failed to autostart network 'default': cannot create bridge 'virbr0' : File existsWelcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # ... But I didn't want to connect to QEMU...
For reasons of history the qemu driver contains the network driver.
<skip/>
The network connection is entirely optional[1], which is why you get the error above but your connection succeeds. I think it`s reasonable to add some "supress errors" option to %_sysconfdir/sysconfig/libvirtd. At least to supress network errors. I get similar errors.
[solar@nameless ~]$ sudo virsh -c openvz:///system dnsmasq: cannot open or create lease file /var/lib/lib/libvirt/dhcp-default.leases: No such file or directory Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # <offtopic> As i`ve almost sawed enough libvirtd to pack for ALTLinux, should i send you ALT-specific init-script and|or specs? </offtopic> -- ALTLinux Team xmpp: solar AT solar.net.ru
On Fri, Feb 22, 2008 at 07:30:23PM +0300, Mikhail A. Pokidko wrote:
<offtopic> As i`ve almost sawed enough libvirtd to pack for ALTLinux, should i send you ALT-specific init-script and|or specs? </offtopic>
It'd certainly be interesting to see them, but normally we leave it up to the distributors to manage their own specfiles. Generic changes which can be merged with us are very useful though. 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 Fri, Feb 22, 2008 at 06:33:37PM +0000, Richard W.M. Jones wrote:
On Fri, Feb 22, 2008 at 07:30:23PM +0300, Mikhail A. Pokidko wrote:
<offtopic> As i`ve almost sawed enough libvirtd to pack for ALTLinux, should i send you ALT-specific init-script and|or specs? </offtopic>
It'd certainly be interesting to see them, but normally we leave it up to the distributors to manage their own specfiles. Generic changes which can be merged with us are very useful though.
Sending them as attachment to this list could be useful to see if you needed anything special, and as an historical archive, it's really good to see such data archived and indexed on the web, 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/
participants (4)
-
Anton Protopopov -
Daniel Veillard -
Mikhail A. Pokidko -
Richard W.M. Jones