WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Re: Guests stops at "Sending DHCP requests ..."

To: xen-users@xxxxxxxxxxxxxxxxxxx, Flavio <fbcyborg@xxxxxxxxx>
Subject: Re: [Xen-users] Re: Guests stops at "Sending DHCP requests ..."
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Sun, 22 Nov 2009 02:23:15 -0800 (PST)
Cc:
Delivery-date: Sun, 22 Nov 2009 02:24:10 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1258885395; bh=QfE0nsaovK7z8Ut2Ohb5QIJZa0NZbavigRKZbKr6zIg=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=HcF5Eq60uKmCqZMWJOWs5i9begx5dWa43lmrg9iM9jXGCEa3e83aIkdyKYdEasjPF+odeluihrnHbkkX9kGGPmt0X2ZVcbF9tEvge1DOf/XhCi6r5R2OKF51MOC0QJjl5wiv7xXJOst7rKICGh6c5447qXlfNgYYncuf+DapaZA=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=bIRdn+R4hjjkCCy9/05AxQR8efgNitFafWyAe/bpoqtq1+9Bs4UmljQN2hQOiyVN9G4GuJfs+ASixSmurIiJuZL9Fmp81YgvtBpGxapIt1WasVFe+Cpt8GgOQWnMztqdbeXh29aQNruOlxjofdQkZskn7J64eK0DrDNiKPHZvV0=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <d75259650911220143i2de9a15bj79fbd99b5930adba@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>This is what happens running tcpdump during the above message appears
>(Sending DHCP requests).
> Here we go:

Usually i ran :-
# tcpdump -vv -s 1600 | tee log
DHCPDISCOVER sends UDP packets.
I cannot see in the report CHECKSUMS diagnostics.

    Been working with Solaris Nevada DomUs (build < 100 ) at Linux Xen Dom0
i always caught wrong UDP checksums during DHCP request from DomUs.
But not Linux, Linux.

> in my case is my ADSL modem router, and
> it always worked for VM guest, and it actually works if I boot a
> VirtualBox guest or whatever PC is connected to the LAN.

Anyway, i would try to disable checksum offloading just for one DomU. Bad checksum
causes packet to be discarded at your router (ADSL modem).

Boris.

--- On Sun, 11/22/09, Flavio <fbcyborg@xxxxxxxxx> wrote:

From: Flavio <fbcyborg@xxxxxxxxx>
Subject: Re: [Xen-users] Re: Guests stops at "Sending DHCP requests ..."
To: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Sunday, November 22, 2009, 4:43 AM

Hi all, and thank you for the reply.

2009/11/22 Ata E Husain <ata.husain@xxxxxxxxxxx>:
> Can you check are you on the network that supports DHCP protocol. I ran in
> to the same problem and found network does not support DHCP.
If you refer to the DHCP server of my real local (physical) area
network the answer is yes.
My DHCP server works like a charm, without any doubt.

> You can try to deactivate DHCP and use some static IP configuration like:
> config file, add this line (replace)
> dhcp = "no"
> vif = ['ip=xxx.xxx.xxx.xxx'] , use what ever IP you want for your domain.
>
Yes, I've just tried it, but it still remain here for a lot of time:
[    4.671098] Sending DHCP requests ...
[   17.040081] ..
I guess something really strange happened to my xen hypervisor.

2009/11/22 Boris Derzhavets <bderzhavets@xxxxxxxxx>
>
> I would run tcpdump somewhere on the LAN ( it's broadcast request) to check
> UDP checksums propagated via Dom0 Ethernet interface.
This is what happens running tcpdump during the above message appears
(Sending DHCP requests).
Here we go:

10:38:44.756297 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
BOOTP/DHCP, Request from 00:16:3e:14:48:41 (oui Unknown), length 548
10:38:45.254567 arp who-has 192.168.1.100 tell 192.168.1.254
10:38:46.254549 arp who-has 192.168.1.100 tell 192.168.1.254
10:38:47.090291 IP6 fe80::216:3eff:fe14:4841 > ff02::2: ICMP6, router
solicitation, length 16
10:38:48.102845 arp who-has 192.168.1.100 tell 192.168.1.254
10:38:48.287299 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
BOOTP/DHCP, Request from 00:16:3e:14:48:41 (oui Unknown), length 548
10:38:48.572881 IP 192.168.1.103.56185 > fx-in-f17.1e100.net.https: .
962638484:962639902(1418) ack 1384000022 win 501 <nop,nop,timestamp
368176 1775246387>
10:38:48.572911 IP 192.168.1.103.56185 > fx-in-f17.1e100.net.https: P
1418:1685(267) ack 1 win 501 <nop,nop,timestamp 368176 1775246387>
10:38:48.573080 IP 192.168.1.103.54102 > nst.tin.it.domain: 28478+
PTR? 17.39.125.74.in-addr.arpa. (43)
10:38:48.660315 IP fx-in-f17.1e100.net.https > 192.168.1.103.56185: .
ack 1685 win 832 <nop,nop,timestamp 1775255999 368176>
10:38:48.664230 IP nst.tin.it.domain > 192.168.1.103.54102: 28478 1/4/1 (174)
10:38:48.724724 IP fx-in-f17.1e100.net.https > 192.168.1.103.56185: P
1:374(373) ack 1685 win 832 <nop,nop,timestamp 1775256062 368176>
10:38:48.724816 IP 192.168.1.103.56185 > fx-in-f17.1e100.net.https: .
ack 374 win 501 <nop,nop,timestamp 368214 1775256062>
10:38:48.725552 IP fx-in-f17.1e100.net.https > 192.168.1.103.56185: P
374:411(37) ack 1685 win 832 <nop,nop,timestamp 1775256062 368176>
10:38:48.725568 IP 192.168.1.103.56185 > fx-in-f17.1e100.net.https: .
ack 411 win 501 <nop,nop,timestamp 368214 1775256062>
10:38:49.099514 arp who-has 192.168.1.100 tell 192.168.1.254
10:38:49.466312 IP6 fe80::216:3eff:fe14:4841 > ff02::16: HBH ICMP6,
multicast listener report v2, 1 group record(s), length 28
10:38:50.099481 arp who-has 192.168.1.100 tell 192.168.1.254
10:38:51.090296 IP6 fe80::216:3eff:fe14:4841 > ff02::2: ICMP6, router
solicitation, length 16

2009/11/22 Geert Janssens <info@xxxxxxxxxxxx>:
> This may not be related to your problem, but I'll mention it anyway.
>
> I had some DHCP problems a while ago as well. DomU's would not receive their
> ip address, while physical hosts did.
>
> In my case it turned out that I hadn't configured my DHCP server as
> authoritative (this is an option in the dhcpd.conf file). After setting that
> parameter, everything worked fine.
>
> Did you check your dhcpd log already (on CentOS this is logged to
> /var/log/messages) ? Is the dhcpd server receiving the requests ? If not, it's
> definitely another problem than mine...

Thank you Geert, but the DHCP server, in my case is my ADSL modem router, and
it always worked for VM guest, and it actually works if I boot a
VirtualBox guest or
whatever PC is connected to the LAN.

Thank you so much,

Flavio

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users