virt-manager failure

[John Lagrue]

TRying to create a guest using virt-manager on Fedora 7. Upon clicking
"Finish" I get this error:

Unable to complete install '<class 'libvirt.libvirtError'>
virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to
bridge 'virbr0' : No such device

Any thoughts?

[Richard W.M. Jones]

John Lagrue wrote:
>  TRying to create a guest using virt-manager on Fedora 7. Upon
> clicking
>  "Finish" I get this error:
>  
>  Unable to complete install '<class 'libvirt.libvirtError'>
>  virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to
>  bridge 'virbr0' : No such device
>  
>  Any thoughts? 
What type of networking did you select?

Is there any further detail in:
   /root/.virt-manager/virt-manager.log
   /var/log/xen/xend.log
   /var/log/xen/xend-debug.log

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

[John Lagrue]

On 04/09/07, Richard W.M. Jones <rjones(a)redhat.com&gt; wrote:
>  John Lagrue wrote:
>  > TRying to create a guest using virt-manager on Fedora 7. Upon clicking
>  > "Finish" I get this error:
>  >
>  > Unable to complete install '<class 'libvirt.libvirtError'>
>  > virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to
>  > bridge 'virbr0' : No such device
>  >
>  > Any thoughts?
>
>  What type of networking did you select?
>
>  Is there any further detail in:
>     /root/.virt-manager/virt-manager.log
>     /var/log/xen/xend.log
>     /var/log/xen/xend-debug.log
>  
I selected Virtual Network, default device. There doesn't seem to be
anything informative in the virt-manager log file, other than the
traceback.

I don't use Xen, so those logs don't exist.

It would seem to me to be saying that the virbr0 device doesn't exist;
how can I check if it does?

JDL

[John Lagrue]

On 04/09/07, John Lagrue <jlagrue(a)gmail.com&gt; wrote:
>  On 04/09/07, Richard W.M. Jones <rjones(a)redhat.com&gt; wrote:
>  > John Lagrue wrote:
>  > > TRying to create a guest using virt-manager on Fedora 7. Upon clicking
>  > > "Finish" I get this error:
>  > >
>  > > Unable to complete install '<class 'libvirt.libvirtError'>
>  > > virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to
>  > > bridge 'virbr0' : No such device
>  > >
>  > > Any thoughts?
>  >
>  > What type of networking did you select?
>  >
>  > Is there any further detail in:
>  >    /root/.virt-manager/virt-manager.log
>  >    /var/log/xen/xend.log
>  >    /var/log/xen/xend-debug.log
>  >
>
>  I selected Virtual Network, default device. There doesn't seem to be
>  anything informative in the virt-manager log file, other than the
>  traceback.
>
>  I don't use Xen, so those logs don't exist.
>
>  It would seem to me to be saying that the virbr0 device doesn't exist;
>  how can I check if it does?
>
>  JDL
>  
It does indeed seem that virbr0 doesn't exist. Is there something that
I haven't installed? I only want qemu-kvm, as Xen isn't a viable
option for me.

JDL

[Daniel P. Berrange]

On Tue, Sep 04, 2007 at 11:07:34PM +0100, John Lagrue wrote:
>  On 04/09/07, John Lagrue <jlagrue(a)gmail.com&gt; wrote:
>  > On 04/09/07, Richard W.M. Jones <rjones(a)redhat.com&gt; wrote:
>  > > John Lagrue wrote:
>  > > > TRying to create a guest using virt-manager on Fedora 7. Upon clicking
>  > > > "Finish" I get this error:
>  > > >
>  > > > Unable to complete install '<class
> 'libvirt.libvirtError'>
>  > > > virDomainCreateLinux() failed Failed to add tap interface 'vnet0'
> to
>  > > > bridge 'virbr0' : No such device
>  > > >
>  > > > Any thoughts?
>  > >
>  > > What type of networking did you select?
>  > >
>  > > Is there any further detail in:
>  > >    /root/.virt-manager/virt-manager.log
>  > >    /var/log/xen/xend.log
>  > >    /var/log/xen/xend-debug.log
>  > >
>  >
>  > I selected Virtual Network, default device. There doesn't seem to be
>  > anything informative in the virt-manager log file, other than the
>  > traceback.
>  >
>  > I don't use Xen, so those logs don't exist.
>  >
>  > It would seem to me to be saying that the virbr0 device doesn't exist;
>  > how can I check if it does?
>  >
>  > JDL
>  >
>  
>  It does indeed seem that virbr0 doesn't exist. Is there something that
>  I haven't installed? I only want qemu-kvm, as Xen isn't a viable
>  option for me. 
virbr0 is (supposed to be) created automatically by libvirt. If it does not
exist there are a couple of things to check

