Can't use network in guests

[Gianluca Sforna]

Hi all,
it seems that after I installed Fedora 11 I can't assign to guests any
ethernet device; in particular, the virt-manager VM creation wizard do
not let me choose any network device, and if I try to assign it later
via the "Add new hardware" button I get a traceback:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/addhardware.py", line 288,
in forward
    if(self.validate(notebook.get_current_page()) != True):
  File "/usr/share/virt-manager/virtManager/addhardware.py", line 882,
in validate
    net = self.get_config_network()
  File "/usr/share/virt-manager/virtManager/addhardware.py", line 407,
in get_config_network
    return ["network", model.get_value(net.get_active_iter(), 0)]
TypeError: iter must be a GtkTreeIter

any idea?

[Mark McLoughlin]

On Tue, 2009-07-28 at 12:24 +0200, Gianluca Sforna wrote:
> Hi all,
> it seems that after I installed Fedora 11 I can't assign to guests any
> ethernet device; in particular, the virt-manager VM creation wizard do
> not let me choose any network device, and if I try to assign it later
> via the "Add new hardware" button I get a traceback:
>
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/addhardware.py", line 288,
> in forward
>     if(self.validate(notebook.get_current_page()) != True):
>   File "/usr/share/virt-manager/virtManager/addhardware.py", line 882,
> in validate
>     net = self.get_config_network()
>   File "/usr/share/virt-manager/virtManager/addhardware.py", line 407,
> in get_config_network
>     return ["network", model.get_value(net.get_active_iter(), 0)]
> TypeError: iter must be a GtkTreeIter

That certainly looks like a virt-manager bug, please do file it in
bugzilla.

Can you use 'virsh edit' to add e.g.:

<interface type='bridge'>
      <mac address='54:52:00:49:73:9a'/>
      <source bridge='br0'/>
    </interface>

See also:

http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging
  https://fedoraproject.org/wiki/Reporting_virtualization_bugs#Networking

Cheers,
Mark.

[Gianluca Sforna]

On Tue, Jul 28, 2009 at 12:29 PM, Mark McLoughlin wrote:
> Can you use 'virsh edit' to add e.g.:
>
> <interface type='bridge'>
>      <mac address='54:52:00:49:73:9a'/>
>      <source bridge='br0'/>
>    </interface>

This leads to another traceback when starting the VM:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 493, in run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 573, in startup
    self.vm.create()
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 287, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error Failed to add tap interface 'vnet%d' to
bridge 'br0' : No such device
> See also:
>
> http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging
>  https://fedoraproject.org/wiki/Reporting_virtualization_bugs#Networking

Thanks for the pointers, I found this suspicious message in virt-manager.log:

[Tue, 28 Jul 2009 12:54:16 virt-manager 3653] ERROR (proxies:400)
Introspect error on
:1.1:/org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7:
dbus.exceptions.DBusException: No device with id
/org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7
[Tue, 28 Jul 2009 12:54:16 virt-manager 3653] DEBUG (proxies:403)
Executing introspect queue due to error
[Tue, 28 Jul 2009 12:54:16 virt-manager 3653] ERROR (connection:218)
Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line
214, in maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/connection.py", line 170,
in _net_phys_device_added
    if objif.QueryCapability("net"):
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line
630, in call_blocking
    message, timeout)
DBusException: org.freedesktop.Hal.NoSuchDevice: No device with id
/org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7

still confused...

[Mark McLoughlin]

On Tue, 2009-07-28 at 12:58 +0200, Gianluca Sforna wrote:
> On Tue, Jul 28, 2009 at 12:29 PM, Mark McLoughlin wrote:
> > Can you use 'virsh edit' to add e.g.:
> >
> >    <interface type='bridge'>
> >      <mac address='54:52:00:49:73:9a'/>
> >      <source bridge='br0'/>
> >    </interface>
>
> This leads to another traceback when starting the VM:

