Red Hat Bugzilla – Bug 1341984
virt-get-kernel prompts an 'invalid value' error when using --format auto
Last modified: 2016-11-03 14:00:48 EDT
Description of problem: virt-get-kernel prompts an 'invalid value' error when using --format auto. Version-Release number of selected component (if applicable): libguestfs-1.32.4-3.el7.aarch64 libguestfs-tools-c-1.32.4-3.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Prepare an rhel7 image: rhel7.1-sr1.qcow2 2. # virt-get-kernel --add rhel7.1-sr1.qcow2 --format auto -v -x libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: trace: add_drive "/home/xchen/my-images/rhel7.1-sr1.qcow2" "readonly:true" "format:auto" "protocol:file" libguestfs: creating COW overlay to protect original drive content libguestfs: trace: get_tmpdir libguestfs: trace: get_tmpdir = "/tmp" libguestfs: trace: disk_create "/tmp/libguestfstyNuRg/overlay1" "qcow2" -1 "backingfile:/home/xchen/my-images/rhel7.1-sr1.qcow2" "backingformat:auto" libguestfs: trace: disk_create = -1 (error) libguestfs: trace: add_drive = -1 (error) virt-get-kernel: error: libguestfs error: invalid value for backingformat parameter 'auto' libguestfs: trace: close libguestfs: closing guestfs handle 0x1fc82e0 (state 0) libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfstyNuRg Actual results: virt-get-kernel: error: libguestfs error: invalid value for backingformat parameter 'auto Expected results: virt-get-kernel should auto-detect the format of the disk image and can get kernel and ramdisk from guests successfully. Or,this option should be deleted from man page if it is not actually provided. Additional info:
Fixed upstream with https://github.com/libguestfs/libguestfs/commit/35fa14152245bcae2c0842abf120cd4ec7bd098c which is in libguestfs >= 1.33.36.
Verified with the packages: libguestfs-1.32.5-6.el7.x86_64 Verify steps: 1. Prepare an rhel7 image: RHEL-Server-7.2-64-hvm.raw 2. # virt-get-kernel --add RHEL-Server-7.2-64-hvm.raw --format auto download: /boot/vmlinuz-3.10.0-327.el7.x86_64 -> ./vmlinuz-3.10.0-327.el7.x86_64 download: /boot/initramfs-3.10.0-327.el7.x86_64.img -> ./initramfs-3.10.0-327.el7.x86_64.img It finished successfully. So verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2576.html