xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Michael Brade <brade@kde.org>
To: xen-devel@lists.xensource.com
Subject: Re: Patch fixing vlan handling when network-bridge scriptis used
Date: Thu, 19 Aug 2010 20:35:47 +0200	[thread overview]
Message-ID: <201008192035.53640.brade@kde.org> (raw)
In-Reply-To: <19565.28906.408019.414127@mariner.uk.xensource.com>


[-- Attachment #1.1: Type: Text/Plain, Size: 3943 bytes --]

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 ?

yup: 
  dom0:
    * running xen-testing from staging, kernel 2.6.32.19 with pvops
    * network interfaces: peth0, peth1, ppp0
    * bridges: eth0, eth1
    * local net is on bridge eth1 with domUs connected there
    * internet is on ppp0
  domU:
    * running PV-GRUB, kernel 2.6.32.19 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' ]

boot='c'
sdl=0
vnc=1
vncunused=1
stdvga=1

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


grub menu.lst:

title vmlinuz-2.6.32.19-domU
   root (hd0)
   kernel /boot/vmlinuz-2.6.32.19 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 
works.

Here's xm list --long:

(domain
    (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)
    (image
        (linux
            (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)
            (notes)
        )
    )
    (status 2)
    (state -b----)
    (store_mfn 1815884)
    (console_mfn 1815883)
    (device
        (vif
            (bridge eth1)
            (mac ....)
            (script '/etc/xen/scripts/vif-bridge bridge=eth1')
            (uuid ....)
            (backend 0)
        )
    )
    (device
        (console
            (protocol vt100)
            (location 2)
            (uuid ....)
        )
    )
    (device
        (tap2
            (protocol x86_64-abi)
            (uuid ....)
            (bootable 1)
            (dev xvda1:disk)
            (uname
                tap:tapdisk:aio:/..../root.img
            )
            (mode w)
            (backend 0)
            (VDI )
        )
    )
    (device
        (tap2
            (protocol x86_64-abi)
            (uuid ....)
            (bootable 0)
            (dev xvda2:disk)
            (uname
                tap:tapdisk:aio:/..../var.img
            )
            (mode w)
            (backend 0)
            (VDI )
        )
    )
)

Hope this helps!

thanks,
-- 
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 #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-08-19 18:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <232221223.568081282131308987.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-18 11:43 ` Patch fixing vlan handling when network-bridge script is used Miroslav Rezanina
2010-08-18 16:02   ` Ian Jackson
2010-08-19  4:20     ` Patch fixing vlan handling when network-bridge scriptis used James Harper
2010-08-19 13:25       ` Ian Jackson
2010-08-19 15:59       ` Michael Brade
2010-08-19 17:59         ` Ian Jackson
2010-08-19 18:35           ` Michael Brade [this message]
2010-08-19 23:11         ` Jeremy Fitzhardinge
2010-08-20 18:25           ` Michael Brade

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008192035.53640.brade@kde.org \
    --to=brade@kde.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).