Bug 1134758

Summary: VirtualBox: YaST2 stops at System Roles and eats all CPU available
Product: [openSUSE] openSUSE Distribution Reporter: Julio González Gil <jgonzalez>
Component: InstallationAssignee: E-mail List <yast2-maintainers>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: lslezak
Version: Leap 15.1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Logs
text mode hangs
top at VM
y2logs

Description Julio González Gil 2019-05-10 16:49:32 UTC
Created attachment 804774 [details]
Logs

I am trying to install Leap 15.0 with https://download.opensuse.org/distribution/leap/15.1/iso/openSUSE-Leap-15.1-NET-x86_64-Current.iso as a VirtuaBox VM.

Using either GUI or Text mode, YaST2 stops after I select the system role and hit "Next", as you can see at the attached screenshot.

At that point I almost unable to move the mouse cursor (GUI) or I can't just do anything else than switching to terminal (text mode).

top at the VM shows that YaST2 is using all available CPU, and htop at the host confirms that the VM is using 100% of the assigned CPU.

I am attaching the whole contents of /var/log (running text mode)

In case it's relevant, this is the info from the host:

OS: Leap 15.0
VirtualBox packages:
> $ rpm -qa|grep virtualbox
> virtualbox-qt-5.2.22-lp150.4.24.1.x86_64
> virtualbox-5.2.22-lp150.4.24.1.x86_64
> virtualbox-host-kmp-default-5.2.22_k4.12.14_lp150.12.48-lp150.4.24.1.x86_64
Comment 1 Julio González Gil 2019-05-10 16:50:09 UTC
Created attachment 804775 [details]
text mode hangs
Comment 2 Julio González Gil 2019-05-10 16:50:47 UTC
Created attachment 804776 [details]
top at VM
Comment 3 Julio González Gil 2019-05-10 17:06:31 UTC
Created attachment 804780 [details]
y2logs
Comment 4 Lukas Ocilka 2019-05-13 08:00:14 UTC
https://github.com/yast/yast-packager/blob/SLE-15-SP1/src/modules/Packages.rb#L827

resolvables = Pkg.ResolvableProperties("", type, "")

Ladislav, I guess this is a known bug. Do we have a solution?
Comment 5 Ladislav Slezák 2019-05-13 08:13:49 UTC
Already reported in bug#1132650.

I have reimplemented that code (https://github.com/yast/yast-packager/pull/434) but the release managers found it too intrusive and too risky to accept it just before the final release.

Therefore we just increased the limit for using the online repositories to 1.5GB RAM. (https://github.com/yast/yast-packager/pull/435)


So the workaround in 15.1 is either to 

1) install with at least 1.5 GB RAM (you can decrease it to 1 GB after the system is installed)
2) or use 1GB RAM + swap (but it needs to be created and activated manually, see https://en.opensuse.org/SDB:Linuxrc#p_addswap).

The full fix will be later merged to Tumbleweed and 15.2.

*** This bug has been marked as a duplicate of bug 1132650 ***
Comment 6 Ladislav Slezák 2019-05-13 08:20:50 UTC
or 

3) install using the text mode (use the "textmode=1" boot parameter), the text mode installation requires less RAM and 1GB should be enough (though I have not tested that). In the installed system you can normally use the graphical system.
Comment 7 Julio González Gil 2019-05-13 09:34:06 UTC
Increasing RAM fixed the issue, thanks for the workaround!

However I think booting with "textmode=1" is the same starting the text mode from the menu, right?

If so, text mode has exactly the same problem (as shown at the screenshots).
Comment 8 Ladislav Slezák 2019-05-13 10:28:09 UTC
Yes, it's the same, so it does not help :-(