You're likely to have less problems with OpenVZ than Xen if you've never used virtualisation before, and that's a good thing since you're unlikely to know how to fix them.

Edit: On that server, I'd say maybe 15 instances of that configuration. Of course, this totally depends and it's a skill you have to learn if you're going OpenVZ, overselling is pretty much part of the business plan on OpenVZ.

I see your point, data in Australia cost to much to start a profitable VPS hosting company. i have had a look around and most costs are reasonable but BW of 1TB a month seems to be going for $300/m by itself.

You go smooth sailing, pretty much entirely autopilot for two weeks. Then all three servers start suffering the same issues, random 5 minute drop outs 24/7, neither the DC, SolusVM or you can work out what the issue is. To fix it, you end up pulling a straight 36 hour session at the desk until you find the issue and clear up the mess.

Stupid OpenVZ kernel was borked, and the drop outs only effected the main IP and sporadically other IP's at random, not a fun weekend.

You go smooth sailing, pretty much entirely autopilot for two weeks. Then all three servers start suffering the same issues, random 5 minute drop outs 24/7, neither the DC, SolusVM or you can work out what the issue is. To fix it, you end up pulling a straight 36 hour session at the desk until you find the issue and clear up the mess.

Stupid OpenVZ kernel was borked, and the drop outs only effected the main IP and sporadically other IP's at random, not a fun weekend.