# virsh net-list --all
Name                 State      Autostart 
-----------------------------------------
default              active     yes       

If that shows it active, then try restarting it with

  virsh net-destroy default
  virsh net-start default

If net-list didn't show it, then it may be deleted or not created in the
first place. You can re-create it with

  virsh net-define /usr/share/libvirt/networks/default.xml
  virsh net-autostart default
  virsh net-start default

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  [phone] -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|

[John Lagrue]

On 05/09/07, Daniel P. Berrange <berrange(a)redhat.com&gt; wrote:
>  On Tue, Sep 04, 2007 at 11:07:34PM +0100, John Lagrue wrote:
>  > On 04/09/07, John Lagrue <jlagrue(a)gmail.com&gt; wrote:
>  > > On 04/09/07, Richard W.M. Jones <rjones(a)redhat.com&gt; wrote:
>  > > > John Lagrue wrote:
>  > > > > TRying to create a guest using virt-manager on Fedora 7. Upon
> clicking
>  > > > > "Finish" I get this error:
>  > > > >
>  > > > > Unable to complete install '<class
> 'libvirt.libvirtError'>
>  > > > > virDomainCreateLinux() failed Failed to add tap interface
> 'vnet0' to
>  > > > > bridge 'virbr0' : No such device
>  > > > >
>  > > > > Any thoughts?
>  > > >
>  > > > What type of networking did you select?
>  > > >
>  > > > Is there any further detail in:
>  > > >    /root/.virt-manager/virt-manager.log
>  > > >    /var/log/xen/xend.log
>  > > >    /var/log/xen/xend-debug.log
>  > > >
>  > >
>  > > I selected Virtual Network, default device. There doesn't seem to be
>  > > anything informative in the virt-manager log file, other than the
>  > > traceback.
>  > >
>  > > I don't use Xen, so those logs don't exist.
>  > >
>  > > It would seem to me to be saying that the virbr0 device doesn't exist;
>  > > how can I check if it does?
>  > >
>  > > JDL
>  > >
>  >
>  > It does indeed seem that virbr0 doesn't exist. Is there something that
>  > I haven't installed? I only want qemu-kvm, as Xen isn't a viable
>  > option for me.
>
>  virbr0 is (supposed to be) created automatically by libvirt. If it does not
>  exist there are a couple of things to check
>
>  # virsh net-list --all
>  Name                 State      Autostart
>  -----------------------------------------
>  default              active     yes
>
>  If that shows it active, then try restarting it with
>
>    virsh net-destroy default
>    virsh net-start default
>
>  If net-list didn't show it, then it may be deleted or not created in the
>  first place. You can re-create it with
>
>    virsh net-define /usr/share/libvirt/networks/default.xml
>    virsh net-autostart default
>    virsh net-start default
>  
Unfortunately, all I get is this:

# virsh net-list --all
error: failed to connect to the hypervisor
error: no valid connection

[Sven Oehme]

try  virsh -c qemu:///system instead of just virsh .. 

sven









"John Lagrue" <jlagrue(a)gmail.com&gt; 
Sent by: fedora-xen-bounces(a)redhat.com
09/05/2007 10:15 AM

To
"Daniel P. Berrange" <berrange(a)redhat.com&gt;
cc
fedora-xen(a)redhat.com
Subject
Re: [Fedora-xen] virt-manager failure






