![]() It’s for the same Fedora system after all. You can use the key pair that you used for the server you’re replacing. ![]() General virtual server instance configuration notes for the new HVM server: Below is what I did and it all worked perfectly.įor more information on AWS Linux AMI virtualization types check out. It all sounded like lots of unnecessary work, so as an experiment I decided to try a much more straightforward process. The /dev directory is a devtmpfs file system and the device nodes there are added by the kernel. My virtual server already has grub and the usual /boot separate partition already set up just like a physical server system. Digging around for that turned up all kinds of how-to posts but they started off with steps such as setting up grub, populating the device (/dev) directory, etc. OK, time to try converting a PV server to HVM. As a test I launched a new F27 hardware virtual machine (HVM) system and updated it with the latest packages and kernel. After some digging around the root issue looked like an issue at the PV-GRUB level and not something with Fedora. I had everything up to date, including the version of PV-GRUB used to start the server. The problem I ran into is that Fedora 27 64-bit 4.15 kernels would not start. Back when I first created the servers we set up paravirtual (PV) servers which use PV-GRUB (a special boot loader) to start them. I keep the servers updated with the latest releases of packages and Fedora versions, run with SELinux enforcing, etc. I’ve had several Fedora servers at AWS for years. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |