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.
Created attachment 1592530[details]
error message at installation windows setup page
Description of problem:
Run unattended_install win2016 to blockdev format vm failed, with automation test.
When Windows setup phase, hit error message "Windows cannot be installed to this hard disk space, This hard disk space is formatted with an unsupported version of the NTFS file system...", detail please refer to attachment.
And the autounattend.xml also upload as attachment.
system disk commands as follows:
===============================================================================
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \
-blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device scsi-hd,id=image1,drive=drive_image1,write-cache=on \
================================================================================
And if the scsi-hd command with serial=TARGET_DISK0(-device scsi-hd,id=image1,drive=drive_image1,write-cache=on,serial=TARGET_DISK0), cannot reproduced this issue.
Version-Release number of selected component (if applicable):
kernel-4.18.0-116.el8.x86_64
qemu-kvm-4.0.0-4.module+el8.1.0+3356+cda7f1ee.x86_64
seabios-bin-1.12.0-1.module+el8.1.0+3258+4c45705b.noarch
virtio-win-prewhql-172
How reproducible:
100%
Steps to Reproduce:
This issue is hit with automation testing, so here reproduce steps need use /home/kvm_autotest_root/images/win2016-64/autounattend.iso file that generated by automation.
1. Boot a guest up with follows commands:
MALLOC_PERTURB_=1 /usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1' \
-machine pc \
-nodefaults \
-device VGA,bus=pci.0,addr=0x2 \
-device pvpanic,ioport=0x505,id=idAZQztJ \
-device qemu-xhci,id=usb1,bus=pci.0,addr=0x3 \
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \
-blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device scsi-hd,id=image1,drive=drive_image1,write-cache=on \
-device virtio-net-pci,mac=9a:34:0f:74:88:d9,id=idoxrVQT,netdev=idiDQO8f,bus=pci.0,addr=0x5 \
-netdev tap,id=idiDQO8f,vhost=on,vhostfd=22,fd=19 \
-m 14336 \
-smp 24,maxcpus=24,cores=12,threads=1,sockets=2 \
-cpu 'Skylake-Server',hv_stimer,hv_synic,hv_vpindex,hv_reset,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv-tlbflush,+kvm_pv_unhalt \
-blockdev node-name=file_cd1,driver=file,read-only=on,filename=/home/kvm_autotest_root/iso/ISO/Win2016/en_windows_server_2016_updated_feb_2018_x64_dvd_11636692.iso,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_cd1,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_cd1 \
-device ide-cd,id=cd1,drive=drive_cd1,write-cache=on,bus=ide.0,unit=0 \
-blockdev node-name=file_winutils,driver=file,read-only=on,filename=/home/kvm_autotest_root/iso/windows/winutils.iso,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_winutils,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_winutils \
-device ide-cd,id=winutils,drive=drive_winutils,write-cache=on,bus=ide.0,unit=1 \
-blockdev node-name=file_unattended,driver=file,read-only=on,filename=/home/kvm_autotest_root/images/win2016-64/autounattend.iso,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_unattended,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_unattended \
-device ide-cd,id=unattended,drive=drive_unattended,write-cache=on,bus=ide.1,unit=0 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-vnc :0 \
-rtc base=localtime,clock=host,driftfix=slew \
-boot order=cdn,once=d,menu=off,strict=off \
-enable-kvm
2. The guest will start install os automatically due to attach autounattend.iso, check the guest os install status. --> message "Windows cannot be installed to this hard disk space, This hard disk space is formatted with an unsupported version of the NTFS file system..."
3.
Actual results:
Error
Expected results:
Install successfully
Additional info:
1. Reproduced this issue without serial=TARGET_DISK0 on scsi-hd.
================================================================================
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \
-blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device scsi-hd,id=image1,drive=drive_image1,write-cache=on
2. Cannot reproduce this issue with serial=TARGET_DISK0 on scsi-hd.
================================================================================
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \
-blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device scsi-hd,id=image1,drive=drive_image1,write-cache=on,serial=TARGET_DISK0
3. Cannot reproduce this issue with drive format.
================================================================================
-device virtio-scsi-pci,id=virtio_scsi_pci0,num_queues=12,bus=pcie.0-root-port-3,addr=0x0 \
-drive id=drive_image1,if=none,snapshot=off,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2 \
-device scsi-hd,id=image1,drive=drive_image1 \
4. Cannot reproduce his issue with ide system image.
================================================================================
-blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device ide-hd,id=image1,drive=drive_image1,write-cache=on,bus=ide.0,unit=0 \
5. Cannot reproduce this issue with virtio-blk system image.
================================================================================
-blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64-virtio.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,bus=pci.0,addr=0x4 \
Created attachment 1592531[details]
autounattend.xml file
<ModifyPartition wcm:action="add"> not exist this item
<Order>2</Order>
<PartitionID>2</PartitionID>
<Label>Windows</Label>
<Letter>C</Letter>
<Format>NTFS</Format>
</ModifyPartition>
Retested with deleted these lines, the installation can be successfully althrough scsi-hd without serial=TARGET_DISK0.
Also hit this issue on win8-32, win2012-64 and win2012-r2 guest vm, tested on rhel8.2.0 host.
Used versions:
virtio-win-prewhql-180
kernel-4.18.0-179.el8.x86_64
qemu-kvm-4.2.0-10.module+el8.2.0+5740+c3dff59e.x86_64
seabios-1.13.0-1.module+el8.2.0+5520+4e5817f3.x86_64
Best Regards~
Peixiu
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://access.redhat.com/errata/RHEA-2020:3055
Created attachment 1592530 [details] error message at installation windows setup page Description of problem: Run unattended_install win2016 to blockdev format vm failed, with automation test. When Windows setup phase, hit error message "Windows cannot be installed to this hard disk space, This hard disk space is formatted with an unsupported version of the NTFS file system...", detail please refer to attachment. And the autounattend.xml also upload as attachment. system disk commands as follows: =============================================================================== -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \ -blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \ -device scsi-hd,id=image1,drive=drive_image1,write-cache=on \ ================================================================================ And if the scsi-hd command with serial=TARGET_DISK0(-device scsi-hd,id=image1,drive=drive_image1,write-cache=on,serial=TARGET_DISK0), cannot reproduced this issue. Version-Release number of selected component (if applicable): kernel-4.18.0-116.el8.x86_64 qemu-kvm-4.0.0-4.module+el8.1.0+3356+cda7f1ee.x86_64 seabios-bin-1.12.0-1.module+el8.1.0+3258+4c45705b.noarch virtio-win-prewhql-172 How reproducible: 100% Steps to Reproduce: This issue is hit with automation testing, so here reproduce steps need use /home/kvm_autotest_root/images/win2016-64/autounattend.iso file that generated by automation. 1. Boot a guest up with follows commands: MALLOC_PERTURB_=1 /usr/libexec/qemu-kvm \ -name 'avocado-vt-vm1' \ -machine pc \ -nodefaults \ -device VGA,bus=pci.0,addr=0x2 \ -device pvpanic,ioport=0x505,id=idAZQztJ \ -device qemu-xhci,id=usb1,bus=pci.0,addr=0x3 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \ -blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \ -device scsi-hd,id=image1,drive=drive_image1,write-cache=on \ -device virtio-net-pci,mac=9a:34:0f:74:88:d9,id=idoxrVQT,netdev=idiDQO8f,bus=pci.0,addr=0x5 \ -netdev tap,id=idiDQO8f,vhost=on,vhostfd=22,fd=19 \ -m 14336 \ -smp 24,maxcpus=24,cores=12,threads=1,sockets=2 \ -cpu 'Skylake-Server',hv_stimer,hv_synic,hv_vpindex,hv_reset,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv-tlbflush,+kvm_pv_unhalt \ -blockdev node-name=file_cd1,driver=file,read-only=on,filename=/home/kvm_autotest_root/iso/ISO/Win2016/en_windows_server_2016_updated_feb_2018_x64_dvd_11636692.iso,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_cd1,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_cd1 \ -device ide-cd,id=cd1,drive=drive_cd1,write-cache=on,bus=ide.0,unit=0 \ -blockdev node-name=file_winutils,driver=file,read-only=on,filename=/home/kvm_autotest_root/iso/windows/winutils.iso,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_winutils,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_winutils \ -device ide-cd,id=winutils,drive=drive_winutils,write-cache=on,bus=ide.0,unit=1 \ -blockdev node-name=file_unattended,driver=file,read-only=on,filename=/home/kvm_autotest_root/images/win2016-64/autounattend.iso,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_unattended,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_unattended \ -device ide-cd,id=unattended,drive=drive_unattended,write-cache=on,bus=ide.1,unit=0 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -vnc :0 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot order=cdn,once=d,menu=off,strict=off \ -enable-kvm 2. The guest will start install os automatically due to attach autounattend.iso, check the guest os install status. --> message "Windows cannot be installed to this hard disk space, This hard disk space is formatted with an unsupported version of the NTFS file system..." 3. Actual results: Error Expected results: Install successfully Additional info: 1. Reproduced this issue without serial=TARGET_DISK0 on scsi-hd. ================================================================================ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \ -blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \ -device scsi-hd,id=image1,drive=drive_image1,write-cache=on 2. Cannot reproduce this issue with serial=TARGET_DISK0 on scsi-hd. ================================================================================ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \ -blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \ -device scsi-hd,id=image1,drive=drive_image1,write-cache=on,serial=TARGET_DISK0 3. Cannot reproduce this issue with drive format. ================================================================================ -device virtio-scsi-pci,id=virtio_scsi_pci0,num_queues=12,bus=pcie.0-root-port-3,addr=0x0 \ -drive id=drive_image1,if=none,snapshot=off,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2 \ -device scsi-hd,id=image1,drive=drive_image1 \ 4. Cannot reproduce his issue with ide system image. ================================================================================ -blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64.qcow2,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \ -device ide-hd,id=image1,drive=drive_image1,write-cache=on,bus=ide.0,unit=0 \ 5. Cannot reproduce this issue with virtio-blk system image. ================================================================================ -blockdev node-name=file_image1,driver=file,filename=/home/kvm_autotest_root/images/win2016-64-virtio.qcow2,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \ -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,bus=pci.0,addr=0x4 \