bug-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #54916] I cannot pass cmd line parameters from XEN's *.cfg file to


From: Krzysztof Leszczyński
Subject: [bug #54916] I cannot pass cmd line parameters from XEN's *.cfg file to xen-grub
Date: Tue, 30 Oct 2018 07:53:25 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

URL:
  <https://savannah.gnu.org/bugs/?54916>

                 Summary: I cannot pass cmd line parameters from XEN's *.cfg
file to xen-grub
                 Project: GNU GRUB
            Submitted by: chewbaccakl
            Submitted on: Tue 30 Oct 2018 11:53:23 AM UTC
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Git master
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

I have several domU-s on my xen machine each uses xen-grub2 configured as
kernel to start, i.e. the virtualname.cfg contains no bootloader (like pygrub)
but


    kernel = /path/to/grub-x86_64-xen.bin


It would be nice if I could pass some parameters using xen's extra= or append=
because each instance might have some different file system scheme. Right now
I just link each grub with a separate compiled in grub.cfg.

It's especially needed for dom-U systems based on zfs or btrfs because it
might have multiple snapshots with different grub.cfg

Before I filled this bug I tried to find a workaround:
https://serverfault.com/questions/936048/is-it-possible-to-pass-command-line-to-grub2-as-xen-kernel






    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?54916>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]