1 |
Ok, so just got the notice that Linode is discontinuing their support |
2 |
for Xen, and forcing everyone to migrate their VMs to KVM. |
3 |
|
4 |
Of course this comes at the worst possible time for me, when I'm out of |
5 |
the country, and won't be back before the deadline (the 9th). |
6 |
|
7 |
I have a week, so am trying to do everything I can to ensure they come |
8 |
up successfully. I have two, one production, and a second one we were |
9 |
going to use as a dev/test server, but in reality, we don't use it, |
10 |
although I want to keep it running too (will perform the migration on it |
11 |
first). |
12 |
|
13 |
I'm especially worried, because these VMs are running an ancient web |
14 |
application that requires older versions of Apache, PHP and Postgresql, |
15 |
so cannot be and haven't been updated in a very long time (I kept them |
16 |
up to date as long as I could by pinning the old apps and testing |
17 |
updates on the dev/test server until it just got to be too much work)... |
18 |
|
19 |
They are both (thankfully) running a current Linode kernel, so I HOPE |
20 |
this migration won't kill either of them. |
21 |
|
22 |
One thing I do seem to recall is there was somewhere that I had to |
23 |
define Xen as the virtualization environment being used, but I can't |
24 |
remember where I did that. Was that in the kernel config? If so, their |
25 |
tool should (hopefully) handle that change. |
26 |
|
27 |
Anyway, was hoping some kind souls here might give me a few things to |
28 |
check and possibly do proactively to ensure a smooth transition. |
29 |
|
30 |
Emerge --info for each one attached |
31 |
|
32 |
Thanks! |
33 |
|
34 |
emerg--i |