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 184.108.40.206 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 220.127.116.11 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',
vif = [ 'mac=...., bridge=eth1' ]
kernel /boot/vmlinuz-18.104.22.168 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:
(script '/etc/xen/scripts/vif-bridge bridge=eth1')
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'
KDE 4: Beyond Your Expectations
Description: This is a digitally signed message part.
Xen-devel mailing list