<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="GENERATOR" content="GtkHTML/4.4.4">
</head>
<body>
ons 2012-12-19 klockan 01:28 +0000 skrev bugzilla@redhat.com:
<blockquote type="CITE">
<pre>
Product: Fedora
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=881579">https://bugzilla.redhat.com/show_bug.cgi?id=881579</a>
--- Comment #3 from Marcelo Tosatti <<a href="mailto:mtosatti@redhat.com">mtosatti@redhat.com</a>> ---
Its very likely the cause for this are instruction emulation upstream
(emulation of invalid guest state by default).
These are being fixed upstream. Once that is completed, it will be necessary to
backport
to FC17.
In the meantime, loading kvm-intel.ko with emulate_invalid_guest_state=0 should
work around the problem (tested locally on kvm.git as of dec/2012).
</pre>
</blockquote>
<br>
For future reference, I want to add what measures have been taken:<br>
<br>
From oVirt Webadmin, the Host was set into Maintenance.<br>
<br>
Then this file:<br>
<b>/etc/sysconfig/modules/kvm.modules</b>:<br>
#!/bin/sh<br>
<br>
grep vmx /proc/cpuinfo >/dev/null 2>&1 && vmx=1<br>
grep svm /proc/cpuinfo >/dev/null 2>&1 && svm=1<br>
<br>
if [ "$vmx" ] || [ "$svm" ]; then<br>
[ "$vmx" ] && modprobe -b >/dev/null 2>&1<br>
[ "$svm" ] && modprobe -b kvm-amd >/dev/null 2>&1<br>
<br>
# no reason why vhost should not work with TCG, but currently it does not<br>
modprobe -b vhost-net >/dev/null 2>&1<br>
else<br>
exit 0<br>
fi<br>
<br>
Was modfied to look like:<br>
#!/bin/sh<br>
<br>
grep vmx /proc/cpuinfo >/dev/null 2>&1 && vmx=1<br>
grep svm /proc/cpuinfo >/dev/null 2>&1 && svm=1<br>
<br>
if [ "$vmx" ] || [ "$svm" ]; then<br>
[ "$vmx" ] && modprobe -b kvm-intel <b>emulate_invalid_guest_state=0</b> >/dev/null 2>&1<br>
[ "$svm" ] && modprobe -b kvm-amd >/dev/null 2>&1<br>
<br>
# no reason why vhost should not work with TCG, but currently it does not<br>
modprobe -b vhost-net >/dev/null 2>&1<br>
else<br>
exit 0<br>
fi<br>
<br>
And after <b>two</b> reboots(didn´t get set after the first reboot, strangly enough) the setting have been confirmed persistant with:<br>
# more /sys/module/kvm_intel/parameters/emulate_invalid_guest_state<br>
N<br>
<br>
The Host was again activated and the guest panics are gone.<br>
<br>
Thanks for the hint!<br>
<br>
/Karli<br>
<br>
</body>
</html>