Dear all, Just an update: I tried the develop version of gem5 to see if this error was fixed, and it looks like it still present.
I have run: > build/X86/gem5.opt configs/example/fs.py --disk-image=ubuntu_disk.img > --kernel=vmlinux_5.12 --cpu-type=X86KvmCPU -n 8 which boots correctly. I took a checkpoint and tried to restore it, but I get a segfault. Here is the output for gem5.debug: > build/X86/gem5.debug configs/example/fs.py > --disk-image=/local/home/mmarazzi/ubuntu_disk.img > --kernel=/local/home/mmarazzi/ubuntu_gem5/vmlinux_5.12 --cpu-type=X86KvmCPU > -n 8 -r 1 --restore-with-cpu=X86KvmCPU > build/X86/cpu/kvm/base.cc:152: info: KVM: Coalesced MMIO disabled by config. > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 2 > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 3 > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 4 > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 5 > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 6 > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 8 > build/X86/cpu/kvm/base.cc:152: info: KVM: Coalesced MMIO disabled by config. > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 2 > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 3 > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 4 > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 5 > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 6 > build/X86/arch/x86/cpuid.cc:181: warn: x86 cpuid family 0x0000: unimplemented > function 8 > build/X86/sim/simulate.cc:107: info: Entering event queue @ 89563256301500. > Starting simulation... > gem5 has encountered a segmentation fault! > > --- BEGIN LIBC BACKTRACE --- > build/X86/gem5.debug(+0xbfef71)[0x558a9b368f71] > build/X86/gem5.debug(+0xc474f6)[0x558a9b3b14f6] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x12980)[0x7f6d72b10980] > /lib/x86_64-linux-gnu/libpthread.so.0(pthread_kill+0x6)[0x7f6d72b0d386] > build/X86/gem5.debug(+0xe686a4)[0x558a9b5d26a4] > build/X86/gem5.debug(+0xe5f98d)[0x558a9b5c998d] > build/X86/gem5.debug(+0x5f14f0)[0x558a9ad5b4f0] > build/X86/gem5.debug(+0x5fa9bf)[0x558a9ad649bf] > build/X86/gem5.debug(+0x5f5b4e)[0x558a9ad5fb4e] > build/X86/gem5.debug(+0x5f2ef3)[0x558a9ad5cef3] > build/X86/gem5.debug(+0x5f64a4)[0x558a9ad604a4] > build/X86/gem5.debug(+0x1d3dae)[0x558a9a93ddae] > build/X86/gem5.debug(+0x1d1d20)[0x558a9a93bd20] > build/X86/gem5.debug(+0xc1191a)[0x558a9b37b91a] > build/X86/gem5.debug(+0xc6fd11)[0x558a9b3d9d11] > build/X86/gem5.debug(+0xc6f92d)[0x558a9b3d992d] > build/X86/gem5.debug(+0xd6944a)[0x558a9b4d344a] > build/X86/gem5.debug(+0xd676b8)[0x558a9b4d16b8] > build/X86/gem5.debug(+0xd63c1f)[0x558a9b4cdc1f] > build/X86/gem5.debug(+0xd63c86)[0x558a9b4cdc86] > build/X86/gem5.debug(+0xc2eade)[0x558a9b398ade] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(PyCFunction_Call+0x96)[0x7f6d72f30736] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(_PyEval_EvalFrameDefault+0x76e0)[0x7f6d72ea1b20] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(+0x17ba0f)[0x7f6d72e98a0f] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(+0x17c0fc)[0x7f6d72e990fc] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(_PyEval_EvalFrameDefault+0x4ec3)[0x7f6d72e9f303] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(+0x17a803)[0x7f6d72e97803] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(+0x17c2be)[0x7f6d72e992be] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(_PyEval_EvalFrameDefault+0x4ec3)[0x7f6d72e9f303] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(+0x17ba0f)[0x7f6d72e98a0f] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(+0x17c0fc)[0x7f6d72e990fc] > /usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0(_PyEval_EvalFrameDefault+0x4ec3)[0x7f6d72e9f303] Note, the checkpoint is correctly restored if a different CPU is used. This points me to believe that the same bug might be present. Has anyone successfully done a checkpoint and restored with KVM and 8 cores? Thanks, Michele _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
