The three Windows VMs I tried were Windows 7, Windows 8.1, and Windows
Server 2012 R2. All experienced the stop error.
On Mon, Oct 27, 2014 at 8:21 AM, Michal Skrivanek <
michal.skrivanek(a)redhat.com> wrote:
On 24 Oct 2014, at 18:43, Markus Stockhausen wrote:
Hi,
we are running the hyperv flags since months in our Win7 VMs without any
issue. As we are still on OVirt 3.4 FC20 infrastructure we set them with
hooks (and really depend on them).
Maybe RHEL related?
It might be. What's running on your host?
Did you see the same problem with anything newer than Windows XP?
Thanks,
michal
Markus
Am 24.10.2014 18:22 schrieb Charles Gruener <cgruener(a)gruener.us>:
https://bugzilla.redhat.com/show_bug.cgi?id=1110305
This enabled the hv_relaxed flag on all my Windows VMs, causing them to
no longer boot. The same thing would happen if I simply booted from the
Windows install media. I would get a screen with a stop error:
Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000001E
Parameters:
0xFFFFFFFFC0000096
0xFFFFF802C4044EA4
0x00000000000000000
0x00000000000000000
I created a file called
/etc/ovirt-engine/osinfo.conf.d/01-windows.properties that had one line:
os.windows_xp.devices.hyperv.enabled.value = false
I restarted ovirt-engine and now I can start my Windows VMs.
Why does this occur? Is it because I upgraded from 3.4 to 3.5? Is
there something else I'm doing wrong? I would like to not need this
workaround. Thanks.
Charles
<InterScan_Disclaimer.txt>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users