Did you file a bug with the first traceback?
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/engine.py", line 493, in run_domain
>     vm.startup()
>   File "/usr/share/virt-manager/virtManager/domain.py", line 573, in startup
>     self.vm.create()
>   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 287, in create
>     if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: internal error Failed to add tap interface 'vnet%d' to
> bridge 'br0' : No such device

What exactly is the guest's configuration? Is 'vnet%d' mentioned
anywhere? What version of libvirt?
> > See also:
> >
> > http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging
> >  https://fedoraproject.org/wiki/Reporting_virtualization_bugs#Networking
>
> Thanks for the pointers, I found this suspicious message in virt-manager.log:
>
> [Tue, 28 Jul 2009 12:54:16 virt-manager 3653] ERROR (proxies:400)
> Introspect error on
> :1.1:/org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7:
> dbus.exceptions.DBusException: No device with id
> /org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7
> [Tue, 28 Jul 2009 12:54:16 virt-manager 3653] DEBUG (proxies:403)
> Executing introspect queue due to error
> [Tue, 28 Jul 2009 12:54:16 virt-manager 3653] ERROR (connection:218)
> Exception in handler for D-Bus signal:
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/dbus/connection.py", line
> 214, in maybe_handle_message
>     self._handler(*args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/connection.py", line 170,
> in _net_phys_device_added
>     if objif.QueryCapability("net"):
>   File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
>     return self._proxy_method(*args, **keywords)
>   File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
>     **keywords)
>   File "/usr/lib/python2.6/site-packages/dbus/connection.py", line
> 630, in call_blocking
>     message, timeout)
> DBusException: org.freedesktop.Hal.NoSuchDevice: No device with id
> /org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7
>
> still confused...

Odd, dbus telling us a device has added and then failing to find it.
Seen this one before Cole?

Cheers,
Mark.

[Cole Robinson]

Mark McLoughlin wrote:
> On Tue, 2009-07-28 at 12:58 +0200, Gianluca Sforna wrote:
> > On Tue, Jul 28, 2009 at 12:29 PM, Mark McLoughlin wrote:
> > > Can you use 'virsh edit' to add e.g.:
> > >
> > >    <interface type='bridge'>
> > >      <mac address='54:52:00:49:73:9a'/>
> > >      <source bridge='br0'/>
> > >    </interface>
> >
> > This leads to another traceback when starting the VM:
>
> Did you file a bug with the first traceback?
> > Traceback (most recent call last):
> >   File "/usr/share/virt-manager/virtManager/engine.py", line 493, in run_domain
> >     vm.startup()
> >   File "/usr/share/virt-manager/virtManager/domain.py", line 573, in startup
> >     self.vm.create()
> >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 287, in create
> >     if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> > libvirtError: internal error Failed to add tap interface 'vnet%d' to
> > bridge 'br0' : No such device
>
> What exactly is the guest's configuration? Is 'vnet%d' mentioned
> anywhere? What version of libvirt?
> > > See also:
> > >
> > > http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging
> > >  https://fedoraproject.org/wiki/Reporting_virtualization_bugs#Networking
> >
> > Thanks for the pointers, I found this suspicious message in virt-manager.log:
> >
> > [Tue, 28 Jul 2009 12:54:16 virt-manager 3653] ERROR (proxies:400)
> > Introspect error on
> > :1.1:/org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7:
> > dbus.exceptions.DBusException: No device with id
> > /org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7
> > [Tue, 28 Jul 2009 12:54:16 virt-manager 3653] DEBUG (proxies:403)
> > Executing introspect queue due to error
> > [Tue, 28 Jul 2009 12:54:16 virt-manager 3653] ERROR (connection:218)
> > Exception in handler for D-Bus signal:
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.6/site-packages/dbus/connection.py", line
> > 214, in maybe_handle_message
> >     self._handler(*args, **kwargs)
> >   File "/usr/share/virt-manager/virtManager/connection.py", line 170,
> > in _net_phys_device_added
> >     if objif.QueryCapability("net"):
> >   File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
> >     return self._proxy_method(*args, **keywords)
> >   File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
> >     **keywords)
> >   File "/usr/lib/python2.6/site-packages/dbus/connection.py", line
> > 630, in call_blocking
> >     message, timeout)
> > DBusException: org.freedesktop.Hal.NoSuchDevice: No device with id
> > /org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7
> >
> > still confused...
>
> Odd, dbus telling us a device has added and then failing to find it.
> Seen this one before Cole?

