Verunix.com is stealing clients VDS resources

Comments

• itzsenu Member

  4:33PM 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.

  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

  @forest

  Thanked by 1mans_xd
• nullwqh Member

  5:16PM

  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
• nullwqh Member

  5:17PM

  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
• Void Member

  5:21PM

  @Verunix
• sillycat Member

  5:27PM

  VMware? In the year of our lord?

  Thanked by 1itzsenu
• itzsenu Member

  5:27PM

  @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.

  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'
• nullwqh Member

  5:37PM

  Hello, weirdly VM now reclaims the RAM
  now im confused here because i really dont know how VMWARE ESXI memory ballooning works i can only guess its stealing someone elses ram while i reclaim my own ram
  also here is the test i ran with the logs:
  https://anotepad.com/note/read/dmfafc4f
• TimboJones Member

  5:42PM

  I was curious if VDS can mean CPU cores only to some hosts, but their own page says CPU and RAM, but uses 8GB for some reason on their page in the example. That seems odd and specific, but I'm using translation.

  What package do you have and when did you open a ticket?

  For something like this, don't start out accusatory, just make it sound like maybe a mistake was made and it was a VPS package by accident and you'd appreciate them checking on it because from your end that's what it appears as.
• itzsenu Member

  5:46PM

  @nullwqh said: Hello, weirdly VM now reclaims the RAM
  now im confused here because i really dont know how VMWARE ESXI memory ballooning > works i can only guess its stealing someone elses ram while i reclaim my own ram

  I dont think its really "stealing someone elses RAM". ESXi is basically moving physical RAM between VMs depending on who actually needs it. Your balloon started around 1278 MB and dropped to around 706 MB when the VM started using more RAM. VMware swap also dropped from 57 MB to 48 MB.

  It looks like ESXi is giving the RAM back when the VM needs it. Still, 1.2 GB ballooned on a 2 GB VM while it was basically idle is a lot, and seeing VMware swap at all means the host had some memory pressure.

  more like the node is clearly overcommitted to some level.

  Thanked by 1rpqu