Hi,
If you aren't running 32-bit Ubuntu then you can probably skip this
message.
A customer reported that they'd updated their 32-bit Ubuntu 18.04
VPS and now the kernel doesn't boot. I had a look and indeed the
latest 32-bit linux-image-generic immediately kernel panics.
This means that if you're on 32-bit and you try to boot into it,
your VPS won't boot. Also it means that currently 32-bit Ubuntu
18.04 installs aren't possible because the installer kernel won't
boot.
I haven't yet had any reports of the same thing happening in other
versions of Ubuntu, but it might do since presumably there is some
security patch being pushed out (I'm going to take a wild stab at
32-bit KPTI protection) that is broken, so it might hit any
supported version of 32-bit Ubuntu.
The only quick way I have found to work around this at present is
to run a 64-bit kernel. Here's how you'd do that, assuming that your
VPS is currently unbootable.
xen-shell> rescue
(boot and log in to rescue VM)
$ sudo mount /dev/xvda1 /mnt
$ sudo mount --bind /dev /mnt/dev
$ sudo mount --bind /sys /mnt/sys
$ sudo mount --bind /proc /mnt/proc
$ sudo chroot /mnt /bin/bash
# dpkg --add-architecture amd64
# apt update
# apt install linux-image-generic:amd64
# exit
$ sudo halt
xen-shell> arch x86_64
xen-shell> boot
This:
1) Enables multi-arch on your VPS and says that amd64 architecture
packages are acceptable
2) Installs a 64-bit kernel
3) Boots into it
You will then be running a 64-bit kernel with a 32-bit user land. It
should work fine and continue offering you updated 64-bit kernel
packages and updates 32-bit packages for everything else.
If you were brave you could completely cross-grade to amd64 but it
is a complicated, risky and unsupported procedure.
Another workaround may be to boot into rescue and do a chroot as
above, but then downgrade the kernel package.
I will attempt to replicate the problem and report it to Ubuntu.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hello,
I'm afraid there's another round of security updates needed as a
flaw has been discovered in some (Xen-specific) parts of the Linux
kernel.
It's not the hypervisor this time but it still needs a kernel
upgrade on our side so the effect is basically the same, so there
will be another reboot of all servers, likely in the early hours (UK
time) of 11–13 August.
Customers will soon receive an individual email confirming the
hour-long maintenance window specific to their server(s). The actual
work is expected to take 10–30 minutes within that window.
As before we should be able to do a suspend/restore if you have
enabled that at:
<https://panel.bitfolk.com/account/config/>
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Hi,
It looks like the recent Debian stretch updated kernel doesn't boot
under Xen:
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903767>
This also means that right now you cannot self-install Debian
stable.
If you reboot and experience this, you will need to boot back into
the previous kernel. I am investigating now if there is any quick
fix or workaround. In the mean time those affected should follow
that bug to know when it is resolved.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
