Boot Issues


 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Boot Issues
Prev   Next
# 2  
Old 02-16-2019
Sounds like it is more of a Hyper-V problem than a Red-Hat issue.
It may well be that Hyper-V didn't support newer technology that
Red-Hat may have implemented at the time.


When running any guest OS through a hypervisor, you should try
the hypervisor forums first. This isn't a Windows 10 forum.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

WAN boot Server issues.

I 'm trying to configure a WAN boot server on Solaris10 x86 for sparc clients .. when i try to set up the server m getting following error ./setup_install_server -w /var/apache2/htdocs/wanboot10/wpath /var/apache2/htdocs/wanboot10/ipath ERROR: Cannot make WAN boot Image file on this... (6 Replies)
Discussion started by: fugitive
6 Replies

2. Solaris

Boot issues Solaris 10 + V440

Hello, I've a very weird problem with one of the machines. When I try to boot off a working DVD that I used to install another system with it spits out the following message: Sun Fire V440, No Keyboard Copyright 2007 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.22.33, 8192 MB... (14 Replies)
Discussion started by: stoci
14 Replies

3. Solaris

Windows,Solaris, Red Hat triple boot issues

I have a pentium IV with 512 MB ram and 80 GB HDD. I first installed windows XP on the first primary partition, then Solaris on the second with 20 GB for the solaris partition, and when rebooted , the grub menu functioned as expected giving me the options to dual boot, so next I wanted to install... (3 Replies)
Discussion started by: saagar
3 Replies

4. SCO

xp/sco 5.0.7 dual boot issues

Hello those more knowledgeable than I: I have been trying to get xp and SCO to coexist on the same system. I have tried several different ways to make both work, here's the list: -install xp, image it, move the partition to the end of drive, verify it boots, image again, -boot off of SCO... (6 Replies)
Discussion started by: stay0ut
6 Replies

5. Solaris

V1280 boot issues

I have a client with a V1280 onsite and it is having boot problems. Below is the message it is returning when trying to boot. Is this something that anybody has run into, or that you might be able to shed some light on? {0} ok boot /ssm@0,0/pci@18,700000/ide@3/cdrom@0,0:f SunOS Release 5.9... (3 Replies)
Discussion started by: xcwhitex
3 Replies

6. UNIX for Advanced & Expert Users

boot issues...

hardware on my first FreeBSD server has crashed. i was planning on swapping the HD into another machine, booting the generic kernel and then custom tailoring it to the new machine specs. however, i'm having a problem. the new machine is using a promise ultra100 card. i don't have any... (2 Replies)
Discussion started by: xyyz
2 Replies

7. UNIX for Advanced & Expert Users

Solaris boot issues

i'm having 2 problems. 1. the system will always look to boot from the net. i've changed the prom settings so that it boots from the disk, by entering "setenv boot-device disk0:3", but the system still seems to want to boot from the net. 2. i replaced my creator3d with an elitem6 and i did... (6 Replies)
Discussion started by: xyyz
6 Replies
Login or Register to Ask a Question
KERNEL-INSTALL(8)						  kernel-install						 KERNEL-INSTALL(8)

NAME
kernel-install - Add and remove kernel and initramfs images to and from /boot SYNOPSIS
kernel-install COMMAND KERNEL-VERSION [KERNEL-IMAGE] DESCRIPTION
kernel-install is used to install and remove kernel and initramfs images to and from /boot. kernel-install will execute the files located in the directory /usr/lib/kernel/install.d/ and the local administration directory /etc/kernel/install.d/. All files are collectively sorted and executed in lexical order, regardless of the directory in which they live. However, files with identical filenames replace each other. Files in /etc/kernel/install.d/ take precedence over files with the same name in /usr/lib/kernel/install.d/. This can be used to override a system-supplied executables with a local file if needed; a symbolic link in /etc/kernel/install.d/ with the same name as an executable in /usr/lib/kernel/install.d/, pointing to /dev/null, disables the executable entirely. Executables must have the extension ".install"; other extensions are ignored. COMMANDS
The following commands are understood: add KERNEL-VERSION KERNEL-IMAGE kernel-install creates the directory /boot/MACHINE-ID/KERNEL-VERSION/ and calls every executable /usr/lib/kernel/install.d/*.install and /etc/kernel/install.d/*.install with the arguments add KERNEL-VERSION /boot/MACHINE-ID/KERNEL-VERSION/ The kernel-install plugin 50-depmod.install runs depmod for the KERNEL-VERSION. The kernel-install plugin 90-loaderentry.install copies KERNEL-IMAGE to /boot/MACHINE-ID/KERNEL-VERSION/linux. It also creates a boot loader entry according to the boot loader specification in /boot/loader/entries/MACHINE-ID-KERNEL-VERSION.conf. The title of the entry is the PRETTY_NAME parameter specified in /etc/os-release, or "Linux KERNEL-VERSION", if unset. If the file initrd is found next to the linux file, the initrd will be added to the configuration. remove KERNEL-VERSION Calls every executable /usr/lib/kernel/install.d/*.install and /etc/kernel/install.d/*.install with the arguments remove KERNEL-VERSION /boot/MACHINE-ID/KERNEL-VERSION/ kernel-install removes the entire directory /boot/MACHINE-ID/KERNEL-VERSION/ afterwards. The kernel-install plugin 90-loaderentry.install removes the file /boot/loader/entries/MACHINE-ID-KERNEL-VERSION.conf. EXIT STATUS
If every executable returns with 0, 0 is returned, a non-zero failure code otherwise. FILES
/usr/lib/kernel/install.d/*.install /etc/kernel/install.d/*.install Drop-in files which are executed by kernel-install. /etc/kernel/cmdline /proc/cmdline The content of the file /etc/kernel/cmdline specifies the kernel command line to use. If that file does not exist, /proc/cmdline is used. /etc/machine-id The content of the file specifies the machine identification MACHINE-ID. /etc/os-release The content of the file specifies the operating system title PRETTY_NAME. SEE ALSO
machine-id(5), os-release(5), Boot loader specification[1] NOTES
1. Boot loader specification http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec systemd 208 KERNEL-INSTALL(8)