search for: grub_initrd

...will only return kernel entries, and I would expect a blank kernel entry to be a parse error, hence this would be redundant. > + > + my $kernel = > + Sys::VirtConvert::Converter::SUSE::_inspect_linux_kernel($g, $path); > + my $version = $kernel->{version}; > + my $grub_initrd = dirname($path)."/initrd-$version"; > + > + # No point in dying if /etc/SuSE-release can't be read > + my ($title) = eval { $g->read_lines('/etc/SuSE-release') }; > + $title ||= 'Linux'; Another change from RedHat.pm, obviously :) I think ther...

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

...urn if $g->aug_match("/files$grub_conf/title/kernel". + "[. = '$grub_path']") ne ''; + + my $kernel = + Sys::VirtConvert::Converter::SUSE::_inspect_linux_kernel($g, $path); + my $version = $kernel->{version}; + my $grub_initrd = dirname($path)."/initrd-$version"; + + # No point in dying if /etc/SuSE-release can't be read + my ($title) = eval { $g->read_lines('/etc/SuSE-release') }; + $title ||= 'Linux'; + + # Set title to just the release string + $title =~ s/ \(.*//; +...

...ot;/files$grub_conf/title/kernel". + "[. = '$grub_path']"); + return if scalar(@entries) > 0; + + my $kernel = + Sys::VirtConvert::Converter::Linux::_inspect_linux_kernel($g, $path); + my $version = $kernel->{version}; + my $grub_initrd = dirname($path)."/initrd-$version"; + + # No point in dying if /etc/(distro)-release can't be read + my ($title) = eval { $g->inspect_get_product_name($root) }; + $title ||= 'Linux'; + + # Remove codename or architecture + $title =~ s/ \(.*\)//; + # Remov...

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

...-251,15 +321,17 @@ sub check return if scalar(@entries) > 0; my $kernel = - Sys::VirtConvert::Converter::RedHat::_inspect_linux_kernel($g, $path); + Sys::VirtConvert::Converter::Linux::_inspect_linux_kernel($g, $path); my $version = $kernel->{version}; my $grub_initrd = dirname($path)."/initrd-$version"; - # No point in dying if /etc/redhat-release can't be read - my ($title) = eval { $g->read_lines('/etc/redhat-release') }; + # No point in dying if /etc/(distro)-release can't be read + my ($title) = eval { $g->inspe...

...#39;$grub_path']"); return if scalar(@entries) > 0; my $kernel = - Sys::VirtConvert::Converter::RedHat::_inspect_linux_kernel($g, $path); + Sys::VirtConvert::Converter::Linux::_inspect_linux_kernel($g, $path); my $version = $kernel->{version}; my $grub_initrd = dirname($path)."/initrd-$version"; - # No point in dying if /etc/redhat-release can't be read - my ($title) = eval { $g->read_lines('/etc/redhat-release') }; + # No point in dying if /etc/(distro)-release can't be read + my ($title) = eval { $g->inspe...

In preparation for an upcoming patch which adds support for SUSE guest conversions, it makes sense to have an intermediate steps that changes the RedHat.pm converter into a more generic Linux converter. The SUSE changes will then be limited in scope to only what is required for SUSE support. This series of patches accomplishes the following: - Renames RedHat.pm to Linux.pm - Modifies Linux.pm

...;$module "); > > + } > > + push(@module_args, "\""); > > + > > + my @env; > > + > > + $g->sh(join(' ', @env).'/sbin/mkinitrd '.join(' ', @module_args). > > + " -i $grub_initrd -k /boot/vmlinuz-$version"); > > I think you're looking for: > > $g->sh(join(' ', @env).' /sbin/mkinitrd -m "'.join(' ', @modules).'" '. > > We should probably modularise this who section somewhere. Ok. I'll change it....

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 >