arch-x86,O3,KVM switching to full simulation bug about gem5

[ivanaamit]

@Foxy-Boxes, I would suggest enabling the exec debug flag after switching CPUs to check if there is something obviously wrong. During the CPU switch, when calling takeOverFrom, ensure that you are not missing any crucial steps in copying important state from one CPU to another. I hope this helps.

[Foxy-Boxes]

I have not changed switching behavior and this is still a bug in the simulator, I am using a workaround to avoid this situation. If I had time I would attempt fixing it but for now I will continue to use the workaround.
Edit: Sorry I pressed close accidentally

[Lukas-Zenick]

Hello, my name is Lukas and I’m working with my partner Emily on a final project for our Virtualization class. We are Computer Science at the University of Texas at Austin and currently enrolled in CS360V Virtualization, taught by Dr. Chidambaram (VJ). As part of our coursework, we are required to contribute to a few issues within an open-source repository relevant to the class.

After reviewing the gem5 repository, we believe that the particular issue aligns well with our objectives and skill set and were wondering if we may be assigned to this issue. If that's possible, before proceeding, we wanted to ask if there are any additional details or considerations regarding this issue that we should be aware of. We are committed to completing all three issues by May 6th to the best of our abilities.

Thank you for considering our request.
Emily and Lukas

[powerjg]

Awesome! Yes, please feel free to try to tackle this issue. If you have any questions, don't hesitate to ask. @BobbyRBruce has successfully reproduced the issue, but we haven't had the resources to fix it. Hopefully Ivana's comment above gives you a starting point.

[lllzy040620]

Has anyone fixed these bugs? I encountered the same issues while trying to run x86-ubuntu-run-with-kvm.py in my disk-image.

[ivanaamit]

@lllzy040620, I don't think this is fixed. If you know how to resolve it, please feel free to create a PR with your changes. Thank you.

[lllzy040620]

@ivanaamit I resolved this issue by downgrading gem5 from version 24.0.1 to 22.0.1. I believe the problem might have been caused by an incompatibility between the gem-resource's version and gem5.