Troubleshooting System Interrupts issue
-
@ember1205 If you want to risk it, you could try to migrate another VM over to that host and see if the performance also deteriorates. That would nail down th eissue to the host vs. the storage (assuming you have the shared storage SRs between the hosts). With a new install on that hosts, did you adjust the dom0 memory allocation to be the same as the original host?
-
@tjkreidl said in Troubleshooting System Interrupts issue:
@ember1205 If you want to risk it, you could try to migrate another VM over to that host and see if the performance also deteriorates. That would nail down th eissue to the host vs. the storage (assuming you have the shared storage SRs between the hosts). With a new install on that hosts, did you adjust the dom0 memory allocation to be the same as the original host?
I have plenty of other guests running on the same host, no issue. I've migrated all guests off to another host, no change.
I have other guests that are materially similar to this one that have no issue. It's very odd...
-
@ember1205 Maybe try to uninstall and re-install XenTools?
-
@tjkreidl said in Troubleshooting System Interrupts issue:
@ember1205 Maybe try to uninstall and re-install XenTools?
I have done that as well. I removed the tools that came with the 7.2 XenServer software and installed the latest Citrix XenTools. No difference.
Same software across all of the Win10 guests...
Launching Task Manager will immediately show the System Interrupts pegging at 100% then settle down. The performance tab of the guest (from another machine) never shows the 4 vCPU go above about 40% (even though task manager claims the CPU is at 100%), the memory (16GB min/max - 'reserved') utilization is at about 4-5GB, and there's little to no network or disk traffic.
-
@ember1205 You have dom0 configured with the same memory allocation? If you run "ioxtat -x" and xentop, do you see anything saturating? The other thought is that something is screwed up with that specific VM as you apparently do not see the symptoms on any other VM.
-
@tjkreidl said in Troubleshooting System Interrupts issue:
@ember1205 You have dom0 configured with the same memory allocation? If you run "ioxtat -x" and xentop, do you see anything saturating? The other thought is that something is screwed up with that specific VM as you apparently do not see the symptoms on any other VM.
I am absolutely of the thought that it's the VM, but my expectation is that it's "inside" of the VM as opposed to an external piece.
I don't know what I would want to be looking for in terms of the saturation items. Also, the xstat output shows 16 vCPU, but these machines are 24 vCPU (dual hexacore with hyperthreading). The XCP-NG Client program shows 24 vCPU in the graphs. This is how it has always been, even with the prior versions of XenServer.
-
@ember1205 Weird. You don't have an older backup of the VM, per chance? Sounds almost like it may have been somehow corrupted.
-
@tjkreidl said in Troubleshooting System Interrupts issue:
@ember1205 Weird. You don't have an older backup of the VM, per chance? Sounds almost like it may have been somehow corrupted.
I don't. And I didn't realize the SSD was giving coalesce warnings (which is where the VHD was stored for a very long time) until I tried to move it off to a NFS repository. I ended up cloning the drive to get "most of it" so that it was functional, but something is corrupted in there somewhere. It has to be.
-
@ember1205 I agree, there is no other reasonable explanation. Alas, backups are so critical. I hope, if need be, you can re-create the VM somehow! That, or you'll have to have it limp along as is I'm afraid.
-
@tjkreidl said in Troubleshooting System Interrupts issue:
@ember1205 I agree, there is no other reasonable explanation. Alas, backups are so critical. I hope, if need be, you can re-create the VM somehow! That, or you'll have to have it limp along as is I'm afraid.
Yeah, I'll just leave it as is for now. Rebuilding is an option, but not a great one as I'm looking to make the move to Win11 "soon."
-
@Marcsteven said in Troubleshooting System Interrupts issue:
To resolve troubleshooting system interrupts errors, many methods can be executed. You can maybe disable sound effects. To do that, you can go to the taskbar and right-click the speaker icon. Then double-click your Default Device (speaker) > open Properties. Now tap the option of Enhancements and check the box which says ‘Disable all sound effects.’ Now press Ok to save the settings, and we will hope this will resolve the method. If it doesn't work then maybe you can update your PC's Bios by launching the Windows search > write CMD > run Command Prompt and then type these commands one after another > hit before you enter after each command systeminfo | findstr /I /c:bios wmic bios get manufacturer, smbiosbiosversion .
Appreciate the ideas here, but most of it pertains to desktop machines not virtual guest instances (upgrading the PC BIOS is not really applicable for this unless it were occurring on ALL guests, for example).
