Unfortunately I'm not able to replace the kernel since grub in the domU doesn't recognize my xvda drive. /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/xvda2. Check your device.map.

I then inserted "(hd0) /dev/xvda" into the /boot/grub/devices.map but with no luck. I'm still getting the bridge-breakdowns. The bridge itself seems to be up but only restarting the domU helps. "/etc/init.d/networking restart" has no effect nor does "ifconfig eth1 down && ifconfig eth1 up".

Please help.

Am 06.09.10 11:21, schrieb Pasi Kärkkäinen:
On Mon, Sep 06, 2010 at 10:31:28AM +0200, Jochen Demmer wrote:
    Hi,

    I'm not sure but I think I suffer under the same problem with a bit
    different setup with squeeze testing and xen 4.0rc5.
    In fact I'm using bridges in the dom0 and the connections to the domU get
    lost sporadically.
    In don't see where's a solution to the problem... Is it now a bug? When
    it's an iptables bug, where's the corresponding bug in the iptables
    bugtracker and what exactly is iptables doing wrong.
    You stated "...but as the syslog message clearly indicates this rule works
    perfectly when the traffic is bridged."
    I'm using bridges but it's not working obviously.

I don't really see any errors in the log below.

Have you tried using different kernel in the domU?
If network is fine from dom0, then this sounds like a bug in the domU kernel.

What kernel are you running in the domU?

-- Pasi


    /etc/network/interfaces
    auto br0
    allow-hotplug br0
    iface br0 inet static
    address 10.100.200.20
    netmask 255.255.255.0
    dns-nameservers 10.100.200.3
    gateway 10.100.200.3
    bridge_ports eth0

    allow-hotplug br1
    auto br1
    iface br1 inet manual
    bridge_ports eth1

    This is my logs:
    Sep  6 09:47:14 elise kernel: [71970.564974] br1: port 2(vif1.1) entering
    disabled state
    Sep  6 09:47:14 elise kernel: [71970.578040] br1: port 2(vif1.1) entering
    disabled state
    Sep  6 09:47:14 elise kernel: [71970.718785] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:14 elise kernel: [71970.718797] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:14 elise kernel: [71970.718803] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:14 elise kernel: [71970.724864] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:14 elise kernel: [71970.724874] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:15 elise kernel: [71970.871846] br0: port 2(vif1.0) entering
    disabled state
    Sep  6 09:47:15 elise kernel: [71970.890073] br0: port 2(vif1.0) entering
    disabled state
    Sep  6 09:47:15 elise kernel: [71971.010275] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:15 elise kernel: [71971.010286] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:15 elise kernel: [71971.016391] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:17 elise kernel: [71972.912040] device vif3.0 entered
    promiscuous mode
    Sep  6 09:47:17 elise kernel: [71972.915898] br0: port 2(vif3.0) entering
    learning state
    Sep  6 09:47:17 elise kernel: [71972.948656] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:17 elise kernel: [71972.953266] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:17 elise kernel: [71972.953273] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:17 elise kernel: [71972.986255] device vif3.1 entered
    promiscuous mode
    Sep  6 09:47:17 elise kernel: [71972.990441] br1: port 2(vif3.1) entering
    learning state
    Sep  6 09:47:17 elise kernel: [71973.011096] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:17 elise kernel: [71973.011102] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:17 elise kernel: [71973.016383] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:17 elise kernel: [71973.016392] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:17 elise kernel: [71973.016398] physdev match: using
    --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
    non-bridged traffic is not supported anymore.
    Sep  6 09:47:18 elise kernel: [71974.706987] blkback: ring-ref 8,
    event-channel 8, protocol 1 (x86_64-abi)
    Sep  6 09:47:18 elise kernel: [71974.734701] blkback: ring-ref 9,
    event-channel 9, protocol 1 (x86_64-abi)
    Sep  6 09:47:32 elise kernel: [71987.913527] br0: port 2(vif3.0) entering
    forwarding state
    Sep  6 09:47:32 elise kernel: [71987.988031] br1: port 2(vif3.1) entering
    forwarding state
_______________________________________________
Pkg-xen-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-xen-devel



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

Reply via email to