Hi,
As previously discussed on the users list:
https://is.gd/wvBvEn
…everyone's booting method has now been changed to pvgrub2.
The short summary is that it will look and behave more like GRUB now
(because it *is* GRUB), and you can expect a typical GRUB2
configuration in /boot/grub/grub.cfg (/boot/grub2/grub.cfg on CentOS
7.x) to work now.
More details at:
https://tools.bitfolk.com/wiki/Booting
If you think you may have reinstalled your VPS using the rescue VM
and changed its architecture in the process, it is important that
you check that we know the correct architecture. You can see what we
think your architecture is by:
- Typing "arch" in the Xen Shell.
- Looking at
https://panel.bitfolk.com/account/ where it is listed
next to what we think your operating system is.
If your architecture is set incorrectly then your VPS will not boot.
If the bootloader appears to detect the correct configuration file
and kernel file but still says it can't load it, then check the
architecture first.
As far as I am aware the only way you could have got a VPS with a
different architecture to what we think you have is if you installed
it manually through the rescue VM. The supported installers only
install the matching architecture.
If you checked that and it's correct but your VPS still does not
boot, do not panic. Contact support and we can revert you to pygrub
until we figure out what is wrong. But having tested many
configurations of VPS now, the only failures encountered so far have
been trying to boot a 64-bit kernel with an i686 bootloader or vice
versa.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce