I had removed the igb-based eth0 from the bonding interface, and the machine
was running fine with it, but when the time had come to get some Xen domUs
running on it, it failed miserably on me once again.
But as soon as I generate any traffic to or from 192.168.54.0/24 and that
virtual machine (notice - not the right VLAN), the whole system instantly
reboots, with no messages in syslog.
I should probably use the hypervisor's noreboot option, but I don't have
a connection to its IPMI out-of-band access controller, and I'm off-site,
so I'm SOL.
This is with linux-image-3.2.0-0.bpo.2-amd64 and with latest .bpo.3.
I'm going to try fiddling with ethtool -K eth2 gro/lro off, but with the
reboots taking >3min on this hardware, this is most annoying...
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120831155203.GA6465@entuzijast.net">http://lists.debian.org/20120831155203.GA6465@entuzijast.net
09-01-2012, 08:45 AM
Bastian Blank
Bug#666386: more info
On Fri, Aug 31, 2012 at 05:52:03PM +0200, Josip Rodin wrote:
> auto vlan2
> iface vlan2 inet manual
> vlan-raw-device xenbr0
Is vlan-over-bridge documented to be supported?
Usually I would use:
| iface xenbr2 inet static
| bridge-ports bond0.2
> But as soon as I generate any traffic to or from 192.168.54.0/24 and that
> virtual machine (notice - not the right VLAN), the whole system instantly
> reboots, with no messages in syslog.
Does it work without bond?
I would switch to openvswitch. It documents bond/vlan setups, so they
most likely work. (I don't use bond yet, but the rest works pretty
flawless, however I have to submit the openvswitch support.)
Bastian
--
It is necessary to have purpose.
-- Alice #1, "I, Mudd", stardate 4513.3
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120901084505.GA21418@wavehammer.waldi.eu.org">ht tp://lists.debian.org/20120901084505.GA21418@wavehammer.waldi.eu.org
09-02-2012, 01:42 PM
Ben Hutchings
Bug#666386: more info
On Sat, 2012-09-01 at 10:45 +0200, Bastian Blank wrote:
> On Fri, Aug 31, 2012 at 05:52:03PM +0200, Josip Rodin wrote:
> > auto vlan2
> > iface vlan2 inet manual
> > vlan-raw-device xenbr0
>
> Is vlan-over-bridge documented to be supported?
If it was not supported then bridge devices would have
NETIF_F_VLAN_CHALLENGED and you would not be able to create VLAN devices
on top of them. But I don't expect this to work *well* at present.
Rebooting, however... something is very wrong here.
> Usually I would use:
> | iface xenbr2 inet static
> | bridge-ports bond0.2
>
> > But as soon as I generate any traffic to or from 192.168.54.0/24 and that
> > virtual machine (notice - not the right VLAN), the whole system instantly
> > reboots, with no messages in syslog.
>
> Does it work without bond?
>
> I would switch to openvswitch. It documents bond/vlan setups, so they
> most likely work. (I don't use bond yet, but the rest works pretty
> flawless, however I have to submit the openvswitch support.)
Definitely worth trying.
Ben.
--
Ben Hutchings
Theory and practice are closer in theory than in practice.
- John Levine, moderator of comp.compilers
09-03-2012, 04:27 PM
Josip Rodin
Bug#666386: more info
On Sun, Sep 02, 2012 at 02:42:38PM +0100, Ben Hutchings wrote:
> On Sat, 2012-09-01 at 10:45 +0200, Bastian Blank wrote:
> > On Fri, Aug 31, 2012 at 05:52:03PM +0200, Josip Rodin wrote:
> > > auto vlan2
> > > iface vlan2 inet manual
> > > vlan-raw-device xenbr0
> >
> > Is vlan-over-bridge documented to be supported?
>
> If it was not supported then bridge devices would have
> NETIF_F_VLAN_CHALLENGED and you would not be able to create VLAN devices
> on top of them. But I don't expect this to work *well* at present.
>
> Rebooting, however... something is very wrong here.
>
> > Usually I would use:
> > | iface xenbr2 inet static
> > | bridge-ports bond0.2
> >
> > > But as soon as I generate any traffic to or from 192.168.54.0/24 and that
> > > virtual machine (notice - not the right VLAN), the whole system instantly
> > > reboots, with no messages in syslog.
> >
> > Does it work without bond?
> >
> > I would switch to openvswitch. It documents bond/vlan setups, so they
> > most likely work. (I don't use bond yet, but the rest works pretty
> > flawless, however I have to submit the openvswitch support.)
>
> Definitely worth trying.
Ah, good catch, I do actually seem to want to use the underlying device for
vlan, rather than the bridge device. All my other setups are like that.
It shouldn't crash anyway...
JFTR the other thing I noticed, before I read the mail, was that the remote
machine was actually visible on that L2 segment through ARP, but the outside
world can't ping it - it's as if xen-netback/front don't let that through,
for no apparent reason. And then, when I initiate traffic towards the
outside world from the machine, it all goes poof.
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120903162712.GA22135@entuzijast.net">http://lists.debian.org/20120903162712.GA22135@entuzijast.net
09-03-2012, 04:39 PM
Josip Rodin
Bug#666386: more info
On Mon, Sep 03, 2012 at 06:27:12PM +0200, Josip Rodin wrote:
> On Sun, Sep 02, 2012 at 02:42:38PM +0100, Ben Hutchings wrote:
> > On Sat, 2012-09-01 at 10:45 +0200, Bastian Blank wrote:
> > > On Fri, Aug 31, 2012 at 05:52:03PM +0200, Josip Rodin wrote:
> > > > auto vlan2
> > > > iface vlan2 inet manual
> > > > vlan-raw-device xenbr0
> > >
> > > Is vlan-over-bridge documented to be supported?
> >
> > If it was not supported then bridge devices would have
> > NETIF_F_VLAN_CHALLENGED and you would not be able to create VLAN devices
> > on top of them. But I don't expect this to work *well* at present.
> >
> > Rebooting, however... something is very wrong here.
> >
> > > Usually I would use:
> > > | iface xenbr2 inet static
> > > | bridge-ports bond0.2
> > >
> > > > But as soon as I generate any traffic to or from 192.168.54.0/24 and that
> > > > virtual machine (notice - not the right VLAN), the whole system instantly
> > > > reboots, with no messages in syslog.
> > >
> > > Does it work without bond?
>
> Ah, good catch, I do actually seem to want to use the underlying device for
> vlan, rather than the bridge device. All my other setups are like that.
Confirming it works with fixed vlan-raw-device, pointed to eth2. I should
test with bond now, that was probably it...
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120903163909.GA26001@entuzijast.net">http://lists.debian.org/20120903163909.GA26001@entuzijast.net
Bug#666386: more info
