Bug 1995000
| Summary: | virt-v2v can't convert bitblocker windows guest with libguestfs error: /dev/mapper/cryptsda: No such file or directory | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | mxie <mxie> | ||||
| Component: | virt-v2v | Assignee: | Richard W.M. Jones <rjones> | ||||
| Status: | CLOSED ERRATA | QA Contact: | mxie <mxie> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 8.5 | CC: | chhu, juzhou, kkiwi, mzhan, rjones, tyan, tzheng, virt-bugs, virt-maint, vwu, xiaodwan | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | 8.5 | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | virt-v2v-1.42.0-15.el8 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-11-16 07:55:27 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
mxie@redhat.com
2021-08-18 09:29:05 UTC
Upstream fix: https://github.com/libguestfs/virt-v2v/commit/0a394c5c2f802098c9e481b4bacee7821e5dd0ae 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
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 |