VirtualBox started crashing with VERR_IEM_INSTR_NOT_IMPLEMENTED
Posted: 16. Apr 2021, 10:06
I believe that this might be different problem than described here (can't paste link but you'll figure it out):
viewtopic.php?f=6&t=102298
but feel free to close / duplicate if you know better.
In my case I was using VirtualBox 6.1 for 4 months on Windows 10 host running Ubuntu 18.04 virtual machine. I've used 2 monitors all the time and my way of working would be to start VM, then at the end of the day save VM state and start it again the next day.
However, couple days ago VirtualBox started crashing with Guru Meditation error when I was trying to load saved state. I've done multiple tests and I figured out that:
1. When I start VM, save and load it works ok.
2. When I start VM, enable second screen, save and load then it will crash every time during load.
3. When I start VM, enable second screen, then disable second screen, save and load then it works ok.
As I've mentioned it worked well for past 4 months and suddenly broken. As a workaround I'll be using approach #3 and disable second screen before saving machine state but maybe there is better way to fix that?
viewtopic.php?f=6&t=102298
but feel free to close / duplicate if you know better.
In my case I was using VirtualBox 6.1 for 4 months on Windows 10 host running Ubuntu 18.04 virtual machine. I've used 2 monitors all the time and my way of working would be to start VM, then at the end of the day save VM state and start it again the next day.
However, couple days ago VirtualBox started crashing with Guru Meditation error when I was trying to load saved state. I've done multiple tests and I figured out that:
1. When I start VM, save and load it works ok.
2. When I start VM, enable second screen, save and load then it will crash every time during load.
3. When I start VM, enable second screen, then disable second screen, save and load then it works ok.
As I've mentioned it worked well for past 4 months and suddenly broken. As a workaround I'll be using approach #3 and disable second screen before saving machine state but maybe there is better way to fix that?