Description of problem: Attempting to install Windows Server 2012R2 on a VM. After runonce is selected user never gets console option. The VM shows status powering up and then rebooting. If Win2008 is selected as OS in VM console access is available but VM reboot loops with following error: Your PC needs to restart. Please hold down the power button. Error Code: 0x000000C4 Parameters: 0x00000000000000 Version-Release number of selected component (if applicable): rhevm-3.2.2-0.41.el6ev.noarch How reproducible: very Steps to Reproduce: 1. create VM (host does not matter) 2. choose Win OS 3. select run once, attaching vfd and iso files Actual results: If 2012 was selected as OS then console access never appears. VM reboots. If 2008 was selected as OS console access appears but VM reboots and error is seen. Expected results: Install screen should appear. Additional info: Googled the error code and found this for virtualbox: http://www.thewindowsclub.com/fix-error-0x000000c4-unable-to-install-windows-8-1-using-virtualization https://www.virtualbox.org/ticket/11899 Maybe similar? Something not being passed correctly? I was able to install in RHEV 3.3 so maybe there is some difference between how the versions are passing the information?
can you please get the actual QEMU command line. Might be something KVM folks can look at...
Windows 2012R2 in RHEL 6.4…not sure we support that. The difference in your tests is due to VNC vs SPICE display. Only VNC is supported/works. Maybe latest virtio drivers helps…check out bug 1032222
indeed, Opteron G1 is missing cx16 and the VM is being run as a G1. That 2345 CPU seem to actually have it though so just change the cluster config to G2? Give it a try
Michal, Is there a way to make this change on the fly? Something in the GUI or DB? The only way I know to change the family is to edit a cluster with no hosts attached.
you may be able to change it when they are all in Maintenance (I'm not sure about that) why not taking one host out and create a new testing cluster?
filtering should be addressed by bug 1096851