search for: initrd_modules

...;Fedora (2.6.29.6-213.fc11.i686.PAE)" ->{kernel} = \kernel ->{cmdline} = "ro root=/dev/mapper/vg_mbooth-lv_root rhgb" ->{initrd} = \initrd ->{default} = 0 The kernel and initrd entries are just references to their top level entries under kernels and initrd_modules respectively. It also changes the way Linux kernels and initrd are discovered. Instead of searching /lib/modules and /boot for files with matching names, kernels and initrds are scanned as they are discovered in grub.conf. --- perl/lib/Sys/Guestfs/Lib.pm | 278 +++++++++++++++++++++++++++++------...

I am trying to take a CentOS 7 img and get hyperv to boot. First step. qemu-img convert "CentOS7.img" -O vhdx -o subformat=dynamic "CentOS7.vhdx" after adding new hyper-v I get dracut-timeout... So doing some searching it says add hv_vmbus hv_netvsc hv_storvsc to INITRD_MODULES. which doesnt really exist any more in CentOS 7. I did find /etc/dracut.conf and add_drivers... I uncommented the line for '#add_drivers += "" ' added the above modules and then ran: grub2-mkconfig -o /boot/grub2/grub.cfg Then redid the convert above... Hyper-V still gives me d...

This is a repost of the patch I sent on Friday. I know it was already ACK'd, but I've changed a fair bit in addition to adding the requested POD. Specifically: I discovered that augeas's grub lens wasn't returning cmdline the way I expected. This is fixed. The kernel package, if known, is output as a property of the kernel. The XML output of virt-inspector is updated with all

Sure - I'm game. I didn't know to run dracut directly I guess (never done it). What is the command for that on CentOS 7. dracut .... Jerry

> man dracut Sure there is always that - thanks. But for a person doing this the first time - one is always wondering if he did something wrong with the command - that is why I asked. I'm doing something like: dracut -f /boot/initramfs-3.10.0-1062.el7.x86_64.img $(uname -r) Thanks again. Is there not a "simpler" command that says take the current kernel and re-run - no command

