Ed W
2006-Feb-11 19:50 UTC
[Xen-users] Xend crashes repeatedly starting DomU - please help...
Hi, this is a repost of a previous question - since then I have tried
rebuilding my Xen0 kernel numerous times and trying different
configurations, but I haven''t yet ever got a single DomU to boot so I
really don''t even know what is supposed to happen, let alone how to
start debugging it...
Can someone please speculate on how to debug this further? It''s a
gentoo hardened base build. I turned off the hardened compiler to build
the Xen0 kernel and the Xend demon, but all I get is a Sig11 every time
I try and start the new domain!! This is a brand new Dell server and it
has recompiled a lot of stuff (the whole installation several times!)
absolutely flawlessly so I don''t suspect any hardware problems
Are there any gentoo users here please who could at least note down some
basic steps that they took so I can at least try and get a ttylinux
domain running!!
Cheers
Ed W
>>>>>> Prev Message >>>>>>
Hi, I have booted into a Dom0 kernel on a fairly stripped down machine
just running the basics needed. However, I haven''t yet managed to get
a
DomU booting. I constantly get the following error "Error: Received
invalid response from Xend, twice." on trying to start the domain
Where do I actually look to try and debug this further? I do have
SELinux compiled in on this kernel, but it''s in non-enforcing mode
nn1 xen # xm create -c ttylinux
Using config file "ttylinux".
Error: Received invalid response from Xend, twice.
nn1 xen # xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 125 2 r----- 641.6
Domain-16 16 64 1 --p--- 0.0
nn1 xen # more ttylinux
kernel = "/boot/vmlinuz-2.6.12.6-xenU"
memory = 64
name = "ttylinux"
vif = [ '''' ]
ip = "80.77.245.163"
disk = [''file:/tmp/ttylinux/ttylinux-xen/rootfs,sda1,w'']
root = "/dev/sda1 ro"
nn1 xen # ls /tmp/ttylinux/ttylinux-xen
/tmp/ttylinux/ttylinux-xen
/var/log/xend says:
[2006-02-09 15:20:48 xend.XendDomainInfo] DEBUG (XendDomainInfo:177)
XendDomainInfo.create([''vm'', [''name'',
''ttylinux''], [''memory'',
''64''],
[''vcpus'', ''1''], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6.12.6-xenU''], [''ip'',
''80.77.245.163:1.2.3.4::::eth0:off''],
[''root'', ''/dev/sda1 ro'']]],
[''device'', [''vbd'',
[''uname'',
''file:/tmp/ttylinux/ttylinux-xen''], [''dev'',
''sda1''], [''mode'', ''w'']]],
[''device'', [''vif'']]])
[2006-02-09 15:20:48 xend.XendDomainInfo] DEBUG (XendDomainInfo:282)
parseConfig: config is [''vm'', [''name'',
''ttylinux''], [''memory'',
''64''],
[''vcpus'', ''1''], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6.12.6-xenU''], [''ip'',
''80.77.245.163:1.2.3.4::::eth0:off''],
[''root'', ''/dev/sda1 ro'']]],
[''device'', [''vbd'',
[''uname'',
''file:/tmp/ttylinux/ttylinux-xen''], [''dev'',
''sda1''], [''mode'', ''w'']]],
[''device'', [''vif'']]]
[2006-02-09 15:20:48 xend.XendDomainInfo] DEBUG (XendDomainInfo:376)
parseConfig: result is {''ssidref'': None,
''uuid'': None, ''on_crash'': None,
''on_reboot'': None, ''image'':
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6.12.6-xenU''], [''ip'',
''80.77.245.163:1.2.3.4::::eth0:off''],
[''root'', ''/dev/sda1 ro'']],
''on_poweroff'': None, ''cpus'': None,
''name'': ''ttylinux'',
''backend'': [],
''vcpus'': 1, ''cpu_weight'': None,
''vcpu_avail'': None, ''memory'': 64,
''device'': [(''vbd'', [''vbd'',
[''uname'',
''file:/tmp/ttylinux/ttylinux-xen''],
[''dev'', ''sda1''], [''mode'',
''w'']]), (''vif'', [''vif''])],
''bootloader'': None,
''cpu'': None, ''maxmem'': None}
[2006-02-09 15:20:48 xend.XendDomainInfo] DEBUG (XendDomainInfo:1130)
XendDomainInfo.construct: None 0
[2006-02-09 15:20:48 xend.XendDomainInfo] DEBUG (XendDomainInfo:1162)
XendDomainInfo.initDomain: 16 1.0
[2006-02-09 15:20:48 xend] DEBUG (balloon:84) Balloon: free 1895; need
65; done.
[2006-02-09 15:20:48 xend] INFO (image:133) buildDomain os=linux dom=16
vcpus=1
[2006-02-09 15:20:48 xend] DEBUG (image:171) dom = 16
[2006-02-09 15:20:48 xend] DEBUG (image:172) image
/boot/vmlinuz-2.6.12.6-xenU
[2006-02-09 15:20:48 xend] DEBUG (image:173) store_evtchn = 1
[2006-02-09 15:20:48 xend] DEBUG (image:174) console_evtchn = 2
[2006-02-09 15:20:48 xend] DEBUG (image:175) cmdline
ip=80.77.245.163:1.2.3.4::::eth0:off root=/dev/sda1 ro
[2006-02-09 15:20:48 xend] DEBUG (image:176) ramdisk [2006-02-09 15:20:48
xend] DEBUG (image:177) vcpus = 1
[2006-02-09 15:20:48 xend] CRITICAL (SrvDaemon:190) Xend died due to
signal 11! Restarting it.
[2006-02-09 15:20:48 xend] INFO (SrvDaemon:278) Xend Daemon started
[2006-02-09 15:20:48 xend] INFO (SrvDaemon:282) Xend changeset: Tue Jan
31 11:04:12 2006 +0100 8738:eff96462fde8.
[2006-02-09 15:20:48 xend.XendDomainInfo] DEBUG (XendDomainInfo:199)
XendDomainInfo.recreate({''paused'': 0,
''cpu_time'': 640829708489L,
''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'': 128000,
''maxmem_kb'': -4, ''max_vcpu_id'': 1,
''crashed'': 0, ''running'': 1,
''shutdown'': 0, ''online_vcpus'': 2,
''blocked'': 0})
[2006-02-09 15:20:48 xend.XendDomainInfo] INFO (XendDomainInfo:211)
Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2006-02-09 15:20:48 xend] DEBUG (XendDomain:151) number of vcpus to use
is 0
[2006-02-09 15:20:48 xend.XendDomainInfo] DEBUG (XendDomainInfo:199)
XendDomainInfo.recreate({''paused'': 1,
''cpu_time'': 0L, ''ssidref'': 0,
''handle'': [95, 69, 121, 38, 202, 12, 213, 93, 246, 190, 23,
141, 252,
207, 203, 47], ''shutdown_reason'': 0,
''dying'': 0, ''dom'': 16,
''mem_kb'':
65536, ''maxmem_kb'': 65536, ''max_vcpu_id'': 0,
''crashed'': 0, ''running'': 0,
''shutdown'': 0, ''online_vcpus'': 1,
''blocked'': 0})
[2006-02-09 15:20:48 xend.XendDomainInfo] INFO (XendDomainInfo:211)
Recreating domain 16, UUID 5f457926-ca0c-d55d-f6be-178dfccfcb2f.
[2006-02-09 15:20:48 xend.XendDomainInfo] DEBUG (XendDomainInfo:663)
Storing VM details: {''ssidref'': ''0'',
''uuid'':
''5f457926-ca0c-d55d-f6be-178dfccfcb2f'',
''on_reboot'': ''restart'',
''image'':
''()'', ''on_poweroff'':
''destroy'', ''name'':
''Domain-16'', ''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''64'',
''on_crash'': ''restart'',
''maxmem'': ''64''}
[2006-02-09 15:20:48 xend.XendDomainInfo] DEBUG (XendDomainInfo:688)
Storing domain details: {''cpu/0/availability'':
''online'',
''memory/target'': ''65536'',
''name'': ''Domain-16'',
''console/limit'':
''1048576'', ''vm'':
''/vm/5f457926-ca0c-d55d-f6be-178dfccfcb2f'',
''domid'': ''16''}
[2006-02-09 15:20:48 xend] INFO (SrvServer:114) unix
path=/var/lib/xend/xend-socket
[2006-02-09 15:20:53 xend.XendDomainInfo] DEBUG (XendDomainInfo:177)
XendDomainInfo.create([''vm'', [''name'',
''ttylinux''], [''memory'',
''64''],
[''vcpus'', ''1''], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6.12.6-xenU''], [''ip'',
''80.77.245.163:1.2.3.4::::eth0:off''],
[''root'', ''/dev/sda1 ro'']]],
[''device'', [''vbd'',
[''uname'',
''file:/tmp/ttylinux/ttylinux-xen''], [''dev'',
''sda1''], [''mode'', ''w'']]],
[''device'', [''vif'']]])
[2006-02-09 15:20:53 xend.XendDomainInfo] DEBUG (XendDomainInfo:282)
parseConfig: config is [''vm'', [''name'',
''ttylinux''], [''memory'',
''64''], [''v
cpus'', ''1''], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6.12.6-xenU''], [''ip'',
''80.77.245.163:1.2.3.4::::eth0:off''],
[''root'', ''/dev/sda1 ro'']]],
[''device'', [''vbd'',
[''uname'',
''file:/tmp/ttylinux/ttylinux-xen''], [''dev'',
''sda1''], [''mode'', ''w'']]],
[''device'', [''vif'']]]
[2006-02-09 15:20:53 xend.XendDomainInfo] DEBUG (XendDomainInfo:376)
parseConfig: result is {''ssidref'': None,
''uuid'': None, ''on_crash'': None,
''on_reboot'': None, ''image'':
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6.12.6-xenU''], [''ip'',
''80.77.245.163:1.2.3.4::::eth0:off''],
[''root'', ''/dev/sda1 ro'']],
''on_poweroff'': None, ''cpus'': None,
''name'': ''ttylinux'',
''backend'': [],
''vcpus'': 1, ''cpu_weight'': None,
''vcpu_avail'': None, ''memory'': 64,
''device'': [(''vbd'', [''vbd'',
[''uname'',
''file:/tmp/ttylinux/ttylinux-xen''],
[''dev'', ''sda1''], [''mode'',
''w'']]), (''vif'', [''vif''])],
''bootloader'': None,
''cpu'': None, ''maxmem'': None}
[2006-02-09 15:20:53 xend.XendDomainInfo] DEBUG (XendDomainInfo:1130)
XendDomainInfo.construct: None 0
[2006-02-09 15:20:53 xend.XendDomainInfo] DEBUG (XendDomainInfo:1162)
XendDomainInfo.initDomain: 17 1.0
[2006-02-09 15:20:53 xend] DEBUG (balloon:84) Balloon: free 1831; need
65; done.
[2006-02-09 15:20:53 xend] INFO (image:133) buildDomain os=linux dom=17
vcpus=1
[2006-02-09 15:20:53 xend] DEBUG (image:171) dom = 17
[2006-02-09 15:20:53 xend] DEBUG (image:172) image
/boot/vmlinuz-2.6.12.6-xenU
[2006-02-09 15:20:53 xend] DEBUG (image:173) store_evtchn = 1
[2006-02-09 15:20:53 xend] DEBUG (image:174) console_evtchn = 2
[2006-02-09 15:20:53 xend] DEBUG (image:175) cmdline
ip=80.77.245.163:1.2.3.4::::eth0:off root=/dev/sda1 ro
[2006-02-09 15:20:53 xend] DEBUG (image:176) ramdisk [2006-02-09 15:20:53
xend] DEBUG (image:177) vcpus = 1
[2006-02-09 15:20:53 xend] CRITICAL (SrvDaemon:190) Xend died due to
signal 11! Restarting it.
[2006-02-09 15:20:53 xend] INFO (SrvDaemon:278) Xend Daemon started
[2006-02-09 15:20:53 xend] INFO (SrvDaemon:282) Xend changeset: Tue Jan
31 11:04:12 2006 +0100 8738:eff96462fde8.
[2006-02-09 15:20:53 xend.XendDomainInfo] DEBUG (XendDomainInfo:199)
XendDomainInfo.recreate({''paused'': 0,
''cpu_time'': 641138787157L,
''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'': 128000,
''maxmem_kb'': -4, ''max_vcpu_id'': 1,
''crashed'': 0, ''running'': 1,
''shutdown'': 0, ''online_vcpus'': 2,
''blocked'': 0})
[2006-02-09 15:20:53 xend.XendDomainInfo] INFO (XendDomainInfo:211)
Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2006-02-09 15:20:53 xend] DEBUG (XendDomain:151) number of vcpus to use
is 0
[2006-02-09 15:20:53 xend.XendDomainInfo] DEBUG (XendDomainInfo:199)
XendDomainInfo.recreate({''paused'': 1,
''cpu_time'': 0L, ''ssidref'': 0,
''handle'': [95, 69, 121, 38, 202, 12, 213, 93, 246, 190, 23,
141, 252,
207, 203, 47], ''shutdown_reason'': 0,
''dying'': 0, ''dom'': 16,
''mem_kb'':
65536, ''maxmem_kb'': 65536, ''max_vcpu_id'': 0,
''crashed'': 0, ''running'': 0,
''shutdown'': 0, ''online_vcpus'': 1,
''blocked'': 0})
[2006-02-09 15:20:53 xend.XendDomainInfo] INFO (XendDomainInfo:211)
Recreating domain 16, UUID 5f457926-ca0c-d55d-f6be-178dfccfcb2f.
[2006-02-09 15:20:53 xend.XendDomainInfo] DEBUG (XendDomainInfo:199)
XendDomainInfo.recreate({''paused'': 1,
''cpu_time'': 0L, ''ssidref'': 0,
''handle'': [95, 69, 121, 38, 202, 12, 213, 93, 246, 190, 23,
141, 252,
207, 203, 47], ''shutdown_reason'': 0,
''dying'': 0, ''dom'': 17,
''mem_kb'':
65536, ''maxmem_kb'': 65536, ''max_vcpu_id'': 0,
''crashed'': 0, ''running'': 0,
''shutdown'': 0, ''online_vcpus'': 1,
''blocked'': 0})
[2006-02-09 15:20:53 xend.XendDomainInfo] INFO (XendDomainInfo:211)
Recreating domain 17, UUID 5f457926-ca0c-d55d-f6be-178dfccfcb2f.
[2006-02-09 15:20:53 xend] ERROR (XendDomain:209) Failed to recreate
information for domain 17. Destroying it in the hope of recovery.
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line
203, in refresh
self._add_domain(
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 235, in recreate
vm = XendDomainInfo(xeninfo, domid, dompath, True, priv)
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 433, in __init__
self.validateInfo()
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 561, in validateInfo
self.check_name(self.info[''name''])
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1118, in check_name
raise VmError("VM name ''%s'' is used in both domains
%d and %d" %
VmError: VM name ''Domain-16'' is used in both domains 17 and 16
[2006-02-09 15:20:53 xend] INFO (SrvServer:114) unix
path=/var/lib/xend/xend-socket
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Milan Holzäpfel
2006-Mar-03 20:08 UTC
[Xen-users] Re: Xend crashes repeatedly starting DomU - please help...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1> Hi, I have booted into a Dom0 kernel on a fairly stripped down machine > just running the basics needed. However, I haven''t yet managed to > get a DomU booting. I constantly get the following error "Error: > Received invalid response from Xend, twice." on trying to start the > domainI seem to have the same problem. It''s gentoo''s uClibc-hardened on x86_32 over here. (system with uClibc as its libc and security enhancements.) Output from # strace -s 256 -f -o str /etc/init.d/xend start & (output is put in the file called "str") [...] 12893 bind(18, {sa_family=AF_FILE, path="/var/lib/xend/xend-socket"}, 27) = 0 12893 listen(18, 5) = 0 12893 accept(18, <unfinished ...> [...] [ loads of old_mmap-ioctl-munmap-... calls from 12893 ] 12893 old_mmap(NULL, 4096, PROT_WRITE, MAP_SHARED, 8, 0) = 0xb75ad000 12893 ioctl(8, SNDCTL_DSP_SPEED or SOUND_PCM_READ_RATE, 0xbe9fbad8) = 0 12893 munmap(0xb75ad000, 4096) = 0 12893 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0) = 0xb75ad000 12893 ioctl(8, SNDCTL_DSP_SPEED or SOUND_PCM_READ_RATE, 0xbe9fbb08) = 0 12893 ioctl(8, SNDCTL_DSP_RESET, 0xbe9fbaf8) = 196608 12893 munmap(0xb75ad000, 4096) = 0 12893 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0) = 0xb75ad000 12893 ioctl(8, SNDCTL_DSP_SPEED or SOUND_PCM_READ_RATE, 0xbe9fbb08) = 0 12893 munmap(0xb75ad000, 4096) = 0 12893 mlock(0xbe9fccb8, 136) = 0 12893 ioctl(8, SNDCTL_DSP_RESET, 0xbe9fbaf8) = 0 12893 munlock(0xbe9fccb8, 136) = 0 12893 munmap(0xb75ae000, 4251648) = 0 12893 mlock(0xbe9fd8c8, 136) = 0 12893 ioctl(8, SNDCTL_DSP_RESET, 0xbe9fbaf8) = 0 12893 munlock(0xbe9fd8c8, 136) = 0 12893 rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0 12893 write(16, "\10\0\0\0\0\0\0\0\0\0\0\0\v\0\0\0", 16) = 16 12893 write(16, "17\0", 3) = 3 12893 write(16, "32451\0", 6) = 6 12893 write(16, "1\0", 2 <unfinished ...> 12890 <... read resumed> "\10\0\0\0\0\0\0\0\0\0\0\0\3\0\0\0", 16) = 16 12893 <... write resumed> ) = 2 12890 read(16, <unfinished ...> 12893 rt_sigprocmask(SIG_SETMASK, NULL, <unfinished ...> 12890 <... read resumed> "OK\0", 3) = 3 12893 <... rt_sigprocmask resumed> [RTMIN], 8) = 0 12890 kill(12893, SIGRTMIN <unfinished ...> 12893 rt_sigsuspend([] <unfinished ...> 12890 <... kill resumed> ) = 0 12893 --- SIGRTMIN (Unknown signal 32) @ 0 (0) --- 12890 read(16, <unfinished ...> 12893 <... rt_sigsuspend resumed> ) = -1 EINTR (Interrupted system call) 12893 sigreturn() = ? (mask now [RTMIN]) 12893 rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0 12893 --- SIGSEGV (Segmentation fault) @ 0 (0) --- 12892 <... accept resumed> 0xbebfecc8, [16]) = ? ERESTARTSYS (To be restarted) 12887 <... accept resumed> 0xbf3ff190, [110]) = ? ERESTARTSYS (To be restarted) 12888 <... accept resumed> 0xbf1ff190, [16]) = ? ERESTARTSYS (To be restarted) 12886 <... poll resumed> [{fd=5, events=POLLIN}], 1, 2000) = -1 EINTR (Interrupted system call) 12890 <... read resumed> 0x800c6590, 16) = ? ERESTARTSYS (To be restarted) 12889 +++ killed by SIGKILL +++ 12885 +++ killed by SIGKILL +++ 12892 +++ killed by SIGKILL +++ 12887 +++ killed by SIGKILL +++ 12888 +++ killed by SIGKILL +++ 12886 +++ killed by SIGKILL +++ 12890 +++ killed by SIGKILL +++ Because no process sent the kill signal, I thougt it could possibly be the stack-smashing-handler getting active. The gentoo''s glibc''s one printed a message when killing the process iirc, the gentoo''s uClibc''s doesn''t seem to do so, as xend doesn''t get killed at this specific location any longer after having recompiled Python with vanilla-gcc (with no SSP, that is). (On gentoo uclibc-hardened, you can verify that SSP isn''t used by a specific binary any longer by doing "readelf -a /usr/bin/python | grep stack_smash_handler", it doens''t show anything if SSP is off.) Now however xm says: | Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Yesssssssss... Regards, Milan (who is terribly happy that he can investigate in yet another error message from xend.... arg. I hate xend. haaaaaate.) (PS: I didn''t intend to provide useful information on the hotplug issue I''m encountering, so don''t spend time on it for now... but if you happen to have some tips ;) ) - -- Milan Holzaepfel <mail(a)mjh(d)name> <URL:http://mjh.name/> pub 4096R/C790FC23 EB8E 5E81 81E3 53A9 9B74 B895 5179 54C0 C790 FC23 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (GNU/Linux) iQIVAwUBRAiiI2GQ1TgKZKJkAQLyYw/+Klsw3zSN8Hz6y6yRu807IW3gWBc6O/S5 5ZkAPELnORUAkUDYj8RvoWhHTgnFUerT/dW3qDsJfDbqZdAgi5k1YeevPIZdWzVq A6wwLUygjo7T3jBwHzlgfvzk3jWjaU6DmCBf1xQU+zS6gYTTH8/jYZDFXA53AJHS p2Padc33VVzMXI9iFHs1bh5N2Mobdzfnmg+W8R+Tj6Yg28MRUSfqyohW3aL19PO9 r5QhrZfWS21qKpZvHnpg8VKp7SyYaV+tH3+eqEtRmBUqXNikE/iInhc3NN+8Y04f 02ueiw2n1Pqbrw0xUY0K6wCpHs1A8wnEMm3HeGvxEYu2mDWUxAqIEauo5qE1O4wA WG6ITgvVysZbOJOCjU3kBP6jAjebm3vWX3wF3yCApt1ma/289tOdeOII26Bm8Re0 31EX8DS0TEMHQxU4Gb6NjcVjJ4NAQFgrMUXao78VfhMLCFzHJ+71z84deG2TAUrR eTMlFN7IKwvGtA4td6gRn/Y7y1mU8E3p54ZDk31FjicRGy81hj8QXn0AjP5MPNiw FX8kvPXOGVIO1/V2YNTwN7SlL6IOmgpXBBiYZHc+rtwiioHBW1/HQDAII3y5jX3M Ns3qpl4IklkKCEJfNSBwqhrUSld9QZ0dQMGvtIXpqwgHYsasPwakVwRoq915VvB5 Nf/eWy+Ut4g=l248 -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Milan Holzäpfel
2006-Mar-03 21:02 UTC
[Xen-users] Re: Xend crashes repeatedly starting DomU - please help...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 3 Mar 2006 21:08:03 +0100 Milan Holzäpfel <listen@mjh.name> wrote:> > Hi, I have booted into a Dom0 kernel on a fairly stripped down > > machine just running the basics needed. However, I haven''t yet > > managed to get a DomU booting. I constantly get the following > > error "Error: Received invalid response from Xend, twice." on > > trying to start the domain > > I seem to have the same problem. It''s gentoo''s uClibc-hardened on > x86_32 over here. (system with uClibc as its libc and security > enhancements.)For completeness: my xend got killed by signal 9 (SIGKILL), whereas yours got killed by signal 11 (SIGSEGV, segmentation fault, "memory access error" I think), but this could be due to different versions of the stack smashing handler.> Now however xm says: > > | Error: Device 2049 (vbd) could not be connected. Hotplug scripts > | not working.I fixed this by replacing the udev I had installed with a working one (079 has never worked on ony of my other system here, which was 2.6.11- and is 2.6.12-based, but 070 works just fine. Xen-system kernel version is also 2.6.12). For details on this you may also consider <URL:http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=527> Regards, Milan PS: of course I still do hate xend. always will. ... - -- Milan Holzaepfel <mail(a)mjh(d)name> <URL:http://mjh.name/> pub 4096R/C790FC23 EB8E 5E81 81E3 53A9 9B74 B895 5179 54C0 C790 FC23 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (GNU/Linux) iQIVAwUBRAiu+mGQ1TgKZKJkAQLsuBAAw4AG8+Dg+ZmHepX2UW9egg0KxqDuF4JY 0E6cJR3uJb+91DOvIMlhm/ttuzClLURudFL9+f9XCLcwzkBqRvZgG6qZwNlnsDPG xpwthmxQhD2GCcYag6Nzp4mOEubE03WJ49WDzM5l7ptWpkM1rXoln9OpneBuieDt eZsvcxNW3LyHyFRnCccouA1bXMbx4N9LICM2nGafcG2qLYhrRdRQ9SnQU/hfHSfN 9lJouAXdULapIujUJMYva46QWmw9sVFRsYV6iiVOkGSv9c9g7UZGBXNXAGOEY0fZ C0hkicM+JiNkAGMysVzpBjzklhtdOZyibOd6VdRsNZlHJKrvTAc7FZB5QnGsAHBb GlGcBAkvPdA56j2myRflhpmpwhE4eJhy4kiI/MlcGd3CGJnieUW4RdMbhZjUGChG SQOgWxF+SJZZ5PE2MO7sInpdJUMJkDVRbSdGowh9LLD7VEMCa9oX8QOmFkdna5AS gSpN0zF4hxwbE2yxoIKfDFpsjY3Ogk57c+xpgTvRA+JRaqjIog9+FbYQnOz2vVD5 cRaE6nYfFeUxD9d9xgLXFTgxE8k/Zq4YidKjflWb2qJfFWVW3VERkvdloMBAl0uA rGtPMzTv0PW6TawFr3f86qYcF6Q6VajFCx6hRRMnjdXXpQuUJc8BSaYRb38qvZv5 0U9qyelMCdI=e8NP -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Reasonably Related Threads
- Problem with reboot of domU''s
- Bug#368417: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD
- [pakrat@private.neotoma.org: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD]
- NFS root on problem on Xen Debian
- Xen Starting DomainU:Error: Device 0 (vif) could not be connected. Hotplug scripts not working