Nope, no snapshots. The bugchecks in the logs vary with the last two being 0x0a and 0x3b - drivers and memory - but this is on both Stable and Latest virtio drivers and memtest86+ comes up clean on the hardware. I’ve never taken a snapshot of this VM since it’s on my workstation and not for production use.
What I have noticed, though, is an increase in memory utilization in the VM at idle, likely due to recent group policy changes and application updates (it is domain-joined). I’ll see if increasing the amount of memory allocated will take care of 0x3b.
I just want it to stop self-destructing every two hours when I’m running it as a VM under Linux.
Maybe that’s one of the features you can enable.
Ah, you must have it set to Windows Millennium Edition mode
Assuming it’s precisely at the 2 hour mark, do you have snapshots enabled for that VM? If so, try turning them off.
Nope, no snapshots. The bugchecks in the logs vary with the last two being 0x0a and 0x3b - drivers and memory - but this is on both Stable and Latest virtio drivers and memtest86+ comes up clean on the hardware. I’ve never taken a snapshot of this VM since it’s on my workstation and not for production use.
What I have noticed, though, is an increase in memory utilization in the VM at idle, likely due to recent group policy changes and application updates (it is domain-joined). I’ll see if increasing the amount of memory allocated will take care of 0x3b.
Wait, what? What happens when you hit the two hour mark? I’d it like one of the router simulators that forces a reboot?
BSOD for whatever reason. Doesn’t matter, I can resume what I was doing pretty quickly, but it is mildly inconvenient.
I just use windows 10 for VM, it hasn’t crashed for me but I don’t use VMs for more than one or two hours