[Xen-devel] 答复: 答复: 答复: Help: a xen crash of 4.8.2 version/////答复: Is there a faster way to restore Virtual machine status in Xen?

["Chenjia (C)" <chenjia09@xxxxxxxxxx>]

Dear Juergen:
        Now we are test project on 2 servers, Both 2 servers have the same 
configuration, but one server is install xen4.8.2 with dom0 linux kernel 
version 4.4.103-92.56-default, the other server is xen 4.8.3 with dom0 linux 
kernel 4.4.121-92.85-default. 
        the server (xen 4.8.3 with dom0 linux kernel 4.4.121-92.85-default) is 
blocked again,  and we got some information by your way, please help us to see 
what the problem maybe, thank you!

Best regards

-----邮件原件-----
发件人: Juergen Gross [mailto:jgross@xxxxxxxx] 
发送时间: 2018年7月5日 13:17
收件人: Chenjia (C) <chenjia09@xxxxxxxxxx>; Jan Beulich <JBeulich@xxxxxxxx>
抄送: zhaobingjian <zhaobingjian@xxxxxxxxxx>; Shentao (Terry) 
<shentao8@xxxxxxxxxx>; Yaoshaomin <yaoshaomin@xxxxxxxxxx>; Zhuxiaolin (A) 
<zhuxiaolin09@xxxxxxxxxx>; wangxu (R) <wangxu0@xxxxxxxxxx>; xen-devel 
<xen-devel@xxxxxxxxxxxxxxxxxxxx>; yuanjinfeng <yuanjinfeng@xxxxxxxxxx>
主题: Re: 答复: [Xen-devel] 答复: Help: a xen crash of 4.8.2 version/////答复: Is there 
a faster way to restore Virtual machine status in Xen?

On 05/07/18 05:51, Chenjia (C) wrote:
> Dear Juergen:
>       Thank your for your help, Here are the message:
> - which kernel version?
> 1、The "xl info " information is:
> 
> host                   : linux
> release                : 4.4.103-92.56-default
> version                : #1 SMP Wed Dec 27 16:24:31 UTC 2017 (2fd2155)
> machine                : x86_64
> nr_cpus                : 24
> max_cpu_id             : 23
> nr_nodes               : 2
> cores_per_socket       : 6
> threads_per_core       : 2
> cpu_mhz                : 2394
> hw_caps                : 
> b7ebfbff:77fef3f7:2c100800:00000021:00000001:000037ab:00000000:00000100
> virt_caps              : hvm hvm_directio
> total_memory           : 261749
> free_memory            : 14127
> sharing_freed_memory   : 0
> sharing_used_memory    : 0
> outstanding_claims     : 0
> free_cpus              : 0
> xen_major              : 4
> xen_minor              : 8
> xen_extra              : .2
> xen_version            : 4.8.2
> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
> hvm-3.0-x86_32p hvm-3.0-x86_64 
> xen_scheduler          : credit
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : 
> xen_commandline        : dom0_mem=174080M,max:174080M dom0_max_vcpus=24 
> hap_1gb=false hap_2mb=false altp2m=1 flask_enforcing=1 console=vga,com1 
> com1=115200 loglvl=all
> cc_compiler            : gcc (SUSE Linux) 4.8.5
> cc_compile_by          : root
> cc_compile_domain      : (none)
> cc_compile_date        : Thu Mar 29 17:42:36 CST 2018
> build_id               : c73cb12afb1a2c2cfc09eb5035d7576b1eb071e9
> xend_config_format     : 4
> 
> 2、the "uname -a " information is:
> Linux linux 4.4.103-92.56-default #1 SMP Wed Dec 27 16:24:31 UTC 2017 
> (2fd2155) x86_64 x86_64 x86_64 GNU/Linux
> 
> - is this in dom0 or in a domU (if domU: HVM or PV)?
>       In Dom0, our domU run windows7 OS. 
> 
> - from the messages in guess the system is hanging, not crashed?
>       the whole server is hanging and can not be connected or operate anyway.
> - what are the other vcpus of the domain doing (how to get this info
>   is depending on the dom0/domU question above)?
>       the whole server is hanging and can not be connected. 

Looking at xen_commandline you seem to have a serial console connected.

When the machine is hanging, please issue ctrl-A three times to switch the 
console from dom0 to Xen.

Then type '0' (just the digit zero) to get the dom0 vcpu state (please do that 
multiple times in order to see which vcpus are in loops).

Then send the log obtained via the serial line for further diagnosis. It will 
help if you translate the obvious kernel addresses of the hex stack dumps of 
the vcpus to symbol+offset using the kernel symbol table.


Juergen

Attachment: info.txt
Description: info.txt

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel