> As for the network-related issues, indeed, this is something which
> is quite unexpected.  I browsed all changes between 1.0 and 1.0.1,
> but I don't see a single change which may have this effect...

I am no dev but I would guess that several gbit/s of TCP-traffic may
trigger any regressions in other parts of the KVM subsystems too, so
perhaps it isn't directly linked to the networking?

> I'll dig further into this in a few next days, but since I can't
> reproduce this I may need more of your help...  Can I rely on a
> bit more of your testing please?

Of course, just let me know what you want me to test.

> Besides, are you sure you're using bridge networking,
> not macvtap networking?

I used virt-manager in Wheezy to set up the machines and selected the
bridges that I created using the same virt-manager.
I did try macvtap as a step in the troubleshooting (on -9) but the
performance was slightly worse not better.

Just so you can be absolutely sure, here is my network configuration:

---
root@kvm1:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
        address 10.0.6.20
        netmask 255.255.255.0
        gateway 10.0.6.1
auto Server
iface Server inet manual
   bridge_ports eth1
   bridge_stp off
   bridge_fd 0

auto DMZ
iface DMZ inet manual
   bridge_ports eth2
   bridge_stp off
   bridge_fd 0
---

I am using the DMZ and Server bridges for the VMs.

---
root@kvm1:~# ifconfig
DMZ       Link encap:Ethernet  HWaddr 00:25:90:56:60:b8
          inet6 addr: fe80::225:90ff:fe56:60b8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5017 errors:0 dropped:0 overruns:0 frame:0
          TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:230962 (225.5 KiB)  TX bytes:7348 (7.1 KiB)

Server    Link encap:Ethernet  HWaddr 00:25:90:56:60:b7
          inet6 addr: fe80::225:90ff:fe56:60b7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5227 errors:0 dropped:0 overruns:0 frame:0
          TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:246674 (240.8 KiB)  TX bytes:7348 (7.1 KiB)

eth0      Link encap:Ethernet  HWaddr 00:25:90:56:60:b6
          inet addr:10.0.6.20  Bcast:10.0.6.255  Mask:255.255.255.0
          inet6 addr: fe80::225:90ff:fe56:60b6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:506 errors:0 dropped:0 overruns:0 frame:0
          TX packets:466 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:45360 (44.2 KiB)  TX bytes:43793 (42.7 KiB)
          Interrupt:16 Memory:fbc00000-fbc20000

eth1      Link encap:Ethernet  HWaddr 00:25:90:56:60:b7
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10481 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4655 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1352037 (1.2 MiB)  TX bytes:462975 (452.1 KiB)
          Interrupt:17 Memory:fbb00000-fbb20000

eth2      Link encap:Ethernet  HWaddr 00:25:90:56:60:b8
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5697 errors:0 dropped:1 overruns:0 frame:0
          TX packets:872 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:378588 (369.7 KiB)  TX bytes:69268 (67.6 KiB)
          Interrupt:18 Memory:fba00000-fba20000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vnet0     Link encap:Ethernet  HWaddr fe:54:00:b0:18:68
          inet6 addr: fe80::fc54:ff:feb0:1868/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:355 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5530 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:24545 (23.9 KiB)  TX bytes:340209 (332.2 KiB)

vnet1     Link encap:Ethernet  HWaddr fe:54:00:db:ee:70
          inet6 addr: fe80::fc54:ff:fedb:ee70/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4568 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10040 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:428413 (418.3 KiB)  TX bytes:1080901 (1.0 MiB)

vnet2     Link encap:Ethernet  HWaddr fe:54:00:f7:25:33
          inet6 addr: fe80::fc54:ff:fef7:2533/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:350 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5524 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:23681 (23.1 KiB)  TX bytes:339435 (331.4 KiB)
---

When I boot up a guest linked to a bridge vnetX adapters are added as
I would expect.

---
root@kvm1:~# brctl show
bridge name     bridge id               STP enabled     interfaces
DMZ             8000.0025905660b8       no              eth2
                                                        vnet0
                                                        vnet2
Server          8000.0025905660b7       no              eth1
                                                        vnet1
---

Regards,
Hans-Kristian



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to