Bug 1566298
| Summary: | [virtio-win][viostor] unattended installation failure on unpartitioned image when using virtio_blk | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Yu Wang <wyu> | ||||||||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||||||
| virtio-win sub component: | virtio-win-prewhql | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||||||||
| Severity: | high | ||||||||||||
| Priority: | high | CC: | ailan, aliang, coli, lijin, phou, siliu, vrozenfe, wyu, xiagao, xuwei, yfu | ||||||||||
| Version: | 7.6 | Keywords: | Regression | ||||||||||
| Target Milestone: | rc | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
| Doc Text: |
NO_DOCS
|
Story Points: | --- | ||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2018-10-30 16:21:50 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
Yu Wang
2018-04-12 02:00:52 UTC
Created attachment 1422948 [details]
screenshot_win2008_auto_manual
When installing guest with win2008, hit similar error with win7.
Manual installing:
It shows "Windows cannot be installed to this hard disk space. Windows must be installed to a partition formatted as NTFS"
Automation:
Windows could not create a partition on disk 0.
Error code:0x80300025
More info refer to these attachments:
Screenshot-win2008-64-manual for manual
Screenshot-win2008-auto for automation
(In reply to Yu Wang from comment #5) > Created attachment 1422948 [details] > screenshot_win2008_auto_manual > > When installing guest with win2008, hit similar error with win7. > > Manual installing: > It shows "Windows cannot be installed to this hard disk space. Windows must > be installed to a partition formatted as NTFS" > > Automation: > Windows could not create a partition on disk 0. > Error code:0x80300025 win2008-32 vioscsi hit the same code but with much lower reproduce percentage(not stable reproduced and not regression). (In reply to Yu Wang from comment #5) > Created attachment 1422948 [details] > screenshot_win2008_auto_manual > > When installing guest with win2008, hit similar error with win7. > > Manual installing: > It shows "Windows cannot be installed to this hard disk space. Windows must > be installed to a partition formatted as NTFS" > > Automation: > Windows could not create a partition on disk 0. > Error code:0x80300025 > > More info refer to these attachments: > Screenshot-win2008-64-manual for manual > Screenshot-win2008-auto for automation I wonder if adding serial number to "-device virtio-blk-pci," makes any difference. Apart from that, for manual install do you use the same qemu cli as mentioned in the bug's description? I'm going to try reproducing the problem on my local setup. Thanks, Vadim. (In reply to Vadim Rozenfeld from comment #7) > (In reply to Yu Wang from comment #5) > > Created attachment 1422948 [details] > > screenshot_win2008_auto_manual > > > > When installing guest with win2008, hit similar error with win7. > > > > Manual installing: > > It shows "Windows cannot be installed to this hard disk space. Windows must > > be installed to a partition formatted as NTFS" > > > > Automation: > > Windows could not create a partition on disk 0. > > Error code:0x80300025 > > > > More info refer to these attachments: > > Screenshot-win2008-64-manual for manual > > Screenshot-win2008-auto for automation > > I wonder if adding serial number to "-device virtio-blk-pci," makes any > difference. The same error "Windows must be installed to a partition formatted as NTFS" after adding serial number to device. > Apart from that, for manual install do you use the same qemu cli > as mentioned in the bug's description? I'm going to try reproducing the > problem on my local setup. > Yes, they use the same cli as comment#0 > Thanks, > Vadim. Created attachment 1423923 [details]
create-submission
Hi Vadim, How about this issue? It still block automation test for win2008/win7/win2008R2. (In reply to lijin from comment #22) > Hi Vadim, > How about this issue? > It still block automation test for win2008/win7/win2008R2. Hi Li Jin. Honestly, I was not able to reproduce this problem on my setup to start debugging the problem. (It was just failing with a different problem). Since it is a regression, I was thinking to return the previous code to the drivers prior to Win10 and keep the new code (which fixes Even Id 158 problem) for Windows 10 /WS 2016 only. I should be build such kind of drivers as soon as virtio-win build system will be fixed again. Vadim. Hi, Tried to verify with build153 on win2008-32/64, win7-32/64 and win2008r2 Win2008r2/win2008-32/win7-32/win7-64: no error occurred now when installing guest, but BSOD when the first reboot to the guest after installation, and cannot boot into the guest (refer to attachment) It similar with the bug1568739, but not the same code. win2008-64: still occurred error on win2008-64 as comment#5. Thanks Yu Wang Created attachment 1443099 [details]
bsod-screenshot
(In reply to Yu Wang from comment #25) > Created attachment 1443099 [details] > bsod-screenshot Thanks, I will try to reproduce and trace the problem asap. Vadim. hit the same issue on rhel8 host, tested on win7-64. Used versions: kernel-4.16.0-10.el8+5.x86_64 qemu-kvm-2.12.0-11.el8+619+ba8f0855.1.x86_64 seabios-bin-1.11.0-1.el8+526+412dc3e0.noarch virtio-win-prewhql-153 verify with build155 on win2008-32/64, win7-32/64 and win2008r2 It can be installed successfully, so change status 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://access.redhat.com/errata/RHBA-2018:3413 |