search for: add_drivers+

...ESXi. I'm seeing errors like this: dracut-initqueue timeout dracut-initqueue timeout .... And it drops to "dracut#" shell, where I can see that there is no /dev/sda listed on /proc/partitions. I think I tried everything! My last try was, during Packer build, to append "add_drivers+=" sd_mod" to /etc/dracut.conf and re-building initramdisk by running "dracut -f". However, it does not boot either (on ESXi)! I can still boot using Rescue mode on VMWare, then, I can see that sd_mod is inside of initramfs as expected (lsinitrd FTW) but, dracut does not load...

https://bugzilla.redhat.com/show_bug.cgi?id=1167921

Howdy, I hit a snag trying to install Xen4CentOS on a Supermicro based system (X9DRD-7LN4F with the Broadcom/LSI 2308 chipset). I spent a few hours on this today, I'm posting this here in case it helps anyone else and saves them the frustration I dealt with. On this system I did a fresh install of CentOS 7, updated it, rebooted it, then installed Xen. The system was booting fine using the

...1 root root 374152 May 16 12:57 > usr/lib/modules/4.9.25-27.el7.x86_64/kernel/drivers/scsi/mpt3sas/mpt3sas.ko > > > After this I was able to get the 4.9 kernel to boot and Xen is now working. You should be able to make this change permanently from /etc/dracut.conf with the add_drivers+= line, or build a generic initrd with hostonly="no" . I don't know why it wasn't originally added. --Sarah

On Thu, 4 Feb 2016, Martinx - ????? wrote: > My last try was, during Packer build, to append "add_drivers+=" > sd_mod" to /etc/dracut.conf and re-building initramdisk by running > "dracut -f". However, it does not boot either (on ESXi)! > > I can still boot using Rescue mode on VMWare, then, I can see that > sd_mod is inside of initramfs as expected (lsinitrd FTW) but...

Does someone have a link to a how-to-do-it with firewalld, not "disable firewalld and use iptables"? mark

Just did an in-place update from 6.1 to 6.2 on my eeepc 901 (Atom CPU). during boot, (if I hit ESC to see the boot messages) it says "starging udev" then nothing else for a few seconds, then a huge register dump scrolls by. it's too big to see the beginning of it. If I boot from the prior kernel and look in /var/log/messages, I don't see any evidence of the failed boot.

...=mbr --append="console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH" +zerombr +clearpart --all --initlabel +autopart --type=plain + +# Halt the system once configuration has finished. +poweroff + +%packages +@core +%end + +%post +# Enable Xen domU support: +pushd /etc/dracut.conf.d +echo 'add_drivers+="xen:vbd xen:vif"' > virt-builder-xen-drivers.conf +popd +# Rerun dracut for the installed kernel (not the running kernel): +KERNEL_VERSION=$(rpm -q kernel --qf '%{version}-%{release}.%{arch}\n') +dracut -f /boot/initramfs-$KERNEL_VERSION.img $KERNEL_VERSION +%end +EOF + +...

On 10/10/2015 05:03 PM, Barry Brimer wrote: > On October 10, 2015 8:34:11 AM CDT, Imre Gergely <gimre at narancs.net> wrote: >> _netdev >> The filesystem resides on a device that requires network >> access (used to prevent the system from attempting to mount these >> filesystems until the network has been enabled on the system). >> >> This

Build script is based on fedora-aarch64.sh. This managed to build and compress an image, but it seems the process itself is not completely unattended. >From some strange reason I had to manually power off the VM after install. Maros Zatko (1): builder: add build script for PPC64 Fedora builder/website/fedora-ppc64.sh | 97 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 97

...> usr/lib/modules/4.9.25-27.el7.x86_64/kernel/drivers/scsi/ > mpt3sas/mpt3sas.ko > > > > > > After this I was able to get the 4.9 kernel to boot and Xen is now > working. > > You should be able to make this change permanently from /etc/dracut.conf > with > the add_drivers+= line, or build a generic initrd with hostonly="no" . > Thank you for this. Adding mpt2sas or mpt3sas to the drivers+ line worked. Running dracut generates a proper image now. > I don't know why it wasn't originally added. > > --Sarah > For some reason each o...

...ble Xen drivers only. + *) + (match os with + | Fedora _ -> + bpf "%%post\n"; + bpf "\ +# Ensure the installation is up-to-date. +dnf -y --best upgrade +"; + if arch = X86_64 then bpf "\ +# Enable Xen domU support. +pushd /etc/dracut.conf.d +echo 'add_drivers+=\"xen:vbd xen:vif\"' > virt-builder-xen-drivers.conf +popd + +# To make the Xen change permanent, we need to rerun dracut. +# Rerun dracut for the installed kernel (not the running kernel). +# See commit 0fa52e4e45d80874bc5ea5f112f74be1d3f3472f and +# https://www.redhat.com/archiv...

...packages we add to the base appliance. case "$osversion" in - centos-*|fedora-*|rhel-*|scientificlinux-*) + centos-*|fedora-*|rhel-*|scientificlinux-*|oraclelinux-*) depsfile="$datadir/dependencies.redhat" cat > $tmpdir/p2v.conf <<'EOF' add_drivers+=" usb-storage " diff --git a/sysprep/sysprep_operation_net_hostname.ml b/sysprep/sysprep_operation_net_hostname.ml index b455e5c93d66..fe3f47412d0f 100644 --- a/sysprep/sysprep_operation_net_hostname.ml +++ b/sysprep/sysprep_operation_net_hostname.ml @@ -28,7 +28,7 @@ let net_hostname_pe...

Now that virt-p2v has its own repository [1] and releases [2], it is time to remove it from libguestfs. [1] https://github.com/libguestfs/virt-p2v [2] http://download.libguestfs.org/virt-p2v/ Pino Toscano (2): Remove virt-p2v Remove remaining virt-p2v bits .gitignore | 4 - Makefile.am | 7 +- bash/Makefile.am