Bug 986665

Summary:	Unable to install/run Fedora 19 with Console protocol set to SPICE.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Alexander Chuzhoy <sasha>
Component:	spice-activex-win	Assignee:	Uri Lublin <uril>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	acathrow, cfergeau, dblechte, iheim, mkrcmari, Rhev-m-bugs, sasha, vgrinco
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-14 12:21:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Spice	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexander Chuzhoy 2013-07-21 12:04:28 UTC

Description of problem:
Tried to install Fedora 19 via the Admin portal. Soon after the VM starts the installation - the VM reboots (and the console is lost).

Version-Release number of selected component (if applicable):
DC/Cluster  compatiblity version 3.2

How reproducible:
Try to install Fedora19 via PXE from the admin portal, while the console protocol is set to SPICE.

Steps to Reproduce:
1. Create a new VM on a DC/Cluster with compatibility version 3.2.
2. Make sure the Console protocol is set to SPICE and the VM is configure to boot via PXE.
3. Start installing Fedora19.

Actual results:
The VM reboots soon right after starting the installation - happens too fast, so I can't see the messages.

Expected results:
The installation of Fedora19 should complete with no issues.

Additional info:
After installing Fedora 19 (works if you set the Console protocol to VNC), I tried switching the protocol to VNC and just work with the VM (not install it). Soon after I boot the VM - it reboots. If I move the protocol back to VNC - it works.

Comment 1 Andrew Cathrow 2013-07-22 12:28:59 UTC

Logs please .....

Comment 2 Andrew Cathrow 2013-07-22 12:30:46 UTC

I'm sure the component is wrong.

Most likely this is a dupe of 952666 but we need to see logs ......

Comment 3 Alexander Chuzhoy 2013-07-22 12:45:51 UTC

What would be the right component for that? Couldn't find anything that would 100% match.

Comment 4 Uri Lublin 2013-08-07 15:27:13 UTC

What is the OS of the client machine ?
What is the version of spice-server and remote-viewer (or virt-viewer) ?

Comment 5 Marian Krcmarik 2013-10-14 12:21:22 UTC

No reply and most likely It was problem in spice-server fixed in 6.4.z.