search for: defaultkernel

...> > Boot into the just installed kernel-plus and check to see if jfs is > working as expected. If all is fine, change the default kernel to > kernel-plus: > > # yum-config-manager --setopt=centosplus.includepkgs=kernel-plus > --enablerepo=centosplus --save > # sed -e 's/^DEFAULTKERNEL=kernel$/DEFAULTKERNEL=kernel-plus/' -i > /etc/sysconfig/kernel > > I would not say there is any downside, but I'm highly biased. ;) > > Akemi > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/...

On 09/15/2020 08:07 PM, Akemi Yagi wrote: > On Tue, Sep 15, 2020 at 3:54 PM H <agents at meddatainc.com> wrote: >> I had installed kmod-jfs in an earlier version of CentOS 7, 7.4 if I remember correctly. I now have a machine running the latest version of jfs module but kmod-jfs does not seem to be available. >> >> Is anyone running it on the current version of CentOS?

It appears that if I do anything to grub.conf, say, take out the rhgb quiet, after every succeding kernel update, I have to manually edit grub.conf, because the kernel update - maybe the post install script? - will set the default to be the previous kernel. Has anyone got a solution to this, so that a kernel update will give the new kernel as the default? mark

...you're using. Hello Jim, thanks for the reply. For some reason that doesnt' work. To test this I booted from an older kernel and removed the most recent Centos-kernel After installing Elrepo's kernel-ml the system boots from kernel-ml, with or without changing /etc/sysconfig/kernel to DEFAULTKERNEL=kernel-ml But after running an update again, and reinstalling the latest Centos kernel, the system boots from that kernel again. Greetings, J. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 _______________________________________________ CentO...

Exit with an error if we would overwrite an existing libvirt domain. Fixes RHBZ#617110 --- lib/Sys/VirtV2V/Connection/LibVirt.pm | 4 ++++ lib/Sys/VirtV2V/Target/LibVirt.pm | 31 ++++++++++++++++++++++++++++++- lib/Sys/VirtV2V/Target/RHEV.pm | 11 +++++++++++ 3 files changed, 45 insertions(+), 1 deletions(-) diff --git a/lib/Sys/VirtV2V/Connection/LibVirt.pm

.. in that expected way where newly installed kernel is set to boot as default. would you suggest where to look, what to check? many thanks.

...lerepo=centosplus install kernel-plus Boot into the just installed kernel-plus and check to see if jfs is working as expected. If all is fine, change the default kernel to kernel-plus: # yum-config-manager --setopt=centosplus.includepkgs=kernel-plus --enablerepo=centosplus --save # sed -e 's/^DEFAULTKERNEL=kernel$/DEFAULTKERNEL=kernel-plus/' -i /etc/sysconfig/kernel I would not say there is any downside, but I'm highly biased. ;) Akemi

...>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel [root@server ~]# [root@server ~]# [root@server ~]# [root@server ~]# [root@server ~]# [root@server ~]# cat /etc/sysconfig/kernel # UPDATEDEFAULT specifies if new-kernel-pkg should make # new kernels the default UPDATEDEFAULT=yes # DEFAULTKERNEL specifies the default kernel package type DEFAULTKERNEL=kernel alias scsi_hostadapter0 aacraid [root@server ~]# [root@server ~]# [root@server ~]# Please advise what to do to get rid of this warning or safely fix the issue. Thank you _______________________________________________ Xen-u...

Hello All, I purchased some Dell Latitude 3570 laptops. They came with Ubuntu preinstalled. ( Which I swapped for Centos7) I have to use Elrepo kernel on these machines to get some of the fn function keys to work. So I installed Elrepo's kernel-ml and selected this kernel with: # grub2-set-default 0 ( after disabling secure boot) The problem I see is that after a next kernel update,

...> > thanks for the reply. > For some reason that doesnt' work. > To test this I booted from an older kernel and removed the most recent Centos-kernel > After installing Elrepo's kernel-ml the system boots from kernel-ml, with or without changing /etc/sysconfig/kernel to > DEFAULTKERNEL=kernel-ml > But after running an update again, and reinstalling the latest Centos kernel, the system boots from that kernel again. There is no reason to keep the CentOS Kernel on your machines if the elrepo kernel is what you want to use. You should be able to (1) boot from an elrepo kernel th...

