Howdy, Stranger!

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


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



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

«1

Comments

  • itzsenuitzsenu Member
    edited October 3

    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

  • 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

  • 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

  • VMware? In the year of our lord?

  • @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'

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

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

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

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

  • 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

  • @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 October 3

    @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 October 3

    @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

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

    Thanked by 2yoursunny buggedout
  • @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

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

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

  • @TimboJones said: But regardless, just move away.

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

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

  • @nullwqh said:

    @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

    None of those really need a VDS. But if the price was so low, I can't fault you if the product was actually decent.

    Thanked by 1yoursunny
  • forestforest Member
    edited October 4

    Just disable memory ballooning

    cat << EOF > /etc/modprobe.d/no-memory-ballooning.conf
    install vmw_balloon /bin/true
    install virtio_balloon /bin/true
    install xen_balloon /bin/true
    install hv_balloon /bin/true
    EOF
    update-initramfs -u
    reboot
    

    I do this preemptively on every VPS I own. Never had any issues.

  • Hello everyone here is an short update about what is the current situation:

    • They refused the fact that they ballooned their VDSes and overcommited nodes and they doubled down saying and i quote "Expecting substantially higher performance than the specifications of the entry-level package does not mean that the allocated resources are missing or that the service is defective. We already informed you that, if your workload requires more CPU or RAM capacity, you should upgrade to a more suitable package." which is crazy because my workloads were personal projects which is enough for me if it wasnt taken by the host
    • I'm still in doubt about their WHMCS because WHMCS license check on musteri.verunix.com
      and im indeed sure it is WHMCS because when i looked at their CSS file they loaded into the client side there was proofs of the panel being WHMCS
      http://cdn.null.org.tr/STORAGE/cdn_cache_1791107043_image.png
  • tarisutarisu Member, Host Rep

    Thanked by 4nullwqh rpqu forest tzuli
  • drama i love drama, lets take this to the turkish cyber department so i can enjoy even more drama

    Thanked by 2nullwqh buggedout
  • rpqurpqu Member

    🍿

    Thanked by 2nullwqh buggedout
  • NeoonNeoon Community Contributor, Veteran

    Thanked by 3nullwqh buggedout RIYAD
  • nullwqhnullwqh Member
    edited October 4

Sign In or Register to comment.