Description of problem: Newly created vms created with VNC as default console Version-Release number of selected component (if applicable): is5 How reproducible: always Steps to Reproduce: 1. create vm 2. look at the console type 3. Actual results: VNC Expected results: SPICE Additional info:
did you choose optimize for server (vnc) or for desktop (spice)? andrew - does it make sense to still default to vnc for servers?
We should default to Spice for all. CPU utilization is actually better for spice than vnc even on run level 3
*** Bug 985896 has been marked as a duplicate of this bug. ***
I verified this is a UI issue (didn't check user portal, though): i can see that vnc is selected by defult on create vm, regardless to server/desktop selection. also tested with REST created vm with the following xml: <vm> <name>omerRest</name> <cluster> <name>rhel</name> </cluster> <template> <name>Blank</name> </template> <memory>536870912</memory> </vm> and it was created with spice.
When creating a VM the default display type is now taken from the template it is based on for desktops and servers VMs. The problem is that the default display type of the 'Blank' template is set to VNC. Regarding the check with REST mentioned in comment #4 - we found that there is a bug that causes the default display type of every VM which is created using REST to be set to SPICE (should be fixed by: http://gerrit.ovirt.org/#/c/17382/).
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=d85ca23448a641c77218125156449a15d6168932
verified on is8
Closing - RHEV 3.3 Released