search for: mkconfig

...s(-) diff --git a/v2v/linux_bootloaders.ml b/v2v/linux_bootloaders.ml index a5e4c8d..0729f17 100644 --- a/v2v/linux_bootloaders.ml +++ b/v2v/linux_bootloaders.ml @@ -189,6 +189,22 @@ class bootloader_grub2 (g : G.guestfs) grub_config = object (self) inherit bootloader + method private grub2_mkconfig_cmd = + let elems = [ + "/sbin/grub2-mkconfig"; + "/usr/sbin/grub2-mkconfig"; + "/sbin/grub-mkconfig" + "/usr/sbin/grub-mkconfig" + ] in + try + List.find ( + let e -> + try g#is_file ~followsymlinks:...

...b..1f5f12c 100644 --- a/v2v/convert_linux.ml +++ b/v2v/convert_linux.ml @@ -109,6 +109,23 @@ let rec convert ~keep_serial_console (g : G.guestfs) inspect source rcaps = Not_found -> error (f_"no grub1/grub-legacy or grub2 configuration file was found") in + let grub2_mkconfig_cmd = + if grub = `Grub2 then + try + (* Red Hat and Suse families *) + ignore (g#command [| "grub2-mkconfig"; "--version" |]); + "grub2-mkconfig" + with G.Error _ -> + try + (* Debian family *) + ignore (g#...

..., 2 deletions(-) diff --git a/v2v/linux_bootloaders.ml b/v2v/linux_bootloaders.ml index a5e4c8d..4f53f87 100644 --- a/v2v/linux_bootloaders.ml +++ b/v2v/linux_bootloaders.ml @@ -186,6 +186,19 @@ end (* Grub2 representation. *) class bootloader_grub2 (g : G.guestfs) grub_config = + + let grub2_mkconfig_cmd = + let elems = [ + "/sbin/grub2-mkconfig"; + "/usr/sbin/grub2-mkconfig"; + "/sbin/grub-mkconfig"; + "/usr/sbin/grub-mkconfig" + ] in + try List.find (g#is_file ~followsymlinks:true) elems + with Not_found -> +...

Il 08/04/20 01:46, Jonathan Billings ha scritto: > On Apr 7, 2020, at 04:14, Alessandro Baggi <alessandro.baggi at gmail.com> wrote: >> thank you for your explanation. So in el8 grubby should be used to update kernel opts and grub2-mkconfig is used to generate an initial config. >> >> If I'm not wrong, grubby updates every single (sperated) entries on /boot/loader/entries and then generate the /boot/efi/EFI/centos/grub.cfg? >> >> Suppose that I want use only grub2-mkconfig to generate the grub.cfg what othe...

...nvert_linux.ml > +++ b/v2v/convert_linux.ml > @@ -109,6 +109,23 @@ let rec convert ~keep_serial_console (g : G.guestfs) inspect source rcaps = > Not_found -> > error (f_"no grub1/grub-legacy or grub2 configuration file was found") in > > + let grub2_mkconfig_cmd = > + if grub = `Grub2 then > + try > + (* Red Hat and Suse families *) > + ignore (g#command [| "grub2-mkconfig"; "--version" |]); > + "grub2-mkconfig" > + with G.Error _ -> > + try > + (...

....ml b/v2v/linux_bootloaders.ml > index a5e4c8d..0729f17 100644 > --- a/v2v/linux_bootloaders.ml > +++ b/v2v/linux_bootloaders.ml > @@ -189,6 +189,22 @@ class bootloader_grub2 (g : G.guestfs) grub_config = > object (self) > inherit bootloader > > + method private grub2_mkconfig_cmd = I'd make it a simple attribute of the object, just like grub_prefix in class bootloader_grub1. > + let elems = [ > + "/sbin/grub2-mkconfig"; > + "/usr/sbin/grub2-mkconfig"; > + "/sbin/grub-mkconfig" > + "/usr/s...

...find nothing. >> Currently I used grubby but it does not write any file that I know like >> /boot/efi/EFI/centos/grub.cfg (I tried to remove and add arg but nothing >> changed on files), so I don't know where it make update. >> >> I never got a problem using grub2-mkconfig -o file on C7 (last used was 7.5) >> It always worked as expected to me (for example when I installed nvidia >> driver using NVIDIA package to blacklist nouveau manually). > In CentOS 8, GRUB2 uses 'blscfg' to store bootloader-independent boot > entries in /boot/loader/ent...

...0 at 12:05 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Thu, Aug 27, 2020 at 11:24:57AM +0300, Sam Eiderman wrote: > > Yes, I understand that, I am just surprised to know that we bind /sys > > for g.sh() commands. > > > > However, "g.command([self.mkconfig, '-o', self.config])" shouldn't > > have the appliances /sys available (I looked briefly in command.c and > > I don't see the same bind-mount code), or maybe I'm missing something. > > guestfs_sh, guestfs_sh_lines, guestfs_command, guestfs_command_lines &g...

Il 06/04/20 11:54, Georgios ha scritto: > Hi there! > I had a similar problem recently with grub. No idea why it doesnt work. > Try using grubby instead of grub2-mkconfig if you want the system to > keep your kernel parameters between boots. > > Something like: > > sudo grubby --args="i915.modeset=0 rd.driver.blacklist=i915" --update- > kernel=ALL > > > Hope it helps! > Have a nice day! > > > On Mon, 2020-04-06 at 11:...

...hree up by going back to the 228.14 kernel. Now, after googling and finding the CentOS bugzilla, 0009860, that referenced the upstream bugzilla, I applied the workaround discussed in it, Adding initcall_blacklist=clocksource_done_booting to GRUB_CMDLINE_LINUX in /etc/default/grub and then grub2-mkconfig -o /etc/grub2.cfg" On one. On the other, that's got a *large* RAID appliance (a JetStor w/ 42 4TB drives...), it seemed to work... then gave me a dozen or so ERROR: unsupported sector size 4096 on /dev/sdd. ERROR: unsupported sector size 4096 on /dev/sde. 0. Did the grub2-mkconfig...

Il 06/04/20 15:21, Simon Matter via CentOS ha scritto: >> Il 06/04/20 11:54, Georgios ha scritto: >>> Hi there! >>> I had a similar problem recently with grub. No idea why it doesnt work. >>> Try using grubby instead of grub2-mkconfig if you want the system to >>> keep your kernel parameters between boots. >>> >>> Something like: >>> >>> sudo grubby --args="i915.modeset=0 rd.driver.blacklist=i915" --update- >>> kernel=ALL >>> >>> >>> Hope...

...gt; > However this /sys has nothing to do with /sys as it may appear in the > guest when it is running. Libguestfs edits filesystems, it doesn't > run the guest. Yes, I understand that, I am just surprised to know that we bind /sys for g.sh() commands. However, "g.command([self.mkconfig, '-o', self.config])" shouldn't have the appliances /sys available (I looked briefly in command.c and I don't see the same bind-mount code), or maybe I'm missing something. > > > It seems that g.ls('/sys') is chrooted correctly. > > But g.sh('ls...

...> 228.14 kernel. > > Now, after googling and finding the CentOS bugzilla, 0009860, that > referenced the upstream bugzilla, I applied the workaround discussed in > it, Adding initcall_blacklist=clocksource_done_booting to > GRUB_CMDLINE_LINUX in /etc/default/grub and then grub2-mkconfig -o > /etc/grub2.cfg" > > On one. On the other, that's got a *large* RAID appliance (a JetStor w/ > 42 4TB drives...), it seemed to work... then gave me a dozen or so > ERROR: unsupported sector size 4096 on /dev/sdd. > ERROR: unsupported sector size 4096 on /dev/sde. &...

When I run "grub2-mkconfig" on my CentOS-7.1 desktop I get the warning (4 times) /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/block/8. Check your device.map. What exactly does this mean? My device map looks perfectly normal to me: [root at helen ~]# cat /boot/grub2/device.map (hd0) /de...

...>> >> Now, after googling and finding the CentOS bugzilla, 0009860, that >> referenced the upstream bugzilla, I applied the workaround discussed in >> it, Adding initcall_blacklist=clocksource_done_booting to >> GRUB_CMDLINE_LINUX in /etc/default/grub and then grub2-mkconfig -o >> /etc/grub2.cfg" You're writing the grub.cfg to the wrong location with the wrong name. It needs to go to /boot/grub2/grub.cfg - that's where the bootloader looks for it. grubby looks for /etc/grub2.cfg which is a symlink to /boot/grub2/grub.cfg, because grubby. >&gt...

Hi. Im trying to set intel_iommu=on on kernel parameters at grub but for some reason it doesnt work. I edit /etc/default/grub file and i add the parameter. then i run grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg and then i reboot. when i run virt-host-validate i get QEMU: Checking if IOMMU is enabled by kernel: WARN (IOMMU appears to be disabled in kernel. Add intel_iommu=on to kernel cmdline arguments) when i edit the grub menu durring boot and i put intel_iommu=on and...

I think i might have solve it. For some reason grub2-mkconfig doesnt work. (Have no idea why) I manage to solve it with grubby. sudo grubby --args="intel_iommu=on" --update-kernel=ALL For some reason it works. I dont know if it works if my kernel gets upgraded.

...nt(g.ls('/sys')) print(g.sh('ls /sys')) I get: [] block bus class dev devices firmware fs hypervisor kernel module power It seems that g.ls('/sys') is chrooted correctly. But g.sh('ls /sys') isn't. I came across this behavior when I used g.command(['grub2-mkconfig', '-o', '....']) on rhel7.8 and it didn't produce the correct linuxefi/initrdefi entries in grub, since in rhel7.8 the uefi detection algorithm is checking in bash '[ -d /sys/firmware/efi ]'. https://src.fedoraproject.org/rpms/grub2/blob/71e0fb4ea646071ec86e4a65bb242...

> Il 06/04/20 11:54, Georgios ha scritto: >> Hi there! >> I had a similar problem recently with grub. No idea why it doesnt work. >> Try using grubby instead of grub2-mkconfig if you want the system to >> keep your kernel parameters between boots. >> >> Something like: >> >> sudo grubby --args="i915.modeset=0 rd.driver.blacklist=i915" --update- >> kernel=ALL >> >> >> Hope it helps! >> Have a nice day!...