Yes, you will get kernel panic after the installation is done, at that point you need to POWER OFF the VPS and reboot it and you will be able to log in via VNC using the root password.
Nope the kernel panic happened after the reboot, it seems like 128MB just didn't cut it for some reason. Tried twice using different image (one with cloud-init and one without) but to no avail
That's right, the kernel panic does happen after the first reboot, the key is that after the kernel panic happens, the normal reboot doesn't work, You need to go to “Full VPS Control Panel” and click “Power Off” instead of other buttons, then reboot again. At this point you should see the login screen.
PS: Make sure you use a cloud image, virmach's default debian 10 image won't run on a VPS with only 128M RAM.
I took this approach to install debian 10.13 on my mystery box.
If you take the proper steps, you can do it too.
It is a cloud image, I might just try Debian 9 instead and I did poweroff before reboot...
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
Yes, you will get kernel panic after the installation is done, at that point you need to POWER OFF the VPS and reboot it and you will be able to log in via VNC using the root password.
Nope the kernel panic happened after the reboot, it seems like 128MB just didn't cut it for some reason. Tried twice using different image (one with cloud-init and one without) but to no avail
That's right, the kernel panic does happen after the first reboot, the key is that after the kernel panic happens, the normal reboot doesn't work, You need to go to “Full VPS Control Panel” and click “Power Off” instead of other buttons, then reboot again. At this point you should see the login screen.
PS: Make sure you use a cloud image, virmach's default debian 10 image won't run on a VPS with only 128M RAM.
I took this approach to install debian 10.13 on my mystery box.
If you take the proper steps, you can do it too.
It is a cloud image, I might just try Debian 9 instead and I did poweroff before reboot...
I'll describe them in order:
enter rescue mode and install the cloud image with DD
exit rescue mode and the system should automatically reboot and go into a kernel panic state
Use the POWER OFF button in the Full VPS Control Panel
@core said: Yes, according to him, he should have suspended me earlier, but he was very considerate and waited until the PayPal payment exceeded 6 months before suspending it
What are you saying here?
@core said: He still didn’t answer my most important question. My VPS returned to normal for a short time, and I didn’t receive any notification
That's not a question it's a statement.
@core said: Also please note that there is no email reminder when the server is restored to normal. Please refresh the page 24 hours after payment until the server is restored.
Surely your monitoring saw it return to service. A relatively minor thing which most will never notice as they will never get suspended.
@core said: Yes, according to him, he should have suspended me earlier, but he was very considerate and waited until the PayPal payment exceeded 6 months before suspending it
What are you saying here?
@core said: He still didn’t answer my most important question. My VPS returned to normal for a short time, and I didn’t receive any notification
That's not a question it's a statement.
@core said: Also please note that there is no email reminder when the server is restored to normal. Please refresh the page 24 hours after payment until the server is restored.
Surely your monitoring saw it return to service. A relatively minor thing which most will never notice as they will never get suspended.
I installed the Windows system through the backend. Where can I monitor whether my VPS has returned to normal? Please tell me the URL
In fact, I visited the virmach website within 2 hours after payment. I don’t know how I can know that my VPS has returned to normal in the first time except this method. At least virmach official does not provide it (if there is no email reminder)
Yes, you will get kernel panic after the installation is done, at that point you need to POWER OFF the VPS and reboot it and you will be able to log in via VNC using the root password.
Nope the kernel panic happened after the reboot, it seems like 128MB just didn't cut it for some reason. Tried twice using different image (one with cloud-init and one without) but to no avail
That's right, the kernel panic does happen after the first reboot, the key is that after the kernel panic happens, the normal reboot doesn't work, You need to go to “Full VPS Control Panel” and click “Power Off” instead of other buttons, then reboot again. At this point you should see the login screen.
PS: Make sure you use a cloud image, virmach's default debian 10 image won't run on a VPS with only 128M RAM.
I took this approach to install debian 10.13 on my mystery box.
If you take the proper steps, you can do it too.
It is a cloud image, I might just try Debian 9 instead and I did poweroff before reboot...
I'll describe them in order:
enter rescue mode and install the cloud image with DD
exit rescue mode and the system should automatically reboot and go into a kernel panic state
Use the POWER OFF button in the Full VPS Control Panel
BOOT
5.login (you need to use VNC)
debian 9 cloud image also works perfectly.
Yup thats exactly what I did, unfortunately I dont think I want to spend more time on this but thanks for the suggestions!
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
I finally had my VirMach only regional failover system fail completely after 1456 days [3.98 years] of continuous website uptime.
Was it VirMach's fault ?
Not this time. it was my fault for not updating a certificate chain.
I had 15 minutes of downtime while I corrected it.
So I'm now down to 99.9992846% uptime with VirMach on this production website.
Haha, is there a problem? 1G switching is the most basic use, isn't it?
No idea, just making fun of yours 30% unused memory.
Honey, I know you gave me 1000$ for the new PC, I only used 70% of budget!!!!!!
-- Oh, ignore that extra loan for 2000$ I've spent.
Are you here to be funny? I bought 768mb of memory and paid for it too. Why do you say I only paid 70% of the money?
Just for the sake of clarity, using 70% swap space isn’t using the memory you paid for; it’s using disk space as memory (thus causing high IOPS) to overcome the fact that 768MB RAM isn’t sufficient.
Tokyo migrations happening likely before February 4th. Emails will go out soon with some more information.
Same contract/partners (xTom/Cat Networks.) What happened was we're currently in BBTower building, and traffic provided through them. BBTower changed connectivity from inbound IIJ to NTT, which negatively affected some customers, mostly in China (a few people mentioned it here.) Server will physically be moved to another building, NTT East Komagome. Even though the building's name is NTT, what will actually happen after this change is that we'll receive network more directly from xTom, which have their own blend, which will restore inbound IIJ. (Just making a note of that, since some people might see "NTT" and incorrectly assume this means it's changing to NTT.) From my understanding, they have NTT East Komagome connected to the other facility they operate out of which is Equinix TY8.
IP addresses stay the same and your service stays on the same node. What will change later in another maintenance afterward (not this one) is that we're finally activating/connecting other servers we sent out here. That may involve some other changes, likely migrations to minimize IP changes, but potentially also some IP changes if necessary.
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.
In stasis until the shitposting stops/abates.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural. 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.
@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?
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 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.
In stasis until the shitposting stops/abates.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural. It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
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.
@Newyawker said:
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.
A wall of text would be required for all the details.
The short version, way I heard it, is that Jon is a dick. When he was still running Colo-Crossings and the VirMach contract came up for renewal he raised VirMach's rates by ~3x. VirMach left Colo-Crossing and Jon and Raindog308 then conducted a smear campaign on OGF in retaliation, so VirMach left LET. VirMach has recently stated that when Jon no longer owns the OGF he will return there.
Personally I expect that this had something to do with RackNerd becoming Jon's new best friend around this time. Because $$$$.
I should also note that even before the above happened there were two groups of members on LET regarding VirMach. They were commonly refereed to as the lovers [licking dogs] and the haters.
EDIT: I really should not have said the crossed out part above. I reacted poorly. Apologies to everyone.
@cybertech said:
thats fucked up really. dont know about the $$$$, but racknerd has better support and stability albeit with much older CPUs.
Some of us were screwed by Dustin the felon from the Alpharacks/Woothosting days and won't buy RN. And the best deals from from Virmach for VPSs to play with are still cheaper.
Last I heard, they don't use in-house support, they use BobCares which is actually pretty good. Their higher prices charged, and older lower cost servers allows money to be spent on this outside support and other things. That is not a knock on RackNerd, it's just two different companies with two different business plans.
@cybertech said:
thats fucked up really. dont know about the $$$$, but racknerd has better support and stability albeit with much older CPUs.
Some of us were screwed by Dustin the felon from the Alpharacks/Woothosting days and won't buy RN. And the best deals from from Virmach for VPSs to play with are still cheaper.
my point being Virmach should not be cheaper if overall stability and support is on par, given that he runs solely on Ryzen, and many of the locations actually utilize better network than many providers as i have compared.
thats a huge pity.
however time is ticking and 3900/3950/5900/5950X are starting to trail off against latest Ryzen and EPYC Milan / Genoa in terms of speed and contention ratio.
i still enjoy YABSing the $7 deals with downtime expectations but not much more.
Last I heard, they don't use in-house support, they use BobCares which is actually pretty good. Their higher prices charged, and older lower cost servers allows money to be spent on this outside support and other things. That is not a knock on RackNerd, it's just two different companies with two different business plans.
Do they?
My interactions so far has been with tons of Indians with fake names 😂
And they are really poor when there is actually an issue, and 90% of the times, I have to escalate directly to Dustin for a resolution.
@FrankZ said: @sh97 Not sure how to respond. As BobCares is out of India.
That makes sense, wow.
And you know what's even more suprising for me? They are based out of Kochi, which is just like an hour away.
But still, my support experience hasn't been the best. Sure, you get sub 10 minutes responses, but for anything even remotely "complex", it has to be escalated to Dustin or Anthony.
Comments
It is a cloud image, I might just try Debian 9 instead and I did poweroff before reboot...
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
I'll describe them in order:
5.login (you need to use VNC)
debian 9 cloud image also works perfectly.
I installed the Windows system through the backend. Where can I monitor whether my VPS has returned to normal? Please tell me the URL
In fact, I visited the virmach website within 2 hours after payment. I don’t know how I can know that my VPS has returned to normal in the first time except this method. At least virmach official does not provide it (if there is no email reminder)
Yup thats exactly what I did, unfortunately I dont think I want to spend more time on this but thanks for the suggestions!
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
Maybe because he ran out of flan
blog archives
I dont understand
Let me catch up on some stuff and then yes.
Just for the sake of clarity, using 70% swap space isn’t using the memory you paid for; it’s using disk space as memory (thus causing high IOPS) to overcome the fact that 768MB RAM isn’t sufficient.
Tokyo migrations happening likely before February 4th. Emails will go out soon with some more information.
Same contract/partners (xTom/Cat Networks.) What happened was we're currently in BBTower building, and traffic provided through them. BBTower changed connectivity from inbound IIJ to NTT, which negatively affected some customers, mostly in China (a few people mentioned it here.) Server will physically be moved to another building, NTT East Komagome. Even though the building's name is NTT, what will actually happen after this change is that we'll receive network more directly from xTom, which have their own blend, which will restore inbound IIJ. (Just making a note of that, since some people might see "NTT" and incorrectly assume this means it's changing to NTT.) From my understanding, they have NTT East Komagome connected to the other facility they operate out of which is Equinix TY8.
IP addresses stay the same and your service stays on the same node. What will change later in another maintenance afterward (not this one) is that we're finally activating/connecting other servers we sent out here. That may involve some other changes, likely migrations to minimize IP changes, but potentially also some IP changes if necessary.
cant wait for black friday 2025 tokyo
I bench YABS 24/7/365 unless it's a leap year.
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.
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.
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!
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.
In stasis until the shitposting stops/abates.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural.
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.
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.
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. :'(
@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.
An error occurred while executing
Do you want to check quick installers? (y/N) yon 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!
In stasis until the shitposting stops/abates.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural.
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.
Jon is that you?
EDIT: Damn auto-correct.
A wall of text would be required for all the details.
The short version, way I heard it, is that Jon is a dick. When he was still running Colo-Crossings and the VirMach contract came up for renewal he raised VirMach's rates by ~3x. VirMach left Colo-Crossing and Jon and Raindog308 then conducted a smear campaign on OGF in retaliation, so VirMach left LET. VirMach has recently stated that when Jon no longer owns the OGF he will return there.
Personally I expect that this had something to do with RackNerd becoming Jon's new best friend around this time. Because $$$$.
I should also note that even before the above happened there were two groups of members on LET regarding VirMach. They were commonly refereed to as the lovers [licking dogs] and the haters.
EDIT: I really should not have said the crossed out part above. I reacted poorly. Apologies to everyone.
thats fucked up really. dont know about the $$$$, but racknerd has better support and stability albeit with much older CPUs.
I bench YABS 24/7/365 unless it's a leap year.
Some of us were screwed by Dustin the felon from the Alpharacks/Woothosting days and won't buy RN. And the best deals from from Virmach for VPSs to play with are still cheaper.
Last I heard, they don't use in-house support, they use BobCares which is actually pretty good. Their higher prices charged, and older lower cost servers allows money to be spent on this outside support and other things. That is not a knock on RackNerd, it's just two different companies with two different business plans.
my point being Virmach should not be cheaper if overall stability and support is on par, given that he runs solely on Ryzen, and many of the locations actually utilize better network than many providers as i have compared.
thats a huge pity.
however time is ticking and 3900/3950/5900/5950X are starting to trail off against latest Ryzen and EPYC Milan / Genoa in terms of speed and contention ratio.
i still enjoy YABSing the $7 deals with downtime expectations but not much more.
end of coffee talk
I bench YABS 24/7/365 unless it's a leap year.
Do they?
My interactions so far has been with tons of Indians with fake names 😂
And they are really poor when there is actually an issue, and 90% of the times, I have to escalate directly to Dustin for a resolution.
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
@sh97 Not sure how to respond. As BobCares is out of India.
That makes sense, wow.
And you know what's even more suprising for me? They are based out of Kochi, which is just like an hour away.
But still, my support experience hasn't been the best. Sure, you get sub 10 minutes responses, but for anything even remotely "complex", it has to be escalated to Dustin or Anthony.
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
He's "officially back" since HostPapa took over.
QuickPacket - Dedicated Servers in Ashburn, Los Angeles, Chicago