These patches "fix" the problem. However, they may not apply cleanly to
HEAD and they definitely are not cleanly implemented.

https://gem5-review.googlesource.com/c/public/gem5/+/7362
https://gem5-review.googlesource.com/c/public/gem5/+/7361

Cheers,
Jason

On Wed, Feb 7, 2018 at 8:49 PM Da Zhang <d...@vt.edu> wrote:

> I am trying to run fs.py with kvm support which might help speedup
> our simulation in full system mode. I find the cpu type X86KvmCPU which is
> a "kvm-based hardware virtualized cpu". But running fs.py failed with the
> error information:
>
> panic: KVM: Failed to enter virtualized mode (hw reason: 0x80000021)
>
> Memory Usage: 2416600 KBytes
>
> Program aborted at tick 53418967500
>
> --- BEGIN LIBC BACKTRACE ---
>
> build/X86/gem5.fast(_Z15print_backtracev+0x1f)[0xaee60f]
>
> build/X86/gem5.fast(_Z12abortHandleri+0x34)[0xaee6f4]
>
> /lib64/libpthread.so.0(+0xf5e0)[0x7f5b9ac685e0]
>
> /lib64/libc.so.6(gsignal+0x37)[0x7f5b9901c1f7]
>
> /lib64/libc.so.6(abort+0x148)[0x7f5b9901d8e8]
>
> build/X86/gem5.fast[0x6627df]
>
> build/X86/gem5.fast[0x95d518]
>
> build/X86/gem5.fast(_ZN10BaseKvmCPU13handleKvmExitEv+0x249)[0xc10859]
>
> build/X86/gem5.fast[0xbade3c]
>
> build/X86/gem5.fast(_ZN10EventQueue10serviceOneEv+0x91)[0xad4fc1]
>
> build/X86/gem5.fast(_Z9doSimLoopP10EventQueue+0xa0)[0xb5b110]
>
> build/X86/gem5.fast(_Z8simulatem+0x1f3)[0xb5b563]
>
> build/X86/gem5.fast[0x93867d]
>
> build/X86/gem5.fast[0x939c65]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x730a)[0x7f5b9a56b0ca]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7f5b9a56cefd]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x663c)[0x7f5b9a56a3fc]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x67bd)[0x7f5b9a56a57d]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x67bd)[0x7f5b9a56a57d]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7f5b9a56cefd]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalCode+0x32)[0x7f5b9a56d002]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5513)[0x7f5b9a5692d3]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7f5b9a56cefd]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x663c)[0x7f5b9a56a3fc]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7f5b9a56cefd]
>
> /lib64/libpython2.7.so.1.0(PyEval_EvalCode+0x32)[0x7f5b9a56d002]
>
> /lib64/libpython2.7.so.1.0(+0x10043f)[0x7f5b9a58643f]
>
> /lib64/libpython2.7.so.1.0(PyRun_StringFlags+0x65)[0x7f5b9a5872a5]
>
> build/X86/gem5.fast(_Z6m5MainiPPc+0x5f)[0xad327f]
>
> build/X86/gem5.fast(main+0x33)[0x5ddf23]
>
> /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f5b99008c05]
>
> build/X86/gem5.fast[0x5df8fc]
>
> --- END LIBC BACKTRACE ---
>
> Aborted (core dumped)
>
> the command is as simple as:
>
> build/X86/gem5.fast -d ~/tmp/output1/ configs/example/fs.py --mem-size=2GB
> --disk-image=linux-x86.img --cpu-type=X86KvmCPU
>
> Any idea? thanks in advance.
>
> best,
> Da
>
> _______________________________________________
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to