-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
rhel-8.3.0
-
None
-
Moderate
-
rhel-virt-tools
-
ssg_virtualization
-
5
-
False
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
Unspecified
-
None
Description of problem:
virt-v2v cannot use parameter --mac to specify guest's ip
Version-Release number of selected component (if applicable):
Version-Release number of selected component (if applicable):
virt-v2v-1.42.0-5.module+el8.3.0+7152+ab3787c3.x86_64
libguestfs-1.42.0-2.module+el8.3.0+6798+ad6e66be.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Check the --mac info from virt-v2v man page:
--mac aa:bb:cc:dd:ee:ff:ip:ipaddr[,gw[,len[,ns,ns,...]]]
Force a particular interface (controlled by its MAC address) to have a static IP address after boot.
The fields in the parameter are: "ipaddr" is the IP address. "gw" is the optional gateway IP address. "len" is the subnet mask length (an
integer). The final parameters are zero or more nameserver IP addresses.
2.Prepare a windows guest which dhcp client is disabled in VMWARE
3.Use virt-v2v to convert the guest to rhv
- virt-v2v -ic vpx://root@10.73.198.169/data/10.73.199.217/?no_verify=1 esx7.0-win2019-no-dhcp -o rhv-upload -os nfs_data -of raw -b ovirtmgmt -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 -oc https://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -oo rhv-cluster=Default -oo rhv-direct -ip /home/passwd -oo rhv-verifypeer=true -oo rhv-cafile=/home/ca.pem --mac 00:50:56:83:fe:60:ip:10.66.147.202,10.66.147.254,24
[ 0.9] Opening the source -i libvirt -ic vpx://root@10.73.198.169/data/10.73.199.217/?no_verify=1 esx7.0-win2019-no-dhcp -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78
[ 2.5] Creating an overlay to protect the source from being modified
[ 5.8] Opening the overlay
[ 14.8] Inspecting the overlay
[ 21.3] Checking for sufficient free disk space in the guest
[ 21.3] Estimating space required on target for each disk
[ 21.3] Converting Windows Server 2019 Standard to run on KVM
virt-v2v: warning: /usr/share/virt-tools/pnp_wait.exe is missing.
Firstboot scripts may conflict with PnP.
virt-v2v: warning: there is no QXL driver for this version of Windows (10.0
x86_64). virt-v2v looks for this driver in
/usr/share/virtio-win/virtio-win.iso
The guest will be configured to use a basic VGA display driver.
virt-v2v: This guest has virtio drivers installed.
[ 37.1] Mapping filesystem data to avoid copying unused and blank areas
[ 38.2] Closing the overlay
[ 38.5] Assigning disks to buses
[ 38.5] Checking if the guest needs BIOS or UEFI to boot
[ 38.5] Initializing the target -o rhv-upload -oc https://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data
[ 39.8] Copying disk 1/1 to qemu URI json:
(raw)
(100.00/100%)
[1720.8] Creating output metadata
[1722.4] Finishing off
4.After conversion finished successfully,boot the guest in rhv and check the ip info.
4.1 There is an error info in C:\Program Files\Guestfs\Firstboot\log.txt,pls see screenshot
4.2 Guest's ip is not specified
Actual results:
As above
Expected results:
virt-v2v can specify guest's ip when use --mac
Additional info:
- external trackers