On 05/09/07, Daniel P. Berrange <berrange(a)redhat.com&gt; wrote:
>  On Tue, Sep 04, 2007 at 11:07:34PM +0100, John Lagrue wrote:
>  > On 04/09/07, John Lagrue <jlagrue(a)gmail.com&gt; wrote:
>  > > On 04/09/07, Richard W.M. Jones <rjones(a)redhat.com&gt; wrote:
>  > > > John Lagrue wrote:
>  > > > > TRying to create a guest using virt-manager on Fedora 7. Upon 
clicking
>  > > > > "Finish" I get this error:
>  > > > >
>  > > > > Unable to complete install '<class
> 'libvirt.libvirtError'>
>  > > > > virDomainCreateLinux() failed Failed to add tap interface 
'vnet0' to
>  > > > > bridge 'virbr0' : No such device
>  > > > >
>  > > > > Any thoughts?
>  > > >
>  > > > What type of networking did you select?
>  > > >
>  > > > Is there any further detail in:
>  > > >    /root/.virt-manager/virt-manager.log
>  > > >    /var/log/xen/xend.log
>  > > >    /var/log/xen/xend-debug.log
>  > > >
>  > >
>  > > I selected Virtual Network, default device. There doesn't seem to be
>  > > anything informative in the virt-manager log file, other than the
>  > > traceback.
>  > >
>  > > I don't use Xen, so those logs don't exist.
>  > >
>  > > It would seem to me to be saying that the virbr0 device doesn't 
exist;
>  > > how can I check if it does?
>  > >
>  > > JDL
>  > >
>  >
>  > It does indeed seem that virbr0 doesn't exist. Is there something that
>  > I haven't installed? I only want qemu-kvm, as Xen isn't a viable
>  > option for me.
>
>  virbr0 is (supposed to be) created automatically by libvirt. If it does  
not
>  exist there are a couple of things to check
>
>  # virsh net-list --all
>  Name                 State      Autostart
>  -----------------------------------------
>  default              active     yes
>
>  If that shows it active, then try restarting it with
>
>    virsh net-destroy default
>    virsh net-start default
>
>  If net-list didn't show it, then it may be deleted or not created in the
>  first place. You can re-create it with
>
>    virsh net-define /usr/share/libvirt/networks/default.xml
>    virsh net-autostart default
>    virsh net-start default
>  
Unfortunately, all I get is this:

# virsh net-list --all
error: failed to connect to the hypervisor
error: no valid connection

--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen

[John Lagrue]

On 05/09/07, Sven Oehme <oehmes(a)de.ibm.com&gt; wrote:
>  try  virsh -c qemu:///system instead of just virsh ..
>   sven 

Thanks for that Sven.

Now I get this:

# virsh -c qemu:///system net-list --all
Name                 State      Autostart
-----------------------------------------
default              active     yes

[Richard W.M. Jones]

Does the bridge actually exist?  eg:

$ /usr/sbin/brctl show
bridge name     bridge id               STP enabled     interfaces
virbr0          8000.000000000000       no

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

[Bryan Kearney]

I have noticed that the xen-libs drips the vibr0. If you are using kvm.. it
is basically busted. I had to create my own bridge and use that explicitly.

On 9/5/07, Richard W.M. Jones <rjones(a)redhat.com&gt; wrote:
>  Does the bridge actually exist?  eg:
>
>  $ /usr/sbin/brctl show
>  bridge name     bridge id               STP enabled     interfaces
>  virbr0          8000.000000000000       no
>
>  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
>
>  --
>  Fedora-xen mailing list
>  Fedora-xen(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>

[Daniel P. Berrange]

On Wed, Sep 05, 2007 at 06:45:51AM -0400, Bryan Kearney wrote:
>  I have noticed that the xen-libs drips the vibr0. 
Urm, huh ? What are you trying to say here ?

>                                                    If you are using
> kvm.. it
>  is basically busted. I had to create my own bridge and use that explicitly. 
This is the desired behaviour - the only reason why Xen provides a xenbr0
is historical baggage. Creating a bridge device out of the box simply does
not work if you are using Wifi, or if your network is not online at boot,
or if you use network manager to switch between devices on the fly, or if 
you are booting off iSCSI or NFS root.

Xen has some hacky heuristics which sort of work if you are lucky enough  to
be booting local disk with a permanent hard wired ethernet device, but these
break horribly just as often as they work. Our intent is to remove the automatic
Xen provided bridge. It is simple to manaully configure a bridge containing
eth0 using the config files in /etc/sysconfig/network-scripts. In addiiton 
libvirt provides virbr0 which is an isolated network device connected to the
outside world using forwarding+NAT.

The two different network config scenarios are described at

http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_lib...

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  [phone] -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|