Your message dated Fri, 4 Jul 2008 22:33:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: xen-linux-system-2.6.18-4-xen-686: Prevents ALSA from 
finding soundcards
has caused the Debian Bug report #415740,
regarding linux-image-2.6.18-4-xen-vserver-amd64: DHCP does not work well over 
XEN virtual networking
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 [EMAIL PROTECTED]
immediately.)


-- 
415740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415740
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: linux-image-2.6.18-4-xen-vserver-amd64
Version: 2.6.18.dfsg.1-11
Severity: normal

I have configured dhcp3-server in dom0 and dhcp3-client in domU. In domU syslog 
I get:

Mar 21 14:58:33 firewall dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 
67 interval 5
Mar 21 14:58:33 firewall dhclient: DHCPOFFER from 192.168.1.1
Mar 21 14:58:33 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 
67
Mar 21 14:58:33 firewall dhclient: DHCPACK from 192.168.1.1
Mar 21 14:58:33 firewall dhclient: bound to 192.168.1.179 -- renewal in 263 
seconds.
Mar 21 15:02:56 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:03:00 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:03:00 firewall dhclient: 6 bad udp checksums in 11 packets
Mar 21 15:03:07 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:03:18 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:03:25 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:03:37 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:03:37 firewall dhclient: 4 bad udp checksums in 5 packets
Mar 21 15:03:46 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:04:05 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:04:24 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:04:24 firewall dhclient: 3 bad udp checksums in 5 packets
Mar 21 15:04:32 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:04:46 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:04:54 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:05:07 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:05:16 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:05:16 firewall dhclient: 5 bad udp checksums in 5 packets
Mar 21 15:05:25 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:05:38 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:05:54 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:06:08 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:06:20 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:06:20 firewall dhclient: 5 bad udp checksums in 5 packets
Mar 21 15:06:38 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:06:57 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:07:17 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Mar 21 15:07:34 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 
67
Mar 21 15:07:34 firewall dhclient: 4 bad udp checksums in 5 packets
Mar 21 15:07:42 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 
67
Mar 21 15:07:54 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 
67
Mar 21 15:08:15 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 
67
Mar 21 15:08:32 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 
67
Mar 21 15:08:32 firewall dhclient: 4 bad udp checksums in 5 packets
Mar 21 15:08:35 firewall dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 
67 interval 3
Mar 21 15:08:35 firewall dhclient: DHCPOFFER from 192.168.1.1
Mar 21 15:08:35 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 
67
Mar 21 15:08:35 firewall dhclient: DHCPACK from 192.168.1.1
Mar 21 15:08:35 firewall dhclient: bound to 192.168.1.179 -- renewal in 265 
seconds.

and in dom0 syslog (timezone differs by 1 hour):

Mar 21 15:58:33 p5bvm dhcpd: DHCPDISCOVER from 06:18:f3:06:85:75 (firewall) via 
eth0
Mar 21 15:58:33 p5bvm dhcpd: DHCPOFFER on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 15:58:33 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 (192.168.1.1) from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 15:58:33 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:02:55 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:02:55 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:02:59 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:02:59 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:03:06 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:03:06 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:03:17 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:03:17 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:03:24 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:03:24 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:03:36 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:03:36 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:03:45 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:03:45 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:04:04 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:04:04 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:04:23 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:04:23 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:04:31 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:04:31 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:04:45 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:04:45 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:04:53 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:04:53 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:05:06 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:05:06 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:05:15 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:05:15 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:05:24 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:05:24 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:05:37 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:05:37 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:05:53 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:05:53 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:06:07 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:06:07 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:06:19 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:06:19 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:06:37 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:06:37 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:06:56 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:06:56 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:07:16 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:07:16 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:07:33 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:07:33 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:07:41 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:07:41 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:07:53 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:07:53 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:08:14 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:08:14 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:08:31 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:08:31 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:08:34 p5bvm dhcpd: DHCPDISCOVER from 06:18:f3:06:85:75 (firewall) via 
eth0
Mar 21 16:08:34 p5bvm dhcpd: DHCPOFFER on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0
Mar 21 16:08:34 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 (192.168.1.1) from 
06:18:f3:06:85:75 (firewall) via eth0
Mar 21 16:08:34 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 
(firewall) via eth0

Another dhcp3-client, running on my etch laptop, does not have any problems
refreshing its address from the same server with a single DHCPREQUEST.

Janusz

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

Versions of packages xen-hypervisor-3.0.3-1-amd64 depends on:
ii  xen-utils-3.0.3-1             3.0.3-0-2  XEN administrative tools

xen-hypervisor-3.0.3-1-amd64 recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 2.6.25-1

upstream merged paravirt_ops Xen. it features enhanced netxen
and block modules.

as this code got rewritten old bug no longer apply.
for guest system it is recommend to upgrade to newer xen.
for more infos on upstream merge status see
http://wiki.xensource.com/xenwiki/XenParavirtOps

for latest 2.6.26-rc8 linux images see
http://wiki.debian.org/DebianKernel

thanks for your report.

-- 
maks


--- End Message ---

Reply via email to