[solved]CentOS 7 don't start in VMware Player

Issues related to applications and software problems
Hanisch
Posts: 57
Joined: 2015/08/10 13:26:03

Re: CentOS 7 don't start in VMware Player

Post by Hanisch » 2019/11/09 20:47:21

TrevorH wrote:
2019/11/09 20:26:30
You are running a prehistoric kernel.

Next thing to check then... If you are having problems with grub2 on CentOS 7, such as new kernels not being detected, you should check the symlink exists between
/etc/grub2.cfg -> ../boot/grub2/grub.cfg (legacy BIOS)
The symlink exists.
In 'yumex' under kernel only the kernel 3.10.0-693.21.1.el7 is shown an can't reinstalled.

Code: Select all

$ sudo dracut --regenerate-all --force
Failed to install module vmxnet3

Broadcast message from systemd-journald@VM-CentOS (Sun 2019-11-10 10:31:38 CET):

dracut[11772]: Failed to install module vmxnet3

Message from syslogd@VM-CentOS at Nov 10 10:31:38 ...
 dracut:Failed to install module vmxnet3
depmod: WARNING: could not open /var/tmp/dracut.mH3zg2/initramfs/lib/modules/3.10.0-514.el7.x86_64/modules.order: No such file or directory
depmod: WARNING: could not open /var/tmp/dracut.mH3zg2/initramfs/lib/modules/3.10.0-514.el7.x86_64/modules.builtin: No such file or directory
What is here wrong?
-------------------------------------------------------------------------------------------------------------------------------------------------------
with a new initramfs created under VirtualBox the problem in VMware Player is the same.

Code: Select all

$ sudo dracut -v -f
Executing: /sbin/dracut -v -f
dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
*** Including module: bash ***
*** Including module: nss-softokn ***
*** Including module: i18n ***
*** Including module: network ***
*** Including module: ifcfg ***
*** Including module: drm ***
*** Including module: plymouth ***
*** Including module: kernel-modules ***
*** Including module: resume ***
*** Including module: rootfs-block ***
*** Including module: terminfo ***
*** Including module: udev-rules ***
Skipping udev rule: 40-redhat-cpu-hotplug.rules
Skipping udev rule: 91-permissions.rules
*** Including module: biosdevname ***
*** Including module: systemd ***
*** Including module: usrmount ***
*** Including module: base ***
*** Including module: fs-lib ***
*** Including module: microcode_ctl-fw_dir_override ***
  microcode_ctl module: mangling fw_dir
    microcode_ctl: reset fw_dir to "/lib/firmware/updates /lib/firmware"
    microcode_ctl: processing data directory  "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-4f-01"...
intel-06-4f-01: model 'GenuineIntel 06-4f-01', path ' intel-ucode/06-4f-01', kvers ' 4.17.0 3.10.0-894 3.10.0-862.6.1 3.10.0-693.35.1 3.10.0-514.52.1 3.10.0-327.70.1 2.6.32-754.1.1 2.6.32-573.58.1 2.6.32-504.71.1 2.6.32-431.90.1 2.6.32-358.90.1'
intel-06-4f-01: blacklist ''
intel-06-4f-01: caveat is disabled in configuration
    microcode_ctl: kernel version "3.10.0-693.21.1.el7.x86_64" failed early load check for "intel-06-4f-01", skipping
    microcode_ctl: processing data directory  "/usr/share/microcode_ctl/ucode_with_caveats/intel"...
intel: model '', path ' intel-ucode/*', kvers ''
intel: blacklist ''
intel: early load kernel version check for '3.10.0-693.21.1.el7.x86_64' against ' 4.10.0 3.10.0-930 3.10.0-862.14.1 3.10.0-693.38.1 3.10.0-514.57.1 3.10.0-327.73.1' failed
    microcode_ctl: kernel version "3.10.0-693.21.1.el7.x86_64" failed early load check for "intel", skipping
    microcode_ctl: processing data directory  "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-2d-07"...
