Bug#455195: linux-image-2.6.18-5-vserver-amd64: forcedeth hears no dhcp reply; linux-image-2.6.18-5-xen-vserver-amd64 IS GOOD

[Moritz Muehlenhoff <jmm@inutil.org>]

On Sat, Dec 08, 2007 at 08:25:56PM -0500, supaplex wrote:
> Package: linux-image-2.6.18-5-vserver-amd64
> Version: 2.6.18.dfsg.1-13etch4
> Severity: normal
> 
> I've stripped the interfaces(5) config down to a plain ordinary dhcp
> host for eth0, loopback etc.  No vlans, No bridging, and no other
> network interfaces in the system.
> 
> For the time being, I wanted to keep it simple, and use a kernel without
> xen support, so I installed this release.  After rebooting between each
> kernel back and forth, dhcp always works in the dom0 xen kernel, and
> never has when not using xen.  At present none of the vserver guests
> have dedicated network interfaces.  They're used in development testing
> and mostly for isolated compiling of packages (eg, backports, one off
> tests, etc).
> 
> syslog on the dhcp server says it's assigning the address, tcpdump on
> the dhcp server says it's assigning an address, but tcpdump running on
> the client only sees dhcp requests until it eventually gives up and goes
> idle.
> 
> I also attempted to stop util-vserver on the bad kernel, stop
> networking, and start it again with no progress on the issue.

Did you upgrade to Lenny in the mean time? If so, did it fix the problem?

Cheers,
        Moritz