|
|
Hello,
A number of serious security vulnerabilities affecting multiple CPU architectures were recently disclosed by Google’s Project Zero team as outlined in our blog post[1]. In order to address the Meltdown vulnerability, your Linode will need to be upgraded from Xen to KVM.
Your Linode will remain in Tokyo 1, and your IP address(es) *will not change*. However, we strongly recommend that you migrate to Tokyo 2 in the near future. Migrating to Tokyo 2 will give you access to our latest plans[2], our new backbone network[3], and soon, our Block Storage[4] Service.
This Linode will enter a migration queue at the time and date listed below. The migration will move at a rate of about 3 - 5 GB per 1 minute:
Thursday, February 15, 2018 at 22:00 UTC (Friday, February 16, 2018 at 07:00 JST)
Your Linode will be cleanly shutdown, migrated to a new KVM host, and booted. Your Linode’s IP address(es) will not change. During the migration, your Linode will be offline. Below are some additional details about this process:
- What do I need to do?
If you’d like to migrate ahead of time, you can do so by clicking the “Migrate” button at the top of the Linode Dashboard. We strongly recommend you run through our Reboot Survival guide[5] before this migration.
If you do nothing, your Linode will enter a migration queue at the above referenced time.
- Can I remain on Xen?
Due to the nature of the Meltdown vulnerability, remaining on Xen is not an option.
- Can I postpone my migration?
The urgent nature of these vulnerabilities has forced us to move quickly. While you cannot postpone your migration deadline, you can start it early at the time of your choosing.
Please reach out to us if you have any additional questions
- Sean Mintiens
Datacenter Operations |
|
English
简体中文
繁體中文
한국 사람
日本語
Deutsch
русский
بالعربية
TÜRKÇE
português
คนไทย
french
发表于 2018-1-31 23:30:32