intel-06-2d-07: model 'GenuineIntel 06-2d-07', path ' intel-ucode/06-2d-07', kvers ''
intel-06-2d-07: blacklist ''
intel-06-2d-07: caveat is disabled in configuration
    microcode_ctl: kernel version "3.10.0-693.21.1.el7.x86_64" failed early load check for "intel-06-2d-07", skipping
    microcode_ctl: final fw_dir: "/lib/firmware/updates /lib/firmware"
*** Including module: shutdown ***
*** Including modules done ***
*** Installing kernel module dependencies and firmware ***
*** Installing kernel module dependencies and firmware done ***
*** Resolving executable dependencies ***
*** Resolving executable dependencies done***
*** Hardlinking files ***
*** Hardlinking files done ***
*** Stripping files ***
*** Stripping files done ***
*** Generating early-microcode cpio image contents ***
*** No early-microcode cpio image needed ***
*** Store current command line parameters ***
*** Creating image file ***
*** Creating image file done ***
*** Creating initramfs image file '/boot/initramfs-3.10.0-693.21.1.el7.x86_64.img' done ***

Code: Select all

$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Hintergrund gefunden: /usr/share/backgrounds/default-mit-Text.tga
Linux-Abbild gefunden: /boot/vmlinuz-3.10.0-693.21.1.el7.x86_64
initrd-Abbild gefunden: /boot/initramfs-3.10.0-693.21.1.el7.x86_64.img
erledigt

with regards
Ch. Hanisch

Hanisch
Posts: 57
Joined: 2015/08/10 13:26:03

Re: CentOS 7 don't start in VMware Player

Post by Hanisch » 2019/11/11 10:44:51

Hello,
the solution is found.
In VirtualBox:

Code: Select all

$ sudo dracut --force --no-hostonly

$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Hintergrund gefunden: /usr/share/backgrounds/default-mit-Text.tga
Linux-Abbild gefunden: /boot/vmlinuz-3.10.0-693.21.1.el7.x86_64
initrd-Abbild gefunden: /boot/initramfs-3.10.0-693.21.1.el7.x86_64.img
erledigt
In VMware Player the CentOS 7 works well now.

with regards
Ch. Hanisch

User avatar
TrevorH
Forum Moderator
Posts: 27152
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: [solved]CentOS 7 don't start in VMware Player

Post by TrevorH » 2019/11/11 10:58:28

You are STILL running a 2 year old kernel that has unfixed security vulnerabilities.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
CentOS 5 has been EOL for nearly 3 years and should no longer be used for anything!
Full time Geek, part time moderator. Use the FAQ Luke

tunk
Posts: 625
Joined: 2017/02/22 15:08:17

Re: [solved]CentOS 7 don't start in VMware Player

Post by tunk » 2019/11/11 11:12:52

Maybe the kernel is excluded from yum updates:
https://access.redhat.com/solutions/10185

Hanisch
Posts: 57
Joined: 2015/08/10 13:26:03

Re: [solved]CentOS 7 don't start in VMware Player

Post by Hanisch » 2019/11/11 14:54:05

Hello,
tunk wrote:
2019/11/11 11:12:52
Maybe the kernel is excluded from yum updates:
https://access.redhat.com/solutions/10185
Yes, in my /etc/yum.conf was

Code: Select all

 ...
# Exclude Kernel Updates
exclude=kernel*
...
I have comment out this line and now I have the newest kernel with yum update.
However a new initramfs is necessary:

Code: Select all

$ sudo dracut --force --no-hostonly

Code: Select all

