https://bugzilla.novell.com/show_bug.cgi?id=801883 https://bugzilla.novell.com/show_bug.cgi?id=801883#c2 Bob Vickers changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |R.Vickers@cs.rhul.ac.uk --- Comment #2 from Bob Vickers 2013-04-05 11:46:13 UTC --- In a Xen environment this bug is very serious (unless I am missing something). I have just upgraded a domU machine from 12.2 to 12.3 and now it will not boot. The dom0 host is running SLES11SP2 and gives: [2013-04-04 16:28:11 11938] DEBUG (XendBootloader:130) Launching bootloader as ['/usr/lib/xen/boot/domUloader.py', '--args=xencons=tty ', '--output=/var/run/xend/boot/xenbl.31011', '-- entry=xvda1:/boot/vmlinuz-xen,/boot/initrd-xen', '/dev/mapper/CS0-puppet--system']. [2013-04-04 16:28:11 6181] ERROR (XendBootloader:231) Boot loader didn't return any data! [2013-04-04 16:28:11 6181] ERROR (XendDomainInfo:489) VM start failed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 475, in start XendTask.log_progress(31, 60, self._initDomain) File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2905, in _initDomain self._configureBootloader() File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 3379, in _configureBootloader bootloader_args, kernel, ramdisk, args) File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py", line 232, in bootloader raise VmError, msg VmError: Boot loader didn't return any data! If you run domUloader.py by hand you get: # /usr/lib/xen/boot/domUloader.py '--args=xencons=tty ' --entry=xvda1:/boot/vmlinuz-xen,/boot/initrd-xen /dev/mapper/CS0-puppet--system Copy kernel /boot/vmlinuz-xen from xvda1 to /var/lib/xen/tmp/kernel.EkWEU3 for booting domUloader error: Too large file /var/lib/xen/tmp/xvda1.hrqij8/boot/initrd-xen (30339848 larger than 16MB) Bob -- 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=801883 https://bugzilla.novell.com/show_bug.cgi?id=801883#c4 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta@cboltz.de --- Comment #4 from Christian Boltz 2013-04-10 19:21:14 CEST --- (In reply to comment #3)

Can the importance of this bug be raised? (it isn't my bug so I don't know if I am allowed to do it myself)

Feel free to update the severity ("Normal", "Major" etc.) of any bug if you think it is wrong, but please don't modify the priority ("P5 - None" etc.) because this is usually set by the developers. For more details about what the different severity values mean, have a look at https://bugzilla.novell.com/page.cgi?id=fields.html#importance -- 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=801883 https://bugzilla.novell.com/show_bug.cgi?id=801883#c6 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmarek@suse.com AssignedTo|mmarek@suse.com |tittiatcoke@gmail.com --- Comment #6 from Michal Marek 2013-09-26 07:38:10 UTC --- IMO we should not include plymouth in the initrd by default, or at least not when a separate /boot partition is used. It's not just the PNG files, but also over 20MB worth of libraries it requires. -- 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=801883 https://bugzilla.novell.com/show_bug.cgi?id=801883#c8 --- Comment #8 from Raymond Wooninck 2013-09-26 07:59:28 UTC --- Michel, Plymouth itself doesn't require that much space and the increase would actually just be the bootsplash png's (in about 5 sizes). The additional libraries are required so that plymouth is able to ask for passwords, etc in order to unlock encrypted bootdisks, home partitions, etc. So we could proceed in three ways: 1) Drop plymouth completely. This would resolve a couple of issues when it comes down to unlocking encrypted disks, etc. 2) Drop the ask-for-password stuff from Plymouth, which would allow us to drop the additional library requirements. 3) Drop plymouth from initrd and start plymouth from disk after password, etc have been required. Currently systemd already has that support. Options 1 and 3 of course would have quite an impact on how the user would see the boot process. Due to plymouth we have now a seamless transition from Grub2 to the Login Manager (KDM, GDM, LightDM, etc). Even with Option 3 there would be quite some text scrolling on the display before plymouth will actually kick in. Raymond -- 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=801883 https://bugzilla.novell.com/show_bug.cgi?id=801883#c10 Raymond Wooninck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #10 from Raymond Wooninck 2014-02-07 09:12:39 UTC --- Closing this bug, as that there is another bug open for the artwork used within plymouth. Also the openSUSE Artwork team has promised to redo the artwork for 13.2 and use different methods. *** This bug has been marked as a duplicate of bug 805767 *** http://bugzilla.novell.com/show_bug.cgi?id=805767 -- 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.