search for: f81f

...in the RHEV cluster On Tue, Jan 14, 2014 at 08:07:43AM +0000, Исаев Виталий Анатольевич wrote: > [00072ms] /usr/libexec/qemu-kvm \ > -global virtio-blk-pci.scsi=off \ > -nodefconfig \ > -nodefaults \ > -nographic \ > -drive file=/dev/mapper/1a9aa971--f81f--4ad8--932f--607034c924fc-666faa62--da73--4465--aed2--912119fcf67f,snapshot=on,if=virtio \ > -nodefconfig \ > -machine accel=kvm:tcg \ > -m 500 \ > -no-reboot \ > -device virtio-serial \ > -serial stdio \ > -device sga \ > -chardev soc...

...“vm” xml file attached); 2. I determine the disk_image_id of the VM’s bootable disk (look at the image_id node in “disks” xml file attached); 3. Now I go to the RHEV-H to look for the disk image itself: [root@rhevh1 /]# find / -name cc6e4400-7c98-4170-9075-5f5790dfcff3 /dev/1a9aa971-f81f-4ad8-932f-607034c924fc/cc6e4400-7c98-4170-9075-5f5790dfcff3 /var/lib/stateless/writable/rhev/data-center/mnt/blockSD/1a9aa971-f81f-4ad8-932f-607034c924fc/images/8a3e02de-d8ab-4357-ba8c-490f3ba3e85c/cc6e4400-7c98-4170-9075-5f5790dfcff3 /rhev/data-center/mnt/blockSD/1a9aa971-f81f-4ad8-932f-607034c924...

[This email is either empty or too large to be displayed at this time]

...in the cluster, while all the Preallocated disks were handled with > libguestfs correctly. I guess these issues were caused by (b) and > probably (c) reasons: > > The backing file of any of the thin provisioned disks does not exist. For instance let’s consider the /dev/mapper/1a9aa971--f81f--4ad8--932f--607034c924fc-666faa62--da73--4465--aed2--912119fcf67f symbolic link pointing to /dev/dm-30 : > [root@rhevh1 mapper]# pwd > /dev/mapper > [root@rhevh1 mapper]# qemu-img info 1a9aa971--f81f--4ad8--932f--607034c924fc-666faa62--da73--4465--aed2--912119fcf67f > image: 1a9aa971--...

On Fri, Jan 17, 2014 at 02:38:43PM +0000, Исаев Виталий Анатольевич wrote: > 3. Now I go to the RHEV-H to look for the disk image itself: > > [root@rhevh1 /]# find / -name cc6e4400-7c98-4170-9075-5f5790dfcff3 > /dev/1a9aa971-f81f-4ad8-932f-607034c924fc/cc6e4400-7c98-4170-9075-5f5790dfcff3 > /var/lib/stateless/writable/rhev/data-center/mnt/blockSD/1a9aa971-f81f-4ad8-932f-607034c924fc/images/8a3e02de-d8ab-4357-ba8c-490f3ba3e85c/cc6e4400-7c98-4170-9075-5f5790dfcff3 > /rhev/data-center/mnt/blockSD/1a9aa971-f81f-4ad8-932f-...

-----Original Message----- From: Richard W.M. Jones [mailto:rjones@redhat.com] Sent: Thursday, January 16, 2014 8:58 PM To: Исаев Виталий Анатольевич Cc: libguestfs@redhat.com Subject: Re: [Libguestfs] LVM mounting issue On Thu, Jan 16, 2014 at 03:57:50PM +0000, Исаев Виталий Анатольевич wrote: > Hello, It's me again with one more misunderstanding of libguestfs usage... > Guestfish

On Tue, Jan 14, 2014 at 08:07:43AM +0000, Исаев Виталий Анатольевич wrote: > [00072ms] /usr/libexec/qemu-kvm \ > -global virtio-blk-pci.scsi=off \ > -nodefconfig \ > -nodefaults \ > -nographic \ > -drive file=/dev/mapper/1a9aa971--f81f--4ad8--932f--607034c924fc-666faa62--da73--4465--aed2--912119fcf67f,snapshot=on,if=virtio \ > -nodefconfig \ > -machine accel=kvm:tcg \ > -m 500 \ > -no-reboot \ > -device virtio-serial \ > -serial stdio \ > -device sga \ > -chardev socket,path...

At Mon, 28 May 2018 19:30:25 -0400 CentOS mailing list <centos at centos.org> wrote: > > On May 28, 2018, at 18:25, Robert Heller <heller at deepsoft.com> wrote: > > > I tried to run efibootmgr, but it wants a model named efivars loaded, but > > there is no such module available. > > Are you not running a CentOS kernel? That module should be available.

...4.efi) > > # blkid | grep sda1 > /dev/sda1: LABEL="ESP" UUID="3850-574E" TYPE="vfat" PARTLABEL="EFI > System Partition" PARTUUID="39484dd8-b1d9-47b2-b4d7-89dfe3ce5e09" > > # sgdisk -i1 /dev/sda > Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI System) > Partition unique GUID: 39484DD8-B1D9-47B2-B4D7-89DFE3CE5E09 > First sector: 2048 (at 1024.0 KiB) > Last sector: 1230847 (at 601.0 MiB) > Partition size: 1228800 sectors (600.0 MiB) > Attribute flags: 0000000000000000 > Partition name: 'EFI...

