Once you install a GUI or any reasonable size projects/tools to the delivered Virtual Machine, the PeopleSoft VM becomes slow (for lack of space to write the logs and cache etc.) and eventually and very quickly becomes unusable. You'll start seeing the servers not booting up or taking forever to boot.
As long as there is no space issue on the host disks, it's always better to extend the size of the delivered disk size. After all we all install the VMs to try out few projects, so it's in fact a necessary step following the initial VM deployment.
Config: Windows 10 Host - PS Campus Solutions 9.2/PUM6 - VirtualBox:Version 5.1.30 r118389 (Qt5.6.2)
Step1: Extend the size of the VMDK
Command line as admin
As long as there is no space issue on the host disks, it's always better to extend the size of the delivered disk size. After all we all install the VMs to try out few projects, so it's in fact a necessary step following the initial VM deployment.
Config: Windows 10 Host - PS Campus Solutions 9.2/PUM6 - VirtualBox:Version 5.1.30 r118389 (Qt5.6.2)
Step1: Extend the size of the VMDK
Command line as admin
- Go to virtualbox installation (C:\program files\oracle\VirtualBox\)
Code Editor
Step2: Once the virtual Disk size has been increased, it's time to allocate that extra space to our OS partition.
- Download Gparted Live and insert into the optical drive of the VM.
- Boot into the Linux guest BIOS(F12) via CD-rom (into Gparted Live)
- In the Gparted GUI and extend /dev/sda2 to use the additional space(ensure you check the mount that need to be expanded)
- In my case there was a sda1 and /sda2 and sda3, sda3 was the unix swap file partition, extend the sda3 to use the new space at the end of the disk and free up the space before the sda3. then use that freed up space to extend /sda2.