search for: _prepare_bootable

...rder of modules here is deliberately the same as the order # specified in the postinstall script of kmod-virtio in RHEL3. The # reason is that the probing order determines the major number of vdX # block devices. If we change it, RHEL 3 KVM guests won't boot. - _prepare_bootable($g, $desc, $kernel, "virtio", "virtio_ring", - "virtio_blk", "virtio_net", - "virtio_pci"); + _prepare_bootable($g, $root, $desc, $kernel, "virtio&...

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 >

...it. + $boot_kernel = $backup_ver if defined($backup_ver); return $boot_kernel; } @@ -1097,8 +1242,8 @@ sub _configure_boot # reason is that the probing order determines the major number of vdX # block devices. If we change it, RHEL 3 KVM guests won't boot. _prepare_bootable($g, $root, $grub, $kernel, "virtio", "virtio_ring", - "virtio_blk", "virtio_net", - "virtio_pci"); +...

...der of modules here is deliberately the same as the order + # specified in the postinstall script of kmod-virtio in RHEL 3. The + # reason is that the probing order determines the major number of vdX + # block devices. If we change it, RHEL 3 KVM guests won't boot. + _prepare_bootable($g, $root, $grub, $kernel, "virtio", "virtio_ring", + "virtio_blk", "virtio_net", + "virtio_pci"); + } else { + _prepare_bootable($g, $...

...rder of modules here is deliberately the same as the order + # specified in the postinstall script of kmod-virtio in RHEL3. The + # reason is that the probing order determines the major number of vdX + # block devices. If we change it, RHEL 3 KVM guests won't boot. + _prepare_bootable($g, $root, $grub, $kernel, "virtio", "virtio_ring", + "virtio_blk", "virtio_net", + "virtio_pci"); + } else { + _prepare_bootable($g, $...

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

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

...$g->aug_save(); + + # Re-generate the grub2 config if grub2 files were changed + if (defined($grub2_remap)) { + $g->command(['grub2-mkconfig', '-o', $grub->{cfg}]); + } }; augeas_error($g, $@) if ($@); @@ -2372,6 +2760,12 @@ sub _prepare_bootable $grub_initrd, $version]); } + elsif (_is_suse_family($g, $root) && ($g->exists('/sbin/mkinitrd'))) { + $g->sh('/sbin/mkinitrd -m "'.join(' ', @modules).'" '. + ' -i '.$grub_initrd....

...*/kernel/root"), > + $g->aug_match("/files$grub->{grub_conf}/*/kernel/resume"), This doesn't work for grub2. However, it does need to be done, and we don't do it in RedHat.pm. Again, I'd like to see a general solution to this. > +sub _prepare_bootable > +{ > + my ($g, $root, $grub, $version, @modules) = @_; > + > + my $path = "/boot/vmlinuz-$version"; > + $grub->write($path); > + my $grub_initrd = $grub->get_initrd($path); > + > + # Backup the original initrd > + $g->mv($grub_initrd...