DomU stuck on "Sending DHCP request"

DomU stuck on "Sending DHCP request"

[Puthiyaparambil, Aravindh]

I am trying to bring a DomU with networking on x86_64 Xen on a Dell
PowerEdge 470 (2x 2GB RAM SLES9 SP2). The DomU is stuck on "Sending DHCP
requests". If I turn off networking I am able to bring up DomUs. DHCP is
working on the subnet otherwise. Any idea why this is happening?

Thanks
Aravindh 

xen_net: Initialising virtual ethernet driver.
xen_net: Using grant tables.
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 16Kbytes
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
=> Sending DHCP requests ......

Re: DomU stuck on "Sending DHCP request"

[Nivedita Singhvi]

Puthiyaparambil, Aravindh wrote:
> I am trying to bring a DomU with networking on x86_64 Xen on a Dell
> PowerEdge 470 (2x 2GB RAM SLES9 SP2). The DomU is stuck on "Sending DHCP
> requests". If I turn off networking I am able to bring up DomUs. DHCP is
> working on the subnet otherwise. Any idea why this is happening?

What do you mean DHCP is working on the subnet otherwise?
Are you saying once you boot without networking, DHCP works?
This is just probably a race condition between getting networking
up and sending out a DHCP request. Can you put in some tracing
in the startup scripts?  Not sure which version of Xen SLES9 SP2
runs (was it 2.0.6?)

thanks,
Nivedita


> Thanks
> Aravindh 
> 
> xen_net: Initialising virtual ethernet driver.
> xen_net: Using grant tables.
> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> NET: Registered protocol family 2
> IP: routing cache hash table of 1024 buckets, 16Kbytes
> TCP established hash table entries: 16384 (order: 6, 262144 bytes)
> TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
> TCP: Hash tables configured (established 16384 bind 16384)
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> => Sending DHCP requests ......
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 

RE: DomU stuck on "Sending DHCP request"

[Puthiyaparambil, Aravindh]

I am seeing a lot of errors in the log. This one is while the DomU is
coming up.

[2005-09-09 18:05:48 xend] ERROR (XendDomainInfo:443) ['vif', ['mac',
'aa:00:00:3b:dc:43']]


