[Bug 632730] New: XEN hypervisor parameter vgamode=0x314: bad syntax
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c0 Summary: XEN hypervisor parameter vgamode=0x314: bad syntax Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: martin.wilck@ts.fujitsu.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.4) Gecko/20100622 Fedora/3.6.4-1.fc13 Firefox/3.6.4 With Xen, YaST (?) adds the hypervisor parameter "vgamode=0x314". This parameter syntax is wrong. It must be "vga=mode-0x314". Reproducible: Always This is a spinoff of bug #623680. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |jbeulich@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c2 Thomas Göttlicher <tgoettlicher@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |juhliarik@novell.com --- Comment #2 from Thomas Göttlicher <tgoettlicher@novell.com> 2010-10-19 08:43:36 UTC --- Jozef, has this to be fixed in yast2-bootloader? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c4 Willy Weisz <Willy.Weisz@univie.ac.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent CC| |Willy.Weisz@univie.ac.at Severity|Normal |Critical --- Comment #4 from Willy Weisz <Willy.Weisz@univie.ac.at> 2010-11-08 13:15:35 UTC --- This hasn't been fixed (at least until last week). The bug is quite critical as any boot of a xen system aborts without leaving any trace as to what happened until the critical moment: the screen is blank and no log file content can be found when the system is rebooted with a non-xen kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c6 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |martin.wilck@ts.fujitsu.com --- Comment #6 from Josef Reidinger <jreidinger@novell.com> 2010-11-15 08:18:26 UTC --- (In reply to comment #4)
This hasn't been fixed (at least until last week).
The bug is quite critical as any boot of a xen system aborts without leaving any trace as to what happened until the critical moment: the screen is blank and no log file content can be found when the system is rebooted with a non-xen kernel.
Hi, please attach all yast logs - http://en.opensuse.org/openSUSE:Report_a_YaST_bug It should be done properly in 11.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c7 Martin Wilck <martin.wilck@ts.fujitsu.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|martin.wilck@ts.fujitsu.com | --- Comment #7 from Martin Wilck <martin.wilck@ts.fujitsu.com> 2010-11-15 09:03:52 UTC --- Josef, Please - I reported this bug 3 months ago. I have clearly stated what needs to be changed. You need no logs to fix it, you know that as well as I do. Please talk to Jan Beulich or some other Xen guy at SUSE to find out what the correct syntax of this boot parameter is, and implement it accordingly. Martin -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c8 --- Comment #8 from Willy Weisz <Willy.Weisz@univie.ac.at> 2010-11-15 09:04:20 UTC --- Created an attachment (id=400157) --> (http://bugzilla.novell.com/attachment.cgi?id=400157) YaSt2 files (In reply to comment #6)
(In reply to comment #4)
This hasn't been fixed (at least until last week).
The bug is quite critical as any boot of a xen system aborts without leaving any trace as to what happened until the critical moment: the screen is blank and no log file content can be found when the system is rebooted with a non-xen kernel.
Hi, please attach all yast logs - http://en.opensuse.org/openSUSE:Report_a_YaST_bug
It should be done properly in 11.3.
Here are the logs. y2log-1 contains the latest kernel update and related installation actions which lead to the faulty boot parameter. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c9 --- Comment #9 from Josef Reidinger <jreidinger@novell.com> 2010-11-15 09:14:52 UTC --- (In reply to comment #7)
Josef,
Please - I reported this bug 3 months ago. I have clearly stated what needs to be changed. You need no logs to fix it, you know that as well as I do.
Please talk to Jan Beulich or some other Xen guy at SUSE to find out what the correct syntax of this boot parameter is, and implement it accordingly.
Martin
Hi, I know correct syntax and there is code which translate parameters for xen entries to format mode-<vga> in 11.3. So problem is not that I don't know how to do it, but to find why it doesn't apply. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c10 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |Willy.Weisz@univie.ac.at --- Comment #10 from Josef Reidinger <jreidinger@novell.com> 2010-11-15 09:38:28 UTC --- (In reply to comment #8)
Created an attachment (id=400157) --> (http://bugzilla.novell.com/attachment.cgi?id=400157) [details] YaSt2 files
(In reply to comment #6)
(In reply to comment #4)
This hasn't been fixed (at least until last week).
The bug is quite critical as any boot of a xen system aborts without leaving any trace as to what happened until the critical moment: the screen is blank and no log file content can be found when the system is rebooted with a non-xen kernel.
Hi, please attach all yast logs - http://en.opensuse.org/openSUSE:Report_a_YaST_bug
It should be done properly in 11.3.
Here are the logs. y2log-1 contains the latest kernel update and related installation actions which lead to the faulty boot parameter.
Thanks for logs. I see from logs that you don't add xen kernel during installation but after. Maybe it is reason. Could you please attach your /etc/sysconfig/bootloader file and tell me how you add xen kernel? Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c11 Willy Weisz <Willy.Weisz@univie.ac.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Willy.Weisz@univie.ac.at | --- Comment #11 from Willy Weisz <Willy.Weisz@univie.ac.at> 2010-11-15 10:05:25 UTC --- (In reply to comment #10)
(In reply to comment #8)
Created an attachment (id=400157) --> (http://bugzilla.novell.com/attachment.cgi?id=400157) [details] [details] YaSt2 files
(In reply to comment #6)
(In reply to comment #4)
This hasn't been fixed (at least until last week).
The bug is quite critical as any boot of a xen system aborts without leaving any trace as to what happened until the critical moment: the screen is blank and no log file content can be found when the system is rebooted with a non-xen kernel.
Hi, please attach all yast logs - http://en.opensuse.org/openSUSE:Report_a_YaST_bug
It should be done properly in 11.3.
Here are the logs. y2log-1 contains the latest kernel update and related installation actions which lead to the faulty boot parameter.
Thanks for logs. I see from logs that you don't add xen kernel during installation but after. Maybe it is reason. Could you please attach your /etc/sysconfig/bootloader file and tell me how you add xen kernel? Thanks
That's it: The line XEN_APPEND="vgamode=0x31a " is in /etc/sysconfig/bootloader! After having installed and updated the 11.3 installation, I added the xen kernel and xen-related stuff via YaST2 software install. That's where probably the error crept in. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c12 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #12 from Josef Reidinger <jreidinger@novell.com> 2010-11-15 10:34:15 UTC --- (In reply to comment #11)
(In reply to comment #10)
(In reply to comment #8)
Created an attachment (id=400157) --> (http://bugzilla.novell.com/attachment.cgi?id=400157) [details] [details] [details] YaSt2 files
(In reply to comment #6)
(In reply to comment #4)
This hasn't been fixed (at least until last week).
The bug is quite critical as any boot of a xen system aborts without leaving any trace as to what happened until the critical moment: the screen is blank and no log file content can be found when the system is rebooted with a non-xen kernel.
Hi, please attach all yast logs - http://en.opensuse.org/openSUSE:Report_a_YaST_bug
It should be done properly in 11.3.
Here are the logs. y2log-1 contains the latest kernel update and related installation actions which lead to the faulty boot parameter.
Thanks for logs. I see from logs that you don't add xen kernel during installation but after. Maybe it is reason. Could you please attach your /etc/sysconfig/bootloader file and tell me how you add xen kernel? Thanks
That's it: The line XEN_APPEND="vgamode=0x31a " is in /etc/sysconfig/bootloader!
After having installed and updated the 11.3 installation, I added the xen kernel and xen-related stuff via YaST2 software install. That's where probably the error crept in.
Yeah, that is the reason, as correctly there should be XEN_VGA=0x31a I check logs again to find who create this line, as it is wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c13 --- Comment #13 from Josef Reidinger <jreidinger@novell.com> 2010-12-03 14:15:46 UTC --- OK, investigating show, that problem is in perl-Bootloader, which gets correct info and write it badly. I continue with investigating what happen in perl-Bootloader -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c14 --- Comment #14 from Josef Reidinger <jreidinger@novell.com> 2010-12-03 14:27:56 UTC --- Hi, mistake found. Creating new section ( so if you not edit it) contain bug, which cause bad parameter. I fixed in trunk and will be in factory in perl-Bootloader 0.5.14 Thanks for report. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=632730 https://bugzilla.novell.com/show_bug.cgi?id=632730#c15 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #15 from Josef Reidinger <jreidinger@novell.com> 2010-12-06 18:04:18 UTC --- sent to factory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com