All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
NatVPS: Migration to KVM
Just received the migration mail from natvps.net
There seem some improvements @Abd promised to make. Thank you very much.
Here is the full mail:
Embracing KVM: A Leap Forward for Your Hosting Experience!
We're thrilled to announce that we're transitioning our hosting platform from OpenVZ-7 to KVM virtualization. This significant upgrade will bring a host of benefits to your hosting experience.
The reason for this migration is not only the numerous benefits of KVM virtualization but also the fact that OpenVZ-7 is no longer maintained and is practically an End-Of-Life platform. As you probably have experienced, we have had numerous issues with OpenVZ virtualization platform which include but not limited to: frequent VM corruption, IPv6 connectivity issues, broken server rebuilds, limited client side controls, ... . Migration to KVM virtualization will provide a stable platform that not only resolves the aforementioned issues but also in conjunction with much more modern VirtFusion control panel, provides a feature-rich interface that provides access to a plethora of features including superior performance due to direct hardware access and minimal overhead, much more secure servers because of isolated kernels, complete server monitoring and statistics interface, domain/port forwarding, IPv6 address management, hostname control, ... .
As part of this migration process, a number of changes will be applied:
• All the current OpenVZ-7 services will be transitioned to KVM virtualization.
• All the clients with 128MB RAM services will be migrated to 256MB RAM service for free.
• Some locations will need to be discontinued because of feasibility concerns as KVM virtualization takes much more resources. These locations include: South Africa, Chile, Hong Kong, Poland, and Switzerland. The active services in these locations will be recreated on one of our other locations.
• Los Angeles & New York will be consolidated to a single location within US for feasibility.
• Clients will get at least 10 days to move their data or make backups of them.
Estimated start date for KVM plans implementation: 4th October 2024
Estimated finish date: 20th November 2024
We're committed to providing you with the best possible hosting experience, and this transition to KVM is a major step in that direction. More details and exact schedule for each location will be communicated later on.
Best regards,
NatVPS Support Team
Comments
Welp I'd like if they did these announcements back when they discontinued Poland (and why is even Poland there when the server crashed a while ago?). Now goodbye to my Chilean VM, I guess
I got frustrated and rage quit all my services with them a couple months ago. Guess I made the right decision since they're closing them all now.
Update on Migration:
France KVM services are ready and clients who have service(s) in that location, can now open a ticket and request for creation of France KVM service(s).
KVM services for other locations will become online in coming days.
Same here. It was 1 year ago.
Will the old OVZ VPS be terminated as soon as the new KVM VPS goes online?
Or will both VPSs be online (temporarily) so that I can manually transfer the data?
We can keep the old VM online so that you can tranfer data. Please mention in ticket if you need it done this way 🙂
We coordinated with the upstream provider (mevspace) to replace the disks twice, but unfortunately, the new disks continued to exhibit errors. It turned out they were consumer-grade drives, not data center grade, and I was informed that replacements could only be initiated when usage reached 70%.
At that point, with the data already corrupted, further attempts seemed futile. Therefore, we decided to close that location and migrate users to more reliable options.
I completely understand the frustration. The challenges arise from bugs related to IPv6 in the newer OVZ7 updates. Their development team has halted work on VZ7 and is now focusing on VZ9, which is still unstable. Additionally, there were other issues in the integration of OVZ7 with control panel.
This is why we made the transition to KVM—to provide a more reliable experience.
Unfortunately, we had to close some of the more exotic locations due to the higher costs associated with them. With the new KVM NAT lineup, we’re operating at cost, no profit margins, as we rely on other sources of income to sustain our services.
KVM virtualization requires significantly more resources since it runs an isolated kernel for each VM, making it unsustainable to absorb those expenses. This is why we cannot continue to support those locations.
Why not use LXC?
I tried LXC twice in the past within a public VPS hosting environment (you can see our offer posts in the comment history too), and both outcomes were disastrous.
Clients faced numerous issues, including open file limits, problems with tun/tap, and Docker applications not working properly with cgroups and snapd. We ultimately had to migrate them to KVM.
While private use is fine, I found LXC unsuitable for public hosting due to significant functionality issues.
Zap has been doing it for years, and both Docker and tun/tap works fine.
Are there any updates for other locations?