This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Patch fixing vlan handling when network-bridge scriptis

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Patch fixing vlan handling when network-bridge scriptis used
From: Michael Brade <brade@xxxxxxx>
Date: Thu, 19 Aug 2010 20:35:47 +0200
Delivery-date: Thu, 19 Aug 2010 11:37:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19565.28906.408019.414127@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: K Desktop Environment
References: <232221223.568081282131308987.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <201008191759.39253.brade@xxxxxxx> <19565.28906.408019.414127@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.13.5 (Linux/; KDE/4.4.5; i686; ; )
On Thursday 19 August 2010 19:59:06 you wrote:
> Michael Brade writes ("Re: [Xen-devel] Patch fixing vlan handling when 
network-bridge scriptis used"):
> > But I had to add the "ethtool -K $vif tx off" to vif-bridge to fix the
> > checksums error. Maybe this could be added by default with a check for
> > ethtool?
> Are we still having this bug ?  I tripped over this about 4 years ago
> when I was just a user of Xen ...

wow... I also thought this must have been fixed already but I didn't find a 
message saying so, nor did I see a patch for it so I concluded ethtool was the 
way to go.

> Can you describe the setup in which you had to do the -K tx off ?

    * running xen-testing from staging, kernel with pvops
    * network interfaces: peth0, peth1, ppp0
    * bridges: eth0, eth1
    * local net is on bridge eth1 with domUs connected there
    * internet is on ppp0
    * running PV-GRUB, kernel as above, but stripped down to 
      the bare minimum
    * only one network interface, dhcp to dom0

relevant domU config:

kernel      = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra       = "(hd0)/boot/grub/menu.lst"
disk        = [ 'tap2:tapdisk:aio:/..../root.img,xvda1,w', 
                'tap2:tapdisk:aio:/..../var.img,xvda2,w' ]


vif         = [ 'mac=...., bridge=eth1' ]

grub menu.lst:

title vmlinuz-
   root (hd0)
   kernel /boot/vmlinuz- console=hvc0 root=/dev/xvda1 ro

If I leave the -K tx off out then I won't even get a dhcp connection in domU.

And btw, vnc doesn't work either, despite the vnc=1. There is no open port, no 
idea why yet. Only xm console is available. If I start a domU with HVM it 

Here's xm list --long:

    (domid 2)
    (cpu_weight 256)
    (cpu_cap 0)
    (on_crash restart)
    (uuid .....)
    (bootloader_args )
    (vcpus 1)
    (name .....)
    (on_poweroff destroy)
    (on_reboot restart)
    (cpus (()))
    (description )
    (bootloader )
    (maxmem 512)
    (memory 512)
    (shadow_memory 0)
    (features )
    (on_xend_start ignore)
    (on_xend_stop ignore)
    (start_time 1282234728.43)
    (cpu_time 16.594413607)
    (online_vcpus 1)
            (kernel /usr/lib/xen/boot/pv-grub-x86_64.gz)
            (args '(hd0)/boot/grub/menu.lst')
            (superpages 0)
            (tsc_mode 0)
            (videoram 4)
            (pci ())
            (nomigrate 0)
    (status 2)
    (state -b----)
    (store_mfn 1815884)
    (console_mfn 1815883)
            (bridge eth1)
            (mac ....)
            (script '/etc/xen/scripts/vif-bridge bridge=eth1')
            (uuid ....)
            (backend 0)
            (protocol vt100)
            (location 2)
            (uuid ....)
            (protocol x86_64-abi)
            (uuid ....)
            (bootable 1)
            (dev xvda1:disk)
            (mode w)
            (backend 0)
            (VDI )
            (protocol x86_64-abi)
            (uuid ....)
            (bootable 0)
            (dev xvda2:disk)
            (mode w)
            (backend 0)
            (VDI )

Hope this helps!

Michael Brade;                                              KDE Developer
  |-mail: echo brade !#|tr -d "c oh"|s\e\d 's/e/\@/2;s/$/.org/;s/bra/k/2'
  °--web: http://www.behindkde.org/people/michaelb/

KDE 4: Beyond Your Expectations

Attachment: signature.asc
Description: This is a digitally signed message part.

Xen-devel mailing list