On 05/01/2011 12:53 AM, Teck Choon Giam wrote:
> On Sun, May 1, 2011 at 10:04 AM, Digimer <linux@xxxxxxxxxxx> wrote:
>> On 04/30/2011 08:47 PM, Teck Choon Giam wrote:
>>> Pasi is right about to use system network configuration so that xend
>>> and system network are separated. Can you explain how it was bugged?
>>> Is it sometimes get set and sometimes not? Have you try to give a
>>> small sleep interval such as 3 seconds before setting the related mtu?
>> I've got three interfaces in my server;
>> - eth0; Internet-facing, bridged as xenbr0
>> - eth1; Storage network, not bridged or used by any domU.
>> - eth2; Back-channel/internal network, bridged as xenbr2, used by some domU.
>> I had a patch in xen-network-common.sh's setup_bridge_port()
>> function that would look at the $dev passed in, parse it and pull the
>> MTU from the corresponding bridge. The bug was that this $dev matched
>> the ethX device in the domU rather than the bridge, so when the second
>> interface (xenbr2 <-> domU's eth1) would look for the MTU of 'xenbr1',
>> which didn't exist.
> Your domUs are all HVM or PV or both in mix with the same problem?
> Kindest regards,
> Giam Teck Choon
They're a mix, and the issue was across the board.
Node Assassin: http://nodeassassin.org
Xen-users mailing list