Windows 11 VM ends up in Error status every few days

hello everyone,
I have a windows VM which I am using to backup my files to the cloud, every few days I will find that the VM is no longer accessible as in, in the process list i can still see opt/incus/bin/qemu-system-x86_64 running but i can’t access the console nor ping it.

When “incus ls” is run it shows:

| windows | ERROR | | | VIRTUAL-MACHINE | 0 |

And “incus info --show-log windows” shows

Name: windows
Status: ERROR
Type: virtual-machine
Architecture: x86_64
Created: 2024/08/31 22:29 +08
Last Used: 2024/11/26 17:55 +08

Log:

qemu-system-x86_64:/run/incus/windows/qemu.conf:273: warning: '-fsdev proxy' and '-virtfs proxy' are deprecated, use 'local' instead of 'proxy, or consider deploying virtiofsd as alternative to 9p

I can restart the VM by running incus restart --force windows however this VM will end up in an error state again soon thereafter.

Could anyone guide me on how to debug this issue?

Thank You

I’ve often found that particular situation to be resolved by setting raw.qemu to -cpu host.
What’s weird is that it doesn’t always do it, it appears to be dependent on the CPU used and just how Windows tickles KVM on that particular day…

Ok thank you, will try that and see if it solves the problem in a few days