Howdy, Stranger!

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


Phoenix 50% off on 1TB and 2TB Storage VPS plans (KVM) - Page 2
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.

Phoenix 50% off on 1TB and 2TB Storage VPS plans (KVM)

2»

Comments

  • djndjn Member

    I put a ticket in to try and enable AES with a bit of a strange reply

    Hello,
    Thanks for your email.
    Unfortunately, we don't support the AES-NI.
    If you have further questions or problems, please do not hesitate to contact our technical department.
    Many Thanks

    I take it's ment to say "This server does not support AES-NI"
    Still a good server for the money

  • @djn said:
    I put a ticket in to try and enable AES with a bit of a strange reply

    Hello,
    Thanks for your email.
    Unfortunately, we don't support the AES-NI.
    If you have further questions or problems, please do not hesitate to contact our technical department.
    Many Thanks

    I take it's ment to say "This server does not support AES-NI"
    Still a good server for the money

    That sounds a bit doubtful, I snagged one of the 1TB on impulse (can't have too many fallback options) and...

    Basic System Information:
    ---------------------------------
    Processor  : Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz
    CPU cores  : 1 @ 2199.998 MHz
    AES-NI     : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM        : 1.9 GiB
    Swap       : 0.0 KiB
    Disk       : 984.2 GiB
    

    The server would have to be prehistoric not to support AES these days. I would just ask them to expose the host CPU in your VM, sounds like a config glitch.

    I have several Inception instances and have never seem them configure the generic QEMU/KVM CPU before.

  • djndjn Member
    edited August 2021

    The server would have to be prehistoric not to support AES these days. I would just ask them to expose the host CPU in your VM, sounds like a config glitch.

    I have several Inception instances and have never seem them configure the generic QEMU/KVM CPU before.

    Someone has reviewed the ticket and was indeed a config error
    Updated yabs

    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    #              Yet-Another-Bench-Script              #
    #                     v2021-06-05                    #
    # https://github.com/masonr/yet-another-bench-script #
    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    
    Thu  5 Aug 14:48:24 BST 2021
    
    Basic System Information:
    ---------------------------------
    Processor  : Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz
    CPU cores  : 1 @ 2199.998 MHz
    AES-NI     : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM        : 1.9 GiB
    Swap       : 975.0 MiB
    Disk       : 982.4 GiB
    
    fio Disk Speed Tests (Mixed R/W 50/50):
    ---------------------------------
    Block Size | 4k            (IOPS) | 64k           (IOPS)
      ------   | ---            ----  | ----           ----
    Read       | 3.98 MB/s      (997) | 74.72 MB/s    (1.1k)
    Write      | 4.01 MB/s     (1.0k) | 75.11 MB/s    (1.1k)
    Total      | 7.99 MB/s     (1.9k) | 149.84 MB/s   (2.3k)
               |                      |
    Block Size | 512k          (IOPS) | 1m            (IOPS)
      ------   | ---            ----  | ----           ----
    Read       | 87.40 MB/s     (170) | 110.71 MB/s    (108)
    Write      | 92.04 MB/s     (179) | 118.09 MB/s    (115)
    Total      | 179.45 MB/s    (349) | 228.80 MB/s    (223)
    
    iperf3 Network Speed Tests (IPv4):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed
                    |                           |                 |
    Clouvider       | London, UK (10G)          | 858 Mbits/sec   | 356 Mbits/sec
    Online.net      | Paris, FR (10G)           | 853 Mbits/sec   | 204 Mbits/sec
    WorldStream     | The Netherlands (10G)     | 830 Mbits/sec   | 393 Mbits/sec
    Biznet          | Jakarta, Indonesia (1G)   | 515 Mbits/sec   | 52.7 Mbits/sec
    Clouvider       | NYC, NY, US (10G)         | 911 Mbits/sec   | 526 Mbits/sec
    Velocity Online | Tallahassee, FL, US (10G) | 901 Mbits/sec   | 590 Mbits/sec
    Clouvider       | Los Angeles, CA, US (10G) | 932 Mbits/sec   | 931 Mbits/sec
    Iveloz Telecom  | Sao Paulo, BR (2G)        | 822 Mbits/sec   | 331 Mbits/sec
    
    Geekbench 5 Benchmark Test:
    ---------------------------------
    Test            | Value
                    |
    Single Core     | 461
    Multi Core      | 464
    
    Thanked by 1Clouvider
  • risharderisharde Patron Provider, Veteran

    Will this be auto fixed for all vps assuming its a config error? Or should I ticket in to check?

  • djndjn Member

    @risharde said:
    Will this be auto fixed for all vps assuming its a config error? Or should I ticket in to check?

    Reboot and if it's still showing as QEMU Virtual CPU I would put in a ticket

  • @jugganuts said:
    Who doesn't setup CPU passthrough and aes in this great age of 2021

    CPU passthrough is bad news if you have multinode clusters with mixed CPUs
    This means that in case of an issue if you migrate the VPS to a node with a different CPU some issues may occur.

    E.g. Some licenses may invalidate if they check hardware hash or the OS may be incompatible with the said cpu.

    We are in 2021 but you will be amazed to find out how many people insist to use outdated/legacy systems that may break if for some reason the CPU is changed.

    Thanked by 1yoursunny
  • @Teucrus said:

    @jugganuts said:
    Who doesn't setup CPU passthrough and aes in this great age of 2021

    CPU passthrough is bad news if you have multinode clusters with mixed CPUs
    This means that in case of an issue if you migrate the VPS to a node with a different CPU some issues may occur.

    E.g. Some licenses may invalidate if they check hardware hash or the OS may be incompatible with the said cpu.

    We are in 2021 but you will be amazed to find out how many people insist to use outdated/legacy systems that may break if for some reason the CPU is changed.

    Interesting thank you for the information. It's definitely not a aspect I had thought about.

    Thanked by 1Teucrus
Sign In or Register to comment.