★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

gdmax · May 2022

hi @VirMach We apologize for the short notice.

Your service(s) on NYCB012, NYCB013, NYCB014, NYCB015 and NYCB018 will be undergoing hardware maintenance tomorrow between approximately 4PM-5PM EST (which is 1PM-2PM PST.) We will be reconfiguring some BIOS settings and adding in a replacement disk to fix some offline services that did not create properly on this node.

We do not expect any data loss, but it's always a good idea to back up your important data.

We will provide any further updates on the network status page. We apologize for any inconvenience.

But now no work anything Ticket #556261 NYCB013 first i have LAKVM9 server but no work

Your service is being migrated on Monday, May 9th, 2022

San Jose: SJKVM8, SJKVM11
Atlanta: ATLKVM11, ATLKVM12, ATLKVM13
Seattle: SEAKVM15
Dallas: DAL10GKVM2
Buffalo: NY10GKVM88, NY10GKVM82, NY10GKVM38, NY10GKVM33, NY10GKVM30, NY10GKVM27, NY10GKVM19, NYKVM21L
Piscataway: NYCKVM16, NYCKVM12
Los Angeles: LAKVM9, LAKVM16, LAKVM26

1 month i cant work please help

msteen · May 2022

@VirMach said:
@msteen said:
@oasisX said:
When the first batch paid migration was opened, I paid 3 dollars to try the migration (San Jose), and the migration was stuck for more than 20 days. So far, it has not been successful, and I have not received a refund. For this I closed the stuck migration request ticket (#594920) and submitted a refund ticket(#324050), but the status of the refund ticket has always been Awaiting Billing Department for three days. And no reply so far.

I saw that I could pay to migrate to Japan today. I tried the migration again(Tokyo, JP) to do a test to see if this migration got stuck again. I didn’t expect it to get stuck again. Just like last time, the migration ticket(#352668) generated after payment(Invoice #1439463) was stuck on the Important Alert page, and the content was as below
Invoice #1439463 has been generated for this request.

Once this invoice has been paid, your request will be added to the queue and handled by our support team.
Seems didn't detect my paid status(After paid $3).

I wonder if it is because of the specifications of the machine that the paid migration has been stuck many times, and I have not figured out what the problem is. Maybe it's a BUG? So I feedback here to see if @VirMach can forward this message to the developer and check what happened to these migration operation. Thanks a lot!
I have to say I meet the same situation as you, several attempts and full of these are failed without the refund.
There's no auto refund on failure feature built in yet. If at any point your migration ticket is closed out and you didn't get a migration or your money back, you should of course contact the billing department and provide the following pieces of information: [1] the fact that the migration was not complete, [2] the invoice ID or the ticket ID for the migration referenced.

I already have one open ticket about this, which contains all those informations you mentioned above, but no billing staff reply this for 3 days. Today, another paid stuck migration happened, should I open the second ticket to apply for the refund or just add extra message in the first ticket?

VirMach · May 2022

@gdmax said:
hi @VirMach We apologize for the short notice.

Your service(s) on NYCB012, NYCB013, NYCB014, NYCB015 and NYCB018 will be undergoing hardware maintenance tomorrow between approximately 4PM-5PM EST (which is 1PM-2PM PST.) We will be reconfiguring some BIOS settings and adding in a replacement disk to fix some offline services that did not create properly on this node.

We do not expect any data loss, but it's always a good idea to back up your important data.

We will provide any further updates on the network status page. We apologize for any inconvenience.

But now no work anything Ticket #556261 NYCB013 first i have LAKVM9 server but no work

Your service is being migrated on Monday, May 9th, 2022
San Jose: SJKVM8, SJKVM11
Atlanta: ATLKVM11, ATLKVM12, ATLKVM13
Seattle: SEAKVM15
Dallas: DAL10GKVM2
Buffalo: NY10GKVM88, NY10GKVM82, NY10GKVM38, NY10GKVM33, NY10GKVM30, NY10GKVM27, NY10GKVM19, NYKVM21L
Piscataway: NYCKVM16, NYCKVM12
Los Angeles: LAKVM9, LAKVM16, LAKVM26
1 month i cant work please help

Is this actually related to the migration that was performed by us or did you also utilize the migrate without data button?

Edit: okay I've checked, it's not related at all to that migration and it's only been created for 6 days, not 1 month?

VirMach · May 2022

@msteen said:
@VirMach said:
@msteen said:
@oasisX said:
When the first batch paid migration was opened, I paid 3 dollars to try the migration (San Jose), and the migration was stuck for more than 20 days. So far, it has not been successful, and I have not received a refund. For this I closed the stuck migration request ticket (#594920) and submitted a refund ticket(#324050), but the status of the refund ticket has always been Awaiting Billing Department for three days. And no reply so far.

I saw that I could pay to migrate to Japan today. I tried the migration again(Tokyo, JP) to do a test to see if this migration got stuck again. I didn’t expect it to get stuck again. Just like last time, the migration ticket(#352668) generated after payment(Invoice #1439463) was stuck on the Important Alert page, and the content was as below
Invoice #1439463 has been generated for this request.

Once this invoice has been paid, your request will be added to the queue and handled by our support team.
Seems didn't detect my paid status(After paid $3).

I wonder if it is because of the specifications of the machine that the paid migration has been stuck many times, and I have not figured out what the problem is. Maybe it's a BUG? So I feedback here to see if @VirMach can forward this message to the developer and check what happened to these migration operation. Thanks a lot!
I have to say I meet the same situation as you, several attempts and full of these are failed without the refund.
There's no auto refund on failure feature built in yet. If at any point your migration ticket is closed out and you didn't get a migration or your money back, you should of course contact the billing department and provide the following pieces of information: [1] the fact that the migration was not complete, [2] the invoice ID or the ticket ID for the migration referenced.
I already have one open ticket about this, which contains all those informations you mentioned above, but no billing staff reply this for 3 days. Today, another paid stuck migration happened, should I open the second ticket to apply for the refund or just add extra message in the first ticket?

I tried to be specific with my words there, so I meant only if the request is closed without a resolution on the migration to do that. Otherwise, my advice wouldn't apply.

For what you've described now, one billing ticket, one migration ticket, you should just close the migration request and reply to the billing ticket to get your refunds. Or if you want the new migration potentially processed, close the billing ticket and wait and create a billing ticket later on after the migration request is closed out.

JabJab · May 2022

I have no idea why people are so keen to migrate to that Ryzen and being mad that they didn't.

People that are in this topic and see daily complains about crowded network, network being dead, dead XPG drives. Are you guys suicidal or something? It's working meh, very meh - why do you want to migrate yours working E5 (slower - yeah, but working) to Ryzens? Just wait for VirMach to fix that stuff and then just migrate...

cgs3238 · May 2022

Hello, any news for Tokyo storage ?

JabJab · May 2022

@VirMach to that AMS 25 node - did you change anything in settings/router?
This is in UTC-1 timezone, but the (mostly idle) traffic tripled around 12 hours and some minutes ago...

VirMach · May 2022

@JabJab said:
I have no idea why people are so keen to migrate to that Ryzen and being mad that they didn't.

People that are in this topic and see daily complains about crowded network, network being dead, dead XPG drives. Are you guys suicidal or something? It's working meh, very meh - why do you want to migrate yours working E5 (slower - yeah, but working) to Ryzens? Just wait for VirMach to fix that stuff and then just migrate...

Which node is that?

msteen · May 2022

@JabJab said:
I have no idea why people are so keen to migrate to that Ryzen and being mad that they didn't.

People that are in this topic and see daily complains about crowded network, network being dead, dead XPG drives. Are you guys suicidal or something? It's working meh, very meh - why do you want to migrate yours working E5 (slower - yeah, but working) to Ryzens? Just wait for VirMach to fix that stuff and then just migrate...

I agree with you. This may be asking for trouble. Several migration failures make me uncomfortable, but people always like to try new things, mostly so.

VirMach · May 2022

@JabJab said:
@VirMach to that AMS 25 node - did you change anything in settings/router?
This is in UTC-1 timezone, but the (idle) traffic tripled around 13 hours ago...

No, but it triggered an alert on our end and I've been trying to get to it all day. My guess at this point is a combination of abuse and said abuse causing the network settings to reset.

msteen · May 2022

@VirMach said:
@msteen said:
@VirMach said:
@msteen said:
@oasisX said:
When the first batch paid migration was opened, I paid 3 dollars to try the migration (San Jose), and the migration was stuck for more than 20 days. So far, it has not been successful, and I have not received a refund. For this I closed the stuck migration request ticket (#594920) and submitted a refund ticket(#324050), but the status of the refund ticket has always been Awaiting Billing Department for three days. And no reply so far.

I saw that I could pay to migrate to Japan today. I tried the migration again(Tokyo, JP) to do a test to see if this migration got stuck again. I didn’t expect it to get stuck again. Just like last time, the migration ticket(#352668) generated after payment(Invoice #1439463) was stuck on the Important Alert page, and the content was as below
Invoice #1439463 has been generated for this request.

Once this invoice has been paid, your request will be added to the queue and handled by our support team.
Seems didn't detect my paid status(After paid $3).

I wonder if it is because of the specifications of the machine that the paid migration has been stuck many times, and I have not figured out what the problem is. Maybe it's a BUG? So I feedback here to see if @VirMach can forward this message to the developer and check what happened to these migration operation. Thanks a lot!
I have to say I meet the same situation as you, several attempts and full of these are failed without the refund.
There's no auto refund on failure feature built in yet. If at any point your migration ticket is closed out and you didn't get a migration or your money back, you should of course contact the billing department and provide the following pieces of information: [1] the fact that the migration was not complete, [2] the invoice ID or the ticket ID for the migration referenced.
I already have one open ticket about this, which contains all those informations you mentioned above, but no billing staff reply this for 3 days. Today, another paid stuck migration happened, should I open the second ticket to apply for the refund or just add extra message in the first ticket?
I tried to be specific with my words there, so I meant only if the request is closed without a resolution on the migration to do that. Otherwise, my advice wouldn't apply.

For what you've described now, one billing ticket, one migration ticket, you should just close the migration request and reply to the billing ticket to get your refunds. Or if you want the new migration potentially processed, close the billing ticket and wait and create a billing ticket later on after the migration request is closed out.

Thanks. I'll choose the first solution to get my money back. May I take the liberty to ask how many days a refund request is usually processed? It has been three days since my first request. Will replying to the first request lead to a reset of the refund processing time?

saosangmo · May 2022

@VirMach

Now, I can cancel my order which you have not been activated yet? My order id is 662525.

thank you!

tototo · May 2022

I am curious if VirMach received tickets like "Ryzen Migrate resulted in lost IP that was reserved for Tokyo".

VirMach · May 2022

@msteen said: Thanks. I'll choose the first solution to get my money back. May I take the liberty to ask how many days a refund request is usually processed? It has been three days since my first request. Will replying to the first request lead to a reset of the refund processing time?

It's all over the place right now honestly, I wouldn't be able to provide an accurate response to that question.

@tototo said:
I am curious if VirMach received tickets like "Ryzen Migrate resulted in lost IP that was reserved for Tokyo".

We've received pretty much every ticket imaginable all the way down to someone being upset they got moved to Ryzen, someone being upset they have a second IP address for free (and I don't mean just reporting it us, like offended somehow.) Then we of course have people upset they lost a second IP they got temporarily thinking they should have had 2 IPv4 addresses permanently, and then we have that one guy that's created like 300 tickets so far that devolved into him being upset I won't let him fornicate with my mother and sister (not that I told him no, he started talking to himself basically and led it there.)

@saosangmo said:
@VirMach

Now, I can cancel my order which you have not been activated yet? My order id is 662525.

thank you!

Yes, just make a ticket and mention refund in the title.

Jones · May 2022

@VirMach

I have changed several browsers and even the operating system (including the mobile phone system), but they all show that there is no optional location in this option
Maybe you could kindly help me solve this problem?
Ticket

571560

(the ticket cannot reply to the content and activate)

I just want to know, if I pay the invoice, Move to JP location?? Because there is no information in the option, maybe you can reactivate the ticket so that I can complete the payment and migration

How do you feel about taking a few minutes to complete the migration? Thank you

AndreDonz · May 2022

This is machine No. 1438588 in NYC. There is a fault that cannot be started after reinstalling the system. We have tried all the systems in the mirror library, and most of them are like this.

AlwaysSkint · May 2022

@Virmach Just to be clear; I was making a comment on perception. In no way am I personally upset by all the shenanigans. It is what it is - said in a trying to be super-chilled-out manner.

I understand the business reasons but a lot of the shitstorm could be avoided by excluding MJJ et al. A more draconian approach to abuse should be implemented ASAP, IMHumbleO

Rockster · May 2022

@VirMach said:

@JabJab said:
@VirMach to that AMS 25 node - did you change anything in settings/router?
This is in UTC-1 timezone, but the (idle) traffic tripled around 13 hours ago...

No, but it triggered an alert on our end and I've been trying to get to it all day. My guess at this point is a combination of abuse and said abuse causing the network settings to reset.

Seems like dead right now.

tototo · May 2022

@AndreDonz said:

This is machine No. 1438588 in NYC. There is a fault that cannot be started after reinstalling the system. We have tried all the systems in the mirror library, and most of them are like this.

Did you select "[Ryzen Compatible]" from SolusVM panel (Billing Panel -> Additional Tools -> VPS Control Panel)?

guagua_ya66 · May 2022

$70 2 year Ryzen JP 3C4G machine is far inferior to the migrated JP machine, I don't think I'll ever buy a Virmach machine again, testing from node 26

Fri 27 May 2022 08:40:52 AM EDT

Basic System Information:
---------------------------------
Uptime     : 4 days, 5 hours, 3 minutes
Processor  : AMD Ryzen 9 5950X 16-Core Processor
CPU cores  : 3 @ 3393.624 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 3.8 GiB
Swap       : 256.0 MiB
Disk       : 78.4 GiB
Distro     : Debian GNU/Linux 11 (bullseye)
Kernel     : 5.10.0-14-amd64

fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 249.39 MB/s  (62.3k) | 1.15 GB/s    (18.0k)
Write      | 250.04 MB/s  (62.5k) | 1.15 GB/s    (18.1k)
Total      | 499.44 MB/s (124.8k) | 2.31 GB/s    (36.1k)
           |                      |
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 2.35 GB/s     (4.5k) | 2.97 GB/s     (2.9k)
Write      | 2.47 GB/s     (4.8k) | 3.17 GB/s     (3.0k)
Total      | 4.82 GB/s     (9.4k) | 6.15 GB/s     (6.0k)

Geekbench 5 Benchmark Test:
---------------------------------
Test            | Value
                |
Single Core     | 907
Multi Core      | 2272
Full Test       | https://browser.geekbench.com/v5/cpu/15151783

sky3967 · May 2022

@VirMach said:

@masterk said:
@VirMach my TYOC026 VPS is still offline,i created a new ticket #580695 as you said,and still no response.it got offline on may 17th, i am interesting in when it will be solved.

It's not going to get completed very quickly with that title, you picked custom department or modified the title if you clicked the correct department. Custom tickets should only be made if you can add more details, not less.

Also if you have two tickets open they'll end up getting merged and most likely closed.

I followed the prompts and recreated the ticket and then the service shows TERMINATED and the dashboard shows the number of services for the account as 0.

However there is no response to the ticket, what does this mean?

Jones · May 2022

@VirMach

#298249  （New）

What should I do next Perhaps it would be more appropriate to submit a new ticket. I hope you can help me complete the migration... If you can, please tell me how to proceed，
Please take a few minutes to deal with it for me. Thank you very much

JabJab · May 2022

Dark mode ruins the screenshot, open in new tab if needed :P

Continuing on that AMS 25 (that seems to little working now and my smokeping graphs loaded )
Ping to gateway (149.57.168.1) is fucked up.

Ping to VNC host (149.57.168.25) is normal, but I guess this never gets processed by NIC on a server and stays as localhost? So the machine is not overloaded, it somehow network (card/stack?) related.

Outside is fucked up too of course - Cloudflare.com by static IP 104.somethingsomethingidontremember

Rockster · May 2022

For the last hour or so wasn't accessible even via control panel. Now is back, but ouch:

Ping statistics for 149.57.xxx.xxx:
    Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 770ms, Maximum = 1604ms, Average = 1231ms

(AMS 025)

nutjob · May 2022

Shakey ping from AMSD026 (149.57.171.0) too:

PING 149.57.168.1 (149.57.168.1) 56(84) bytes of data.
64 bytes from 149.57.168.1: icmp_seq=1 ttl=64 time=10.7 ms
64 bytes from 149.57.168.1: icmp_seq=2 ttl=64 time=7.89 ms
64 bytes from 149.57.168.1: icmp_seq=3 ttl=64 time=0.832 ms
64 bytes from 149.57.168.1: icmp_seq=4 ttl=64 time=24.7 ms
64 bytes from 149.57.168.1: icmp_seq=5 ttl=64 time=3.84 ms
64 bytes from 149.57.168.1: icmp_seq=6 ttl=64 time=3.19 ms
64 bytes from 149.57.168.1: icmp_seq=7 ttl=64 time=3.31 ms
64 bytes from 149.57.168.1: icmp_seq=8 ttl=64 time=46.9 ms
64 bytes from 149.57.168.1: icmp_seq=9 ttl=64 time=9.73 ms
64 bytes from 149.57.168.1: icmp_seq=10 ttl=64 time=98.5 ms
64 bytes from 149.57.168.1: icmp_seq=11 ttl=64 time=36.8 ms
64 bytes from 149.57.168.1: icmp_seq=12 ttl=64 time=1.79 ms
64 bytes from 149.57.168.1: icmp_seq=13 ttl=64 time=2.89 ms
64 bytes from 149.57.168.1: icmp_seq=14 ttl=64 time=196 ms
64 bytes from 149.57.168.1: icmp_seq=15 ttl=64 time=15.7 ms
64 bytes from 149.57.168.1: icmp_seq=16 ttl=64 time=0.826 ms
64 bytes from 149.57.168.1: icmp_seq=17 ttl=64 time=11.1 ms
64 bytes from 149.57.168.1: icmp_seq=18 ttl=64 time=32.8 ms
64 bytes from 149.57.168.1: icmp_seq=19 ttl=64 time=1.57 ms
64 bytes from 149.57.168.1: icmp_seq=20 ttl=64 time=12.8 ms
64 bytes from 149.57.168.1: icmp_seq=21 ttl=64 time=44.1 ms
64 bytes from 149.57.168.1: icmp_seq=22 ttl=64 time=0.945 ms
64 bytes from 149.57.168.1: icmp_seq=23 ttl=64 time=2.78 ms
64 bytes from 149.57.168.1: icmp_seq=24 ttl=64 time=32.9 ms
64 bytes from 149.57.168.1: icmp_seq=25 ttl=64 time=0.873 ms
64 bytes from 149.57.168.1: icmp_seq=26 ttl=64 time=3.54 ms
64 bytes from 149.57.168.1: icmp_seq=27 ttl=64 time=1.01 ms
64 bytes from 149.57.168.1: icmp_seq=28 ttl=64 time=66.2 ms
64 bytes from 149.57.168.1: icmp_seq=29 ttl=64 time=1.03 ms
64 bytes from 149.57.168.1: icmp_seq=31 ttl=64 time=35.6 ms
64 bytes from 149.57.168.1: icmp_seq=32 ttl=64 time=0.884 ms
64 bytes from 149.57.168.1: icmp_seq=33 ttl=64 time=0.808 ms
64 bytes from 149.57.168.1: icmp_seq=34 ttl=64 time=24.6 ms
64 bytes from 149.57.168.1: icmp_seq=35 ttl=64 time=0.702 ms
64 bytes from 149.57.168.1: icmp_seq=36 ttl=64 time=1.15 ms
64 bytes from 149.57.168.1: icmp_seq=37 ttl=64 time=0.809 ms
64 bytes from 149.57.168.1: icmp_seq=38 ttl=64 time=38.10 ms
64 bytes from 149.57.168.1: icmp_seq=39 ttl=64 time=0.794 ms
64 bytes from 149.57.168.1: icmp_seq=40 ttl=64 time=0.830 ms
64 bytes from 149.57.168.1: icmp_seq=41 ttl=64 time=28.0 ms
64 bytes from 149.57.168.1: icmp_seq=42 ttl=64 time=1.49 ms
64 bytes from 149.57.168.1: icmp_seq=43 ttl=64 time=1.24 ms
64 bytes from 149.57.168.1: icmp_seq=44 ttl=64 time=40.1 ms
64 bytes from 149.57.168.1: icmp_seq=45 ttl=64 time=23.4 ms
64 bytes from 149.57.168.1: icmp_seq=46 ttl=64 time=9.51 ms
64 bytes from 149.57.168.1: icmp_seq=47 ttl=64 time=17.9 ms
64 bytes from 149.57.168.1: icmp_seq=48 ttl=64 time=57.3 ms
64 bytes from 149.57.168.1: icmp_seq=49 ttl=64 time=78.2 ms
64 bytes from 149.57.168.1: icmp_seq=50 ttl=64 time=3.41 ms

opshk · May 2022

@Virmach My tokyo server on TYOC26 cannot be boot since provision (last batch of tokyo ryzen pre-order ), similar with some comments above.

So far, I've created a ticket a few days ago to report this issue and demand for a fix, not sure if I open the right department and title.

department: Technical Support
title: Reporting Service Confirmed Offline - TYOC026 (147.78.xx.xx)
priority: medium

Will my issue be addressed soon? Just ask here to ensure my ticket will be handled properly. Thanks.

AndreDonz · May 2022

@opshk said:
@Virmach My tokyo server on TYOC26 cannot be boot since provision (last batch of tokyo ryzen pre-order ), similar with some comments above.

So far, I've created a ticket a few days ago to report this issue and demand for a fix, not sure if I open the right department and title.

department: Technical Support
title: Reporting Service Confirmed Offline - TYOC026 (147.78.xx.xx)
priority: medium

Will my issue be addressed soon? Just ask here to ensure my ticket will be handled properly. Thanks.

i figured out theres something in soluvm...try again there

opshk · May 2022

@AndreDonz said:

@opshk said:
@Virmach My tokyo server on TYOC26 cannot be boot since provision (last batch of tokyo ryzen pre-order ), similar with some comments above.

So far, I've created a ticket a few days ago to report this issue and demand for a fix, not sure if I open the right department and title.

department: Technical Support
title: Reporting Service Confirmed Offline - TYOC026 (147.78.xx.xx)
priority: medium

Will my issue be addressed soon? Just ask here to ensure my ticket will be handled properly. Thanks.

i figured out theres something in soluvm...try again there

Thanks,
I have already tried most of the "ryzen compatible" template, but none of those work.

cybertech · May 2022

@opshk said:

@AndreDonz said:

@opshk said:
@Virmach My tokyo server on TYOC26 cannot be boot since provision (last batch of tokyo ryzen pre-order ), similar with some comments above.

So far, I've created a ticket a few days ago to report this issue and demand for a fix, not sure if I open the right department and title.

department: Technical Support
title: Reporting Service Confirmed Offline - TYOC026 (147.78.xx.xx)
priority: medium

Will my issue be addressed soon? Just ask here to ensure my ticket will be handled properly. Thanks.

i figured out theres something in soluvm...try again there

Thanks,
I have already tried most of the "ryzen compatible" template, but none of those work.

have you tried booting from an ISO to see if it works

AlwaysSkint · May 2022

@opshk said: ..and demand for a fix..

Hmm, says it all, really.
A least two ways to take this phrase.

Howdy, Stranger!

Categories

In this Discussion

★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

Comments

571560

Howdy, Stranger!

Quick Links

Categories

In this Discussion

★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

Comments

571560