Red Hat Bugzilla – Bug 986665
Unable to install/run Fedora 19 with Console protocol set to SPICE.
Last modified: 2014-01-27 19:36:03 EST
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
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.
The VM reboots soon right after starting the installation - happens too fast, so I can't see the messages.
The installation of Fedora19 should complete with no issues.
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.
Logs please .....
I'm sure the component is wrong.
Most likely this is a dupe of 952666 but we need to see logs ......
What would be the right component for that? Couldn't find anything that would 100% match.
What is the OS of the client machine ?
What is the version of spice-server and remote-viewer (or virt-viewer) ?
No reply and most likely It was problem in spice-server fixed in 6.4.z.