This morning I was uploading a couple of small gif files to one of my
website hosting on a Windows
VPS Hosting when the
VPS Hosting was shutdown.
Immediately got onto live support who tell me that my
VPS Hosting was running 90% of the physical nodes CPU.
I was told that
- 'I think you are running very heavy applications on it'
- 'Might be MSSQL Server or ftp service creating load'
Now, there are no heavy apps running on there - there is 1 VBulleting instance running live and that is by no means heavy usage.
I have MSSQL installed but no databases conifigure yet.
I had just transferred about 4 or 5 gif files each of about 12k each - maybe that had overloaded FTP then
I have been sent a graph showing that my
VPS Hosting was reporting 90% but of course that only comes from the
VPS Hosting software - it doesn't look inside the
VPS Hosting at whats going on in there.
Luckily for me, I am recording stats within the
VPS Hosting and there was nowhere near 90% cpu utilisation, it was well below 20% and on further inspection a max spike of 12.6% was recorded about 30 minutes before the shutdown.
Overnight there were 2 small spikes and these tied in with the automaintenance jobs that run on the
VPS Hosting nodes to send out stats.
I was also told that 'If your
VPS Hosting is not having MSSQL Server or any other application then it is must having viruses' - this is after I have stated that inside the
VPS Hosting node all is well.
When I suggested it was a bug in Virtuozzo I was told categorically 'It is not a bug. It is the software provided by swsoft who created virtuozzo'
Support have suggested that I monitor task manager inside my
VPS Hosting to watch for problems, this despite me already having performance manager logging CPU/Mem/Bandwidth stats every 15 seconds.

I only set these up because of problems I experienced when I first got the
VPS Hosting - the console would appear to hang for no reason and this was with no
website hostings running and the CPU was spiking then. Somebody from support 'tweaked' something and that fixed it - maybe the tweak neads tweaking a bit more.
Just one thing to add - I've held off transferring my more important sites over until I got a decent period of stability - I was just approaching that stage when this has happened so we're back to square one on this. My current feeling is go back to my original host.