[Xen-bugs] [Bug 431] Starting Xen disconnects machine from network

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=431





------- Additional Comments From jacquesb@xxxxxxxxx  2005-12-07 07:18 -------
(In reply to comment #11)
> Try doing a xend start again, making sure that loglevel=DEBUG in your
> xend-config.sxp file (/etc/xen). The debug log is /var/log/xend-debug.log.

There are absolutely no funny things in the log after I set loglevel to debug.

Here is the complete startup from the log when I start xend.

[2005-12-07 07:07:52 xend.XendDomainInfo] DEBUG (XendDomainInfo:198)
XendDomainInfo.recreate({'paused': 0, 'cpu_time': 11725409307L, 'ssidref': 0,
'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason':
0, 'dying': 0, 'dom': 0, 'mem_kb': 262144, 'maxmem_kb': -4, 'max_vcpu_id': 3,
'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 4, 'blocked': 0})
[2005-12-07 07:07:52 xend.XendDomainInfo] INFO (XendDomainInfo:210) Recreating
domain 0, UUID 00000000-00000000-00000000-00000000.
[2005-12-07 07:07:52 xend.XendDomainInfo] WARNING (XendDomainInfo:232) No vm
path in store for existing domain 0
[2005-12-07 07:07:52 xend.XendDomainInfo] DEBUG (XendDomainInfo:655) Storing VM
details: {'ssidref': '0', 'uuid': '00000000-00000000-00000000-00000000',
'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0', 'vcpus':
'4', 'vcpu_avail': '15', 'memory': '256', 'on_crash': 'restart', 'maxmem': 
'256'}
[2005-12-07 07:07:52 xend.XendDomainInfo] DEBUG (XendDomainInfo:680) Storing
domain details: {'cpu/1/availability': 'online', 'cpu/3/availability': 'online',
'name': 'Domain-0', 'console/limit': '1048576', 'cpu/2/availability': 'online',
'vm': '/vm/00000000-00000000-00000000-00000000', 'domid': '0',
'cpu/0/availability': 'online', 'memory/target': '262144'}
[2005-12-07 07:07:52 xend] DEBUG (XendDomain:151) number of vcpus to use is 0
[2005-12-07 07:07:52 xend] INFO (SrvServer:112) unix 
path=/var/lib/xend/xend-socket

Maybe you can see something interesting in that.

I fixed the broadcast address, that didn't fix the problem though, but it got me
thingking whether it actually talks to the network.

I setup tcpdump on another machine, and tried to ping it, all I see is a load of
arp request, which it answers:

tcpdump -n -i eth0 -vv host 10.43.234.101
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
08:57:35.260980 arp who-has 10.43.234.108 tell 10.43.234.101
08:57:35.261119 arp reply 10.43.234.108 is-at 00:0d:60:c9:80:fe
08:57:36.260863 arp who-has 10.43.234.108 tell 10.43.234.101
08:57:36.260893 arp reply 10.43.234.108 is-at 00:0d:60:c9:80:fe
08:57:37.260798 arp who-has 10.43.234.108 tell 10.43.234.101

But when I look on 101 (the machine running Xend) it never shows a complete arp
table, it's like it never recieves the who-has from 108.

Any pointers to fix this ?


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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