This work alone does not solve the virtual hard disk space problem.Ĭomments: Consider the Windows Host box and physical drives where you have a physical drive of a certain size or capacity and partitions within that drive, like Primary Partitions, or creating an Extended Partition to a particular Primary Partition containing possible Logical Partitions within it the collective/aggregate size of all the Partitions cannot exceed the maximum size or capacity of the drive, in our case the capacity of a Virtual Drive. So, you should consider that when increasing the "Virtual Size" of the virtual hard disk. So, you can go up but you cannot go down. You will receive an error if you accidently try to shrink the size of the virtual drive. Shrinking the size of a drive is not currently permitting or supported. Important Notes: Setting the Virtual Size to 100 GB in the GUI will be equivalent to setting the 102400 MB in the Terminal mode. Optionally, there is a command line option to increase the "Virtual Size" of the drive. I found information about the "Virtual Size" limit and the "Actual Size" consumed by my VM.Ĥ.) I found that VirtualBox 6.1 | Virtual Media Manager allows the user to graphically increase the "Virtual Size" limit of the virtual drive, like buying a new higher capacity hard drive which I modified when the Ubuntu VM was off, not running. Note: This would be a good point to make a snapshot of your VM, like a restore point in Windows.ģ.) I reviewed the information about my dynamic virtual hard disk (*.vdi) by going to Oracle VirtualBox 6.1 | Settings | Storage | Controller: SATA. This allowed me to get to the VHD and delete the Gradle directories I had just installed to gain and recover disk space.Ģ.) I rebooted my computer and the black screen with the hanging cursor was eliminated. I originally thought this problem issue might have been tied to my black screen problem by possibly having the wrong binaries loaded.*ġ.) I discovered that Ubuntu 20.04 had a boot-up recovery mode. As I understand it, it turns out that the same files can be installed on either platform. Gradle was new to me, so I was very concerned about installation issues. I copied one of the Gradle zip files from the Host to the VM to save downloading data. I downloaded these also to my Windows Host which I believe can also be used on the Ubuntu 20.04 VM. It was not clear to me whether the Gradle distributions, zip file containers, were platform specific or not. My Comments / Side Notes: I had earlier downloaded and installed the same Gradle versions on the Windows Host OS. My focus remained on disk space limitations as the real problem which turned out to be correct path to solve the problem. I focused on my immediate last actions which had to do with installing software and having low disk space available. I learned a good lesson here in that setting up snaphots or VM directory backup periodically is very important. My initial impression was that my VM was ready for the recycle bin. I used a terminal screen to unzip and install these two distributions. I had last downloaded two container files, 'gradle-7.0.2-all.zip' and '' from the Gradle distribution website. I experienced booting to a black screen with a blinking or frozen cursor just after downloading and then attempting to install software, in my case two versions of Gradle (7.0.2 and 7.2) for Android Studio (Artic Fox | 2020.3.1) running Ubuntu Linux (20.04) in VirtualBox (6.1) as a Virtual Machine within Microsoft Windows 10 Professional (2). VDI Dynamic Hard Disk with 20 GB upgraded to 100 GB as the solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |