Recent content by MrPete

More often than not, qm stop fails because the lock file can't be locked. The very common workaround DOES work: delete the lock file, then run qm stop. But if that's all it takes, why bother messing with lock files at all? What's the correct way to fix this, so qm stop actually works without...

I have my first Windows VM. I was shocked to discover, when examining the Event Viewer, that qemu-ga is recording a "Ping" event every 11 seconds, 24/7. ("guest-ping called") That's enough to massively fill the event log with stupid stuff. How can I disable this atrocious logging behavior...

Thanks. Well, I do encourage adding documentation about the decline in quality/growing issues. Quite sad... at least RDP is working without breaking the world.

@dcsapak Dominik, I've submitted the bug report. I also browsed the spice-devel email list, and overall activity of the project. UNFORTUNATELY:. Did you know: RedHat deprecated SPICE in fall of 2022?!! AND they removed it from RHEL 9. See https://bugzilla.redhat.com/show_bug.cgi?id=2030592#c4...

I've been going crazy... Moved my long-stable Retrospect network backup system to a Windows VM All kinds of strange anomalies have been seen My backup catalog file needs rebuilding... a long/slow process when crunching 17TB of backups, many millions of files and metadata I simply could NOT get...

Great ideas! I will check them out. Not aware of RPC Shutdown, but having never had this happen to any other device on our network, that seems least likely. I'll be back at some point ;)

I don't mind sharing the logs. Just... boring :) I'm thinking it's in noVNC -- not internal to the VM, and not (exactly) in ProxMox either LOL. Here's a sample log. VM 710 is the VM of interest:

Ummm... that page provides rather "subtle" documentation :) ... It's a sentence within an explanatory note?! Emphasis mine: In further searching, I don't find "prelaunch" anywhere in the Wiki, nor the Administrator's Guide. And I don't find a clear explanation of this risk anywhere in the...

Thanks, good questions. nothing at all in journalctl at that time... only when the shutdown is complete. So honestly I can't see how ProxMox is involved in initiating the shutdown. Haven't set up auto-restart (although starting to wonder if that's a necessary workaround :( ) I can disconnect...

I am new to using Windows in a VM, but VERY experienced with windows. Very often (multiple times a day), I'm online via noVNC in the ProxMox console, doing stuff in the VM. Suddenly, the VM starts to shut down. Windows event viewer says Explorer.exe did it at my request, "other (planned)"...

@fiona I think the biggest caution for me is this: Until now, I literally had NO idea, nor reason to believe, that a stopped VM would or could ever go active (even partially) "all by itself" in any scenario. I always think of a VM as literally a virtual computer system If off, it is OFF Truly...

THAT leads to the root of the problem, combined with side effects unknown to me until now: ProxMox auto-schedules VM backups at 00:00:00 Saturday morning Those backups temporarily partly-activate all VM's even if off Apparently, that partial-activation is sufficient to activate passed-through...

Sure... and I think you found it!!! ;) See below. Not only is this PCIe passthrough for the nVIdia card (hostpci0: 0000:01:00,pcie=1) but ALSO, VM 791 (also disabled) is an almost-duplicate with the same pass through. Here's a strange thought... at the moment I am traveling and can't test the...

I could but that sounds like a bandaid, not a solution ;)

So perhaps there's an unusual bug related to this... talk about obscure. May need to deep-dive on debug levels of the process.