Your message dated Fri, 3 Oct 2008 16:13:28 +0200 with message-id <200810031613.34790.holger@layer-acht.org> and subject line Re: Bug#500888: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests has caused the Debian Bug report #500888, regarding linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests 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.) -- 500888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500888 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests
- From: Matthew Sackman <matthew@wellquite.org>
- Date: Thu, 02 Oct 2008 12:14:42 +0100
- Message-id: <[🔎] 20081002111442.9107.60451.reportbug@caffeinated>
Package: linux-image-2.6.26-1-vserver-amd64 Version: 2.6.26-6 Severity: important Each of my vserver guests has a separate loopback interface. This is specified as normal in /etc/vserver/$guest/interfaces/. For example, I have: .../1/dev is "lo" .../1/ip is "127.32.0.1" .../1/prefix is "8" Under 2.6.22-3-vserver-amd64 (and earlier), this all worked fine. Under 2.6.26-1-vserver-amd64 this does not work: every vserver guest is started with lo as 127.0.0.1, thus breaking the internal network badly. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-3-vserver-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-vserver-amd64 depends on: ii debconf [debconf-2.0] 1.5.23 Debian configuration management sy ii initramfs-tools [linux-initra 0.92l tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-vserver-amd64 recommends: ii util-vserver 0.30.216~r2772-2 user-space tools for Linux-VServer Versions of packages linux-image-2.6.26-1-vserver-amd64 suggests: ii grub 0.97-47 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 <none> (no description available) -- debconf information: linux-image-2.6.26-1-vserver-amd64/postinst/old-system-map-link-2.6.26-1-vserver-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-vserver-amd64/postinst/bootloader-error-2.6.26-1-vserver-amd64: linux-image-2.6.26-1-vserver-amd64/prerm/removing-running-kernel-2.6.26-1-vserver-amd64: true linux-image-2.6.26-1-vserver-amd64/preinst/abort-overwrite-2.6.26-1-vserver-amd64: linux-image-2.6.26-1-vserver-amd64/preinst/abort-install-2.6.26-1-vserver-amd64: linux-image-2.6.26-1-vserver-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-vserver-amd64/postinst/create-kimage-link-2.6.26-1-vserver-amd64: true linux-image-2.6.26-1-vserver-amd64/preinst/failed-to-move-modules-2.6.26-1-vserver-amd64: linux-image-2.6.26-1-vserver-amd64/preinst/initrd-2.6.26-1-vserver-amd64: linux-image-2.6.26-1-vserver-amd64/postinst/kimage-is-a-directory: linux-image-2.6.26-1-vserver-amd64/postinst/depmod-error-2.6.26-1-vserver-amd64: false linux-image-2.6.26-1-vserver-amd64/prerm/would-invalidate-boot-loader-2.6.26-1-vserver-amd64: true linux-image-2.6.26-1-vserver-amd64/postinst/old-initrd-link-2.6.26-1-vserver-amd64: true linux-image-2.6.26-1-vserver-amd64/preinst/elilo-initrd-2.6.26-1-vserver-amd64: true linux-image-2.6.26-1-vserver-amd64/postinst/bootloader-test-error-2.6.26-1-vserver-amd64: linux-image-2.6.26-1-vserver-amd64/postinst/depmod-error-initrd-2.6.26-1-vserver-amd64: false linux-image-2.6.26-1-vserver-amd64/preinst/overwriting-modules-2.6.26-1-vserver-amd64: true linux-image-2.6.26-1-vserver-amd64/preinst/bootloader-initrd-2.6.26-1-vserver-amd64: true linux-image-2.6.26-1-vserver-amd64/preinst/lilo-initrd-2.6.26-1-vserver-amd64: true linux-image-2.6.26-1-vserver-amd64/postinst/old-dir-initrd-link-2.6.26-1-vserver-amd64: true
--- End Message ---
--- Begin Message ---
- To: Matthew Sackman <matthew@wellquite.org>
- Cc: 500888-done@bugs.debian.org
- Subject: Re: Bug#500888: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests
- From: Holger Levsen <holger@layer-acht.org>
- Date: Fri, 3 Oct 2008 16:13:28 +0200
- Message-id: <200810031613.34790.holger@layer-acht.org>
- In-reply-to: <20081003125432.GB31155@arkansas.doc.ic.ac.uk>
- References: <[🔎] 20081002111442.9107.60451.reportbug@caffeinated> <200810021413.33924.holger@layer-acht.org> <20081003125432.GB31155@arkansas.doc.ic.ac.uk>
Hi Matthew, On Friday 03 October 2008 14:54, Matthew Sackman wrote: > You're right; I'm an idiot. I didn't realise they'd added this feature. > So sorry for wasting your time. np, we're all being stupid once in a while :-) Thanks for confirming it works as it should! regards, HolgerAttachment: pgpfiIOeMD5Mp.pgp
Description: PGP signature
--- End Message ---