|
Bugzilla – Full Text Bug Listing |
| Summary: | VirtualBox: YaST2 stops at System Roles and eats all CPU available | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Julio González Gil <jgonzalez> |
| Component: | Installation | Assignee: | 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 804775 [details]
text mode hangs
Created attachment 804776 [details]
top at VM
Created attachment 804780 [details]
y2logs
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? 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 *** 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. 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). Yes, it's the same, so it does not help :-( |