I don't think so. Filing a bug with both those tracebacks would be best.

Thanks,
Cole

[Gianluca Sforna]

On Tue, Jul 28, 2009 at 1:20 PM, Mark McLoughlin wrote:
> On Tue, 2009-07-28 at 12:58 +0200, Gianluca Sforna wrote:
> > On Tue, Jul 28, 2009 at 12:29 PM, Mark McLoughlin wrote:
> > > Can you use 'virsh edit' to add e.g.:
> > >
> > >    <interface type='bridge'>
> > >      <mac address='54:52:00:49:73:9a'/>
> > >      <source bridge='br0'/>
> > >    </interface>
> >
> > This leads to another traceback when starting the VM:
>
> Did you file a bug with the first traceback?

I just did it:
https://bugzilla.redhat.com/show_bug.cgi?id=514228
> > Traceback (most recent call last):
> >   File "/usr/share/virt-manager/virtManager/engine.py", line 493, in run_domain
> >     vm.startup()
> >   File "/usr/share/virt-manager/virtManager/domain.py", line 573, in startup
> >     self.vm.create()
> >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 287, in create
> >     if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> > libvirtError: internal error Failed to add tap interface 'vnet%d' to
> > bridge 'br0' : No such device
>
> What exactly is the guest's configuration? Is 'vnet%d' mentioned
> anywhere? What version of libvirt?

libvirt-0.6.2-13.fc11.x86_64

<domain type='kvm'>
 <name>test</name>
 <uuid>13f7c43f-de93-4836-74b7-97b6796fae42</uuid>
 <memory>1048576</memory>
 <currentMemory>1048576</currentMemory>
 <vcpu>1</vcpu>
 <os>
   <type arch='x86_64' machine='pc'>hvm</type>
   <boot dev='hd'/>
 </os>
 <features>
   <acpi/>
   <apic/>
   <pae/>
 </features>
 <clock offset='utc'/>
 <on_poweroff>destroy</on_poweroff>
 <on_reboot>restart</on_reboot>
 <on_crash>restart</on_crash>
 <devices>
   <emulator>/usr/bin/qemu-kvm</emulator>
   <disk type='file' device='disk'>
     <source file='/var/lib/libvirt/images/test.img'/>
     <target dev='hda' bus='ide'/>
   </disk>
   <disk type='file' device='cdrom'>
     <target dev='hdc' bus='ide'/>
     <readonly/>
   </disk>
   <interface type='bridge'>
     <mac address='54:52:00:49:73:9a'/>
     <source bridge='br0'/>
     <target dev='vnet%d'/>
   </interface>
   <serial type='pty'>
     <target port='0'/>
   </serial>
   <console type='pty'>
     <target port='0'/>
   </console>
   <input type='mouse' bus='ps2'/>
   <graphics type='vnc' port='-1' autoport='yes'/>
   <sound model='es1370'/>
 </devices>
</domain>

--
Gianluca Sforna

http://morefedora.blogspot.com
http://www.linkedin.com/in/gianlucasforna

[Mark McLoughlin]

