{"id":2778,"date":"2014-11-05T07:25:52","date_gmt":"2014-11-05T07:25:52","guid":{"rendered":"http:\/\/blog.cloudthat.com\/?p=2778"},"modified":"2024-06-25T11:14:09","modified_gmt":"2024-06-25T11:14:09","slug":"steps-to-convert-rhel-based-pv-instances-to-hvm","status":"publish","type":"blog","link":"https:\/\/www.cloudthat.com\/resources\/blog\/steps-to-convert-rhel-based-pv-instances-to-hvm","title":{"rendered":"Steps to convert RHEL-BASED PV instances to HVM"},"content":{"rendered":"

My previous blog will give you an idea as to why HVM instances in AWS are better than PV instances and why people prefer using HVM instances over PV instances. Moreover, the HVM instances offered by Amazon are cheaper than the PV ones. For example, PV m1.medium costs $0.087 per Hour whereas, HVM m3.medium costs $0.070 per Hour. Inspite of the reduced price, we get same memory plus one more extra core with HVM. If you have a PV machine, you should definitely convert it to HVM because of the lower cost and also, PV instances might retire eventually.<\/p>\n

Here are the detailed steps for doing so:<\/h2>\n

These steps are strictly for RHEL based <\/b>PV instances like Amazon Linux, CentOS, RedHat etc.<\/p>\n

1. Login to your instance (SSH) .<\/p>\n

2. Install grub on it.<\/p>\n

*<\/i>Grub<\/i><\/b> selects a specific kernel configuration available on a particular operating system’s partitions.<\/i><\/p>\n

sudo yum install grub \u2013y<\/pre>\n
3. Stop the instance and create snapshot of the root volume.<\/p>\n
*To overcome the<\/i> downtime<\/i><\/b> here, you can alternatively create an image of your instance and launch another machine.<\/i><\/p>\n
4. \u00a0Launch an Amazon Linux ‘working<\/i>‘ instance (PV) and login to that instance.<\/p>\n
ssh -i path-to-your-pem-file.pem ec2-user@<machine-public-dns-name><\/pre>\n
5. Create a new ‘source’ volume (in the same AZ) from the snapshot created in step 3 and attach it to the ‘working<\/i>‘ instance as \/dev\/xvdf. The ideal size of this volume could be kept same as your source instance (Step 1) or it can even be increased.<\/p>\n
6. Create a new ‘destination’ volume (in the same AZ) from the snapshot created in step 3 and attach it to the ‘working<\/i>‘ instance as \/dev\/xvdo.<\/p>\n
7. Next, we partition the destination volume.<\/p>\n
a. We use parted<\/strong><\/em> for partitioning the destination volume.<\/p>\n
*<\/i>Parted <\/i><\/b>is a program for creating and manipulating partition tables.<\/i><\/p>\n
sudo parted \/dev\/xvdo --script 'mklabel msdos mkpart primary 1M -1s print quit'<\/pre>\n
Output:<\/p>\n
Model: Xen Virtual Block Device (xvd)\r\n\r\nDisk \/dev\/xvdo: 8590MB\r\n\r\nSector size (logical\/physical): 512B\/512B\r\n\r\nPartition Table: msdos\r\n\r\nNumber \u00a0Start \u00a0\u00a0End \u00a0\u00a0\u00a0Size \u00a0Type \u00a0\u00a0\u00a0\u00a0File system \u00a0Flags\r\n\r\n1 \u00a0\u00a0\u00a0\u00a0\u00a01049kB \u00a08590MB \u00a08589MB \u00a0primary\r\n\r\n<\/pre>\n
b. The OS \u00a0kernel checks the partition table of destination volume which was modified and updates the table.<\/p>\n
*<\/i>partprobe<\/i><\/b> to informs the operating system kernel of partition table changes, by requesting that the operating system re-read the partition table.<\/i><\/p>\n
\u00a0sudo partprobe \/dev\/xvdo<\/pre>\n
c. Update the destination information.<\/p>\n
*udevadm settle\u00a0<\/i><\/b>waits for <\/i>udevd<\/i> to process the device creation events for all hardware devices, thus ensuring that any device nodes have been created successfully before proceeding.<\/i><\/p>\n
\u00a0 udevadm settle<\/pre>\n
8. \u00a0Check the ‘source’ volume.\u00a0\u00a0<\/b><\/p>\n
a. <\/i>e2fsck<\/i><\/b> is used to check a Linux second extended file system.<\/i><\/p>\n
\u00a0sudo e2fsck -f \/dev\/xvdf<\/pre>\n
Output:<\/p>\n
e2fsck 1.42.8 (4-Nov-2014)\r\n\r\nPass 1: Checking inodes, blocks, and sizes\r\n\r\nPass 2: Checking directory structure\r\n\r\nPass 3: Checking directory connectivity\r\n\r\nPass 4: Checking reference counts\r\n\r\nPass 5: Checking group summary information\r\n\r\n\/: 39159\/524288 files (0.3% non-contiguous), 366426\/2097152 blocks<\/pre>\n
b. Minimize the size of original filesystem to speed up the process and also to eliminate a copy free disk space in the next step.<\/p>\n
*resize2fs<\/i><\/b> program will resize ext2, ext3, or ext4 file systems. Run resize2fs to resize the ext2 filesystem to use all of the space in the newly enlarged partition.<\/i><\/p>\n
\u00a0sudo resize2fs -M \/dev\/xvdf<\/pre>\n
Output:<\/p>\n
resize2fs 1.42.8 (4-Nov-2014)\r\nResizing the filesystem on \/dev\/xvdf to 346784 (4k) blocks.\r\n\r\nThe filesystem on \/dev\/xvdf is now 346784 blocks long.<\/pre>\n
Note:<\/i><\/b> Write down the blocks and 4k values.<\/i><\/p>\n
9. Duplicate the source volume to the newly partitioned destination volume.<\/p>\n
*<\/i>dd<\/i><\/b> is a command on Unix systems whose primary purpose is to convert and copy a file.<\/i> Note<\/i>: Make sure you specify the exact number of bs and count values. (returned from the previous command). The execution of this command might take some time.<\/p>\n
sudo dd if=\/dev\/xvdf of=\/dev\/xvdo1 bs=4K count=346784<\/pre>\n
Output:<\/p>\n
346784+0 records in\r\n\r\n346784+0 records out\r\n\r\n1420427264 bytes (1.4 GB) copied, 166.497 s, 8.5 MB\/s<\/pre>\n
10. \u00a0Resize the filesystem on the newly partitioned destination volume.<\/p>\n
sudo resize2fs \/dev\/xvdo1<\/pre>\n
11. \u00a0Next, we have to prepare the newly partitioned destination volume for the chrooted grub installation.<\/p>\n
a. Mount the newly partitioned destination.<\/p>\n
\u00a0sudo mount \/dev\/xvdo1 \/mnt<\/pre>\n
b. Copy all the files archived from old destination to the newly partitioned one.<\/p>\n
\u00a0sudo cp -a \/dev\/xvdo \/dev\/xvdo1 \/mnt\/dev\/\r\n<\/pre>\n
c.<\/p>\n
\u00a0sudo rm -f \/mnt\/boot\/grub\/*stage*<\/pre>\n
d.<\/p>\n
sudo cp \/mnt\/usr\/*\/grub\/*\/*stage* \/mnt\/boot\/grub\/<\/pre>\n
e.<\/p>\n
sudo rm -f \/mnt\/boot\/grub\/device.map<\/pre>\n
12. Next, we do an offline grub installation on the destination device in the chroot environment, which is required for the HVM instance. You need to be a root user to perform this step:<\/p>\n
\u00a0\u00a0sudo su<\/pre>\n
Execute the code below:<\/p>\n
sudo cat <<EOF | chroot \/mnt grub \u2013batch\r\n\r\ndevice (hd0) \/dev\/xvdo\r\n\r\nroot (hd0,0)\r\n\r\nsetup (hd0)\r\n\r\nEOF<\/pre>\n
13. \u00a0\u00a0Remove the old destination volume from the new destination volume.<\/p>\n
sudo rm -f \/mnt\/dev\/xvdo \/mnt\/dev\/xvdo1<\/pre>\n
14. Updating the new grub configuration. \u00a0<\/b><\/p>\n
*tty<\/b> prints the filename of the terminal connected to standard input.<\/p>\n
vi \/mnt\/boot\/grub\/menu.lst<\/pre>\n
Change root (hd0) to root (hd0,0)<\/p>\n
– Add (or replace console=*) console=ttyS0 to kernel line.<\/p>\n
– Replace root=* with root=LABEL=\/ in the kernel line.<\/p>\n
– Go to \/mnt\/boot\/grub\/menu.lst – *ensure the filenames match the files in \/mnt\/boot<\/p>\n
a.<\/p>\n
\u00a0cd \/mnt\/boot<\/pre>\n
b.<\/p>\n
\u00a0 ls<\/pre>\n
Output:<\/p>\n
config-3.4.43-43.43.amzn1.x86_64 \u00a0initramfs-3.4.43-43.43.amzn1.x86_64.img\r\n\r\nefi \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0System.map-3.4.43-43.43.amzn1.x86_64\r\n\r\ngrub \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0vmlinuz-3.4.43-43.43.amzn1.x86_64<\/pre>\n
c. Once you verify that the filenames are same, save and quit the file (:wq).<\/p>\n
vi \/mnt\/boot\/grub\/menu.lst<\/pre>\n
15. Update.<\/p>\n
*fstab<\/i><\/b> gives you the static information about the filesystems.<\/i><\/p>\n
vi \/mnt\/etc\/fstab<\/pre>\n
Update the root (\/) entry in \/mnt\/etc\/fstab, as per the sample fstab below:<\/p>\n
Output:<\/p>\n
LABEL=\/ \/ ext4 defaults,noatime 1 1\r\n\r\nnone \/dev\/pts devpts gid=5,mode=620 0 0\r\n\r\nnone \/dev\/shm tmpfs defaults 0 0\r\n\r\nnone \/proc proc defaults 0 0\r\n\r\nnone \/sys sysfs defaults 0 0\u00a0\r\n<\/pre>\n
16. Change the label on the filesystem.<\/p>\n
a.\u00a0e2label<\/b> command changes the label on an ext2 filesystem i.e; \/dev\/xvdo1<\/p>\n
\u00a0e2label \/dev\/xvdo1 \/<\/pre>\n
b.<\/p>\n
\u00a0 sync<\/pre>\n
c. Come out of mnt directory and unmount the device:<\/p>\n
\u00a0umount \/mnt<\/pre>\n
17. Final Steps<\/b>. Create a snapshot of the ‘destination’ volume. Select your snapshot and under Actions<\/b> click Create Image<\/b> as shown in the below image. \"Screen<\/a><\/p>\n
Select Virtualization type<\/b> as Hardware-assisted virtualization, use the default Kernel ID<\/b> and click Create.<\/p>\n
\"Screen<\/a><\/p>\n
Launch instance from the above AMI. The new HVM instance should now boot successfully and will be an exact copy of the old source PV instance (if you used the correct source volume). Once you have confirmed that everything is working, the source instance can be stopped. Cleanup by removing all temporary volumes (source and destination).<\/p>\n
Stay tuned to my next blog<\/a> where I talk about converting Ubuntu-based PV to HVM along with detailed steps.<\/p>\n
Let me know if you have any questions by commenting below.<\/p>\n","protected":false},"author":219,"featured_media":0,"parent":0,"comment_status":"open","ping_status":"open","template":"","blog_category":[3606,3607,3664,3665],"user_email":"prarthitm@cloudthat.com","published_by":"324","primary-authors":"","secondary-authors":"","acf":[],"_links":{"self":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/2778"}],"collection":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/types\/blog"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/users\/219"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/comments?post=2778"}],"version-history":[{"count":1,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/2778\/revisions"}],"predecessor-version":[{"id":45658,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/2778\/revisions\/45658"}],"wp:attachment":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/media?parent=2778"}],"wp:term":[{"taxonomy":"blog_category","embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog_category?post=2778"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}