Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1104235

Summary: wrong default value of single_qxl_pci for VM created from API causes VM creation to fail
Product: Red Hat Enterprise Virtualization Manager Reporter: movciari
Component: ovirt-engineAssignee: Shahar Havivi <shavivi>
Status: CLOSED WORKSFORME QA Contact: movciari
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: acathrow, gklein, iheim, lpeer, michal.skrivanek, movciari, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-10 06:44:02 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:

Description movciari 2014-06-03 15:10:44 UTC
Description of problem:
if you try creating VM with VNC display from API without specifying single_qxl_pci (which should always be false for VMs with VNC), it will default to single_qxl_pci = true, and fail to create VM

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. create VM with VNC display without specifying single_qxl_pci

Actual results:
it will fail:
<reason>Operation Failed</reason>
    <detail>[Cannot add VM. Cannot set single display device via VNC display.]</detail>

Expected results:
single_qxl_pci should be implicitly set to false when creating VM with VNC display

Additional info:
webadmin works correctly and doesn't allow user to set single_qxl_pci to true for VM with VNC display

Comment 1 Shahar Havivi 2014-06-05 09:03:11 UTC
Hi,
I just test your scenario and couldn't reproduce the error.
I send the following xml:
<vm>
 <name>rest1</name>
 <cluster href= "/api/clusters/00000001-0001-0001-0001-0000000001dd" id="00000001-0001-0001-0001-0000000001dd"/>
 <template href= "/api/templates/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"/>
 <display>
  <type>vnc</type>
 </display>
</vm>

Do you use a template the the single_pci is enabled?
Can you post your xml?

Comment 2 movciari 2014-07-09 11:14:37 UTC
i'm pretty sure i used blank template, but i reproduced this on old version and can't reproduce it again right now

Comment 3 Shahar Havivi 2014-07-10 06:44:02 UTC
Cannot reproduce it on upstream as well as on 3.4,
Closing the bug - if you do reproduce the error please reopen and submit the xml that sent via the API.