On Tue, 2009-07-28 at 15:40 +0200, Gianluca Sforna wrote:
> On Tue, Jul 28, 2009 at 1:20 PM, Mark McLoughlin wrote:
> > On Tue, 2009-07-28 at 12:58 +0200, Gianluca Sforna wrote:
> > > On Tue, Jul 28, 2009 at 12:29 PM, Mark McLoughlin wrote:
> > > > Can you use 'virsh edit' to add e.g.:
> > > >
> > > >    <interface type='bridge'>
> > > >      <mac address='54:52:00:49:73:9a'/>
> > > >      <source bridge='br0'/>
> > > >    </interface>
> > >
> > > This leads to another traceback when starting the VM:
> >
> > Did you file a bug with the first traceback?
>
> I just did it:
> https://bugzilla.redhat.com/show_bug.cgi?id=514228

Thanks.
> > > Traceback (most recent call last):
> > >   File "/usr/share/virt-manager/virtManager/engine.py", line 493, in run_domain
> > >     vm.startup()
> > >   File "/usr/share/virt-manager/virtManager/domain.py", line 573, in startup
> > >     self.vm.create()
> > >   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 287, in create
> > >     if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> > > libvirtError: internal error Failed to add tap interface 'vnet%d' to
> > > bridge 'br0' : No such device
> >
> > What exactly is the guest's configuration? Is 'vnet%d' mentioned
> > anywhere? What version of libvirt?
>
> libvirt-0.6.2-13.fc11.x86_64
>
> <domain type='kvm'>
>  <name>test</name>
>  <uuid>13f7c43f-de93-4836-74b7-97b6796fae42</uuid>
>  <memory>1048576</memory>
>  <currentMemory>1048576</currentMemory>
>  <vcpu>1</vcpu>
>  <os>
>    <type arch='x86_64' machine='pc'>hvm</type>
>    <boot dev='hd'/>
>  </os>
>  <features>
>    <acpi/>
>    <apic/>
>    <pae/>
>  </features>
>  <clock offset='utc'/>
>  <on_poweroff>destroy</on_poweroff>
>  <on_reboot>restart</on_reboot>
>  <on_crash>restart</on_crash>
>  <devices>
>    <emulator>/usr/bin/qemu-kvm</emulator>
>    <disk type='file' device='disk'>
>      <source file='/var/lib/libvirt/images/test.img'/>
>      <target dev='hda' bus='ide'/>
>    </disk>
>    <disk type='file' device='cdrom'>
>      <target dev='hdc' bus='ide'/>
>      <readonly/>
>    </disk>
>    <interface type='bridge'>
>      <mac address='54:52:00:49:73:9a'/>
>      <source bridge='br0'/>
>      <target dev='vnet%d'/>

Try deleting this line

Cheers,
Mark.

[Gianluca Sforna]

On Tue, Jul 28, 2009 at 4:13 PM, Mark McLoughlin wrote:
> > <interface type='bridge'>
> >      <mac address='54:52:00:49:73:9a'/>
> >      <source bridge='br0'/>
> >      <target dev='vnet%d'/>
>
> Try deleting this line

I tried removing the line with virsh edit, but restarting the VM with
virsh start leads to the same error. I double checked and the line
appeared again, I've no idea how it got there again...

[Rich Mahn]

> On Tue, Jul 28, 2009 at 4:13 PM, Mark McLoughlin wrote:
> > > <interface type='bridge'>
> > >      <mac address='54:52:00:49:73:9a'/>
> > >      <source bridge='br0'/>
> > >      <target dev='vnet%d'/>
> >
> > Try deleting this line
> I tried removing the line with virsh edit, but restarting the VM with
> virsh start leads to the same error. I double checked and the line
> appeared again, I've no idea how it got there again...

