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-devel

RE: [Xen-devel] DomU stuck on "Sending DHCP request"

To: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] DomU stuck on "Sending DHCP request"
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Fri, 9 Sep 2005 18:43:40 -0400
Cc: "Koren, Bradley J" <Bradley.Koren@xxxxxxxxxx>, "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>, "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx>
Delivery-date: Fri, 09 Sep 2005 22:47:26 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcW1jHHtLEtAZfemS8qf6zlVvGD7vgAAZuTwAAA/5GA=
Thread-topic: [Xen-devel] DomU stuck on "Sending DHCP request"
I also noticed that when I do an "xm destroy" on the domain sending out
the DHCP request, I get the following error when I do an "xm list". 

Unexpected error: xen.xend.XendProtocol.XendError

Please report to xen-devel@xxxxxxxxxxxxxxxxxxx
Traceback (most recent call last):
  File "/usr/sbin/xm", line 10, in ?
    main.main(sys.argv)
  File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xm/main.py"
, line 707, in main
    rc = cmd(args)
  File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xm/main.py"
, line 226, in xm_list
    doms = server.xend_domains()
  File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendCl
ient.py", line 199, in xend_domains
    return self.xendGet(self.domainurl())
  File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendCl
ient.py", line 152, in xendGet
    return self.client.xendGet(url, args)
  File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendPr
otocol.py", line 86, in xendGet
    return self.xendRequest(url, "GET", args)
  File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendPr
otocol.py", line 170, in xendRequest
    val = self.handleStatus(resp.version, resp.status, resp.reason)
  File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendPr
otocol.py", line 106, in handleStatus
    return self.handleException(XendError(message))
  File
"/root/xen/xen-unstable.hg/dist/install/usr/lib64/python/xen/xend/XendPr
otocol.py", line 132, in handleException
    raise err
xen.xend.XendProtocol.XendError: Internal server error


Thereafter xm works fine. But it always give me the error on the first
xm command after the "destroy".


I am getting the following output from tcpdump.

> 
> You could run 'tcpdump -I vifX.0' in dom0 on the appropriate vif to
see
> if packets are coming out.