...le > exists. This module was renamed in more recent kernels (to > xen-netfront.ko), so it happened to not detect modern kernels as > PV-only, but this was by chance. Just stumbled upon this bit in v2v/convert_linux.ml: if family = `SUSE_family then ( (* Remove xen modules from INITRD_MODULES and DOMU_INITRD_MODULES. *) let variables = ["INITRD_MODULES"; "DOMU_INITRD_MODULES"] in let xen_modules = ["xennet"; "xen-vnif"; "xenblk"; "xen-vbd"] in should the list above be updated with the newer names of the Xen modules...

...my $distro = $1; @@ -1051,7 +1051,7 @@ like: %oses = { '/dev/VG/Root' => \%os, } - + (There can be multiple roots for a multi-boot VM). The C<\%os> hash contains the following keys (any can be omitted): @@ -1701,7 +1701,7 @@ sub _inspect_initrd $initrd_modules = {}; $os->{initrd_modules} = $initrd_modules; } - + $initrd_modules->{$version} = \@modules; return \@modules; -- 1.6.2.5

Hello, Any one know how to enable Fiber Channel QLOGIC driver for xen kernel? This driver is available in CentOS4.3 as default. But when i compile xen-3.0.2-2 with linux-2.6.16 or xen-3.0.1with linux-2.6.12, the driver is not there. I tried to turn on QLOGIC by using "make menuconfig" and modified .config file but there is no change in /lib/modules/2.6.x-xen/kernel/drivers/scsi after

...ver 10 SP2, when I try to make initrd img as README descirbed, but it tells me: #depmod 2.6.16.29-xen #mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen.img 2.6.16-xen Unknown option: -v Try mkinitrd -h Then I added the "aacraid, sd_mod, scsi_mod" to "INITRD_MODULES" section in "/etc/sysfconfig/kernel" and executed #mkinitrd initrd-2.6.16.29-xen.img 2.6.16.29-xen /sbin/mkinitrd: line 2965: initrd-2.6.16.29-xen.img/etc/fstab: No such file or directory No ''/'' mountpoint specified in initrd-2.6.16.29-xen.img/etc/fstab Is ther...

Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /. It gets past waiting for /dev/md0 to appear. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /. It gets past waiting for /dev/md0 to appear. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...st" List of file names for the initrd; position have match to "kernel list". Defaults to all all kernels found in /boot. -m "module list" Modules to include in initrd. Defaults to the INITRD_MODULES variable in /etc/sysconfig/kernel. -b boot_dir Boot directory. Defaults to /boot. -d root_device Root device. Defaults to the device from which the root_dir is mounted. Overrides the rootdev enviroment variable if set....

The following series of patches adds support for converting SUSE guests through virt-v2v. These changes should not impact non-SUSE guest conversions. Mike Latimer (4): Add perl-Bootloader support to grub packages Add conversion support for SUSE guests Add SUSE to capabilities db and conf Add SUSE support documentation lib/Sys/VirtConvert/Converter/Linux.pm | 480

...can be found on RHEL 3 machines my @remove; @@ -1230,6 +1364,27 @@ sub _unconfigure_xen $g->write_file('/etc/rc.local', join("\n", @rc_local)."\n", $size); } } + + if (_is_suse_family($g, $root)) { + # Remove xen modules from INITRD_MODULES and DOMU_INITRD_MODULES + my $sysconfig = '/etc/sysconfig/kernel'; + my @variables = qw(INITRD_MODULES DOMU_INITRD_MODULES); + my @xen_modules = qw(xennet xen-vnif xenblk xen-vbd); + my $modified; + + foreach my $var (@variables) { + foreach my...

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.

...can be found on RHEL 3 machines my @remove; @@ -1230,6 +1375,27 @@ sub _unconfigure_xen $g->write_file('/etc/rc.local', join("\n", @rc_local)."\n", $size); } } + + if (_is_suse_family($g, $root)) { + # Remove xen modules from INITRD_MODULES and DOMU_INITRD_MODULES + my $sysconfig = '/etc/sysconfig/kernel'; + my @variables = qw(INITRD_MODULES DOMU_INITRD_MODULES); + my @xen_modules = qw(xennet xen-vnif xenblk xen-vbd); + my $modified; + + foreach my $var (@variables) { + foreach my...

...ort keys %aliases; if (@keys) { - print " Modprobe aliases:\n"; + print __" Modprobe aliases:\n"; foreach (@keys) { printf " %-30s %s\n", $_, $aliases{$_}->{modulename} } @@ -389,7 +390,7 @@ sub output_text_os my %modvers = %{$os->{initrd_modules}}; my @keys = sort keys %modvers; if (@keys) { - print " Initrd modules:\n"; + print __" Initrd modules:\n"; foreach (@keys) { my @modules = @{$modvers{$_}}; print " $_:\n"; @@ -398,13 +399,13 @@ sub output_text_os } } - print &...

...arch); > + > + # We want an i586 guest for i[346]86 > + return 'i586' if($arch =~ /^i[346]86$/); RedHat.pm diff. > +# Unconfigure Xen specific guest modifications > +sub _unconfigure_xen > +{ > + my ($g, $apps) = @_; > + > + # Remove xen modules from INITRD_MODULES and DOMU_INITRD_MODULES variables > + my $sysconfig = '/etc/sysconfig/kernel'; > + my @variables = qw(INITRD_MODULES DOMU_INITRD_MODULES); > + my @xen_modules = qw(xennet xen-vnif xenblk xen-vbd); > + my $modified; > + > + foreach my $var (@variables) { >...

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

On Friday, October 04, 2013 09:38:58 AM Matthew Booth wrote: > It's specifically an error if we're attempting to configure virtio, and > there's no detected virtio kernel. It shouldn't have been possible to > get here in that state, hence it's a programmer error. The code below > attempts to install *any* kernel in the case that we aren't configuring >