thr3ads.net - Xen users - [Xen-users] Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors [Feb 2007]

If this information is useful, please help other people find it:
Share via:

Allen Brooker

2007-Feb-02 21:44 UTC

[Xen-users] Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

Hi all,

I''m having an annoying problem with Xen on a Dell PowerEdge 2500 (with 
disks configured for hardware RAID striping). Basically the dom0 starts 
and runs fine. I''ve also tried the Xen LiveCD 1.5 and that can boot 
debian dom0 and boot a debian domU perfectly fine. However, I just
can''t
get a domU to start from my install. I''ve tried all the versions of xen
from 3.0.2 up that I can get my hands on to no avail.

What happens is this: domU appears to start up, but never appears to 
attach to the console. If I stick the domU on preserve mode, I can see 
that the domU reportedly runs for 0.1 seconds before crashing. I cannot 
find any errors or messages anywhere to indicate why the domU crashes. I 
appear to get no output from the domU itself at all.

Below is the contents of /var/log/xend.log for the creation (and crash 
and destruction) of the domU.

Is there anyone running Xen on a Dell PowerEdge 2500 that might be able 
to send me their host and domU kernel configs?

I did have Xen running perfectly on a previous machine (which 
unfortunately died of an unknown hardware problem) and I''ve tried 
copying the kernel configs from that and using those with only the 
necessary modifications for the hardware of the new machine, all to no 
avail.

I also asked about this problem on #xen on OFTC and ##xen on Freenode 
for a week solid without any progress. If you want to talk to me, I can 
usually be found there (I''m a lazy bum of a university student, so
I''m
on most of the time during the British daytime).

I can''t think of any further information that might be useful at the 
moment - If you want to know something, just ask.

Thanks in advance,

AllenJB


