Bug 962231
Summary: | anaconda issues a spurious 'not asking for VNC' due to ram size message when 'text' or 'vnc' boot parameters are used | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Reartes Guillermo <rtguille> | ||||||||||||||||||||||||||||||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||||||||||||||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||||||||||
Severity: | low | Docs Contact: | |||||||||||||||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||||||||||||||
Version: | 19 | CC: | anaconda-maint-list, awilliam, dshea, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora | ||||||||||||||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||||||||||||||
OS: | Linux | ||||||||||||||||||||||||||||||||||||
Whiteboard: | |||||||||||||||||||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||||||||||||||
Last Closed: | 2013-08-08 14:41:59 UTC | Type: | Bug | ||||||||||||||||||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||||||||||||
Embargoed: | |||||||||||||||||||||||||||||||||||||
Attachments: |
|
Created attachment 746990 [details]
screenshot F19b TC4 showing vnc / text mode dialog (this does not work with 512mb)
Additional Info:
* KVM [X86_64] Guest (535mb RAM) boot-parameter: text
--> GRAPHICAL MODE --> Anaconda starts up in this mode.
--> VNC Server ------> No error message, dialog offers either VNC or Text Mode
--> TEXT MODE -------> No error message, dialog offers either VNC or Text Mode
I wonder if this really does not fit in 512mb.
for this to work:
* 535mb ram for. X86_64 F19b TC4
* 528mb ram for i386 F19b TC4
Comment #1 is incorrect: screenshot F19b TC4 showing vnc / text mode dialog (this does not work with 512mb) Additional Info: * KVM [X86_64] Guest (535mb RAM) boot-parameter: text > --> GRAPHICAL MODE --> N/A --> VNC Server ------> No error message, dialog offers either VNC or Text Mode --> TEXT MODE -------> No error message, dialog offers either VNC or Text Mode I wonder if this really does not fit in 512mb. for this to work: * 535mb ram for. X86_64 F19b TC4 * 528mb ram for i386 F19b TC4 Please switch to tty1 and attach the logs from /tmp/*log to this bug as individual text/plain files. In general the logs are much more useful than screenshots. Created attachment 747979 [details]
anaconda.log
KVM Guest (512mb RAM) boot-parameter: text
Created attachment 747980 [details]
program.log
KVM Guest (512mb RAM) boot-parameter: text
Created attachment 747981 [details]
storage.log
KVM Guest (512mb RAM) boot-parameter: text
Created attachment 747982 [details]
syslog
Created attachment 747983 [details]
anaconda.log
KVM Guest (512mb RAM) boot-parameter: vnc
Created attachment 747984 [details]
program.log
Created attachment 747985 [details]
storage.log
KVM Guest (512mb RAM) boot-parameter: vnc
Created attachment 747986 [details]
syslog
Created attachment 747987 [details]
vncserver.log
Created attachment 747988 [details]
anaconda.log
KVM [X86_64] Guest (535mb RAM) boot-parameter: text
Created attachment 747989 [details]
program.log
KVM [X86_64] Guest (535mb RAM) boot-parameter: text
Created attachment 747990 [details]
storage.log
KVM [X86_64] Guest (535mb RAM) boot-parameter: text
Created attachment 747991 [details]
syslog
KVM [X86_64] Guest (535mb RAM) boot-parameter: text
Created attachment 747992 [details]
vncserver.log
KVM [X86_64] Guest (535mb RAM) boot-parameter: text
Ends up the blivet total_memory wasn't rounding up like Anaconda's total_memory. This was ACK'ed: https://lists.fedorahosted.org/pipermail/anaconda-patches/2013-May/004186.html but doesn't yet appear to have been pushed, did you forget about it bcl? Doesn't look too critical for F19 so I won't bother marking as FE, but OTOH it seems pretty safe so if you want to sneak it in there, no objections. I tried this with 'text' and 'vnc' with a 512mb guest (only x86_64) and there was no more spurious messages about memory. It just works. (F19b RC4). Looks like this change was pushed with python-blivet-0.14-1 |
Created attachment 746975 [details] screenshot F19b TC4 showing vnc working and the fake error message Description of problem: A spurious message about not enough ram for vnc is shown. If 'vnc' boot parameter is specified, vnc starts ok, after the message. Version-Release number of selected component (if applicable): F19b TC4 How reproducible: always Steps to Reproduce: See below. Actual results: an error message, harmless when 'vnc' boot parameter is specified. confusing, when no boot parameter is used, it might lead to think that there is not enough ram to use vnc and do not try further. Expected results: no error or warning should be issued if not really necessary. Additional info: F18 Release: * KVM Guest (512mb RAM) boot-parameter: NONE --> GRAPHICAL MODE --> Anaconda starts up in this mode. --> VNC Server ------> N/A --> TEXT MODE -------> N/A * KVM Guest (512mb RAM) boot-parameter: text --> GRAPHICAL MODE --> N/A --> VNC Server ------> Not Offered / Skipped --> TEXT MODE -------> Anaconda stars up in this mode. * KVM Guest (512mb RAM) boot-parameter: vnc --> GRAPHICAL MODE --> N/A --> VNC Server ------> Anaconda shows an ip to connect to. (no password). * KVM Guest (512mb RAM) boot-parameter: vnc vncpassword=password --> GRAPHICAL MODE --> N/A --> VNC Server ------> Anaconda shows an ip to connect to. (with specified password). F19b TC4: * KVM Guest (512mb RAM) boot-parameter: NONE --> GRAPHICAL MODE --> Anaconda starts up in this mode. --> VNC Server ------> N/A --> TEXT MODE -------> N/A * KVM Guest (512mb RAM) boot-parameter: text --> GRAPHICAL MODE --> N/A --> VNC Server ------> VNC is tried first, but fails with not enough RAM. --> TEXT MODE -------> After failed VNC, Anaconda stars up in this mode. * KVM Guest (512mb RAM) boot-parameter: vnc --> GRAPHICAL MODE --> N/A --> VNC Server ------> Anaconda reports not enough ram for VNC, but anaconda starts it anyway. Shows ip to connect to. (no password). * KVM Guest (512mb RAM) boot-parameter: vnc vncpassword=password --> GRAPHICAL MODE --> N/A --> VNC Server ------> Anaconda reports not enough ram for VNC, but anaconda starts it anyway. Shows ip to connect to. (with specified password).