I was merely showing that the host CPU doesn't peak when a sound is played, which is why I showed the volume control so you can see what I did.mpack wrote:Thank you, but that is not useful information.
When trying to identify a CPU or I/O hog you should be looking at the process list, not a graphic showing total CPU use, and certainly not a picture of the guest's volume control. Your PC has not locked up, you are just getting glitchy sound. So look at the host process list and see who is using the most CPU and I/O bandwidth. Guest overheads may be worth looking at too.
Anyway, how can I provide you more info?
Does output/screenshot from the 'top' command help?
Do you need it when I play the sound, or in general, or both?
As to the I/O bandwith, does iotop give you what you need?
From all that I'm looking at (I'm obviously not an expert), the system is not stressed, so anything I can provide to help someone troubleshoot this, just let me know...