xend.log:
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:178) 
XendDomainInfo.create([''domain'', [''domid'',
1], [''uuid'',
''b7a7d9c7-8140-0309-fb3b-a1e657930d22''],
[''ssidref'', 0], [''vcpus'', 1],
[''vcpu_avail'', 1], [''cpu_weight'', 1.0],
[''memory'', 256], [''maxmem'',
256], [''name'', ''ace''],
[''on_poweroff'', ''destroy''],
[''on_reboot'',
''restart''], [''on_crash'',
''restart''], [''image'',
[''linux'', [''kernel'',
''/boot-xen/kernel-linux-2.6.16.28-xen-r1''],
[''ip'',
'':1.2.3.4::::eth0:dhcp'']]], [''device'',
[''vbd'', [''backend'', 0],
[''dev'',
''sda6''], [''uname'',
''phy:sda6''], [''mode'',
''w'']]], [''device'', [''vbd'',
[''backend'', 0], [''dev'',
''sda7''], [''uname'',
''phy:sda7''], [''mode'',
''w'']]],
[''state'', ''----c-''],
[''shutdown_reason'', ''crash''],
[''cpu_time'',
0.079047243000000003], [''online_vcpus'', 1],
[''up_time'',
''1.71687698364''], [''start_time'',
''1170425428.88''], [''store_mfn'',
145660], [''console_mfn'', 145659]])
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:284) 
parseConfig: config is [''domain'', [''domid'',
1], [''uuid'',
''b7a7d9c7-8140-0309-fb3b-a1e657930d22''],
[''ssidref'', 0], [''vcpus'', 1],
[''vcpu_avail'', 1], [''cpu_weight'', 1.0],
[''memory'', 256], [''maxmem'',
256], [''name'', ''ace''],
[''on_poweroff'', ''destroy''],
[''on_reboot'',
''restart''], [''on_crash'',
''restart''], [''image'',
[''linux'', [''kernel'',
''/boot-xen/kernel-linux-2.6.16.28-xen-r1''],
[''ip'',
'':1.2.3.4::::eth0:dhcp'']]], [''device'',
[''vbd'', [''backend'', 0],
[''dev'',
''sda6''], [''uname'',
''phy:sda6''], [''mode'',
''w'']]], [''device'', [''vbd'',
[''backend'', 0], [''dev'',
''sda7''], [''uname'',
''phy:sda7''], [''mode'',
''w'']]],
[''state'', ''----c-''],
[''shutdown_reason'', ''crash''],
[''cpu_time'',
0.079047243000000003], [''online_vcpus'', 1],
[''up_time'',
''1.71687698364''], [''start_time'',
''1170425428.88''], [''store_mfn'',
145660], [''console_mfn'', 145659]]
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:380) 
parseConfig: result is {''ssidref'': 0,
''uuid'':
''b7a7d9c7-8140-0309-fb3b-a1e657930d22'',
''on_crash'': ''restart'',
''on_reboot'': ''restart'',
''image'': [''linux'',
[''kernel'',
''/boot-xen/kernel-linux-2.6.16.28-xen-r1''],
[''ip'',
'':1.2.3.4::::eth0:dhcp'']], ''on_poweroff'':
''destroy'', ''cpus'': None,
''name'': ''ace'', ''backend'':
[], ''vcpus'': 1, ''cpu_weight'': 1.0,
''vcpu_avail'': 1, ''memory'': 256,
''device'': [(''vbd'', [''vbd'',
[''backend'',
0], [''dev'', ''sda6''],
[''uname'', ''phy:sda6''],
[''mode'', ''w'']]), (''vbd'',
[''vbd'', [''backend'', 0],
[''dev'', ''sda7''], [''uname'',
''phy:sda7''], [''mode'',
''w'']])], ''bootloader'': None,
''cpu'': None, ''maxmem'': 256}
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164) 
XendDomainInfo.construct: None 0
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1196) 
XendDomainInfo.initDomain: 2 1.0
[2007-02-02 14:10:30 xend] DEBUG (balloon:130) Balloon: free 31; need 257.
[2007-02-02 14:10:30 xend] DEBUG (balloon:139) Balloon: setting dom0 
target to 519.
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:945) 
Setting memory target of domain Domain-0 (0) to 519 MiB.
[2007-02-02 14:10:30 xend] DEBUG (balloon:139) Balloon: setting dom0 
target to 541.
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:945) 
Setting memory target of domain Domain-0 (0) to 541 MiB.
[2007-02-02 14:10:31 xend] DEBUG (balloon:139) Balloon: setting dom0 
target to 572.
[2007-02-02 14:10:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:945) 
Setting memory target of domain Domain-0 (0) to 572 MiB.
[2007-02-02 14:10:31 xend] DEBUG (balloon:139) Balloon: setting dom0 
target to 620.
[2007-02-02 14:10:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:945) 
Setting memory target of domain Domain-0 (0) to 620 MiB.
[2007-02-02 14:10:31 xend] DEBUG (balloon:126) Balloon: free 382; need 
257; done.
[2007-02-02 14:10:31 xend] INFO (image:135) buildDomain os=linux dom=2 
vcpus=1
[2007-02-02 14:10:31 xend] DEBUG (image:173) dom            = 2
[2007-02-02 14:10:31 xend] DEBUG (image:174) image          = 
/boot-xen/kernel-linux-2.6.16.28-xen-r1
[2007-02-02 14:10:31 xend] DEBUG (image:175) store_evtchn   = 1
[2007-02-02 14:10:31 xend] DEBUG (image:176) console_evtchn = 2
[2007-02-02 14:10:31 xend] DEBUG (image:177) cmdline        = 
ip=:1.2.3.4::::eth0:dhcp
[2007-02-02 14:10:31 xend] DEBUG (image:178) ramdisk        [2007-02-02 14:10:31
xend] DEBUG (image:179) vcpus          = 1
[2007-02-02 14:10:31 xend] DEBUG (image:180) features       [2007-02-02 14:10:32
xend] DEBUG (DevController:103) DevController:
writing {''virtual-device'': ''2054'',
''backend-id'': ''0'',
''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/2/2054''} to
/local/domain/2/device/vbd/2054.
[2007-02-02 14:10:32 xend] DEBUG (DevController:105) DevController: 
writing {''domain'': ''ace'',
''frontend'':
''/local/domain/2/device/vbd/2054'',
''dev'': ''sda6'', ''state'':
''1'', ''params'': ''sda6'',
''mode'': ''w'',
''frontend-id'': ''2'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/2/2054.
[2007-02-02 14:10:32 xend] DEBUG (DevController:103) DevController: 
writing {''virtual-device'': ''2055'',
''backend-id'': ''0'',
''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/2/2055''} to
/local/domain/2/device/vbd/2055.
[2007-02-02 14:10:32 xend] DEBUG (DevController:105) DevController: 
writing {''domain'': ''ace'',
''frontend'':
''/local/domain/2/device/vbd/2055'',
''dev'': ''sda7'', ''state'':
''1'', ''params'': ''sda7'',
''mode'': ''w'',
''frontend-id'': ''2'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/2/2055.
[2007-02-02 14:10:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:671) 
Storing VM details: {''ssidref'': ''0'',
''uuid'':
''b7a7d9c7-8140-0309-fb3b-a1e657930d22'',
''on_reboot'': ''restart'',
''start_time'': ''1170425432.11'',
''on_poweroff'': ''destroy'',
''name'': ''ace'',
''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''256'',
''on_crash'': ''restart'',
''image'': ''(linux (kernel
/boot-xen/kernel-linux-2.6.16.28-xen-r1) (ip
:1.2.3.4::::eth0:dhcp))'', ''maxmem'':
''256''}
[2007-02-02 14:10:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:696) 
Storing domain details: {''console/ring-ref'':
''75642'', ''console/port'':
''2'', ''name'': ''ace'',
''console/limit'': ''1048576'',
''vm'':
''/vm/b7a7d9c7-8140-0309-fb3b-a1e657930d22'',
''domid'': ''2'',
''cpu/0/availability'': ''online'',
''memory/target'': ''262144'',
''store/ring-ref'': ''75643'',
''store/port'': ''1''}
[2007-02-02 14:10:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:877) 
XendDomainInfo.handleShutdownWatch
[2007-02-02 14:10:32 xend.XendDomainInfo] WARNING (XendDomainInfo:819) 
Domain has crashed: name=ace id=2.
[2007-02-02 14:10:32 xend.XendDomainInfo] ERROR (XendDomainInfo:1467) VM 
ace restarting too fast (1.973117 seconds since the last restart). 
Refusing to restart to avoid loops.
[2007-02-02 14:10:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327) 
XendDomainInfo.destroy: domid=2
[2007-02-02 14:10:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335) 
XendDomainInfo.destroyDomain(2)

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

Allen Brooker

2007-Feb-03 10:13 UTC

head link

[Xen-users] Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

Hi all,

I''m having an annoying problem with Xen on a Dell PowerEdge 2500 (with
disks configured for hardware RAID striping). Basically the dom0 starts
and runs fine. I''ve also tried the Xen LiveCD 1.5 and that can boot
debian dom0 and boot a debian domU perfectly fine. However, I just
can''t
get a domU to start from my install. I''ve tried all the versions of xen
from 3.0.2 up that I can get my hands on to no avail.

What happens is this: domU appears to start up, but never appears to
attach to the console. If I stick the domU on preserve mode, I can see
that the domU reportedly runs for 0.1 seconds before crashing. I cannot
find any errors or messages anywhere to indicate why the domU crashes. I
appear to get no output from the domU itself at all.

Below is the contents of /var/log/xend.log for the creation (and crash
and destruction) of the domU.

Is there anyone running Xen on a Dell PowerEdge 2500 that might be able
to send me their host and domU kernel configs?

I did have Xen running perfectly on a previous machine (which
unfortunately died of an unknown hardware problem) and I''ve tried
copying the kernel configs from that and using those with only the
necessary modifications for the hardware of the new machine, all to no
avail.

I also asked about this problem on #xen on OFTC and ##xen on Freenode
for a week solid without any progress. If you want to talk to me, I can
usually be found there (I''m a lazy bum of a university student, so
I''m
on most of the time during the British daytime).

I can''t think of any further information that might be useful at the
moment - If you want to know something, just ask.

Thanks in advance,

AllenJB


xend.log:
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:178)
XendDomainInfo.create([''domain'', [''domid'',
1], [''uuid'',
''b7a7d9c7-8140-0309-fb3b-a1e657930d22''],
[''ssidref'', 0], [''vcpus'', 1],
[''vcpu_avail'', 1], [''cpu_weight'', 1.0],
[''memory'', 256], [''maxmem'',
256], [''name'', ''ace''],
[''on_poweroff'', ''destroy''],
[''on_reboot'',
''restart''], [''on_crash'',
''restart''], [''image'',
[''linux'', [''kernel'',
''/boot-xen/kernel-linux-2.6.16.28-xen-r1''],
[''ip'',
'':1.2.3.4::::eth0:dhcp'']]], [''device'',
[''vbd'', [''backend'', 0],
[''dev'',
''sda6''], [''uname'',
''phy:sda6''], [''mode'',
''w'']]], [''device'', [''vbd'',
[''backend'', 0], [''dev'',
''sda7''], [''uname'',
''phy:sda7''], [''mode'',
''w'']]],
[''state'', ''----c-''],
[''shutdown_reason'', ''crash''],
[''cpu_time'',
0.079047243000000003], [''online_vcpus'', 1],
[''up_time'',
''1.71687698364''], [''start_time'',
''1170425428.88''], [''store_mfn'',
145660], [''console_mfn'', 145659]])
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:284)
parseConfig: config is [''domain'', [''domid'',
1], [''uuid'',
''b7a7d9c7-8140-0309-fb3b-a1e657930d22''],
[''ssidref'', 0], [''vcpus'', 1],
[''vcpu_avail'', 1], [''cpu_weight'', 1.0],
[''memory'', 256], [''maxmem'',
256], [''name'', ''ace''],
[''on_poweroff'', ''destroy''],
[''on_reboot'',
''restart''], [''on_crash'',
''restart''], [''image'',
[''linux'', [''kernel'',
''/boot-xen/kernel-linux-2.6.16.28-xen-r1''],
[''ip'',
'':1.2.3.4::::eth0:dhcp'']]], [''device'',
[''vbd'', [''backend'', 0],
[''dev'',
''sda6''], [''uname'',
''phy:sda6''], [''mode'',
''w'']]], [''device'', [''vbd'',
[''backend'', 0], [''dev'',
''sda7''], [''uname'',
''phy:sda7''], [''mode'',
''w'']]],
[''state'', ''----c-''],
[''shutdown_reason'', ''crash''],
[''cpu_time'',
0.079047243000000003], [''online_vcpus'', 1],
[''up_time'',
''1.71687698364''], [''start_time'',
''1170425428.88''], [''store_mfn'',
145660], [''console_mfn'', 145659]]
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:380)
parseConfig: result is {''ssidref'': 0,
''uuid'':
''b7a7d9c7-8140-0309-fb3b-a1e657930d22'',
''on_crash'': ''restart'',
''on_reboot'': ''restart'',
''image'': [''linux'',
[''kernel'',
''/boot-xen/kernel-linux-2.6.16.28-xen-r1''],
[''ip'',
'':1.2.3.4::::eth0:dhcp'']], ''on_poweroff'':
''destroy'', ''cpus'': None,
''name'': ''ace'', ''backend'':
[], ''vcpus'': 1, ''cpu_weight'': 1.0,
''vcpu_avail'': 1, ''memory'': 256,
''device'': [(''vbd'', [''vbd'',
[''backend'',
0], [''dev'', ''sda6''],
[''uname'', ''phy:sda6''],
[''mode'', ''w'']]), (''vbd'',
[''vbd'', [''backend'', 0],
[''dev'', ''sda7''], [''uname'',
''phy:sda7''], [''mode'',
''w'']])], ''bootloader'': None,
''cpu'': None, ''maxmem'': 256}
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164)
XendDomainInfo.construct: None 0
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:1196)
XendDomainInfo.initDomain: 2 1.0
[2007-02-02 14:10:30 xend] DEBUG (balloon:130) Balloon: free 31; need 257.
[2007-02-02 14:10:30 xend] DEBUG (balloon:139) Balloon: setting dom0
target to 519.
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:945)
Setting memory target of domain Domain-0 (0) to 519 MiB.
[2007-02-02 14:10:30 xend] DEBUG (balloon:139) Balloon: setting dom0
target to 541.
[2007-02-02 14:10:30 xend.XendDomainInfo] DEBUG (XendDomainInfo:945)
Setting memory target of domain Domain-0 (0) to 541 MiB.
[2007-02-02 14:10:31 xend] DEBUG (balloon:139) Balloon: setting dom0
target to 572.
[2007-02-02 14:10:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:945)
Setting memory target of domain Domain-0 (0) to 572 MiB.
[2007-02-02 14:10:31 xend] DEBUG (balloon:139) Balloon: setting dom0
target to 620.
[2007-02-02 14:10:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:945)
Setting memory target of domain Domain-0 (0) to 620 MiB.
[2007-02-02 14:10:31 xend] DEBUG (balloon:126) Balloon: free 382; need
257; done.
[2007-02-02 14:10:31 xend] INFO (image:135) buildDomain os=linux dom=2
vcpus=1
[2007-02-02 14:10:31 xend] DEBUG (image:173) dom            = 2
[2007-02-02 14:10:31 xend] DEBUG (image:174) image         
/boot-xen/kernel-linux-2.6.16.28-xen-r1
[2007-02-02 14:10:31 xend] DEBUG (image:175) store_evtchn   = 1
[2007-02-02 14:10:31 xend] DEBUG (image:176) console_evtchn = 2
[2007-02-02 14:10:31 xend] DEBUG (image:177) cmdline       
ip=:1.2.3.4::::eth0:dhcp
[2007-02-02 14:10:31 xend] DEBUG (image:178) ramdisk        [2007-02-02 14:10:31
xend] DEBUG (image:179) vcpus          = 1
[2007-02-02 14:10:31 xend] DEBUG (image:180) features       [2007-02-02 14:10:32
xend] DEBUG (DevController:103) DevController:
writing {''virtual-device'': ''2054'',
''backend-id'': ''0'',
''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/2/2054''} to
/local/domain/2/device/vbd/2054.
[2007-02-02 14:10:32 xend] DEBUG (DevController:105) DevController:
writing {''domain'': ''ace'',
''frontend'':
''/local/domain/2/device/vbd/2054'',
''dev'': ''sda6'', ''state'':
''1'', ''params'': ''sda6'',
''mode'': ''w'',
''frontend-id'': ''2'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/2/2054.
[2007-02-02 14:10:32 xend] DEBUG (DevController:103) DevController:
writing {''virtual-device'': ''2055'',
''backend-id'': ''0'',
''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/2/2055''} to
/local/domain/2/device/vbd/2055.
[2007-02-02 14:10:32 xend] DEBUG (DevController:105) DevController:
writing {''domain'': ''ace'',
''frontend'':
''/local/domain/2/device/vbd/2055'',
''dev'': ''sda7'', ''state'':
''1'', ''params'': ''sda7'',
''mode'': ''w'',
''frontend-id'': ''2'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/2/2055.
[2007-02-02 14:10:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:671)
Storing VM details: {''ssidref'': ''0'',
''uuid'':
''b7a7d9c7-8140-0309-fb3b-a1e657930d22'',
''on_reboot'': ''restart'',
''start_time'': ''1170425432.11'',
''on_poweroff'': ''destroy'',
''name'': ''ace'',
''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''256'',
''on_crash'': ''restart'',
''image'': ''(linux (kernel
/boot-xen/kernel-linux-2.6.16.28-xen-r1) (ip
:1.2.3.4::::eth0:dhcp))'', ''maxmem'':
''256''}
[2007-02-02 14:10:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:696)
Storing domain details: {''console/ring-ref'':
''75642'', ''console/port'':
''2'', ''name'': ''ace'',
''console/limit'': ''1048576'',
''vm'':
''/vm/b7a7d9c7-8140-0309-fb3b-a1e657930d22'',
''domid'': ''2'',
''cpu/0/availability'': ''online'',
''memory/target'': ''262144'',
''store/ring-ref'': ''75643'',
''store/port'': ''1''}
[2007-02-02 14:10:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
XendDomainInfo.handleShutdownWatch
[2007-02-02 14:10:32 xend.XendDomainInfo] WARNING (XendDomainInfo:819)
Domain has crashed: name=ace id=2.
[2007-02-02 14:10:32 xend.XendDomainInfo] ERROR (XendDomainInfo:1467) VM
ace restarting too fast (1.973117 seconds since the last restart).
Refusing to restart to avoid loops.
[2007-02-02 14:10:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327)
XendDomainInfo.destroy: domid=2
[2007-02-02 14:10:32 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335)
XendDomainInfo.destroyDomain(2)


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

Henning Sprang

2007-Feb-03 12:42 UTC

head link

Re: [Xen-users] Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

On 2/3/07, Allen Brooker <allen@allenjb.me.uk>
wrote:> Below is the contents of /var/log/xend.log for the creation (and crash
> and destruction) of the domU.
As far as my experience goes, xend.log is almost always useless to
help with finding problems (as long as you''re nmot very deep into the
details of the python code).
What does xend-debug.log and xen-hotplug.log say?

Henning

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

Allen Brooker (AllenJB)

2007-Feb-03 13:22 UTC

head link

[Xen-users] Re: Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

Henning Sprang wrote:> On 2/3/07, Allen Brooker <allen@allenjb.me.uk> wrote:
>> Below is the contents of /var/log/xend.log for the creation (and crash
>> and destruction) of the domU.
> 
> As far as my experience goes, xend.log is almost always useless to
> help with finding problems (as long as you''re nmot very deep into
the
> details of the python code).
> What does xend-debug.log and xen-hotplug.log say?
> 
> Henning
Previously these files had been giving me no messages at all (so I had 
kind of stopped checking them), but...

It seems that my last set of changes actually got me further than I 
thought - The last time I changed my domU kernel (which was to use the 
config file from the xen livecd) I forgot to change the domU''s config 
file (in /etc/xen) to point to the new kernel. I''ve now corrected this 
and for the first time on this machine I''m getting kernel output from 
the domU - granted it''s not about to mount the root filesystem, but I 
suspect I can sort this out from here.

It''s still both annoying and weird that previously I''ve been
getting no
kernel output at all and no messages to tell me why the domU has crashed 
after 0.1 seconds. If this happens again, is there anything I can do to 
try to find out what''s going wrong?

AllenJB

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

Henning Sprang

2007-Feb-03 13:52 UTC

head link

Re: [Xen-users] Re: Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

On 2/3/07, Allen Brooker (AllenJB) <allen@allenjb.me.uk>
wrote:> It''s still both annoying and weird that previously I''ve
been getting no
> kernel output at all and no messages to tell me why the domU has crashed
> after 0.1 seconds. If this happens again, is there anything I can do to
> try to find out what''s going wrong?
That is indeed strange. I have no other idea but the one mentioned -
look in other log files.
I''m not sure is trying to use the config from the demo cd is a good
idea.
Better just start with the examp,e configs from /etc/xen

Henning

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

Allen Brooker (AllenJB)

2007-Feb-03 13:56 UTC

head link

[Xen-users] Re: Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

Henning Sprang wrote:> On 2/3/07, Allen Brooker (AllenJB) <allen@allenjb.me.uk> wrote:
>> It''s still both annoying and weird that previously
I''ve been getting no
>> kernel output at all and no messages to tell me why the domU has
crashed
>> after 0.1 seconds. If this happens again, is there anything I can do to
>> try to find out what''s going wrong?
> 
> That is indeed strange. I have no other idea but the one mentioned -
> look in other log files.
> I''m not sure is trying to use the config from the demo cd is a
good idea.
> Better just start with the examp,e configs from /etc/xen
> 
> HenningNot that it particularly matters, but I actually meant kernel config - 
sorry if I wasn''t clear.

AllenJB


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

Xen users - Feb 2007 - Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

[Xen-users] Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

[Xen-users] Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

Re: [Xen-users] Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

[Xen-users] Re: Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

Re: [Xen-users] Re: Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

[Xen-users] Re: Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors