Bug 1213324
| Summary: | virt-v2v: warning: unknown guest operating system: windows windows 6.3 when converting win8,win8.1,win2012,win2012R2,win10 to rhev | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | tingting zheng <tzheng> | ||||||||
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 7.2 | CC: | juzhou, mxie, mzhan, ptoscano, rjones, shavivi, xiaodwan | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | V2V | ||||||||||
| Fixed In Version: | libguestfs-1.32.2-5.el7 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2016-11-03 17:50:00 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: | |||||||||||
| Bug Depends On: | 1190669 | ||||||||||
| Bug Blocks: | |||||||||||
| Attachments: |
|
||||||||||
The warning about the NFS server is the same as: https://bugzilla.redhat.com/show_bug.cgi?id=1143887#c15 The warning virt-v2v: warning: unknown guest operating system: windows windows 6.3 (Windows Server 2012 R2 Standard) is wrong and only happens because the output is RHEV (I didn't test Windows >= 8 output to RHEV). I will fix that soon. Upstream fix: https://github.com/libguestfs/libguestfs/commit/3c51302d691cc204e4d43f4ab9837095d424bf3b Tested with: virt-v2v-1.28.1-1.28.el7.x86_64 libguestfs-1.28.1-1.28.el7.x86_64 When converting these windows guest to rhev,there is no such warning shows as description:virt-v2v: warning: unknown guest operating system: windows windows 6.3 (Windows Server 2012 R2 Standard) Refer to the above comments,change the bug to VERIFIED. The commit doesn't send the correct OS description for Windows 2012 R2. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1219857#c9 Therefore moving back to ASSIGNED. Upstream fix: https://github.com/libguestfs/libguestfs/commit/6f9d5dce47f8502bee5d7285faf7695b22b5300b Problem description:
virt-v2v: warning: unknown guest operating system: windows windows 6.3 when converting win8.1 x86 to rhev
Test with builds:
virt-v2v-1.32.2-3.el7.x86_64
libguestfs-1.32.2-3.el7.x86_64
RHEVM3.6:3.6.2.6-0.1.el6
Steps:
1..Use virt-v2v to convert it to rhev,warning shows as below:
virt-v2v: warning: unknown guest operating system: windows windows 6.3
(Windows 8.1 Enterprise)
# virt-v2v -o rhev -os 10.73.69.63:/home/nfs_export -n ovirtmgmt -b ovirtmgmt esx5.1-win8.1-i386 -of raw -on win8.1-i386-rhev
[ 0.0] Opening the source -i libvirt esx5.1-win8.1-i386
[ 0.0] Creating an overlay to protect the source from being modified
[ 0.4] Initializing the target -o rhev -os 10.73.69.63:/home/nfs_export
[ 0.7] Opening the overlay
[ 5.2] Inspecting the overlay
[ 6.8] Checking for sufficient free disk space in the guest
[ 6.8] Estimating space required on target for each disk
[ 6.8] Converting Windows 8.1 Enterprise to run on KVM
virt-v2v: warning: there is no QXL driver for this version of Windows (6.3
i386). virt-v2v looks for this driver in /usr/share/virtio-win
The guest will be configured to use standard VGA.
virt-v2v: This guest has virtio drivers installed.
[ 8.6] Mapping filesystem data to avoid copying unused and blank areas
[ 9.0] Closing the overlay
[ 9.1] Checking if the guest needs BIOS or UEFI to boot
[ 9.1] Assigning disks to buses
[ 9.1] Copying disk 1/1 to /tmp/v2v.bUgej1/d5b21b75-57d6-4b1a-bd40-e949232067df/images/4eacfd4d-2ed0-483a-84c1-4a6a4ff407da/a0c38d5e-93c3-40f9-9fa3-aca7f6540b82 (raw)
(100.00/100%)
[ 261.2] Creating output metadata
virt-v2v: warning: unknown guest operating system: windows windows 6.3
(Windows 8.1 Enterprise)
[ 261.6] Finishing off
2.After conversion, import guest from export domain to data domain,check OS name of win8.1 x86 guest in general info, it shows "other OS"
Test bug with builds: virt-v2v-1.32.2-3.el7.x86_64 libguestfs-1.32.2-3.el7.x86_64 RHEVM3.6:3.6.2.6-0.1.el6 Host:3.10.0-349.el7.x86_64 Result now: 1.As comment 10, win8.1 x86 still has virt-v2v: warning: unknown guest operating system: windows windows 6.3 (Windows 8.1 Enterprise) when converting to rhev.Details please refer to attachment "log_win8.1_x86_rhev " 2.Win10 x86 and win10 x64 both have virt-v2v: warning: unknown guest operating system: windows windows 6.3 (Windows 8.1 Enterprise) when converting to rhev.Details please refer to attachment "log_win10_x64_rhev " 3.Win8.1 x64, win8 x86, win8 x64,win2012,win2012r2 have no virt-v2v warning like " unknown guest operating system: windows windows 6.3 " when converting to rhev. Created attachment 1128161 [details]
log_win8.1_x86_rhev
Created attachment 1128162 [details]
log_win10_x64_rhev
(In reply to mxie from comment #11) > Test bug with builds: > virt-v2v-1.32.2-3.el7.x86_64 > libguestfs-1.32.2-3.el7.x86_64 > RHEVM3.6:3.6.2.6-0.1.el6 > Host:3.10.0-349.el7.x86_64 > > Result now: > 1.As comment 10, win8.1 x86 still has virt-v2v: warning: unknown guest > operating system: windows windows 6.3 (Windows 8.1 Enterprise) when > converting to rhev.Details please refer to attachment "log_win8.1_x86_rhev " RHEV doesn't have a mapping for Windows 8.1 32 bit (only for Windows 8.0 32 bit), so I suppose this is a bug in RHEV. Shahar: What do you think about this? > 2.Win10 x86 and win10 x64 both have virt-v2v: warning: unknown guest > operating system: windows windows 6.3 (Windows 8.1 Enterprise) when > converting to rhev.Details please refer to attachment "log_win10_x64_rhev " The warning is actually: virt-v2v: warning: unknown guest operating system: windows windows 10.0 I have fixed this upstream in: https://github.com/libguestfs/libguestfs/commit/d87c6fd6f206d4749f32ebcb821bbe3e423895ff so I'll add that fix to the next virt-v2v build. Refer to comment 11 and 14,move this bug to ASSIGNED. Same as bz 1309580 in comment #4. Upstream commit is cbf0714e0745af18a27d8ac2dc72689a8cb296e4 Verify bug with builds:
virt-v2v-1.32.2-5.el7.x86_64
libguestfs-1.32.2-5.el7.x86_64
virtio-win-1.8.0-4.el7.noarch
RHEVM3.6:3.6.2.6-0.1.el6
Host:3.10.0-350.el7.x86_64
Result now:
1.win8.1 x86 guest have no virt-v2v: warning: unknown guest operating system: windows windows 6.3 (Windows 8.1 Enterprise) when converting to rhev
# virt-v2v -o rhev -os 10.73.69.63:/home/nfs_export -n ovirtmgmt -b ovirtmgmt esx5.1-win8.1-i386 -on win8.1-x86-new -of raw
[ 0.0] Opening the source -i libvirt esx5.1-win8.1-i386
[ 0.0] Creating an overlay to protect the source from being modified
[ 0.3] Initializing the target -o rhev -os 10.73.69.63:/home/nfs_export
[ 0.5] Opening the overlay
[ 5.3] Inspecting the overlay
[ 6.2] Checking for sufficient free disk space in the guest
[ 6.2] Estimating space required on target for each disk
[ 6.2] Converting Windows 8.1 Enterprise to run on KVM
virt-v2v: warning: there is no QXL driver for this version of Windows (6.3
i386). virt-v2v looks for this driver in /usr/share/virtio-win
The guest will be configured to use standard VGA.
virt-v2v: This guest has virtio drivers installed.
[ 7.3] Mapping filesystem data to avoid copying unused and blank areas
[ 7.6] Closing the overlay
[ 7.9] Checking if the guest needs BIOS or UEFI to boot
[ 7.9] Assigning disks to buses
[ 7.9] Copying disk 1/1 to /tmp/v2v.NuH29h/d5b21b75-57d6-4b1a-bd40-e949232067df/images/38c13ef6-36a0-47d9-b58f-51af7529e654/e25dd281-1449-4f96-885f-742204c1e5c6 (raw)
(100.00/100%)
[ 189.5] Creating output metadata
[ 189.7] Finishing off
2.Both Win10 x86 guest and win10 x64 guest have no virt-v2v: warning: unknown guest operating system: windows windows 10.0 when converting to rhev
# virt-v2v -o rhev -os 10.73.69.63:/home/nfs_export -n ovirtmgmt -b ovirtmgmt esx5.1-win10-x86_64 -on win10-x64-new -of raw
[ 0.0] Opening the source -i libvirt esx5.1-win10-x86_64
[ 0.0] Creating an overlay to protect the source from being modified
[ 0.4] Initializing the target -o rhev -os 10.73.69.63:/home/nfs_export
[ 0.6] Opening the overlay
[ 5.0] Inspecting the overlay
[ 6.6] Checking for sufficient free disk space in the guest
[ 6.6] Estimating space required on target for each disk
[ 6.6] Converting Windows 10 Enterprise 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
The guest will be configured to use standard VGA.
virt-v2v: This guest has virtio drivers installed.
[ 8.9] Mapping filesystem data to avoid copying unused and blank areas
[ 9.4] Closing the overlay
[ 9.7] Checking if the guest needs BIOS or UEFI to boot
[ 9.7] Assigning disks to buses
[ 9.7] Copying disk 1/1 to /tmp/v2v.PmPb6f/d5b21b75-57d6-4b1a-bd40-e949232067df/images/5fd20161-5208-4d7b-968f-4c8b2f3890a7/244668e2-6f91-4138-9814-9847b3709fbe (raw)
(100.00/100%)
[ 621.0] Creating output metadata
[ 621.5] Finishing off
# virt-v2v -ic vpx://root.4.103/tzheng-demo/10.66.106.63/?no_verify=1 -b virbr0 esx5.5-win10-i386 -on win10-x86-new -of raw --password-file /tmp/passwd -o rhev -os 10.73.69.63:/home/nfs_export -b ovirtmgmt -n ovirtmgmt
[ 0.0] Opening the source -i libvirt -ic vpx://root.4.103/tzheng-demo/10.66.106.63/?no_verify=1 esx5.5-win10-i386
[ 1.1] Creating an overlay to protect the source from being modified
[ 1.8] Initializing the target -o rhev -os 10.73.69.63:/home/nfs_export
[ 2.2] Opening the overlay
[ 13.2] Inspecting the overlay
[ 81.8] Checking for sufficient free disk space in the guest
[ 81.8] Estimating space required on target for each disk
[ 81.8] Converting Windows 10 Enterprise to run on KVM
virt-v2v: warning: there is no QXL driver for this version of Windows (10.0
i386). virt-v2v looks for this driver in /usr/share/virtio-win
The guest will be configured to use standard VGA.
virt-v2v: This guest has virtio drivers installed.
[ 98.1] Mapping filesystem data to avoid copying unused and blank areas
[ 98.8] Closing the overlay
[ 98.9] Checking if the guest needs BIOS or UEFI to boot
[ 98.9] Assigning disks to buses
[ 98.9] Copying disk 1/1 to /tmp/v2v.UJ8weB/d5b21b75-57d6-4b1a-bd40-e949232067df/images/fe001baf-9dbd-4ff3-a1be-8b9a5f6f1834/45c44383-b096-49c3-9ddb-34131624d670 (raw)
(100.00/100%)
[1118.3] Creating output metadata
[1118.7] Finishing off
Verify the bug with builds: virt-v2v-1.32.5-10.el7.x86_64 libguestfs-1.32.5-10.el7.x86_64 qemu-kvm-1.5.3-116.el7.x86_64 libvirt-2.0.0-1.el7.x86_64 virtio-win-1.8.0-5.el7.noarch libguestfs-winsupport-7.2-1.el7.x86_64 Steps: 1.Convert win8 x64/x86 guests to rhev, the warning shows as below virt-v2v: warning: there is no QXL driver for this version of Windows (6.2 i386). virt-v2v looks for this driver in /usr/share/virtio-win 2.Convert win2012 guests to rhev, the warning shows as below virt-v2v: warning: there is no QXL driver for this version of Windows (6.2 i386). virt-v2v looks for this driver in /usr/share/virtio-win 3.Convert win8.1 x64/x86 guests to rhev, the warning shows as below virt-v2v: warning: there is no QXL driver for this version of Windows (6.3 i386). virt-v2v looks for this driver in /usr/share/virtio-win 4.Convert win2012r2 guest to rhev, the warning shows as below virt-v2v: warning: there is no QXL driver for this version of Windows (6.3 x86_64). virt-v2v looks for this driver in /usr/share/virtio-win 5.Convert win10 x86/x64 guests to rhev, the warning shows as below 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 Result now: Above step's warning show correct, so 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 1016313 [details] log file for converting win8.1 to rhev. Description of problem: Warning shows when convert win8,win8.1,win2012,win2012R2 to rhev Version-Release number of selected component (if applicable): libguestfs-1.28.1-1.25.el7.x86_64 virt-v2v-1.28.1-1.25.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Prepare a win8,win8.1,win2012,win2012R2 guest on xen or esx server. 2.Use virt-v2v to convert it to rhev,warning shows as below: virt-v2v: warning: unknown guest operating system: windows windows 6.2 (Windows 8 Enterprise) # virt-v2v -ic xen+ssh://10.66.106.64 -o rhev -os 10.66.90.115:/vol/v2v_auto/iscsi_export -n rhevm xen-hvm-win8-x86_64 -of raw [ 0.0] Opening the source -i libvirt -ic xen+ssh://10.66.106.64 xen-hvm-win8-x86_64 [ 1.0] Creating an overlay to protect the source from being modified [ 1.0] Opening the overlay [ 9.0] Initializing the target -o rhev -os 10.66.90.115:/vol/v2v_auto/iscsi_export virt-v2v: warning: cannot write files to the NFS server as 36:36, even though we appear to be running as root. This probably means the NFS client or idmapd is not configured properly. You will have to chown the files that virt-v2v creates after the run, otherwise RHEV-M will not be able to import the VM. [ 9.0] Inspecting the overlay [ 14.0] Checking for sufficient free disk space in the guest [ 14.0] Estimating space required on target for each disk [ 14.0] Converting Windows 8 Enterprise to run on KVM virt-v2v: This guest has virtio drivers installed. [ 16.0] Mapping filesystem data to avoid copying unused and blank areas [ 17.0] Closing the overlay [ 18.0] Copying disk 1/1 to /tmp/v2v.4HzmF5/f6d2eaca-b8b0-45ec-ace7-e947a7c0d150/images/205ec09e-4e2c-4e2d-b566-c08ded1d04af/44b7b34c-651a-481f-b4ac-b270bb704519 (raw) (100.00/100%) [ 377.0] Creating output metadata virt-v2v: warning: unknown guest operating system: windows windows 6.2 (Windows 8 Enterprise) [ 377.0] Finishing off Actual results: As description. Expected results: No such warning shows. Additional info: For win8.1 and win2012R2 guest,the below waring info shows. virt-v2v: warning: unknown guest operating system: windows windows 6.3 (Windows 8.1 Enterprise) [ 607.0] Finishing off umount '/tmp/v2v.VHJa20' virt-v2v: warning: unknown guest operating system: windows windows 6.3 (Windows Server 2012 R2 Standard)