I can understand why a provider may not want this information known however I can not fathom why an end-user would want it unknown.Seeing the number of containers on a node should ABSOLUTELY POSITIVELY NOT be
allowed! If there is enough interest to make it a feature (I highly doubt
there is) someone can enable fine but NO WAY should container owners ever be
able to see this kind of information on the node by default.
Please add this patch to the kernel asap.
Yep, it's being discussed in the last several comments.It's worth pointing out that this is a bug in the kernel and is being patched by Parallels so don't get too used to being able to do this guys.
Exactly. I've been using OpenVZ since 2006. Sadly, you ask the random person on VPSBoards, LET, WHT, or any other community which virtualization technology is the worst, and most of them will say OpenVZ. Then you ask them why? "Because the host can oversell" is the common response.The mixed feelings on this are totally cool, and expected, really. I actually agree with a lot of what Joe said.
I just wish we had a happy medium...just some little way of saying "Yes, we run OVZ but we're not being blatant f***ing idiots about the number of containers running on our nodes." Yada, yada, yada...
There are actually a few commands you can throw at a container that can tell you whether or not it's nested inside Xen/KVM, but that can be for a rainy day or something.But then you would not see all those containers in /proc/cgroups? Slabbing implies you are basically virtualizing your OpenVZ nodes which in turn would effectively "hide" containers running in the other slabs.
Exactly! The common people has no clue Xen has been able to be oversold for a long time now...all a different couple ways too. Though you mostly need the know-how to even perform this, so it's still better then Joe Smo overselling his 32GB E3 with 100+ customers hehe.Back in the day, Xen didn't allow for memory and disk overselling and some people still to this day think that virtual machines can't be oversold. Even back then, they could oversell disk I/O, CPU, network I/O, etc.
Well I agree, but do take some slight issues with this.Luckily there are a ton of clients and knowledgeable people on this forum who understand that overselling != diminished performance, unfortunately for every one of those there are thousands that don't understand that and thus why advertising the population of a node is not beneficial to a VPS provider who's business relies on sales from the general public where the vast majority aren't very technically inclined and will quickly judge a company based on the negatives of the virtualization use...
The bottom line is that the number of VPSs per node has no impact on anything and cannot be used to quantify anything performance-wise. All you have is a number out of context of anything and will mean different things for different providers. If the number was broken down to show you have much RAM and disk space each VPS got, then you could see how oversold a node is but even that doesn't give you a view point of the server's performance. Now if the number was broken down by CPU, RAM/swap, or disk IO usage, then you can get an idea of how over/underworked the server is...