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?

    Thanked by 1itzsenu
  • 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'

  • nullwqhnullwqh Member

    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

  • TimboJonesTimboJones Member

    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.

  • itzsenuitzsenu Member

    @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 2rpqu TimboJones
  • nullwqhnullwqh Member

    @TimboJones said:
    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.

    It was an VDS specifically TR-SSD-01 from https://verunix.com/en/vds-server
    Also i've made sure that my argument is correct and indeed there is ballooning

  • nullwqhnullwqh Member

    Also i think they are using WHMCS(musteri.verunix.com) but when i try to verify its whmcs license at https://www.whmcs.com/members/verifydomain.php/verifydomain.php it says the domain is not authorized to use WHMCS

  • nullwqhnullwqh Member

    @itzsenu said:

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

    Ah thanks for the explanation

  • TimboJonesTimboJones Member
    edited 6:26PM

    @nullwqh said:

    @TimboJones said:
    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.

    It was an VDS specifically TR-SSD-01 from https://verunix.com/en/vds-server
    Also i've made sure that my argument is correct and indeed there is ballooning

    When did you open the ticket? CloudatCost once defended 24/7 support as in that you can open a ticket 24/7, not that they have tech support working 24/7. That's a redflag if it's been more than 24 hours since response.

    The way they advertise entirely Xeon Platinum and then list half a dozen non-platinum processors and potential DDR3 should be redflag that you're not getting what you think you're getting.

  • itzsenuitzsenu Member
    edited 6:29PM

    @nullwqh said:

    @TimboJones said:
    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.

    It was an VDS specifically TR-SSD-01 from https://verunix.com/en/vds-server
    Also i've made sure that my argument is correct and indeed there is ballooning

    Come on, activate full MJJ mode and wake up to reality
    Are you sure? A VDS with 2 dedicated CPU cores for only $1.83/month?
    TR-SSD 1: 89.90 TL × 0.0204 = $1.83 :confused:


    just joking

    Thanked by 1rpqu
  • nullwqhnullwqh Member

    @itzsenu said:

    @nullwqh said:

    @TimboJones said:
    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.

    It was an VDS specifically TR-SSD-01 from https://verunix.com/en/vds-server
    Also i've made sure that my argument is correct and indeed there is ballooning

    Come on, activate full MJJ mode and wake up to reality

    TR-SSD 1: 89.90 TL × 0.0204 = $1.83 :confused:

    xD for real but to be honest yeah i do get shit services in tr location specifically i should stop getting virtual server from tr location

  • NeoonNeoon Community Contributor, Veteran

    That's a loose term, VDS is basically a VPS.
    You could blacklist the ballooning kernel module or try to allocate 2GB and see if it works fine.

  • nullwqhnullwqh Member

    @Neoon said:
    That's a loose term, VDS is basically a VPS.
    You could blacklist the ballooning kernel module or try to allocate 2GB and see if it works fine.

    So deleting the ballooning module indeed worked but now i wonder would they suspend me for it but at this point i dont even care

  • NeoonNeoon Community Contributor, Veteran

    @nullwqh said:

    @Neoon said:
    That's a loose term, VDS is basically a VPS.
    You could blacklist the ballooning kernel module or try to allocate 2GB and see if it works fine.

    So deleting the ballooning module indeed worked but now i wonder would they suspend me for it but at this point i dont even care

    Well, some providers are getting upset, but if you are one of 50 on the oversold node, I guess it doesn't do much :D

  • nullwqhnullwqh Member

    @Neoon said:

    @nullwqh said:

    @Neoon said:
    That's a loose term, VDS is basically a VPS.
    You could blacklist the ballooning kernel module or try to allocate 2GB and see if it works fine.

    So deleting the ballooning module indeed worked but now i wonder would they suspend me for it but at this point i dont even care

    Well, some providers are getting upset, but if you are one of 50 on the oversold node, I guess it doesn't do much :D

    Gotta note some people are so greedy that they would do whatever they can to get back what they stolen :p

  • TimboJonesTimboJones Member

    @nullwqh said:

    @Neoon said:
    That's a loose term, VDS is basically a VPS.
    You could blacklist the ballooning kernel module or try to allocate 2GB and see if it works fine.

    So deleting the ballooning module indeed worked but now i wonder would they suspend me for it but at this point i dont even care

    Check terms of services if they require it and will suspend you if you don't.

    But regardless, just move away.

  • itzsenuitzsenu Member

    @TimboJones said: But regardless, just move away.

    Just move away and get a VPS. It’ll be faster than this for sure.

  • nullwqhnullwqh Member

    @itzsenu said:

    @TimboJones said: But regardless, just move away.

    Just move away and get a VPS. It’ll be faster than this for sure.

    i do have an VPS this VDS was for ip tunneling, reverse proxy and an VPN service but i guess it cant even classified for that

Sign In or Register to comment.