search for: 744e

...<= 0) { reply_with_error ("partition number must be >= 1"); @@ -814,6 +815,8 @@ do_part_get_gpt_type(const char *device, int partnum) return NULL; } + int fieldlen = strlen (field); + /* Parse the output of sgdisk -i: * Partition GUID code: 21686148-6449-6E6F-744E-656564454649 (BIOS boot partition) * Partition unique GUID: 19AEC5FE-D63A-4A15-9D37-6FCBFB873DC0 @@ -832,28 +835,22 @@ do_part_get_gpt_type(const char *device, int partnum) /* Split the line in 2 at the colon */ char *colon = strchr (line, ':'); if (colon) { -#define SEAR...

...= split_lines (out); + if (lines == NULL) { + reply_with_error ("'%s %s -i %i' returned no output", + str_sgdisk, device, partnum); + free (out); + return NULL; + } + + /* Parse the output of sgdisk -i: + * Partition GUID code: 21686148-6449-6E6F-744E-656564454649 (BIOS boot partition) + * Partition unique GUID: 19AEC5FE-D63A-4A15-9D37-6FCBFB873DC0 + * First sector: 2048 (at 1024.0 KiB) + * Last sector: 411647 (at 201.0 MiB) + * Partition size: 409600 sectors (200.0 MiB) + * Attribute flags: 0000000000000000 + * Partition name: '...

Hi, attached there are few patches to implement a way to get the label of GPT partitions (refactoring an existing function and adding a new daemon API) and using it in virt-resize to restore them when copying partitions. Thanks, Pino Toscano (3): daemon: parted: refactor sgdisk info parsing code New API: part-get-name (RHBZ#593511). resize: preserve GPT partition names (RHBZ#1060404).

As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume. The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory. Is this OK? At this point I am not worried about snapshots or any other complexities. If the subvolume name is known. should grub2 be able to

...undef, ['grub2'], undef, $g, $self->{root}, $self->{config}, $self) > + or v2vdie __x('Failed to install non-EFI grub2'); > + > + # Relabel the EFI boot partition as a BIOS boot partition > + $g->part_set_gpt_type($device, 1, '21686148-6449-6E6F-744E-656564454649'); > + > + # Delete the fstab entry for the EFI boot partition > + eval { > + foreach my $node ($g->aug_match("/files/etc/fstab/*[file = '/boot/efi']")) > + { > + $g->aug_rm($node); > + } > + }...

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 >

...stall_any + (undef, ['grub2'], undef, $g, $self->{root}, $self->{config}, $self) + or v2vdie __x('Failed to install non-EFI grub2'); + + # Relabel the EFI boot partition as a BIOS boot partition + $g->part_set_gpt_type($device, 1, '21686148-6449-6E6F-744E-656564454649'); + + # Delete the fstab entry for the EFI boot partition + eval { + foreach my $node ($g->aug_match("/files/etc/fstab/*[file = '/boot/efi']")) + { + $g->aug_rm($node); + } + }; + augeas_error($g, $@) if $@; + +...

...stall_any + (undef, ['grub2'], undef, $g, $self->{root}, $self->{config}, $self) + or v2vdie __x('Failed to install non-EFI grub2'); + + # Relabel the EFI boot partition as a BIOS boot partition + $g->part_set_gpt_type($device, 1, '21686148-6449-6E6F-744E-656564454649'); + + # Delete the fstab entry for the EFI boot partition + foreach my $node ($g->aug_match("/files/etc/fstab/*[file = '/boot/efi']")) { + $g->aug_rm($node); + } + eval { $g->aug_save(); }; + augeas_error($g, $@) if $@; + + # Ins...

...nvert::Convert::Linux::_install_any (undef, ['grub2'], undef, $g, $self->{root}, $self->{config}, $self) or v2vdie __x('Failed to install non-EFI grub2'); @@ -494,7 +577,8 @@ sub convert_efi $g->part_set_gpt_type($device, 1, '21686148-6449-6E6F-744E-656564454649'); # Delete the fstab entry for the EFI boot partition - foreach my $node ($g->aug_match("/files/etc/fstab/*[file = '/boot/efi']")) { + foreach my $node ($g->aug_match("/files/etc/fstab/*[file = '/boot/efi']")) + {...

I think this fixes everything mentioned: - Added the Optgroups module as suggested. - Remove command temporary files. - Replace command ~flags with ?fold_stdout_on_stderr. - Nest _with_mounted function. - Rebase & retest. Rich.

v1 was posted here: https://www.redhat.com/archives/libguestfs/2017-July/msg00098.html This series now depends on two small patches which I posted separately: https://www.redhat.com/archives/libguestfs/2017-July/msg00207.html https://www.redhat.com/archives/libguestfs/2017-July/msg00209.html v1 -> v2: - Previously changes to generator/daemon.ml were made incrementally through the patch

Previously posted as part of the mega utilities/inspection series here: https://www.redhat.com/archives/libguestfs/2017-June/msg00232.html What I've done is to extract just the parts related to rewriting daemon APIs in OCaml, rebase them on top of the current master, fix a few things, and recompile and test everything. Rich.

v6 was posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00103.html and this requires the utilities refactoring posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html Inspection is now complete[*], although not very well tested. I'm intending to compare the output of many guests using old & new virt-inspector to see if I can find any

v5: https://www.redhat.com/archives/libguestfs/2017-June/msg00065.html Since v5, this now implements inspection almost completely for Linux and Windows guests. Rich.

v7 was: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html https://www.redhat.com/archives/libguestfs/2017-June/msg00184.html I believe this addresses all comments received so far. Also it now passes a test where I compared about 100 disk images processed with old and new virt-inspector binaries. The output is identical in all cases except one which is caused by a bug in blkid