February 28, 20179 yr Hello all, Thought I'd post what I believe is a solution to a problem I've been having. In a nutshell, over the last few weeks, whenever I went to access my Windows 10 VM once it had been running for an extended period of time (over night), it would show as paused. I would be unable to unpause it, and unfortunately, more often than not, force stopping it (or using a virsh destroy by command line), and restarting it would freeze the whole server and force me to hard reboot. Due to the timing, I was pretty sure it was a 6.3 issue (as it didn't use to do it on 6.2 and earlier). With this in mind, I rolled back to 6.2.4, and lo and behold, I still had the problem. This made me look at plugins and add-ons, and I believe what seems to be causing my VM issues, is my implementation of the auto vm backup script. I had it backing up my img file every night (I used to have it do it once a month), and in the settings, I set it to force stop the vm if it didn't gracefully shutdown before backup, and also to restart on completion. It's only been one night, but I disabled it last night, and for the first time in awhile, my VM was still humming along this morning. This still doesn't answer the question why the whole server would freeze and disconnect from the network when I killed and restarted the paused VM, but at least I'm making progress. I'm going to re-enable the plugin (because it's super handy to have it backup my vms for me), but I'll try it without the force stop set. If anyone has some thoughts on why the server would behave i this manner, feel free to respond! And in case anyone else is having a similar problem and are running the auto vm backup script, try disabling it and seeing if the pausing goes away :).
Archived
This topic is now archived and is closed to further replies.