Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
K.N Cloud — High-Performance KVM VPS in Miami,Frankfurt and Amsterdam
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
CloudLinux
MeduzaVPN
Servury - Anonymous & Privacy-focused VPS Hosting
Animated Silicon Kiwi cloud ad featuring VPS from $4.90/month, 100 GB S3 storage from $1.49/month, Kiwi Apps from $12/month and cloud backup from $3/month

Categories

In this Discussion

Home › Reviews
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Verunix.com is stealing clients VDS resources

nullwqhnullwqh Member
in Reviews



As it can be seen here my VDS which has 2 core and 2 gb ram but hypervisor eats 1.2 gb of my ram which more than half of the ram that i bought and its worth noting that i bought the server as VDS not as VPS

Comments

  • itzsenuitzsenu Member
    edited 4:57PM

    vmware-toolbox-cmd stat balloon showing 1278 MB is not the hypervisor itself consuming 1.2 GB. It means VMware's balloon driver has reclaimed roughly 1.2 GB from inside the guest.

    The interesting result here is memres = 0 MB. If VMware Tools is reporting that correctly, the VM doesnt appear to have a memory reservation.

    vmware-toolbox-cmd stat balloon
vmware-toolbox-cmd stat swap
vmware-toolbox-cmd stat memres
vmware-toolbox-cmd stat memlimit
cat /proc/pressure/memory
vmstat 1

    load it a bit and watch the balloon, swap and vmstat. :confused:

    If that 1.2 GB balloon stays there or goes even higher once the VM actually needs RAM, then yeah, that looks pretty bad for something sold as a 2 GB VDS.

    The balloon number doesn't prove they're "stealing" RAM, but reclaiming 1.2 GB GB with memres = 0 MB is :confused:

    @forest

    Thanked by 1mans_xd
  • nullwqhnullwqh Member

    Hello, thanks for your comment and here is the output of the command
    as guessed its still high

    also they are ghosting me so i cant get more information about this incident

  • nullwqhnullwqh Member

    from what i can see it goes around 1.39gb and 1.45gb of usage normally i only expect these types of issues on vpses but on vds? not on my usual checklist

  • VoidVoid Member

    @Verunix

  • sillycatsillycat Member

    VMware? In the year of our lord?

  • itzsenuitzsenu Member

    @nullwqh said: as guessed its still high

    balloon = 1278 MB means Vmware is reclaiming around 1.25 GB from inside the VM. So it is not just the hypervisor itself using that ram. vmware has actually taken that memory back from the guest.

    interesting part is swap = 57 MB. That is vmware side swap, while inside Linux swpd is still 0 and there is basically no si/so activity.

    memres = 0 MB also means there is no guaranteed RAM reservation for this VM. memlimit = 4294967295 MB looks like there is no actual memory limit configured either.
    Also the PSI memory values are all 0.00 and the VM is almost idle, but the balloon is still sitting at 1278 MB. :confused:

    can u put some real memory load on the VM and watch these at the same time:
    watch -n1 'vmware-toolbox-cmd stat balloon; vmware-toolbox-cmd stat swap; free -h'

Sign In or Register to comment.