Description of problem: After migrating from RHEV 3.3 to RHEV 3.4, a pre-existing VM may have SPICE display type configured which results in inability to create templates Version-Release number of selected component (if applicable): rhev-m 3.4.0 How reproducible: always Steps to Reproduce: 1) create VM on RHEV 3.3, set OS to "Windows 2012 x64" 2) ensure SPICE display type is set in VM settings (default for RHEV 3.3) 3) shut down the VM 4) Upgrade to RHEV 3.4 5) right click on the VM, select "Create Template" 6) fill in the form 7) press OK Actual results: Nothing happens, there's no error or action. Expected results: Warning appears about wrong videocard settings (just like when starting such a VM) Additional info: I noticed this in following scenario: 1) VM was created in RHEV 3.3, it had SPICE video assigned by default. 2) the VM was shut down to create a template, but there was a RHEV upgrade scheduled 3) after upgrading to 3.4, I went on with my plan to make the template but the form did not do anything. 4) after some attempts to create the tempale I decided to just start the VM without one. That's where I got the warning about display type. I also imagine there may be problems with VMs spawned from windows 2012 templates created in RHEV 3.3, but don't have one to test at the moment.
> ... > 6) fill in the form > 7) press OK > > Actual results: > Nothing happens, there's no error or action. nothing happens it means the dialog doesnt close? or it close but template is not created? if dialog doesn't close, are you sure nothing is highlighted in the dialog (marking that there is something missing)? if it does close, there is no event log? any errors maybe in engine.log? worth attaching the engine.log anyway.. is it possible to create template from other vms? (newly created in 3.4 or other from 3.3 - maybe with different os/display type)? if you change the os or display type, is it possible then to create the template? thanks!
Nothing happens, nothing is highlited as the window for template creation does not have console type selection.
I am also wondering what will happen to a win2012 VM if it's created on 3.3 with SPICE and started, then the manager is upgraded to 3.4. Will it even be possible to live-migrate? Will RHEV-M create a proper migration process with the SPICE card or the destination host will be assigned a VNC card which will crash the VM upon migration?
Please try to change the display type to vnc and see if you can create the VM.
Windows 2012 are not supported with SPICE (lack of virtio drivers), it wasn't supported in 3.3 either, the fact you've been able to reate it was a bug fixed in 3.4 So the 3.3 VMs have qxl display? How about drivers? As a workaround (if you really want to use SPICE and you didn't have any issue with that) you can allow the qxl/spice in osinfo
Changing to VNC resolves the issue. I understand that this was done to fix a bug in 3.3 but the fix shouldn't have broken existing VMs created with wrong settings.
Verified in rhevm-3.5.0-0.13.beta.el6ev.noarch (vt4). First, verified that in RHEVM 3.5 it is not possible to create Windows 2012 VM with SPICE console (as is defined in osinfo). Verification steps: 1. Have a Windows 2012 VM with SPICE console set (e.g., from older 3.3 RHEVM or hack it in 3.5 via osinfo). 2. Create template from this VM. Results: Created template has console set to VNC and cannot be changed to SPICE.
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-2015-0158.html