Install a Linux server on a virtual machine on your host computer.
To fix this limitation, we will show you how to build a Linux router image for EVE-NG that boots from a virtual hard disk, can be accessed via Telnet to simplify configuration and management, and that has a persistent file system onto which we can install software and modify configuration files.Īdd a custom Linux server image to UNetLab or EVE-NG by following the procedure below: This is not suitable for emulating Linux routers or servers. In their default configuration, UNetLab and EVE-NG support Linux nodes running boot-able live CD disk images that offer a graphical user interface accessible via VNC. Fortunately, it is easy to extend UNetLab and EVE-NG to support powerful, general-purpose Linux router and server images. However, When first installed, they support Linux images only in a limited way. I'm a CLI junkie so no plans of me finding out how a GUI works anytime soon.The UNetLab and EVE-NG network emulators can become powerful tools for emulating open-source networks. If you use the Ubuntu GUI some tools contain the entire process in a single tool. We must follow this flow or the resize will either fail or encounter problems. Important to remember is the path of the resize Physical Volume -> Volume Group -> Logical Volume -> Filesystem. Hopefully this tutorial will save you time and give you a little more background on the flow of a resize. The filesystem on /dev/mapper/ubuvg-ubulv is now 4871168 blocks df -k Step 8 Extend the Filesystem to fill the logical resize2fs /dev/mapper/ubuvg-ubulvįilesystem at /dev/mapper/ubuvg-ubulv is mounted on / on-line resizing required.Logical volume ubulv successfully resized dev/mapper/ubuvg-ubulv 8726456 7739868 520260 94% lvextend -L +10G /dev/mapper/ubuvg-ubulvĮxtending logical volume ubulv to 18.58 GiB Ubuvg 2 5 0 wz-n- 24.99g Step 7 Next we need to extend the Logical Volume with df -kįilesystem 1K-blocks Used Available Use% Mounted on
Run the command vgs in order to get the name of your volume group vgsĮxpand the volume group with vgextend then verify your volume group again once complete with vgs vgextend ubuvg /dev/sda3 PV UUID OEADew-tamR-EHil-FU4p-kIuW-F5rT-V0CTcY "/dev/sda3" is a new physical volume of "9.00 GiB" First rerun pvdisplay to show the new physical volume details.
Step 4 Update the partition table tool using cfdisk Step 3 Reboot your Ubuntu machine in order for Ubuntu to recognize the reboot Last sector, +sectors or +size (33552384-33554431, default 33554431):Īccept the default values that are provide that the "n" option returns.
N (create new partition, select start and end cylinders, all free space is selected by default) Step 2 Manipulate the disk partition table with fdisk /dev/sdb.PV UUID HiNAY2-sfqz-7fwT-tLvy-XKfT-3QR6-BXash5 Step 1 Before we get started run pvdisplay in order to see the current state of the physical pvdisplay.In my scenario I increased the size of my Virtual Machine disk in VMware from 18GB to 28 GB.
Physical Volume -> Volume Group -> Logical Volume -> Filesystem We have to expand components of the filesystem in the following order. So a quick recap for those that don't remember. So instead of racking my brain in the future I will jot down the process here for anyone else stuck in the same situation. Today my brain blue screened on me while trying to expand my Ubuntu machine's root volume group, logical volume, and filesystem. I used to be able to do these tasks with my eyes closed with AIX and other version of Linux and Unix.