(Virtualbox) Installing with no swap partition results in corrupted system, despite having high RAM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virtualbox (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Image: ubuntu-
DISCLAIMER: I did this in a Virtualbox VM (5.1.2, and then tried 5.1.4) with 2GB of RAM running on a Windows 8.1 64-bit host. I am not able to test this natively, due to lack of appropriate hardware, but I don't think it matters that it's in a VM.
Reproduction steps:
1) Create a VirtualBox VM with standard options. Change RAM to 2GB. Set network cable to unplugged (doesn't affect reproduction, but will make the process faster)
2) Start the installer, and select "Install Ubuntu MATE". Go through default options, except when specified.
3) At the Installation Type step (partition dialog), select Something Else
4) Configure a single partition table with a single primary/logical partition mounted on root (ie the default settings), then select Install Now. Accept the warning saying you have not selected any swap space. Write the changes to disk, and proceed.
5) When installation has completed, reboot the system as instructed
6) When the system boots, you will get completely corrupted (see attachment mate-corrupted-
Observations:
-If I install and use the default partitioning scheme ("Erase disk and install Ubuntu MATE"), which does contain a swap partition, then the OS boots just fine
-If I select "Try Ubuntu MATE" during install, I get a working, high-res desktop
description: | updated |
description: | updated |
no longer affects: | ubuntu-mate |
Changed in virtualbox (Ubuntu): | |
importance: | Undecided → High |
Changed in virtualbox (Ubuntu): | |
status: | Confirmed → Fix Released |
I reproduced this in Virtualbox using a Ubuntu MATE 16.04 LTS host:
Same iso: ubuntu- mate-16. 04.1-desktop- amd64.iso
Same VM settings: 2GB RAM, No network connector.
Same partition layout: no swap, only "/" partition using entire 16GB dynamic size disk
ouroumov@ Box:~/Desktop$ apt-cache policy virtualbox dfsg-0ubuntu1. 16.04.1 0.24-dfsg- 0ubuntu1. 16.04.1 500 fr.archive. ubuntu. com/ubuntu xenial- updates/ multiverse amd64 Packages fr.archive. ubuntu. com/ubuntu xenial/multiverse amd64 Packages dpkg/status
virtualbox:
Installed: 5.0.18-dfsg-2build1
Candidate: 5.0.24-
Version table:
5.
500 http://
*** 5.0.18-dfsg-2build1 500
500 http://
100 /var/lib/
See attachment for graphics bug screenshot.
Note: Switching to tty1 using (left control key + F1) then using "sudo systemctl restart lightdm.service" allows me to work around this issue and lands me on the correct login screen.