I've just gone through similar situations and now have everything
working like I want.  One of many problems I had was the one above
(and I'm not sure which thing I did fixed it.)
So here's some ideas:

1. Make sure you aren't using NetworkManager.  It seems to do unexpected
   things automatically, and according to
      http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging
   is doesn't support bridging as of F9.  The instructions at that URL
   pretty much gave me everything I needed to get things going.

2. When I set my interface as you have (mac address and soruce bridge only)
   it adds a target dev=vnet0 automatically.  And this works.

3. You might need to update some packages.  On the client I was unable
   to make NIS work until I updated the ypbind package.

Good luck.

Rich

[Rich Mahn]

> On Tue, Jul 28, 2009 at 4:13 PM, Mark McLoughlin wrote:
> > > <interface type='bridge'>
> > >      <mac address='54:52:00:49:73:9a'/>
> > >      <source bridge='br0'/>
> > >      <target dev='vnet%d'/>
> >
> > Try deleting this line
> I tried removing the line with virsh edit, but restarting the VM with
> virsh start leads to the same error. I double checked and the line
> appeared again, I've no idea how it got there again...

I've just gone through similar situations and now have everything
working like I want.  One of many problems I had was the one above
(and I'm not sure which thing I did fixed it.)
So here's some ideas:

1. Make sure you aren't using NetworkManager.  It seems to do unexpected
   things automatically, and according to
      http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging
   is doesn't support bridging as of F9.  The instructions at that URL
   pretty much gave me everything I needed to get things going.

2. When I set my interface as you have (mac address and soruce bridge only)
   it adds a target dev=vnet0 automatically.  And this works.

3. You might need to update some packages.  On the client I was unable
   to make NIS work until I updated the ypbind package.

Good luck.

Rich

[Richard W.M. Jones]

On Tue, Jul 28, 2009 at 04:35:43PM +0200, Gianluca Sforna wrote:
> On Tue, Jul 28, 2009 at 4:13 PM, Mark McLoughlin wrote:
> > > <interface type='bridge'>
> > >      <mac address='54:52:00:49:73:9a'/>
> > >      <source bridge='br0'/>
> > >      <target dev='vnet%d'/>
> >
> > Try deleting this line
>
> I tried removing the line with virsh edit, but restarting the VM with
> virsh start leads to the same error. I double checked and the line
> appeared again, I've no idea how it got there again...

'virsh edit' isn't editing a simple configuration file, that's why.

When the domain is running, it asks libvirt to create an XML
representation of the domain running domain (from libvirtd's internal
data structures), which it edits, then that is parsed back by libvirt
into some internal structures.

When the domain is inactive, ... actually I know it uses a different
path, but I'm not sure what precisely happens with KVM guests, but Dan
will be able to tell us all.

Anyway there is plenty of scope for edits to go strangely.

Rich.

[Mark McLoughlin]

On Tue, 2009-07-28 at 16:35 +0200, Gianluca Sforna wrote:
> On Tue, Jul 28, 2009 at 4:13 PM, Mark McLoughlin wrote:
> > >    <interface type='bridge'>
> > >      <mac address='54:52:00:49:73:9a'/>
> > >      <source bridge='br0'/>
> > >      <target dev='vnet%d'/>
> >
> > Try deleting this line
>
> I tried removing the line with virsh edit, but restarting the VM with
> virsh start leads to the same error. I double checked and the line
> appeared again, I've no idea how it got there again...

Please file a bug on this - dumpxml/edit should never show dev='vnet%d'

Thanks,
Mark.

[Gianluca Sforna]

On Wed, Jul 29, 2009 at 9:19 AM, Mark McLoughlin wrote:
> On Tue, 2009-07-28 at 16:35 +0200, Gianluca Sforna wrote:
> > On Tue, Jul 28, 2009 at 4:13 PM, Mark McLoughlin wrote:
> > > > <interface type='bridge'>
> > > >      <mac address='54:52:00:49:73:9a'/>
> > > >      <source bridge='br0'/>
> > > >      <target dev='vnet%d'/>
> > >
> > > Try deleting this line
> >
> > I tried removing the line with virsh edit, but restarting the VM with
> > virsh start leads to the same error. I double checked and the line
> > appeared again, I've no idea how it got there again...
>
> Please file a bug on this - dumpxml/edit should never show dev='vnet%d'

https://bugzilla.redhat.com/show_bug.cgi?id=514472