Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Wonders if the ping results are better to my MIA VM.. previously measured in seconds.
[Update] Seems to be a routing problem from a different provider in Texas. Other routes/providers/VM look OK.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Looks like a route change happened too in AMS.
Earlier, it was via Arelion for me, 280ms routed via US.
Now it's properly routed (it looks like a direct peering with my ISP at LINX), and getting 130ms.
@VirMach - Regarding the Debian 12 template I see the following error when doing apt upgrade:
apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
linux-image-6.1.0-29-amd64
The following packages will be upgraded:
bsdutils eject fdisk libblkid1 libfdisk1 libglib2.0-0 libglib2.0-data libmount1 libnss-systemd libpam-systemd libpython3.11 libpython3.11-minimal
libpython3.11-stdlib libsmartcols1 libsystemd-shared libsystemd0 libudev1 libuuid1 linux-image-amd64 mount openssh-client openssh-server openssh-sftp-server
python3-pkg-resources python3-urllib3 python3.11 python3.11-minimal systemd systemd-sysv systemd-timesyncd ucf udev util-linux util-linux-extra
34 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
24 not fully installed or removed.
Need to get 0 B/90.5 MB of archives.
After this operation, 409 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up base-files (12.4+deb12u9) ...
Installing new version of config file /etc/debian_version ...
(Reading database ... 66449 files and directories currently installed.)
Preparing to unpack .../python3-pkg-resources_66.1.1-1+deb12u1_all.deb ...
Segmentation fault
dpkg: warning: old python3-pkg-resources package pre-removal script subprocess returned error exit status 139
dpkg: trying script from the new package instead ...
Segmentation fault
dpkg: error processing archive /var/cache/apt/archives/python3-pkg-resources_66.1.1-1+deb12u1_all.deb (--unpack):
new python3-pkg-resources package pre-removal script subprocess returned error exit status 139
Traceback (most recent call last):
File "/usr/bin/py3compile", line 323, in <module>
main()
File "/usr/bin/py3compile", line 302, in main
compile(files, versions,
File "/usr/bin/py3compile", line 187, in compile
cfn = interpreter.cache_file(fn, version)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/python3/debpython/interpreter.py", line 212, in cache_file
(fname[:-3], self.magic_tag(version), last_char))
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/python3/debpython/interpreter.py", line 246, in magic_tag
return self._execute('import imp; print(imp.get_tag())', version)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/python3/debpython/interpreter.py", line 359, in _execute
raise Exception('{} failed with status code {}'.format(command, output['returncode']))
Exception: ('python3.11', '-c', 'import imp; print(imp.get_tag())') failed with status code -11
Segmentation fault
dpkg: error while cleaning up:
installed python3-pkg-resources package post-installation script subprocess returned error exit status 139
Preparing to unpack .../bsdutils_1%3a2.38.1-5+deb12u3_amd64.deb ...
Unpacking bsdutils (1:2.38.1-5+deb12u3) over (1:2.38.1-5+deb12u2) ...
Errors were encountered while processing:
/var/cache/apt/archives/python3-pkg-resources_66.1.1-1+deb12u1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Not a Debian user so not sure if it is just me, or the template.
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
@FrankZ said: @VirMach - Regarding the Debian 12 template I see the following error when doing apt upgrade:
apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
linux-image-6.1.0-29-amd64
The following packages will be upgraded:
bsdutils eject fdisk libblkid1 libfdisk1 libglib2.0-0 libglib2.0-data libmount1 libnss-systemd libpam-systemd libpython3.11 libpython3.11-minimal
libpython3.11-stdlib libsmartcols1 libsystemd-shared libsystemd0 libudev1 libuuid1 linux-image-amd64 mount openssh-client openssh-server openssh-sftp-server
python3-pkg-resources python3-urllib3 python3.11 python3.11-minimal systemd systemd-sysv systemd-timesyncd ucf udev util-linux util-linux-extra
34 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
24 not fully installed or removed.
Need to get 0 B/90.5 MB of archives.
After this operation, 409 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up base-files (12.4+deb12u9) ...
Installing new version of config file /etc/debian_version ...
(Reading database ... 66449 files and directories currently installed.)
Preparing to unpack .../python3-pkg-resources_66.1.1-1+deb12u1_all.deb ...
Segmentation fault
dpkg: warning: old python3-pkg-resources package pre-removal script subprocess returned error exit status 139
dpkg: trying script from the new package instead ...
Segmentation fault
dpkg: error processing archive /var/cache/apt/archives/python3-pkg-resources_66.1.1-1+deb12u1_all.deb (--unpack):
new python3-pkg-resources package pre-removal script subprocess returned error exit status 139
Traceback (most recent call last):
File "/usr/bin/py3compile", line 323, in <module>
main()
File "/usr/bin/py3compile", line 302, in main
compile(files, versions,
File "/usr/bin/py3compile", line 187, in compile
cfn = interpreter.cache_file(fn, version)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/python3/debpython/interpreter.py", line 212, in cache_file
(fname[:-3], self.magic_tag(version), last_char))
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/python3/debpython/interpreter.py", line 246, in magic_tag
return self._execute('import imp; print(imp.get_tag())', version)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/python3/debpython/interpreter.py", line 359, in _execute
raise Exception('{} failed with status code {}'.format(command, output['returncode']))
Exception: ('python3.11', '-c', 'import imp; print(imp.get_tag())') failed with status code -11
Segmentation fault
dpkg: error while cleaning up:
installed python3-pkg-resources package post-installation script subprocess returned error exit status 139
Preparing to unpack .../bsdutils_1%3a2.38.1-5+deb12u3_amd64.deb ...
Unpacking bsdutils (1:2.38.1-5+deb12u3) over (1:2.38.1-5+deb12u2) ...
Errors were encountered while processing:
/var/cache/apt/archives/python3-pkg-resources_66.1.1-1+deb12u1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Not a Debian user so not sure if it is just me, or the template.
What node? I want to see if it's the latest version or an older one. That problem was very specifically taken out so I'm hoping it's due to an incorrect sync. Did your version come up with an annoying setup script when you first logged in?
@VirMach said: Did your version come up with an annoying setup script when you first logged in?
Yes.
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
I wanted to try reinstalling my system yesterday using the debian 12 template, I selected “[Ryzen Compatible] Debian 12 (64-Bit) BETA” and pressed the reinstall button, the page gave me a new password and the template name showed up as debian 12, but Nothing has happened since then, not even my vps running debian 11 was automatically rebooted.
@VirMach you may be developing a disk, or disk abuse issue on LAXA022. Wait states are uncharacteristically high at 30+% for the last 90 minutes.
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
@VirMach said: That problem was very specifically taken out so I'm hoping it's due to an incorrect sync. Did your version come up with an annoying setup script when you first logged in?
An error occurred while executing Do you want to check quick installers? (y/N) y on the LAXA030 node.
Linux ******-VM 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
-----------------------------------------
Initial Setup. Press ENTER or N to skip.
-----------------------------------------
Do you want to install a desktop environment? (y/N)
n
Enter new SSH port number or leave blank for default (22)
Do you want to enable stricter firewall rules? (Only permit SSH) (y/N)
y
Do you want to see more options? (y/N)
y
modprobe: ERROR: could not insert 'nf_tables': Key was rejected by service
Firewall stopped and disabled on system startup
Resetting all rules to installed defaults. This may disrupt existing ssh
connections. Proceed with operation (y|n)? Backing up 'user.rules' to '/etc/ufw/user.rules.20250112_073345'
Backing up 'before.rules' to '/etc/ufw/before.rules.20250112_073345'
Backing up 'after.rules' to '/etc/ufw/after.rules.20250112_073345'
Backing up 'user6.rules' to '/etc/ufw/user6.rules.20250112_073345'
Backing up 'before6.rules' to '/etc/ufw/before6.rules.20250112_073345'
Backing up 'after6.rules' to '/etc/ufw/after6.rules.20250112_073345'
Default incoming policy changed to 'deny'
(be sure to update your rules accordingly)
Default outgoing policy changed to 'allow'
(be sure to update your rules accordingly)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Rules updated
Rules updated (v6)
Command may disrupt existing ssh connections. Proceed with operation (y|n)? Firewall is active and enabled on system startup
Firewall reloaded
Do you want to generate SSH key and disable root password login? (y/N)
n
Do you want to check quick installers? (y/N)
y
Hit:1 https://deb.debian.org/debian bookworm InRelease
Hit:2 https://deb.debian.org/debian bookworm-updates InRelease
Hit:3 https://deb.debian.org/debian-security bookworm-security InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libcurl4
The following NEW packages will be installed:
curl libcurl4
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 705 kB of archives.
After this operation, 1,359 kB of additional disk space will be used.
Get:1 https://deb.debian.org/debian bookworm/main amd64 libcurl4 amd64 7.88.1-10+deb12u8 [390 kB]
Get:2 https://deb.debian.org/debian bookworm/main amd64 curl amd64 7.88.1-10+deb12u8 [315 kB]
Fetched 705 kB in 0s (5,094 kB/s)
Selecting previously unselected package libcurl4:amd64.
(Reading database ... 32518 files and directories currently installed.)
Preparing to unpack .../libcurl4_7.88.1-10+deb12u8_amd64.deb ...
Unpacking libcurl4:amd64 (7.88.1-10+deb12u8) ...
Selecting previously unselected package curl.
Preparing to unpack .../curl_7.88.1-10+deb12u8_amd64.deb ...
Unpacking curl (7.88.1-10+deb12u8) ...
Setting up libcurl4:amd64 (7.88.1-10+deb12u8) ...
Setting up curl (7.88.1-10+deb12u8) ...
Processing triggers for libc-bin (2.36-9+deb12u9) ...
Hit:1 https://deb.debian.org/debian bookworm InRelease
Hit:2 https://deb.debian.org/debian bookworm-updates InRelease
Hit:3 https://deb.debian.org/debian-security bookworm-security InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libjq1 libonig5
The following NEW packages will be installed:
jq libjq1 libonig5
0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 388 kB of archives.
After this operation, 1,165 kB of additional disk space will be used.
Get:1 https://deb.debian.org/debian bookworm/main amd64 libonig5 amd64 6.9.8-1 [188 kB]
Get:2 https://deb.debian.org/debian bookworm/main amd64 libjq1 amd64 1.6-2.1 [135 kB]
Get:3 https://deb.debian.org/debian bookworm/main amd64 jq amd64 1.6-2.1 [64.9 kB]
Fetched 388 kB in 0s (4,058 kB/s)
Selecting previously unselected package libonig5:amd64.
(Reading database ... 32531 files and directories currently installed.)
Preparing to unpack .../libonig5_6.9.8-1_amd64.deb ...
Unpacking libonig5:amd64 (6.9.8-1) ...
Selecting previously unselected package libjq1:amd64.
Preparing to unpack .../libjq1_1.6-2.1_amd64.deb ...
Unpacking libjq1:amd64 (1.6-2.1) ...
Selecting previously unselected package jq.
Preparing to unpack .../archives/jq_1.6-2.1_amd64.deb ...
Unpacking jq (1.6-2.1) ...
Setting up libonig5:amd64 (6.9.8-1) ...
Setting up libjq1:amd64 (1.6-2.1) ...
Setting up jq (1.6-2.1) ...
Processing triggers for libc-bin (2.36-9+deb12u9) ...
parse error: Invalid numeric literal at line 1, column 7
Pick a number to install, or just press enter to skip:
root@******-VM:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
linux-image-6.1.0-29-amd64
The following packages will be upgraded:
linux-image-amd64
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 69.0 MB of archives.
After this operation, 409 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://deb.debian.org/debian bookworm/main amd64 linux-image-6.1.0-29-amd64 amd64 6.1.123-1 [69.0 MB]
Get:2 https://deb.debian.org/debian bookworm/main amd64 linux-image-amd64 amd64 6.1.123-1 [1,488 B]
Fetched 69.0 MB in 1s (108 MB/s)
Selecting previously unselected package linux-image-6.1.0-29-amd64.
(Reading database ... 32580 files and directories currently installed.)
Preparing to unpack .../linux-image-6.1.0-29-amd64_6.1.123-1_amd64.deb ...
Unpacking linux-image-6.1.0-29-amd64 (6.1.123-1) ...
Preparing to unpack .../linux-image-amd64_6.1.123-1_amd64.deb ...
Unpacking linux-image-amd64 (6.1.123-1) over (6.1.119-1) ...
Setting up linux-image-6.1.0-29-amd64 (6.1.123-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-28-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-28-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-29-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-29-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-29-amd64
W: initramfs-tools configuration sets RESUME=UUID=ea05c755-b18b-41dd-a151-c1dc91e405b4
W: but no matching swap device is available.
I: The initramfs will attempt to resume from /dev/vda2
I: (UUID=3be0b4d9-9285-4f1b-9e80-d2b5dd1137a2)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-29-amd64
Found initrd image: /boot/initrd.img-6.1.0-29-amd64
Found linux image: /boot/vmlinuz-6.1.0-28-amd64
Found initrd image: /boot/initrd.img-6.1.0-28-amd64
Found linux image: /boot/vmlinuz-6.1.0-18-amd64
Found initrd image: /boot/initrd.img-6.1.0-18-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
Setting up linux-image-amd64 (6.1.123-1) ...
root@******-VM:~#
PHXZ004 Update - I'll be working on finalizing these, and watching the node to see if it stays stable. I'll likely ship off PHXZ004 to Los Angeles so it's there as a replacement for PHXZ004 (by being actually PHXZ004 but fixed.) I'm also probably going to visit Los Angeles soon which means potentially some short notice maintenance might happen there if I notice anything needs poking.
@FrankZ said: @VirMach you may be developing a disk, or disk abuse issue on LAXA022. Wait states are uncharacteristically high at 30+% for the last 90 minutes.
Not to brag but I caught this within the first 5 minutes of it starting to happen. And then I failed to fix it and just eventually rebooted. I've already added a note to do some poking for this one specifically. Others on the unofficial poking list are LAXA031, LAXA024, LAXA012, LAXA011, LAXA005, LAX1Z013, LAXA028, LAX1Z019. Most of them just maybe need thermal paste and maybe redoing the NVMe heatsinks. But I'll probably discover other things while there.
@tototo said: An error occurred while executing Do you want to check quick installers? (y/N) y on the LAXA030 node.
That's mostly expected unless I skipped over reading something.
@VirMach said: Did your version come up with an annoying setup script when you first logged in?
Yes.
Okay that's probably not good but it's also good in some other way. I won't elaborate any further as we'd have to have a wall of essay lesson/moaning about SolusVM.
Virmach left the safety of Buffalo and transitioned to Ryzen is what happened.
Ended up alienating a huge portion of the customer base in the process.
That, uhhh, is one of the more slanted ways of presenting a couple facts.
I encourage you to present your version of what happened over the last few years that took Virmach on LET from being the king of bargain VPSes to a pariah.
Comments
paaaaaaaaaaaaaaaaanic Amsterdam down
also Frankfurt if someone didn't update theirs hostnames
https://status.virm.ac
also dead
epic panic deadpool omg
We back!
Downtime: 6 min
omg deadpool cancelled
--
And we dead again after 3 minutes
omg deadpool back on track!
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
mine in AMS is still down. thats a pity it was up for quite a while
going to the cancellation queue.
I bench YABS 24/7/365 unless it's a leap year.
Is AMSD dead?
down for me. the recently migrated node right?
I bench YABS 24/7/365 unless it's a leap year.
VirBot appears to be down also.
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
I hope Virmach restores the $3 transfer function. time to reconsolidate after BF/CM/XMAS/NY
I bench YABS 24/7/365 unless it's a leap year.
AMS and virbot are back online!
Have the honor of being the crybaby who pays $20 for a 128MB VPS at VirMach in 2023.
ok so it was network related
I bench YABS 24/7/365 unless it's a leap year.
Wonders if the ping results are better to my MIA VM.. previously measured in seconds.
[Update] Seems to be a routing problem from a different provider in Texas. Other routes/providers/VM look OK.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Call the AMS 911
xTom's own branch V.PS also is going to migrate their Tokyo location tomorrow.
AMS connection hickups, seem to be starting again
Ok possibly false alarm, seems fine, think was just an isolated case this time with only 1 of my AMS.
Looks like a route change happened too in AMS.
Earlier, it was via Arelion for me, 280ms routed via US.
Now it's properly routed (it looks like a direct peering with my ISP at LINX), and getting 130ms.
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
@VirMach - Regarding the Debian 12 template I see the following error when doing apt upgrade:
Not a Debian user so not sure if it is just me, or the template.
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
What node? I want to see if it's the latest version or an older one. That problem was very specifically taken out so I'm hoping it's due to an incorrect sync. Did your version come up with an annoying setup script when you first logged in?
Node: ATLZ006
Yes.
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Good evening. Any deals?
I wanted to try reinstalling my system yesterday using the debian 12 template, I selected “[Ryzen Compatible] Debian 12 (64-Bit) BETA” and pressed the reinstall button, the page gave me a new password and the template name showed up as debian 12, but Nothing has happened since then, not even my vps running debian 11 was automatically rebooted.
Node name: ATLZ034 @VirMach
I had to manually reinstall debian 12.8 and a few hours later debian released the latest 12.9 and today I reinstalled the system again.
Have the honor of being the crybaby who pays $20 for a 128MB VPS at VirMach in 2023.
@VirMach you may be developing a disk, or disk abuse issue on LAXA022. Wait states are uncharacteristically high at 30+% for the last 90 minutes.
Peace on earth will come to stay, when we all live as LESbians every day.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
An error occurred while executing
Do you want to check quick installers? (y/N) y
on the LAXA030 node.PHXZ004 Update - I'll be working on finalizing these, and watching the node to see if it stays stable. I'll likely ship off PHXZ004 to Los Angeles so it's there as a replacement for PHXZ004 (by being actually PHXZ004 but fixed.) I'm also probably going to visit Los Angeles soon which means potentially some short notice maintenance might happen there if I notice anything needs poking.
Not to brag but I caught this within the first 5 minutes of it starting to happen. And then I failed to fix it and just eventually rebooted. I've already added a note to do some poking for this one specifically. Others on the unofficial poking list are LAXA031, LAXA024, LAXA012, LAXA011, LAXA005, LAX1Z013, LAXA028, LAX1Z019. Most of them just maybe need thermal paste and maybe redoing the NVMe heatsinks. But I'll probably discover other things while there.
That's mostly expected unless I skipped over reading something.
Sounds like this one needs a resync.
Okay that's probably not good but it's also good in some other way. I won't elaborate any further as we'd have to have a wall of essay lesson/moaning about SolusVM.
Virtfusion whennnnnnnnnnnnbb
I bench YABS 24/7/365 unless it's a leap year.
Have you considered creating a Telegram channel to announce these messages? Not every user watches LES.
Tough shit!
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
A bit harsh .... ;-)
Running Debian 12.9 version
What happened?
https://lowendtalk.com/discussion/201767/virmach-not-recommended-for-2025
Virmach left the safety of Buffalo and transitioned to Ryzen is what happened.
Ended up alienating a huge portion of the customer base in the process.
That, uhhh, is one of the more slanted ways of presenting a couple facts.
I encourage you to present your version of what happened over the last few years that took Virmach on LET from being the king of bargain VPSes to a pariah.