$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Hintergrund gefunden: /usr/share/backgrounds/default-mit-Text.tga
Linux-Abbild gefunden: /boot/vmlinuz-3.10.0-1062.4.1.el7.x86_64
initrd-Abbild gefunden: /boot/initramfs-3.10.0-1062.4.1.el7.x86_64.img
Linux-Abbild gefunden: /boot/vmlinuz-3.10.0-693.21.1.el7.x86_64
initrd-Abbild gefunden: /boot/initramfs-3.10.0-693.21.1.el7.x86_64.img
Linux-Abbild gefunden: /boot/vmlinuz-0-rescue-0c4f199c0ce74a65839bf578091ff91d
initrd-Abbild gefunden: /boot/initramfs-0-rescue-0c4f199c0ce74a65839bf578091ff91d.img
erledigt
Why it is recommendet exclude Kernel Updates?

The newest Kernel

Code: Select all

$ uname -r
3.10.0-1062.4.1.el7.x86_64
has only the resolutions:

Code: Select all

$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
   1024x768       0.00* 
   800x600        0.00  
   640x480        0.00  
That is not so good, because I will get 1280x720.
How can I change it?

with regards
Ch. Hanisch

User avatar
TrevorH
Forum Moderator
Posts: 27152
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: [solved]CentOS 7 don't start in VMware Player

Post by TrevorH » 2019/11/11 17:09:07

Why it is recommendet exclude Kernel Updates?
It isn't recommended at all.
However a new initramfs is necessary:
If you just installed it then it will have built a new one when it was installed. Do you really need to do it again?
CentOS 6 will die in November 2020 - migrate sooner rather than later!
CentOS 5 has been EOL for nearly 3 years and should no longer be used for anything!
Full time Geek, part time moderator. Use the FAQ Luke

Hanisch
Posts: 57
Joined: 2015/08/10 13:26:03

Re: [solved]CentOS 7 don't start in VMware Player

Post by Hanisch » 2019/11/11 17:36:21

TrevorH wrote:
2019/11/11 17:09:07
However a new initramfs is necessary:
Do you really need to do it again?
Yes.

with regards
Ch. Hanisch

User avatar
TrevorH
Forum Moderator
Posts: 27152
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: [solved]CentOS 7 don't start in VMware Player

Post by TrevorH » 2019/11/11 19:07:59

I'm not understanding why you think you need to do it again but if you do then it's dracut that you need to use. The list of kernel versions that you need to use are in /lib/modules/ - one directory per version. There may be directories still there for kernels that you don't have installed any more so pick the right one.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
CentOS 5 has been EOL for nearly 3 years and should no longer be used for anything!
Full time Geek, part time moderator. Use the FAQ Luke

Hanisch
Posts: 57
Joined: 2015/08/10 13:26:03

Re: [solved]CentOS 7 don't start in VMware Player

Post by Hanisch » 2019/11/11 19:13:20

TrevorH wrote:
2019/11/11 19:07:59
I'm not understanding why you think you need to do it again but if you do then it's dracut that you need to use. The list of kernel versions that you need to use are in /lib/modules/ - one directory per version. There may be directories still there for kernels that you don't have installed any more so pick the right one.
I think the Option '--no-hostonly'
in

Code: Select all

$ sudo dracut --force --no-hostonly
is the solution for my problem in VMware Player.

with regards
Ch. Hanisch
Last edited by Hanisch on 2019/11/12 09:00:47, edited 1 time in total.

User avatar
TrevorH
Forum Moderator
Posts: 27152
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: [solved]CentOS 7 don't start in VMware Player

Post by TrevorH » 2019/11/11 19:34:50

I mean the Parameter '--no-hostonly'
is the solution for my problem in VMware Player.
No. It's not.

That's ONLY the solution if you have an initramfs built on one machine (or VM) and need to translate it to another machine (or VM) with different "hardware". And then it needs to be done once ONLY, on the old machine/VM, before you move it to the new machine/VM in order just to get the system to boot on the new hardware. Once you are on the new hardware there should be no further changes required. All subsequent kernels that are installed on the new machine/VM will automatically detect the new hardware configuration on that machine/VM and generate the correct initramfs file for it.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
CentOS 5 has been EOL for nearly 3 years and should no longer be used for anything!
Full time Geek, part time moderator. Use the FAQ Luke

Post Reply

Return to “CentOS 7 - Software Support”