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.