I'm going to push this because it's a test blocker, but FYI. Rich.

...0,0x12c000)/File(\EFI\fedora\shimx64.efi) # blkid | grep sda1 /dev/sda1: LABEL="ESP" UUID="3850-574E" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="39484dd8-b1d9-47b2-b4d7-89dfe3ce5e09" # sgdisk -i1 /dev/sda Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI System) Partition unique GUID: 39484DD8-B1D9-47B2-B4D7-89DFE3CE5E09 First sector: 2048 (at 1024.0 KiB) Last sector: 1230847 (at 601.0 MiB) Partition size: 1228800 sectors (600.0 MiB) Attribute flags: 0000000000000000 Partition name: 'EFI System Partition'

...| grep sda1 > > /dev/sda1: LABEL="ESP" UUID="3850-574E" TYPE="vfat" PARTLABEL="EFI > > System Partition" PARTUUID="39484dd8-b1d9-47b2-b4d7-89dfe3ce5e09" > > > > # sgdisk -i1 /dev/sda > > Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI System) > > Partition unique GUID: 39484DD8-B1D9-47B2-B4D7-89DFE3CE5E09 > > First sector: 2048 (at 1024.0 KiB) > > Last sector: 1230847 (at 601.0 MiB) > > Partition size: 1228800 sectors (600.0 MiB) > > Attribute flags: 0000000000000000 >...

...alled operating system (it might be, for example, an installer disk or live CD). If this is wrong, it is probably a bug in libguestfs. root=%s fmt=%s") root fmt > > -and has_uefi_bootable_device g = > +and get_uefi_bootable_device g = > let rec uefi_ESP_guid = "C12A7328-F81F-11D2-BA4B-00A0C93EC93B" > and is_uefi_ESP dev { G.part_num = partnum } = > g#part_get_gpt_type dev (Int32.to_int partnum) = uefi_ESP_guid > + and part_dev_name dev { G.part_num = partnum } = > + sprintf "%s%d" dev (Int32.to_int partnum) > and parttype_is...

Hi All; I have a new server we're setting up that supports EFI or Legacy in the bios I am a solid database guy but my SA skills are limited to what I need to get by 1) I used EFI because I wanted to create a raid 10 array with 6 4TB drives and apparently I cannot setup gpt partitions via parted in legacy mode (at least that's what I've read - is this true?) 2) I installed the OS

Hi all, We're using the classic boot BIOS syslinux successfully for many years, but meanwhile it's getting harder to buy hardware the still supports this boot mode. The option for us would be syslinux EFI boot. To avoid too many changes we would like to generate an image for our different hardware parts that supports both - classic BIOS boot and (U)EFI boot. This would allow us to leave

...s of partitioning: - Legacy: One to four MBR partitions. One of them bears the type 0xef. - GPT: Only one MBR partition, starting at LBA 1 and ending at the end of the ISO image. It must bear type 0xee. The EFI System partition is then marked by a GPT partition with type GUID C12A7328-F81F-11D2-BA4B-00A0C93EC93B Both alternatives demand neat partitioning. Especially no nested partitions. isohybrid violates UEFI by combining both methods and by nesting partitions. The motivation for this is given by Matthew Garrett in http://mjg59.dreamwidth.org/11285.html I made a lengthy analysis...

Hi, piranna wrote: > > Quoting http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI: > > "The additional isohybrid feature for UEFI adds a partition to the MBR > > partition table pointing to the same file in the ISO 9660 filesystem > > as does the El Torito catalog entry for EFI." Ady wrote: > IMHO, the current content of the Isohybrid page in the Syslinux

...t + # partition. We can't be sure which device is the boot device, so we just + # check them all. + foreach my $device ($g->list_devices()) { + my $guid = eval { $g->part_get_gpt_type($device, 1) }; + next unless defined($guid); + + if ($guid eq 'C12A7328-F81F-11D2-BA4B-00A0C93EC93B') { + $self->convert_efi($device); + last; + } + } +} + + +# Methods for inspecting and manipulating grub legacy +package Sys::VirtConvert::Converter::SUSE::GrubLegacy; + +use Sys::VirtConvert::Util; + +use File::Basename; +use Locale::T...

...t + # partition. We can't be sure which device is the boot device, so we just + # check them all. + foreach my $device ($g->list_devices()) { + my $guid = eval { $g->part_get_gpt_type($device, 1) }; + next unless defined($guid); + + if ($guid eq 'C12A7328-F81F-11D2-BA4B-00A0C93EC93B') { + $self->convert_efi($device); + last; + } + } +} + + +# Methods for inspecting and manipulating grub legacy +package Sys::VirtConvert::Converter::Linux::GrubLegacy; + +use Sys::VirtConvert::Util; + +use File::Basename; +use Locale::...

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