similar to: [PATCH node-image] kdump support

top-level kickstart file contains only includes, example custom-template.ks is provided with documented customization points. Signed-off-by: Alan Pevec <apevec at redhat.com> --- recipe/common-manifest-post.ks | 31 +++++++++++ recipe/common-manifest-pre.ks | 11 ++++ recipe/common-post-chroot.ks | 46 ++++++++++++++++ recipe/common-post.ks | 24 +++++++++

On Thu, Mar 28, 2019 at 6:55 AM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: > > -----Original Messages----- > > From: "Benjamin Hauger" <hauger at noao.edu> > > Sent Time: 2019-03-28 01:31:40 (Thursday) > > To: wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn>, centos at centos.org > > Cc: > > Subject: Re: [CentOS] How to specify

rhbz#733357 Signed-off-by: Mike Burns <mburns at redhat.com> --- recipe/common-nochroot.ks | 19 +++++++++++++++++-- 1 files changed, 17 insertions(+), 2 deletions(-) diff --git a/recipe/common-nochroot.ks b/recipe/common-nochroot.ks index c5d009f..c6dd76d 100644 --- a/recipe/common-nochroot.ks +++ b/recipe/common-nochroot.ks @@ -17,6 +17,9 @@ sed -i -e 's/ quiet//'

What do you mean? Wouldn't the kernel version always be the actual running version of the kernel that was booted? Ben On 3/26/19 6:16 PM, wuzhouhui wrote: >> -----Original Messages----- >> From: "Benjamin Hauger" <hauger at noao.edu> >> Sent Time: 2019-03-27 00:15:21 (Wednesday) >> To: centos at centos.org >> Cc: >> Subject: Re: [CentOS]

The purpose of this patch is to add the matahari qmf agent package (http://git.et.redhat.com/?p=matahari.git;a=summary) to the node image. Matahari is a qmf agent that publishes hardware information to an amqp broker, replacing functionality from ovirt-identify-node. However, since the capability is not ovirt specific, the agent is maintained as a separate project (see link above). Dependencies

(depends on Advance Storage Configuration patch) This patch adds the option of requesting, at install time, that swap LVs be encrypted. The modifications include: * Introduction of the ovirt_swap_encrypt install parameter * Inclusion of all required packages * Inclusion of required kernel modules * Introduction of /etc/ovirt-crypttab to hold encrypted swap configuration (Couldn't use

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Removed ks files, now in ovirt-node-recipe, which is subpackage of ovirt-node. Removed tools, these are now in ovirt-node-recipe which is subpackage of ovirt-node.

Is there already a way to read directly from the disk, perhaps via INT22/19h, using the COM32 open()/read() functions? If not, I'd like to propose adding the ability to do something like: int fd = open("//", O_RDONLY); to allow reading from the raw disk. I am working on building a COM32 module out of the checkisomd5 tool from isomd5sum, but I need a way to access the raw disk in

Unable to boot using qemu-kvm and gPXE from virt-preview repository https://bugzilla.redhat.com/show_bug.cgi?id=512358 Signed-off-by: Alan Pevec <apevec at redhat.com> --- common-blacklist.ks | 9 +++++++++ common-pkgs.ks | 3 +++ 2 files changed, 12 insertions(+), 0 deletions(-) diff --git a/common-blacklist.ks b/common-blacklist.ks index 7c19aa4..2f8842f 100644 ---

Hi All, During booting from network i am getting the following error initrd too large to handle, disabling initrd Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Size of initrd0.img is approx. 317 MB Size of vmlinuz is approx. 4 MB Following is the part of my default file in pxelinux.cfg/ label linux0 menu label MyFedora13 (default) kernel vmlinuz0 APPEND

Hello, I am trying to build a PXE boot image for CentOS 7. livemedia-creator --make-pxe-live --ks=ks --no-virt It runs the entire process and then it says: losetup: /dev/: detach failed: Inappropriate ioctl for device 2019-12-26 11:49:47,293: Disk Image install successful 2019-12-26 11:49:47,293: working dir is /var/tmp/tmpKwqC77 mount: /dev/loop0 is write-protected, mounting read-only mount:

I have "issues" with later versions of Centos/RHEL 7 also. PXE boot seems to work, but after the new kernel kexec's, it seems to drop the NICS and further in the process for some reason, the nics never come up, which leads to all kindsof issues of course (trying to boot a cluster that way). I also have the impression that it is a dracut issue, however, I have not pinpointed it

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Moves tools and kickstart files form ovirt-node-image to subpackage ovirt-node-recipe. Removes old sub packages form ovirt-node, stateless, logos, selinux. Modifies init scripts to meet Fedora packaging guidelines: added status, reload, and lockfile, rhbz: 514221 Added License file.

Oh, alright my specific issue is just about creating the actual pxe image.. not what happens after -----Original Message----- From: CentOS <centos-bounces at centos.org> On Behalf Of R C Sent: Thursday, December 26, 2019 12:18 PM To: centos at centos.org Subject: Re: [CentOS] livemedia-creator --make-pxe-live CentOS 7 I have "issues" with later versions of Centos/RHEL 7 also.

I'm trying to build a bugfixed anaconda package for 5.3 x84_64, but there are some fairly basic failures, like pkg-config .pc files not being found. When I modify the spec file accordingly, linking fails because installed libraries are not found. $ rpmbuild -ba anaconda.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.25019 + umask 022 + cd /usr/src/redhat/BUILD + LANG=C + export LANG +

this is cleaner and avoids rebuilding initramfs in the kickstart post it is built with correct configuration for the node image the first time, in kernel posttrans --- dracut/Makefile.am | 3 + ...-3d88d27810acc7782618d67a03ff5c0e41494ca4.patch | 20 ++++++++ ...-93724aa28fc20c8b7f0167201d1759b7118ba890.patch | 37 +++++++++++++++ dracut/ovirt-dracut.conf

Howdy, Running a round of updates from 6.3 to 6.4 and I'm seeing the following on all the servers. Want to make sure I'm not going to end up with a kernel panic if I reboot into the new kernel or have any other issues. Apr 22 11:10:21 www kdump: kexec: unloaded kdump kernel Apr 22 11:10:21 www kdump: stopped Apr 22 11:10:21 www kdump: mkdumprd: failed to make kdump initrd Apr 22

I've finally gotten back to my work on syslinux, and I've updated the patches I have for the advanced menu system and for COM32 to apply against the current git tree. I've got ten patches - mostly bug fixes, but a few are for additional COM32 or menu functionality. I've got them checked into a local git repository - what is the best way for me to pass them along?

Kexec / Kdump - xen-3.0.4-testing-13098 Kexec Kexec Kexec Kexec Kdump Hardware Xen -> Xen -> bzImage -> Xen -> Xen -> Arch Platform Xen bzImage Xen vmlinux vmlinux i386 A PASS PASS PASS PASS PASS i386 B (VMX) PASS PASS PASS PASS

I seem to be struggling with setting up kdump to debug Xen/dom0 freeze. According to http://xenbits.xen.org/docs/unstable/misc/kexec_and_kdump.txt the "crashkernel=" parameter must be passed to the Xen hypervisor. When it is passed to Xen I dont see "Crash Kernel" under System RAM in /proc/iomem inside dom0. I am missing something obvious here. Could someone please explain why