No, switching to grub legacy doesnt help. But I found that if I start yast2 bootloader, Click Edit -> fill Additional Xen Hypervisor Parameters it works. Yast just ignoring for some reason parameters set through config file. Should I file bug report? On Wed, Nov 20, 2013 at 3:30 PM, Felix Miata wrote:

On 2013-11-20 14:39 (GMT+0900) Vitaliy Tomin composed:

...

What script using entries from /etc/sysconfig/bootloader? I've trying to set XEN_APPEND parameter, but this ignored by yast-bootloader, and even cleared after yast-bootloader run.

...

grub2-mkconfig seems to ignore this too.

I don't know, but I'll bet if you can and do switch from Grub2 to Grub Legacy that this problem will disappear. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Ok, I filled bug about yast bnc#851734 On Fri, Nov 22, 2013 at 4:30 AM, Christian Boltz wrote:

Hello,

Am Mittwoch, 20. November 2013 schrieb Vitaliy Tomin:

...

No, switching to grub legacy doesnt help. But I found that if I start yast2 bootloader, Click Edit -> fill Additional Xen Hypervisor Parameters it works. Yast just ignoring for some reason parameters set through config file.

...

Should I file bug report?

Hmm, let me think about it...

...

On Wed, Nov 20, 2013 at 3:30 PM, Felix Miata wrote:

...

On 2013-11-20 14:39 (GMT+0900) Vitaliy Tomin composed:

...

What script using entries from /etc/sysconfig/bootloader? I've trying to set XEN_APPEND parameter, but this ignored by yast-bootloader, and even cleared after yast-bootloader run.

Hmm, Yast modifies/clears a config file without anybody asking it to do so. Yes, that's what I call a bug ;-) (as usual, attach the y2logs)

...

...

...

grub2-mkconfig seems to ignore this too.

Nice, that's another bug ;-)

As usual: if something looks strange, don't ask. Just open a bugreport. The worst thing that can happen is a reply saying "wontfix, that's intentional behaviour". IMHO that's still better than asking on the ML and then forgetting to open a bugreport ;-)

Regards,

Christian Boltz --

...

Kann man ohne Motivation ein "Mailsystem" betreiben? hotmail? ;-) [> Marcus Stolzenberg und Jan P. Kessler in postfixbuch-users]

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sat, 23 Nov 2013 12:35:13 +0400 Andrey Borzenkov wrote:

В Wed, 20 Nov 2013 14:39:34 +0900 Vitaliy Tomin пишет:

...

What script using entries from /etc/sysconfig/bootloader? I've trying to set XEN_APPEND parameter, but this ignored by yast-bootloader, and even cleared after yast-bootloader run.

This is used by perl-Bootloader (update-bootloader) if current bootloader is set to GRUB (legacy) or LILO.

No, please no rumors. The file was introduced to fix problem when you switch different flavors of kernel. In such case it can happen that old kernel is removed before new one appear. In such case your kernel append line disappear and is empty -> users complain. So I introduce these lines to /etc/sysconfig/bootloader where yast2-bootloader store kernel append which customer choose. Important part is - IT IS USED ONLY WHEN NO OLD KERNEL APPEND IS FOUND. Reason is that many users aren't familiar with this file and edit directly lilo.conf, elilo.conf or menu.lst so we want to preserve even users manual change. So values in /etc/sysconfig/bootloader are used only as fallback defaults! Only important think in /etc/sysconfig/bootloader is bootloader type, so perl-bootloader know which bootloader update and how.

...

grub2-mkconfig seems to ignore this too.

Yes, I could not find where XEN options can be set for GRUB2 in yast, at least after cursory check.

yes, grub2 ignores it. Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org