Bug 1995000 - virt-v2v can't convert bitblocker windows guest with libguestfs error: /dev/mapper/cryptsda: No such file or directory
Summary: virt-v2v can't convert bitblocker windows guest with libguestfs error: /dev/m...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: virt-v2v
Version: 8.5
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.5
Assignee: Richard W.M. Jones
QA Contact: mxie@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-18 09:29 UTC by mxie@redhat.com
Modified: 2021-11-16 08:58 UTC (History)
11 users (show)

Fixed In Version: virt-v2v-1.42.0-15.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 07:55:27 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
windows-bitlocker-rhel8.5av-v2v.log (2.24 MB, text/plain)
2021-08-18 09:29 UTC, mxie@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-93939 0 None None None 2021-08-18 09:30:49 UTC
Red Hat Product Errata RHBA-2021:4684 0 None None None 2021-11-16 07:57:17 UTC

Description mxie@redhat.com 2021-08-18 09:29:05 UTC
Created attachment 1815121 [details]
windows-bitlocker-rhel8.5av-v2v.log

Description of problem:
virt-v2v can't convert bitblocker windows guest with libguestfs error: /dev/mapper/cryptsda: No such file or directory

Version-Release number of selected component (if applicable):
virt-v2v-1.42.0-14.module+el8.5.0+11846+77888a74.x86_64
libguestfs-1.44.0-3.module+el8.5.0+10681+17a9b157.x86_64
libvirt-libs-7.6.0-2.module+el8.5.0+12219+a5ea13d2.x86_64
qemu-img-6.0.0-27.module+el8.5.0+12121+c40c8708.x86_64
nbdkit-1.24.0-1.module+el8.4.0+9341+96cf2672.x86_64


How reproducible:
100%

Steps to Reproduce:
1.Prepare a windows guest whose disk is encrypted by Bitblocker on VMware, then convert the guest from VMware to rhv4.4 by v2v
#  virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0 -io  vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 -ip /home/passwd -o rhv-upload -of qcow2 -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd  -os nfs_data -b ovirtmgmt esx7.0-win2019-ntfs-3g-bitblocker --key "/dev/sda2":file:windows-key 
[   1.0] Opening the source -i libvirt -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 esx7.0-win2019-ntfs-3g-bitblocker -it vddk  -io vddk-libdir=/home/vddk7.0 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78
[   4.1] Creating an overlay to protect the source from being modified
[   6.0] Opening the overlay
[  15.9] Inspecting the overlay
[  24.1] Checking for sufficient free disk space in the guest
[  24.1] Converting Windows Server 2019 Standard to run on KVM
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: error: libguestfs error: blockdev_getsize64: 
blockdev_getsize64_stub: /dev/mapper/cryptsda: No such file or directory

If reporting bugs, run virt-v2v with debugging enabled and include the 
complete output:

  virt-v2v -v -x [...]



Actual results:
As above description


Expected results:
Virt-v2v should can convert windows BitLocker guest since bug1808977 has been fixed


Additional info:

Comment 4 mxie@redhat.com 2021-08-19 09:46:28 UTC
Verify the bug with below builds:
virt-v2v-1.42.0-15.module+el8.5.0+12264+1ee0d523.x86_64
libguestfs-1.44.0-3.module+el8.5.0+10681+17a9b157.x86_64
libvirt-libs-7.6.0-2.module+el8.5.0+12219+a5ea13d2.x86_64
qemu-img-6.0.0-28.module+el8.5.0+12271+fffa967b.x86_64
nbdkit-1.24.0-1.module+el8.4.0+9341+96cf2672.x86_64
virtio-win-1.9.17-4.el8_4.noarch


Steps:
1.Prepare a windows guest whose disk is encrypted by Bitblocker on VMware, then convert the guest from VMware to local libvirt by v2v

# virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk6.7 -io  vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 -ip /home/passwd esx7.0-win2019-ntfs-3g-bitblocker --key "/dev/sda2":file:windows-key 
[   0.0] Opening the source -i libvirt -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 esx7.0-win2019-ntfs-3g-bitblocker -it vddk  -io vddk-libdir=/home/vddk6.7 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78
[   1.8] Creating an overlay to protect the source from being modified
[   2.5] Opening the overlay
[  17.4] Inspecting the overlay
[  23.8] Checking for sufficient free disk space in the guest
[  23.8] Estimating space required on target for each disk
[  23.8] Converting Windows Server 2019 Standard to run on KVM
virt-v2v: warning: this guest has Windows Group Policy Objects (GPO) and a 
new virtio block device driver was installed.  In some circumstances, Group 
Policy may prevent new drivers from working (resulting in a 7B boot error). 
 If this happens, try disabling Group Policy before doing the conversion.
virt-v2v: This guest has virtio drivers installed.
[  48.8] Mapping filesystem data to avoid copying unused and blank areas
virt-v2v: warning: fstrim on guest filesystem /dev/mapper/cryptsda2 failed. 
 Usually you can ignore this message.  To find out more read "Trimming" in 
virt-v2v(1).

Original message: fstrim: fstrim: /sysroot/: the discard operation is not 
supported
[  49.7] Closing the overlay
[  50.1] Assigning disks to buses
[  50.1] Checking if the guest needs BIOS or UEFI to boot
[  50.1] Initializing the target -o libvirt -os default
[  50.1] Copying disk 1/1 to /var/lib/libvirt/images/esx7.0-win2019-ntfs-3g-bitblocker-sda (raw)
    (100.00/100%)
[ 409.0] Creating output metadata
[ 409.1] Finishing off


2.Check guest after v2v finishing conversion, checkpoints of guest are passed


Result:
   Virt-v2v can convert windows BitLocker guest now, move the bug from ON_QA to VERIFIED

Comment 6 errata-xmlrpc 2021-11-16 07:55:27 UTC
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 (virt:av bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2021:4684


Note You need to log in before you can comment on or make changes to this bug.