Aravindh


 
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + set -e
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
OP=start
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + shift
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + export
bridge=xen-br0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
bridge=xen-br0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + export
antispoof=no
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
antispoof=no
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
bridge=xen-br0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
netdev=eth0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
antispoof=no
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + echo
'*network start bridge=xen-br0 netdev=eth0 antispoof=no'
[2005-09-09 18:05:30 xend] INFO (process:35) [network-bridge] network
start bridge=xen-br0 netdev=eth0 antispoof=no
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
op_start
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + '['
xen-br0 == null ']'
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
create_bridge xen-br0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + local
bridge=xen-br0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + brctl
show
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + grep -q
xen-br0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + brctl
addbr xen-br0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + brctl
stp xen-br0 off
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + brctl
setfd xen-br0 0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
ifconfig xen-br0 up
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
ifconfig
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + grep -q
veth0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
ifconfig veth0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + grep -q
veth0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] ++
ifconfig eth0
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] ++ grep
HWadd
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] ++ sed -e
's/.*\(..:..:..:..:..:..\).*/\1/'
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] +
mac=00:12:3F:34:9B:D9
[2005-09-09 18:05:30 xend] ERROR (process:37) [network-bridge] + ifdown
eth0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + ip link
set eth0 name peth0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + ip link
set veth0 name eth0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] +
ifconfig peth0 0.0.0.0 -arp down
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] +
ifconfig peth0 hw ether fe:ff:ff:ff:ff:ff
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] +
ifconfig eth0 hw ether 00:12:3F:34:9B:D9
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] +
add_to_bridge xen-br0 vif0.0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + local
bridge=xen-br0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + local
dev=vif0.0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + brctl
show
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + grep -q
vif0.0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + brctl
addif xen-br0 vif0.0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] +
add_to_bridge xen-br0 peth0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + local
bridge=xen-br0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + local
dev=peth0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + brctl
show
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + grep -q
peth0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + brctl
addif xen-br0 peth0
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + ip link
set xen-br0 up
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + ip link
set vif0.0 up
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + ip link
set peth0 up
[2005-09-09 18:05:31 xend] ERROR (process:37) [network-bridge] + ifup
eth0
[2005-09-09 18:05:48 xend] DEBUG (image:156) initDomain: cpu=-1
mem_kb=262144 ssidref=-1 dom=1
[2005-09-09 18:05:48 xend] DEBUG (XendDomainInfo:843) init_domain>
Created domain=1 name=dom64_1 memory=256
[2005-09-09 18:05:48 xend] INFO (XendRoot:141) EVENT> xend.domain.create
['dom64_1', 1]
[2005-09-09 18:05:48 xend] INFO (image:217) buildDomain os=linux dom=1
vcpus=4
[2005-09-09 18:05:48 xend] DEBUG (image:255) dom            = 1
[2005-09-09 18:05:48 xend] DEBUG (image:256) image          =
/boot/vmlinuz-2.6-xenU
[2005-09-09 18:05:48 xend] DEBUG (image:257) store_evtchn   = 1
[2005-09-09 18:05:48 xend] DEBUG (image:258) console_evtchn = 2
[2005-09-09 18:05:48 xend] DEBUG (image:259) cmdline        =
ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 ro 3
[2005-09-09 18:05:48 xend] DEBUG (image:260) ramdisk        = 
[2005-09-09 18:05:48 xend] DEBUG (image:261) flags          = 0
[2005-09-09 18:05:48 xend] DEBUG (image:262) vcpus          = 4
[2005-09-09 18:05:48 xend] INFO (xsobj:326) DBMap>introduceDomain> 1
119629 <EventChannel dom1:0:16 dom2:1:1>
/domain/7b0182be-4858-405a-9bdc-be0a85c29cbb
[2005-09-09 18:05:48 xend] DEBUG (XendDomainInfo:698) writing key
availability=online to path /cpu/0 in store
[2005-09-09 18:05:48 xend] DEBUG (XendDomainInfo:698) writing key
availability=online to path /cpu/1 in store
[2005-09-09 18:05:48 xend] DEBUG (XendDomainInfo:698) writing key
availability=online to path /cpu/2 in store
[2005-09-09 18:05:48 xend] DEBUG (XendDomainInfo:698) writing key
availability=online to path /cpu/3 in store
[2005-09-09 18:05:48 xend] WARNING (XendDomainInfo:1100) Unknown config
field boot
[2005-09-09 18:05:48 xend] WARNING (XendDomainInfo:1100) Unknown config
field display
[2005-09-09 18:05:48 xend] ERROR (XendDomainInfo:443) ['vif', ['mac',
'aa:00:00:3b:dc:43']]
[2005-09-09 18:05:48 xend] INFO (XendRoot:141) EVENT>
xend.domain.unpause ['dom64_1', 1]
[2005-09-09 18:06:53 xend] DEBUG (XendDomain:465)
domain_restart_schedule> 1 halt 1
[2005-09-09 18:06:53 xend] INFO (XendDomain:478) Cancelling restart for
domain: name=dom64_1 id=1
[2005-09-09 18:06:53 xend] INFO (XendRoot:141) EVENT>
xend.domain.restart ['dom64_1', 1, 'cancel']
[2005-09-09 18:06:53 xend] INFO (XendDomain:507) Destroying domain:
name=dom64_1
[2005-09-09 18:06:53 xend] INFO (XendRoot:141) EVENT>
xend.domain.destroy ['dom64_1', 1]
[2005-09-09 18:06:54 xend] INFO (xsobj:337) DBMap>releaseDomain> 1
[2005-09-09 18:06:54 xend] INFO (xsobj:343) DBMap>releaseDomain> (2, 'No
such file or directory')

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Puthiyaparambil, Aravindh
> Sent: Friday, September 09, 2005 6:19 PM
> To: xen-devel
> Cc: Koren, Bradley J; Subrahmanian, Raj; Vessey, Bruce A
> Subject: [Xen-devel] DomU stuck on "Sending DHCP request"
> 
> I am trying to bring a DomU with networking on x86_64 Xen on a Dell
> PowerEdge 470 (2x 2GB RAM SLES9 SP2). The DomU is stuck on "Sending
DHCP
> requests". If I turn off networking I am able to bring up DomUs. DHCP
is
> working on the subnet otherwise. Any idea why this is happening?
> 
> Thanks
> Aravindh
> 
> xen_net: Initialising virtual ethernet driver.
> xen_net: Using grant tables.
> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> NET: Registered protocol family 2
> IP: routing cache hash table of 1024 buckets, 16Kbytes
> TCP established hash table entries: 16384 (order: 6, 262144 bytes)
> TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
> TCP: Hash tables configured (established 16384 bind 16384)
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> => Sending DHCP requests ......
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

RE: DomU stuck on "Sending DHCP request"

[Ian Pratt]

> I am trying to bring a DomU with networking on x86_64 Xen on 
> a Dell PowerEdge 470 (2x 2GB RAM SLES9 SP2). The DomU is 
> stuck on "Sending DHCP requests". If I turn off networking I 
> am able to bring up DomUs. DHCP is working on the subnet 
> otherwise. Any idea why this is happening?

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

ifconfig will give you some packet counts too.

Best,
Ian


> xen_net: Initialising virtual ethernet driver.
> xen_net: Using grant tables.
> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> NET: Registered protocol family 2
> IP: routing cache hash table of 1024 buckets, 16Kbytes TCP 
> established hash table entries: 16384 (order: 6, 262144 
> bytes) TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
> TCP: Hash tables configured (established 16384 bind 16384) 
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> => Sending DHCP requests ......
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

RE: DomU stuck on "Sending DHCP request"

[Puthiyaparambil, Aravindh]

> What do you mean DHCP is working on the subnet otherwise?

I meant to say that DHCP works on other physical machines on the
network.

> This is just probably a race condition between getting networking
> up and sending out a DHCP request. Can you put in some tracing
> in the startup scripts?  Not sure which version of Xen SLES9 SP2
> runs (was it 2.0.6?)

I am running xen-unstable 
changeset:   6714:41a74438bcba
tag:         tip
user:        shand@ubuntu.eng.hq.xensource.com
date:        Fri Sep  9 14:36:48 2005 -0800
summary:     Fix 'xm info' (sizeof(param) doesn't do that one might
hope).

> 
> thanks,
> Nivedita

RE: DomU stuck on "Sending DHCP request"

[Puthiyaparambil, Aravindh]

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@lists.xensource.com
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

RE: DomU stuck on "Sending DHCP request"

[Puthiyaparambil, Aravindh]

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

I did a 

tcpdump -I vifX.0 | grep DHCP
tcpdump -I peth0 | grep DHCP
tcpdump -I xen-br0 | grep DHCP

and I did not see any messages.

My other question is that should not DomU give up and continue booting
if it does not obtain an IP?

Thanks
Aravindh

RE: DomU stuck on "Sending DHCP request"

[Ian Pratt]

> My other question is that should not DomU give up and 
> continue booting if it does not obtain an IP?

Unless you're using NFS or iSCSI/gnbd root there's no need to get an IP
address in the kernel -- just use the normal distro startup scripts.
ip=off

Ian

RE: DomU stuck on "Sending DHCP request"

[Puthiyaparambil, Aravindh]

Ian,

Thanks. The distro startup scripts did the trick.

Aravindh

> -----Original Message-----
> From: Ian Pratt [mailto:m+Ian.Pratt@cl.cam.ac.uk]
> Sent: Friday, September 09, 2005 7:41 PM
> To: Puthiyaparambil, Aravindh; xen-devel
> Cc: Koren, Bradley J; Subrahmanian, Raj; Vessey, Bruce A;
> ian.pratt@cl.cam.ac.uk; Nivedita Singhvi; ian.pratt@cl.cam.ac.uk
> Subject: RE: [Xen-devel] DomU stuck on "Sending DHCP request"
> 
> > My other question is that should not DomU give up and
> > continue booting if it does not obtain an IP?
> 
> Unless you're using NFS or iSCSI/gnbd root there's no need to get an
IP
> address in the kernel -- just use the normal distro startup scripts.
> ip=off
> 
> Ian