[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

Your message dated Mon, 15 Feb 2010 20:18:14 +0100
with message-id <20100215191814.GN9624@baikonur.stro.at>
and subject line Re: Xen || vserver troubles
has caused the Debian Bug report #455195,
regarding linux-image-2.6.18-5-vserver-amd64: forcedeth hears no dhcp reply; linux-image-2.6.18-5-xen-vserver-amd64 IS GOOD
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
455195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455195
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-xen-vserver-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-5-vserver-amd64 depends on:
ii  coreutil 5.97-5.3                        The GNU core utilities
ii  debconf  1.5.11                          Debian configuration management sy
ii  e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib
ii  initramf 0.85h                           tools for generating an initramfs
ii  module-i 3.3-pre4-2                      tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-5-vserver-amd64 recommends:
ii  util-vserver                  0.30.212-1 user-space tools for Linux-VServer

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
the 2.6.18 linux images from Etch are no longer supported, thus closing
this bug report.  As both Xen or vserver stayed out of tree it is very
unlikely that they improved a lot since.

With modern hardware kvm or lxc (linux containers) are recommended.
if you still haven't upgraded to Lenny please notice that Etch has
no security support any more as of today:
http://www.debian.org/News/2010/20100121


if you can reproduce said bugs with 2.6.32 linux images from
unstable please shout on said box and bug can be reopened:
reportbug -N <bugnr>

thank you for your report.

--- End Message ---
Reply to: