Bug 1507847

Summary:	Can't run High Performance VMs as non headless with the VNC graphics protocol
Product:	[oVirt] ovirt-engine	Reporter:	Sharon Gratch <sgratch>
Component:	BLL.Virt	Assignee:	Sharon Gratch <sgratch>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Polina <pagranat>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs, sgratch, tjelinek
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-22 09:58:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sharon Gratch 2017-10-31 09:58:24 UTC

Description of problem:
When trying to run a High Performance VM as non headless (via regular run or run-once) and set the graphics protocol to be VNC, the VM failed to start with the following libvirt error:
"libvirtError: unsupported configuration: Can't add USB input device. USB bus is disabled"

The reason is that VNC protocol requires USB device installed but since USB is automatically disabled for High Performance VMs and there is no UI support for enabling USB then we have a problem.

Version-Release number of selected component (if applicable):
4.2 master 
libvirt-3.7.0-2.fc26.x86_64
vdsm-4.20.3-216.git87725ec52.fc26.x86_64

How reproducible:
100%


Steps to Reproduce:
1.Edit or create a VM with 'Optimized for' field set to 'High Performance'. 
2.un-check the 'Headless Mode' within the Console tab - to set the VM to non-headless.
3.Save and run this VM.

Actual results:
The VM failed to run with libvirt error:
"libvirtError: unsupported configuration: Can't add USB input device. USB bus is disabled"

Expected results:
The VM should run with both SPICE and VNC protocol or we should give an option to enable the "OS depended" USB just for High Performance VMs.

Comment 1 Sharon Gratch 2017-10-31 10:01:55 UTC

This is a known issue that we need to decide how to handle. Maybe just remove the VNC option from graphics protocols pull down menu for HP VMs.

Comment 2 Michal Skrivanek 2017-11-01 05:03:48 UTC

Why don't we just enable Usb silently for VNC?
If that's too ugly(but is it?) we can just drop the tablet device

Comment 3 Yaniv Kaul 2017-11-01 08:03:10 UTC

(In reply to Michal Skrivanek from comment #2)
> Why don't we just enable Usb silently for VNC?
> If that's too ugly(but is it?) we can just drop the tablet device

Doesn't USB perform some polling which affects performance?

Comment 4 Michal Skrivanek 2017-11-01 10:07:22 UTC

(In reply to Yaniv Kaul from comment #3)
> (In reply to Michal Skrivanek from comment #2)
> > Why don't we just enable Usb silently for VNC?
> > If that's too ugly(but is it?) we can just drop the tablet device
> 
> Doesn't USB perform some polling which affects performance?

It's like with Server/Desktop, it's just a preset so you should be able to override whatever you need. A graphical display might be quite common especially since we ended up with our somewhat complex serial console solution, and VNC is certainly less intrusive than qxl and its set of usb1&2 controllers
Again, even if we give up the tablet device it still might be useful to get a glance at the text console in virt-viewer

Comment 5 Tomas Jelinek 2017-11-02 10:01:27 UTC

Okey, so targeting 4.2 to remove the tablet for VNC for HP VMs.

Comment 6 Polina 2018-02-12 12:25:46 UTC

Verified in rhv-release-4.2.1-9-001.noarch

the tests performed:

Edit VM that was created from a template. Choose 'High Performance' (general tab), uncheck 'Headless' in the console tab, choose VNC graphic protocol. Run VM - ok

Change the graphic protocol to SPICE+VNC, stop/start VM. - ok

Create new VM, choose 'High Performance', uncheck 'Headless', choose VNC graphic protocol. run once - no error.

Comment 7 Sandro Bonazzola 2018-02-22 09:58:26 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.