dear jan grant, On Tue, Sep 02, 2008 at 12:27:08PM +0100, Jan Grant wrote: > Package: linux-image-2.6.26-1-openvz-amd64 > Version: 2.6.26-4 > > I'm trying to get openvz working in a somewhat complex networking > environment, and hitting a hard lock-up when using multiple bridges. > > I attach /etc/network/interfaces from CT0, plus the CT100 config and a > script used (manually at the moment) to bring up the bridges once the > CT100 has been started.
i see, could you please file that upstream so that openvz devs read about it and tell us the upstream bug number so that we can keep track of it. -> http://bugzilla.openvz.org/ > CT0 is networked to three separate subnets, called "main", "deploy" and > "ilom" respectively. > > "deploy": this is physically plumbed into eth0. > "main": this is physically plumbed into bond0 (eth1 and eth2). > "ilom": this is physically plumbed into eth3. > > There are three bridge devices created (and assigned IP addresses) > within CT0, named as above - see the attached interfaces for details. > The only subtle thing here is that the "main" bridge is on a bonded > interface. > > This all works, and the box boots and can see its attached networks. > > I can do the following: > > vzctl start 100 > > and the zone comes up. The zone itself only has its ethIlom configured > and allocated a network address. > > Once the vzbridge script (attached) is run, the veth devices of the new > CT100 are attached to their respective bridges. > > All good so far: I have visibility to the ILOM network from CT0 and from > the VE. > > However, once I attempt to bring up ethDeploy within the VE, the host > locks up hard: > > vzctl enter 100 > ifconfig ethDeploy up > [hard lockup] > > I've a requirement to multiply-connect these containers, so any help > here would be appreciated. Certainly a hard lockup doesn't sound like > the correct behaviour. > > Cheers, > jan thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
