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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More
This discussion has been closed.

Comments
Yeah, we changed them before activation.
A few days will not be re-adjusted again. If you want though you can make a ticket in the billing department and ask for credits.
往返行程的估计时间(以毫秒为单位):
最短 172ms,最长 480ms,平均 = 405ms
Can you see this ?
I still don't understand the way of activation here. Is it per order date or by plan (maybe from small to bigger RAM)? If it's the order date, then what is the current date being activated?
This will help me and others understand the progress and will not leave us thinking why the due date was changed but still not activated (for the sake of transparency)
Thanks
Can you see this?
@VirMach > @VirMach said:
I'm sure I'll forget in two years, please help me now to change the due date to
Next Due Date 04/07/2024
In addition, others show the CPU model, I installed any system templates (cendos, debian10, none of them are displayed, AES-NI and VM-x/AMD-V are also closed), please help me deal with it
Processor : QEMU Virtual CPU version 2.5+
CPU cores: 1 @ 3693.060 MHz
AES-NI : ❌ Disabled
VM-x/AMD-V : ❌ Disabled
Invoice #1403703
I suggest you might want to open a ticket there.
This may help you guys.
Can you read? Virmach has said at least 2-3 times they believe the network issue is due to cpu abuse from kernel panic. It is not because of speed limits or restrictions on mjjs.
Also, can you be patient?
These were from your first 14 comments and there's 50 more comments from you on virmach threads which I won't bother quoting.
Actually, on second thought you should keep commenting. Your continuous bumps are bringing virmach sales and maybe they will eventually notice you and speed limit you specifically. That's good for everyone involved.
It's automatic now for the most part, and it tries to go in order of the time it was placed but this is not a 100% guarantee.
Bill #1412760
We're not processing any of these further at this time. We have no interest in swindling you out of money, but it would be best if you contact us if you are billed early. That way you do not have to worry about it and we do not get overloaded with these requests at this time when we're extremely busy.
Of course if you contacted us at a later time when we are not as busy I'm sure we would assist you then as well, it doesn't necessarily have to be at the last moment but that's how I am answering you to ensure that it will absolutely be done by then. It's the only guarantee I can provide, that we won't force you to make a payment when the due date is incorrect.
If he handles it like this, can he really let him show the CPU model?
Why do others directly install debian10 will show
I'll try it though, thank you
is the activation still per minute?
This is a storage special, I was only speaking of the Tokyo pre-orders. In any case, I'm not sure where you are getting 05/07/2022 due date from as yours has remained as 04/04/2024.
Yes and I'm monitoring the usage levels and will pause it if it goes above some expected figures.
Do you mean you don't trust the netboot.xyz image provided by VirMach?
Then you can download it from the official download page and try it out.
Okay, since apparently now its automatic, then within 24hrs, the 2k+ in queue you've mentioned before, should have or be done by today or tomorrow atleast.
I will try, thank you
Maybe has a little different, but I think this page will be helpful.
https://gist.github.com/AndersonIncorp/9fb7402cf69a0994e175ebec8194847c
Because I saw that the payment date is April 11, 2022, I just wondered. If it is a system problem, I can wait for correction. After all, there are many bugs. I purchased a 40-node server, and the current i/o is only 600M. But I've been waiting for your fix, and as for my storage server, I'm waiting too. I hope to deliver results that I am satisfied with.
What about os broken template? Ubuntu 20.04 not working in tyoco 40
We have to throttle these so it may take longer than 1 per minute. If too many people start setting them up at once, the node overloads right now or causes the issues previously described. I'm monitoring it actively and will give it room to breath before resuming, so you can assume a few stop/restarts in the automated scripts throughout the day.
These are still in the queue. I had a very busy day with no time to even post around here, but it's getting a little bit less busy so I should get to it soon.
@VirMach Hi, I applied to replace rDNS, but it has not been replaced after a day, Solusvm says.
I guess it's because the rDNS API hasn't been updated, I checked xtom's documentation, there is a way to modify rDNS.

curl -X POST "https://console.xtom.com/api/service/@id/rdns" \\ -H "Content-Type: application/json" \\ -d "{ \"ipaddress\": { \"key\": \"value\" } }"https://console.xtom.com/userapi#reverse-dns-101
Hope it helps your work
PS: These texts are copied from page 110, I hope I didn't make the mistake last time, I hope the problem can be solved, thank you.
When will the large storage server be activated? Let's have an idea, no need to wait so uninformed
This is a request from a different region.The first one is the 21.07.07 migration payment, which is about to expire and has not yet been migrated.Second, it was fine the other day, so why did it start fluctuating last night and no fixes were made, and I wasn't the only one having problems.Thirdly, has it been tested since yesterday until now? No breaks are taken in between.Fourth, why are other nodes not affected when they are also constantly being tested?I send these just to let him find the problem earlier and correct it in time.I send these just to let him find the problem earlier and correct it in time
Ofen ticket the boss have no time to deal with.
If I had an update on these, it would be provided. I'm going to try to provide an overall update for everything by Monday.
Please explain why other nodes have no cpu abuse from kernel panic and please pose more moments let people to say i said is wrong opr not.