On 01/02/18 10:14, Jan Beulich wrote:
On 01.02.18 at 08:29, wrote:
>> On 01/02/18 07:20, Zhang, Xiong Y wrote:
>>> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
>>> (XEN) [ Xen-4.11-unstable x86_64 debug=y Not tainted ]
>>> (XEN) CPU:0
>>> (XEN) RIP:e033:[]
>>> (XEN) RFLAGS: 0
>>> On 01.02.18 at 08:29, wrote:
> On 01/02/18 07:20, Zhang, Xiong Y wrote:
>> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
>> (XEN) [ Xen-4.11-unstable x86_64 debug=y Not tainted ]
>> (XEN) CPU:0
>> (XEN) RIP:e033:[]
>> (XEN) RFLAGS: 0292 EM: 1 CONTEXT: pv guest (
On 01/02/18 07:20, Zhang, Xiong Y wrote:
> This is the message with debug=y
> Xen 4.11-unstable
> (XEN) Xen version 4.11-unstable (test@) (gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4)
> 5.4.0 20160609) debug=y Tue Jan 30 02:38:14 CST 2018
> (XEN) Latest ChangeSet: Wed Jan 24 12:01:55 2018 + git:1252e2
e -f -e vmlinux 8281ba11
xen_start_kernel
arch/x86/xen/enlighten_pv.c:1264
All the other are data address, not code address.
thanks
> -Original Message-
> From: Juergen Gross [mailto:jgr...@suse.com]
> Sent: Tuesday, January 30, 2018 6:01 PM
> To: Zhang, Xio
On 30/01/18 01:33, Zhang, Xiong Y wrote:
> The message is really short. Dom0 error happens before the first kernel
> message:
>
> ▒ Xen 4.11-unstable
> (XEN) Xen version 4.11-unstable (test@) (gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4)
> 5.4.0 20160609) debug=n Tue Jan 30 02:38:14 CST 2018
Aah, just
hed: rebooting machine in 5 seconds.
(XEN) APIC error on CPU0: 40(00)
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
thanks
> -Original Message-
> From: Juergen Gross [mailto:jgr...@suse.com]
> Sent: Monday, January 29, 2018 1:45 PM
> To: Zhang, Xiong Y ; Xen-devel
>
>
On 29/01/18 06:28, Zhang, Xiong Y wrote:
> Today I found xen 4.10 (or staging branch) with dom0 4.15 kernel, dom0
> couldn’t boot up and it print the following error, is it a known issue ?
Please post more information. Please add the following to the hypervisor
boot parameters:
loglvl=all guest_l
