Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionmxie@redhat.com
2015-11-02 09:24:49 UTC
Created attachment 1088495[details]
screenshot of convert host to vdsm
Description of problem:
Virt-p2v client shouldn't present the vdsm option because it's not usable
Version-Release number of selected component (if applicable):
virt-p2v-1.28.1-1.51.3.el7.1
virt-v2v-1.28.1-1.55.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
# man virt-p2v |grep vdsm
#
There is not any info about vdsm in virt-p2v paper
#man virt-v2v |grep vdsm
-o rhev is used to write to a RHEV-M / oVirt target. -o vdsm is only
-o vdsm
Set the output method to vdsm.
--vdsm-image-uuid UUID
--vdsm-vol-uuid UUID
--vdsm-vm-uuid UUID
--vdsm-ovf-output
· the image directory of each guest disk (--vdsm-image-uuid)
· UUIDs for each guest disk (--vdsm-vol-uuid) (this option is
· the OVF file name (--vdsm-vm-uuid).
(--vdsm-ovf-output).
1. Check rhev Data Center path and mount it to p2v server's local:
Path: 10.66.90.115:/vol/v2v_auto/
# mount 10.66.90.115:/vol/v2v_auto/ /mnt
2.Boot the source machine into virt-p2v client via PXE and input the ip and password of conversion server
3.Try to convert host to vdsm,input name, vcpus, memory and set "-o" as vdsm and "-os" as /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964, please refer to screenshot"convert host to vdsm"
4.It is failed because virt-v2v: error: -o vdsm: --vdsm-image-uuid was not specified, please refer to conversion log "conversion log of vdsm "
Actual results:
As above description
Expected results:
vdsm option shouldn't be presented in virt-p2v client
Addtional info:
If using virt-v2v to convert guests to vdsm, the commands is like below:
# virt-v2v -o vdsm -of raw --vdsm-image-uuid 12345678-1234-1234-1234-123456789001 --vdsm-image-uuid 12345678-1234-1234-1234-123456789003 --vdsm-vol-uuid 12345678-1234-1234-1234-123456789002 --vdsm-vol-uuid 12345678-1234-1234-1234-123456789004 --vdsm-vm-uuid 12345678-1234-1234-1234-123456789005 --vdsm-ovf-output /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/master/vms/12345678-1234-1234-1234-123456789005/ -os /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/ rhel7.2
[ 0.0] Opening the source -i libvirt rhel7.2
[ 0.0] Creating an overlay to protect the source from being modified
[ 0.0] Opening the overlay
[ 5.0] Initializing the target -o vdsm -os /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/ --vdsm-image-uuid 12345678-1234-1234-1234-123456789001 --vdsm-image-uuid 12345678-1234-1234-1234-123456789003 --vdsm-vol-uuid 12345678-1234-1234-1234-123456789002 --vdsm-vol-uuid 12345678-1234-1234-1234-123456789004 --vdsm-vm-uuid 12345678-1234-1234-1234-123456789005 --vdsm-ovf-output /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/master/vms/12345678-1234-1234-1234-123456789005/
[ 5.0] Inspecting the overlay
[ 21.0] Checking for sufficient free disk space in the guest
[ 21.0] Estimating space required on target for each disk
[ 21.0] Converting Red Hat Enterprise Linux Server release 7.2 Beta (Maipo) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 127.0] Mapping filesystem data to avoid copying unused and blank areas
[ 128.0] Closing the overlay
[ 128.0] Checking if the guest needs BIOS or UEFI to boot
[ 128.0] Copying disk 1/2 to /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/images/12345678-1234-1234-1234-123456789001/12345678-1234-1234-1234-123456789002 (raw)
(100.00/100%)
[ 197.0] Copying disk 2/2 to /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/images/12345678-1234-1234-1234-123456789003/12345678-1234-1234-1234-123456789004 (raw)
(100.00/100%)
[ 208.0] Creating output metadata
[ 208.0] Finishing off
I can reproduce it with build:
virt-p2v-1.28.1-1.51.3.el7.1
Verify it with build:
virt-p2v-1.32.4-1.el7
Steps:
1.Check the manual page of virt-p2v
#man virt-p2v | grep -i vdsm
There is not any info about vdsm in virt-p2v paper
2.Boot the source machine into virt-p2v client via PXE and input the correct ip and password of conversion server
3.Go to the next page via click the "next "
4.Check the output option,there is no vdsm option in the "output to" option list
Test Result:
According the testing result, the bug has been fixed
So move the bug from ON_QA to 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
Created attachment 1088495 [details] screenshot of convert host to vdsm Description of problem: Virt-p2v client shouldn't present the vdsm option because it's not usable Version-Release number of selected component (if applicable): virt-p2v-1.28.1-1.51.3.el7.1 virt-v2v-1.28.1-1.55.el7.x86_64 How reproducible: 100% Steps to Reproduce: # man virt-p2v |grep vdsm # There is not any info about vdsm in virt-p2v paper #man virt-v2v |grep vdsm -o rhev is used to write to a RHEV-M / oVirt target. -o vdsm is only -o vdsm Set the output method to vdsm. --vdsm-image-uuid UUID --vdsm-vol-uuid UUID --vdsm-vm-uuid UUID --vdsm-ovf-output · the image directory of each guest disk (--vdsm-image-uuid) · UUIDs for each guest disk (--vdsm-vol-uuid) (this option is · the OVF file name (--vdsm-vm-uuid). (--vdsm-ovf-output). 1. Check rhev Data Center path and mount it to p2v server's local: Path: 10.66.90.115:/vol/v2v_auto/ # mount 10.66.90.115:/vol/v2v_auto/ /mnt 2.Boot the source machine into virt-p2v client via PXE and input the ip and password of conversion server 3.Try to convert host to vdsm,input name, vcpus, memory and set "-o" as vdsm and "-os" as /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964, please refer to screenshot"convert host to vdsm" 4.It is failed because virt-v2v: error: -o vdsm: --vdsm-image-uuid was not specified, please refer to conversion log "conversion log of vdsm " Actual results: As above description Expected results: vdsm option shouldn't be presented in virt-p2v client Addtional info: If using virt-v2v to convert guests to vdsm, the commands is like below: # virt-v2v -o vdsm -of raw --vdsm-image-uuid 12345678-1234-1234-1234-123456789001 --vdsm-image-uuid 12345678-1234-1234-1234-123456789003 --vdsm-vol-uuid 12345678-1234-1234-1234-123456789002 --vdsm-vol-uuid 12345678-1234-1234-1234-123456789004 --vdsm-vm-uuid 12345678-1234-1234-1234-123456789005 --vdsm-ovf-output /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/master/vms/12345678-1234-1234-1234-123456789005/ -os /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/ rhel7.2 [ 0.0] Opening the source -i libvirt rhel7.2 [ 0.0] Creating an overlay to protect the source from being modified [ 0.0] Opening the overlay [ 5.0] Initializing the target -o vdsm -os /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/ --vdsm-image-uuid 12345678-1234-1234-1234-123456789001 --vdsm-image-uuid 12345678-1234-1234-1234-123456789003 --vdsm-vol-uuid 12345678-1234-1234-1234-123456789002 --vdsm-vol-uuid 12345678-1234-1234-1234-123456789004 --vdsm-vm-uuid 12345678-1234-1234-1234-123456789005 --vdsm-ovf-output /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/master/vms/12345678-1234-1234-1234-123456789005/ [ 5.0] Inspecting the overlay [ 21.0] Checking for sufficient free disk space in the guest [ 21.0] Estimating space required on target for each disk [ 21.0] Converting Red Hat Enterprise Linux Server release 7.2 Beta (Maipo) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 127.0] Mapping filesystem data to avoid copying unused and blank areas [ 128.0] Closing the overlay [ 128.0] Checking if the guest needs BIOS or UEFI to boot [ 128.0] Copying disk 1/2 to /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/images/12345678-1234-1234-1234-123456789001/12345678-1234-1234-1234-123456789002 (raw) (100.00/100%) [ 197.0] Copying disk 2/2 to /mnt/auto_export/838c19a0-f0a7-47a0-a57b-cc94cd921964/images/12345678-1234-1234-1234-123456789003/12345678-1234-1234-1234-123456789004 (raw) (100.00/100%) [ 208.0] Creating output metadata [ 208.0] Finishing off