tcpdump: WARNING: vif7.0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on vif7.0, link-type EN10MB (Ethernet), capture size 96 bytes
18:34:31.900480 802.1d unknown version
18:34:32.100218 802.1d unknown version
18:34:33.031626 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:34:33.230123 802.1d unknown version
18:34:34.146180 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:34:35.229988 802.1d unknown version
18:34:36.113436 arp who-has trsa-rtrport209.tr.unisys.com tell
nt-pub19-pr.tr.unisys.com
18:34:37.229973 802.1d unknown version
18:34:37.534388 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:34:39.142391 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:34:39.229954 802.1d unknown version
18:34:39.553378 arp who-has 192.63.209.83 tell
trsa-rtrport209.tr.unisys.com
18:34:39.553387 arp who-has 192.63.209.231 tell
trsa-rtrport209.tr.unisys.com
18:34:39.553610 arp who-has 192.63.209.232 tell
trsa-rtrport209.tr.unisys.com
18:34:39.553614 arp who-has 192.63.209.233 tell
trsa-rtrport209.tr.unisys.com
18:34:39.553752 arp who-has 192.63.209.234 tell
trsa-rtrport209.tr.unisys.com
18:34:39.554350 arp who-has 192.63.209.235 tell
trsa-rtrport209.tr.unisys.com
18:34:39.554357 arp who-has 192.63.209.241 tell
trsa-rtrport209.tr.unisys.com
18:34:39.554360 arp who-has 192.63.209.242 tell
trsa-rtrport209.tr.unisys.com
18:34:39.554364 arp who-has 192.63.209.243 tell
trsa-rtrport209.tr.unisys.com
18:34:39.554368 arp who-has 192.63.209.244 tell
trsa-rtrport209.tr.unisys.com
18:34:39.554601 arp who-has 192.63.209.245 tell
trsa-rtrport209.tr.unisys.com
18:34:40.143635 IP trsa-rtrport209.tr.unisys.com > DVMRP.MCAST.NET: igmp
dvmrp Probe
18:34:41.229949 802.1d unknown version
18:34:41.900142 802.1d unknown version
18:34:42.100021 802.1d unknown version
18:34:43.229812 802.1d unknown version
18:34:43.939736 IP USTR-stanultl.na.uis.unisys.com.netbios-dgm >
192.63.209.255.netbios-dgm: NBT UDP PACKET(138)
18:34:45.229800 802.1d unknown version
18:34:46.144849 IP trsa-rtrport209.tr.unisys.com >
ALL-SYSTEMS.MCAST.NET: igmp query v2
18:34:46.784183 arp who-has trpresti.tr.unisys.com tell
trsa-rtrport209.tr.unisys.com
18:34:47.229774 802.1d unknown version
18:34:49.229638 802.1d unknown version
18:34:49.416890 IP docserv03.na.uis.unisys.com.netbios-dgm >
192.63.209.255.netbios-dgm: NBT UDP PACKET(138)
18:34:49.724351 IP USTR-CAVANAET.na.uis.unisys.com.netbios-dgm >
192.63.209.255.netbios-dgm: NBT UDP PACKET(138)
18:34:50.143810 IP trsa-rtrport209.tr.unisys.com > DVMRP.MCAST.NET: igmp
dvmrp Probe
18:34:51.147058 IP 192.63.209.91 > 224.0.0.251: igmp v2 report
224.0.0.251
18:34:51.229615 802.1d unknown version
18:34:51.829618 IP 192.63.209.5.netbios-dgm >
192.63.209.255.netbios-dgm: NBT UDP PACKET(138)
18:34:51.899820 802.1d unknown version
18:34:52.099696 802.1d unknown version
18:34:52.901936 IP 192.63.209.116.netbios-dgm >
192.63.209.255.netbios-dgm: NBT UDP PACKET(138)
18:34:53.229599 802.1d unknown version
18:34:53.416989 arp who-has trprogp.tr.unisys.com tell
trsa-rtrport209.tr.unisys.com
18:34:53.691685 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:34:54.818978 IP 192.63.209.82 > 239.255.255.250: igmp v2 report
239.255.255.250
18:34:55.143146 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:34:55.229466 802.1d unknown version
18:34:57.229460 802.1d unknown version
18:34:57.298286 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:34:57.903655 IP USTR-GANISTJJ-2.na.uis.unisys.com.netbios-dgm >
192.63.209.255.netbios-dgm: NBT UDP PACKET(138)
18:34:59.145112 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:34:59.229438 802.1d unknown version
18:35:00.143003 IP trsa-rtrport209.tr.unisys.com > DVMRP.MCAST.NET: igmp
dvmrp Probe
18:35:01.229307 802.1d unknown version
18:35:01.421929 arp who-has cheetahwei.tr.unisys.com tell
trsa-rtrport209.tr.unisys.com
18:35:01.591447 IP 192.63.209.6.netbios-dgm >
192.63.209.255.netbios-dgm: NBT UDP PACKET(138)
18:35:01.899625 802.1d unknown version
18:35:01.991947 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:35:02.099499 802.1d unknown version
18:35:02.131479 IP nt-repro-pr.tr.unisys.com.netbios-dgm >
192.63.209.255.netbios-dgm: NBT UDP PACKET(138)
18:35:03.142597 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:35:03.229285 802.1d unknown version
18:35:05.229276 802.1d unknown version
18:35:05.474993 arp who-has 192.63.209.72 tell 192.63.209.102
18:35:06.013663 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:35:06.144583 IP trsa-rtrport209.tr.unisys.com >
ALL-SYSTEMS.MCAST.NET: igmp query v2
18:35:06.833128 IP 192.63.209.82 > 239.255.255.250: igmp v2 report
239.255.255.250
18:35:06.893217 arp who-has 192.63.209.46 tell
trsa-rtrport209.tr.unisys.com
18:35:07.145306 IP trsa-rtrport209.tr.unisys.com >
reserved-multicast-range-NOT-delegated.example.com: igmp query v2 [max
resp time 10] [gaddr reserved-multicast-range-NOT-delegated.example.com]
18:35:07.229254 802.1d unknown version
18:35:08.252237 (NOV-802.3) 00000000.00:04:00:08:74:d3.83c2 >
00000000.ff:ff:ff:ff:ff:ff.0452:ipx-sap-resp[|ipx 64]
18:35:09.229120 802.1d unknown version

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