I have been reading the bug reports about the problem with initializing Logitech wireless devices using the current stock Centos 7 kernel. It's my understanding that this issue will be fixed in the Centos Plus kernel. However, I suspect that the issue will also be fixed at some point when Red Hat get around to fixing their kernel as well. My main computer has a Logitech wireless mouse

I'm trying to figure out how to replace the vmlinuz and initrd.img from CentOS 7.4 with "fixed" kernel-plus versions in order create CentOS 7.4 VM's. So far I'm stuck booting via 7.3 install, adding new kernel-plus and upgrading to 7.4. I've not found any complete Google answers and was looking for help making sure I choose the correct approach. I've tried to build

...file "/etc/sysconfig/kernel" "followsymlinks:true" > guestfsd: main_loop: new request, len 0x48 > guestfsd: main_loop: proc 37 (is_file) took 0.00 seconds > libguestfs: trace: v2v: is_file = 1 > libguestfs: trace: v2v: aug_match > "/files/etc/sysconfig/kernel/DEFAULTKERNEL/value" > guestfsd: main_loop: new request, len 0x5c > guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds > libguestfs: trace: v2v: aug_match = > ["/files/etc/sysconfig/kernel/DEFAULTKERNEL/value"] > libguestfs: trace: v2v: aug_set > "/files/etc/sysconfi...

v1: https://www.redhat.com/archives/libguestfs/2017-April/msg00031.html v2: https://www.redhat.com/archives/libguestfs/2017-April/msg00040.html v3: https://www.redhat.com/archives/libguestfs/2017-April/msg00051.html v3 -> v4: - Properly fix Xen PV-only kernel detection, and test it. Rich.

Yaniv pointed out in https://bugzilla.redhat.com/show_bug.cgi?id=1438794 that virt-v2v both doesn't install the virtio-rng driver for Windows, and doesn't give the guest a virtio-rng PCI device either. There are two problems here: Firstly the Windows virtio-rng driver isn't included in the exploded tree (/usr/share/virtio-win) so it doesn't get copied into the guest. The solution

v1 was posted here: https://www.redhat.com/archives/libguestfs/2017-April/msg00031.html v1 -> v2: - Add support for -o glance. - Add support for -o qemu. - Fix the -o libvirt support for balloon as pointed out by Dan. - Fix a test failure caused by changing libvirt XML output. Rich.

v1: https://www.redhat.com/archives/libguestfs/2017-April/msg00031.html v2: https://www.redhat.com/archives/libguestfs/2017-April/msg00040.html v2 -> v3: - Fix Xen PV-only kernel detection. Rich.

...gt; "$kernel_pkg"); + } + } + } + + # Check we have a bootable kernel. + v2vdie __('No bootable kernels installed, and no replacement '. + "is available.\nUnable to continue.") + unless defined($boot_kernel); + + # Ensure DEFAULTKERNEL is set to boot kernel package name + # It's not fatal if this rpm command fails + my ($kernel_pkg) = + eval { $g->command_lines(['rpm', '-qf', "/lib/modules/$boot_kernel", + '--qf', '%{NAME}\n']) }...

...rnel_pkg.$kernel_arch"); + } + } + } + + # Check we have a bootable kernel. + v2vdie __('No bootable kernels installed, and no replacement '. + "is available.\nUnable to continue.") + unless defined($boot_kernel); + + # Ensure DEFAULTKERNEL is set to boot kernel package name + # It's not fatal if this rpm command fails + my ($kernel_pkg) = + eval { $g->command_lines(['rpm', '-qf', "/lib/modules/$boot_kernel", + '--qf', '%{NAME}\n']) }...

This is a new conversion module to convert SUSE Linux and openSUSE guests. The converter is based on the RedHat module, and should offer the same functionality on both SUSE and RedHat hosts. There are a few additional messages in this module, such as reporting of packages when installing through zypper or the local virt-v2v repo. These messages don't necessarily flow unless verbose switches