Re: [Xen-devel] Xenalyze questions

[Simon Graham <simon.graham@xxxxxxxxxx>]

> > init_pcpus: through first trace write, done for now.
> > hvm_generic_postprocess_init: Strange, h->postprocess set!
> 
> Hmm, it looks like this is the problem here.
> 
> Can you try adding this patch, and then running the following?
> 
> xenalyze -a -s --tolerance=1 [filename] > [filename.dump]?
> 
> The resulting file may be pretty big; I'll just need the last 50 or so lines.
> 

Actually it was pretty small - must be the 1st record that is bad!

Tolerating errors at or below 1
scan_for_new_pcpu: Activating pcpu 0 at offset 0
Creating vcpu 0 for dom 32768
scan_for_new_pcpu: Activating pcpu 1 at offset 1560
Creating vcpu 1 for dom 32768
scan_for_new_pcpu: Activating pcpu 2 at offset 1772
Creating vcpu 2 for dom 32768
scan_for_new_pcpu: Activating pcpu 3 at offset 68428
Creating vcpu 3 for dom 32768
scan_for_new_pcpu: Activating pcpu 5 at offset 68520
Creating vcpu 5 for dom 32768
scan_for_new_pcpu: Activating pcpu 10 at offset 73632
Creating vcpu 10 for dom 32768
scan_for_new_pcpu: Activating pcpu 11 at offset 90588
Creating vcpu 11 for dom 32768
init_pcpus: through first trace write, done for now.
]               .... .    x. d32768v10 vmexit exit_reason EXCEPTION_NMI eip 
fffff88005a25ad0
]               .... .    x. d32768v10 fast mmio va fffff88008808df0
]               .... .    x. d32768v10 cpuid [ 1 206c2 400800 83b82203 178bfbff 
]
hvm_generic_postprocess_init: Strange, h->postprocess set!

Simon


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel