[Xen-users] Xen crash unexpectedly

[noh4ooqu@xxxxxxxxxxxx]

Hello,

Sometimes, randomly and with no clues, I see one of my VM crashing.
Can you give me a hint to prevent this from happening again ?
Here the details of the machine and the crash.

Configuration :

Debian GNU/Linux 5.0 
Linux hostname 2.6.26-2-xen-686 #1 SMP i686 GNU/Linux
# cat /etc/apt/sources.list
deb http://ftp.us.debian.org/debian/ lenny main contrib non-free
deb-src http://ftp.us.debian.org/debian/ lenny main contrib non-free

deb http://security.debian.org/ lenny/updates main contrib
deb-src http://security.debian.org/ lenny/updates main contrib

# xm li
Name                                    ID   Mem VCPUs      State   
Time(s)
Domain-0                                0  8978    16     r-----  
32910.5
vm1                                     5  4000     4     r-----   
8350.4
vm2                                     3  2500     4     -b---- 
129496.6

Issue :

vm1 crashed a few hours ago, it was started at the same time as 
vm2, I've not 
found any clue in the vm's log, only a crash report with `xm dmesg' 
(see bellow for the output).
It happens randomly, not always on the same machine...

The vm1 has the following line in the configuration file, 
clocksource is not present in vm2's one, 
is there a possible relation between this and the crash ?

extra = 'console=hvc0 xencons=tty clocksource=jiffies'

xm dmesg (truncated) : 

(XEN) domain_crash_sync called from entry.S (ff188600)
(XEN) Domain 4 (vcpu#0) crashed on cpu#5:
(XEN) ----[ Xen-3.2-1  x86_32p  debug=n  Not tainted ]----
(XEN) CPU:    5
(XEN) EIP:    0061:[<c01013a7>]
(XEN) EFLAGS: 00000246   CONTEXT: guest
(XEN) eax: 00000000   ebx: 00000001   ecx: 00000000   edx: c0389fc8
(XEN) esi: 00000000   edi: 00000000   ebp: 00000000   esp: c0389fbc
(XEN) cr0: 8005003b   cr4: 000026f0   cr3: 001acca0   cr2: b7e327b0
(XEN) ds: 007b   es: 007b   fs: 00d8   gs: 0000   ss: 0069   cs: 
0061
(XEN) Guest stack trace from esp=c0389fbc:
(XEN)    c0105f52 ffffffff 00000000 0bd17883 0007c648 00000000 
00000020 ffffffff
(XEN)    c01028ab c0102810 00000020 c1810000 00000000 c038f88b 
c03ac580 17100800
(XEN)    00000000 c038f5c3 c038f5cb c038f5d3 c0102374 c010263c 
c01027c8 c0102981
(XEN)    c0102fd7 c0102ff8 c0103480 c0103520 c0103609 c0103a81 
c0103b3d c0103bfa
(XEN)    c0103c59 c0103d03 c01042f9 c010430c c0104332 c010433f 
c01043db c0104999
(XEN)    c0104a5c c010506c c01050ec c01051bc c0105ebf c0105eff 
c0105f58 c0106238
(XEN)    c0106323 c010664a c0106a80 c0106be4 c039453d c0394546 
c0108085 c0108093
(XEN)    c0108108 c0108116 c0395faf c0395fc2 c01085ef c0108679 
c010934c c0109547
(XEN)    c0109572 c010957b c010985d c0109865 c010a3ae c010a425 
c010a434 c010a468
(XEN)    c010a4a2 c010a4ab c010a4b4 c02c5fb1 c02c6155 c02c61ac 
c02c61cc c02c6392
(XEN)    c02c6456 c02c687e c03962cb c03962d3 c02c6da5 c0396429 
c0396432 c039643b
(XEN)    c0396444 c0396453 c039645c c039646b c0396474 c02c6e85 
c02c6eee c02c7051
(XEN)    c02c70c7 c02c7121 c02c7127 c02c7365 c02c73ab c02c7423 
c02c7433 c02c74af
(XEN)    c02c74c3 c02c75d0 c02c75e1 c02c75e8 c02c7767 c02c79f6 
c02c7bdd c02c7c2e
(XEN)    c02c7cce c02c7cd3 c02c7ce1 c02c7e14 c02c7e29 c02c807e 
c02c80cb c02c8153
(XEN)    c02c8174 c02c825b c02c826a c02c8279 c02c829a c02c82a9 
c010b59e c010b5c7
(XEN)    c010b5ef c010bbad c010bbe0 c010bc47 c010bc9d c010bccf 
c010bd07 c010bd91
(XEN)    c010be10 c010be59 c010c0e7 c039753b c039755e c039798f 
c010ce93 c010de56
(XEN)    c039867c c03986a3 c0398797 c0398a78 c010e3f9 c010f656 
c010fec4 c0110fb9
(XEN)    c0110fc3 c01111ba c01111c4 c01116a8 c0111a69 c0111ab0 
c0111b39 c0111cba

xm log (truncated) : 

[2009-12-14 17:20:52 4054] DEBUG (DevController:151) Waiting for 
devices vtpm.
[2009-12-14 17:20:52 4054] INFO (XendDomain:1165) Domain vm1 (4) 
unpaused.
[2009-12-27 23:00:39 4054] WARNING (XendDomainInfo:1258) Domain has 
crashed: name=vm1 id=4.
[2009-12-27 23:00:39 4054] DEBUG (XendDomainInfo:1914) 
XendDomainInfo.destroyDomain(4)
[2009-12-27 23:00:40 4054] DEBUG (XendDomainInfo:1529) Destroying 
device model
[2009-12-27 23:00:40 4054] DEBUG (XendDomainInfo:1536) Releasing 
devices

Then it tries to restart vm1 unsuccessfully, but this is not my 
current issue.
Is it related to Xen or to the pvm guest ?

I look forward to read your answers.
Thanks in advance.

// Franck.


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