+++ This bug was initially created as a clone of Bug #1232586 +++ add Windows 10 to OS Type selection and a default icon
webadmin > edit VM - Icon tab is missing. screenshot attached. User portal - win10 icon displayed properly for basic/extended tabs. sysprep functionality test - passed. See external trackers for polarion test case. version: rhevm-3.5.5-0.1.el6ev (vt17.3) sanlock-3.2.2-2.el7.x86_64 qemu-kvm-rhev-2.1.2-23.el7_1.1.x86_64 vdsm-4.16.16-1.el7ev.x86_64 libvirt-client-1.2.8-16.el7_1.2.x86_64
Created attachment 1085413 [details] webadmin - missing edit VM > icon tab
moving to 3.5.6, as WGT with win10 support will only be avaliable in 3.5.6
this is UI side It is in 3.5 already, so ON_QA is correct state. For full Windows 10 support take a look at the tracker bug 1232559
moving back to 3.5.5 as the change is in 3.5.5 and we _must_ document it
Reassigned: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED occurs on VM when installing Windows 10 from ISO file (see screenshot attached). UI side for adding Windows 10 and Windows 10 x64 for OS list dropbox fixed. I'm not sure which RHEL version and CPU type should be supported for 3.5.5 environment, but if host CPU model is not supporting Windows 10 guest, it should be derived from operating system selected by the user and reject accordingly by webadmin when trying to run VM. Setup info: engine: RHEL 6.7, rhevm-3.5.5-0.1.el6ev (vt 17.1) Host: CPU type: Vendor ID: GenuineIntel, CPU family: 6, Model: 44 (Intel Nehalem Family) sanlock-2.8-1.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.446.el6.x86_64 libvirt-client-0.10.2-46.el6_6.4.x86_64 vdsm-4.16.13-1.el6ev.x86_64 Verification scenario: 1. Create new VM and set operating system to Windows 10. add IDE disk. 2. Install Windows 10 from ISO file on the VM using run once option. VDSM and engine logs attached.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Created attachment 1091695 [details] Thread exception screenshot
Created attachment 1091696 [details] Thread exception engine.log
Created attachment 1091699 [details] Thread exception vdsm.log
Hi Nisim, the setup described in comment 6, especially combination of guest OS Windows 10 and host CPU Nehalem, is not supported. There is a bug https://bugzilla.redhat.com/1269828 explicitly preventing engine from running Windows 10 on hosts with unsupported CPUs. You might encountered this problem because #1269828 is targeted for 3.5.6.
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Nisim, Jakub, please read the bug description carefully This bug is about *UI side*, to match relity the bug Target Release is supposed to be 3.5.5 because that's where it was shipped out I can't set 3.5.5 any longer - but stating 3.5.6 or 3.5.7 is wrong. Moran, why are those milestones/releases removed?
(In reply to Michal Skrivanek from comment #13) > Nisim, Jakub, please read the bug description carefully > This bug is about *UI side*, to match relity the bug Target Release is > supposed to be 3.5.5 because that's where it was shipped out > > I can't set 3.5.5 any longer - but stating 3.5.6 or 3.5.7 is wrong. Moran, > why are those milestones/releases removed? The reason is that i would like the official zstream supporting windows 10 guest will be tested end to end on the targeted version.
(In reply to Moran Goldboim from comment #14) > (In reply to Michal Skrivanek from comment #13) > > Nisim, Jakub, please read the bug description carefully > > This bug is about *UI side*, to match relity the bug Target Release is > > supposed to be 3.5.5 because that's where it was shipped out > > > > I can't set 3.5.5 any longer - but stating 3.5.6 or 3.5.7 is wrong. Moran, > > why are those milestones/releases removed? > > The reason is that i would like the official zstream supporting windows 10 > guest will be tested end to end on the targeted version. which is fine but this bug is _only_ about the UI change...and that had happened, ever since 3.5.5 it's there. So it should have been tested and the release note added to say that it's not supposed to be used.
so once again, I'm resetting it to the earlier available release in bugzilla which is 3.5.6 right now. This bug should be acknowledged, tested(or not, I don't really care), and note should be added to docs that Windows 10 OS type is not supported yet
i don't understand this logic. if 3.5.6 will be released without win10 support, and this bug won't be verified as part of this release, then why target it to 3.5.6 and not 3.5.7, where it will actually get verified? there is no logic to target non-verified bugs to released versions, as will happen now with 3.5.6.
Verified. webadmin > edit VM - Icon tab is missing. screenshot attached. User portal - win10 icon displayed properly for basic/extended tabs. sysprep functionality test - passed. See external trackers for polarion test case. Full support of Windows 10 is targeted to 3.5.7 according to https://bugzilla.redhat.com/show_bug.cgi?id=1272924
(In reply to Eyal Edri from comment #17) > i don't understand this logic. > if 3.5.6 will be released without win10 support, and this bug won't be that's the thing - it _will_ be released with the UI change. It already is, even 3.5.5 has it. Do not confuse this bug with bug 1232559 > verified as part of this release, then why target it to 3.5.6 and not 3.5.7, > where it will actually get verified? > > there is no logic to target non-verified bugs to released versions, as will > happen now with 3.5.6. This bug could have been verified ever since 3.5.5. The major thing to consider is to add a Known Issue that despite seeing Windows 10 in the UI we do not support it yet.
See https://bugzilla.redhat.com/show_bug.cgi?id=1238303#c18
oVirt 3.5.6 has been released and the bz verified, moving to closed current release.