|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] Kernel backwards compatibility
I'm using Xen 3.0.0 back from December last year. I downloaded and
compiled a new kernel (2.6.16.13 from Xen 3.0.2-testing) to use in my
domU. It crashed with the following log in xen dmesg:
(XEN) Domain 34 (vcpu#0) crashed on cpu#1:
(XEN) CPU: 1
(XEN) EIP: e019:[<c010000e>]
(XEN) EFLAGS: 00000246 CONTEXT: guest
(XEN) eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000000
(XEN) esi: c0468000 edi: 00000000 ebp: 00000000 esp: c03ddff4
(XEN) cr0: 8005003b cr3: 09bc3000
(XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019
(XEN) Guest stack trace from esp=c03ddff4:
(XEN) c010000e 0001e019 00010046
Any pointers? Or should I just upgrade my Xen and dom0 kernel too..
--
Regards,
wK (www.doubleukay.com)
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-users] Kernel backwards compatibility,
Woon Wai Keen @ doubleukay.com <=
|
|
|
|
|