Does your setup require the ACS patch or are you running a unmodified kernel? <div class="gmail_quote">On Oct 25, 2015 1:05 AM, <<a href="mailto:globalgorrilla@fastmail.fm">globalgorrilla@fastmail.fm</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">qemu and EDK2/OVMF from git have me running again on 4.2.4 and 4.3.0-rc6. Performance seems quite a bit down with 4.3.0-rc6. Performance in 4.2.4 seems much closer to that with 4.1. On 20 Oct 2015, at 21:54, <a href="mailto:globalgorrilla@fastmail.fm" target="_blank">globalgorrilla@fastmail.fm</a> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> It appears it may have been blind luck that I got anything to boot at all. Seems all the work required for the fix is not done yet...: <a href="https://www.mail-archive.com/kvm@vger.kernel.org/msg121381.html" rel="noreferrer" target="_blank">https://www.mail-archive.com/kvm@vger.kernel.org/msg121381.html</a> On 10/20/2015 03:03 PM, <a href="mailto:globalgorrilla@fastmail.fm" target="_blank">globalgorrilla@fastmail.fm</a> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Sry, short reference should be 529a5a8: <a href="https://github.com/tianocore/edk2/commit/529a5a860996b5e83941bab50a7b8604139264a1" rel="noreferrer" target="_blank">https://github.com/tianocore/edk2/commit/529a5a860996b5e83941bab50a7b8604139264a1</a> I'm also using qemu 2.4.0.1. I'm seeing high CPU load on boot the (TianoCore/EDK/OVMF bit) but eventually things settle down once Windows is running. Thanks to Janusz and others who have driven and are driving the issue with the EDK team. On 20 Oct 2015, at 10:05, francesco dicarlo wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> can you link the commit on github? can't seem to find it... 2015-10-20 18:49 GMT+02:00 <<a href="mailto:globalgorrilla@fastmail.fm" target="_blank">globalgorrilla@fastmail.fm</a>>: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I'm now able to boot my VM again with OVMF and 4.3.0-rc6. I think this is the fix for OVMF: edk2 git commit 39264a1 ... 1) Swap PTE init order for QEMU compatibility. Current PTE initialization algorithm works on HW but breaks QEMU emulator. Update the PTE initialization order to be compatible with both. ... I haven't yet discovered if any MTRR fixes went into 4.3.0-rc6 for this to happen or if this fixes for 4.2 as well. On 19 Oct 2015, at 23:53, Okky Hendriansyah wrote: Yes, the maintainer made the LTS version because of the issue on the 4.2.x <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> kernel. -- Okky Hendriansyah On October 20, 2015 at 13:50:58, Alexander Petrenz (<a href="mailto:petrenz.a@gmail.com" target="_blank">petrenz.a@gmail.com</a>) wrote: Oh there is an lts version? Thanks! I wasn´t aware of that. Regards Alex On Tue, Oct 20, 2015 at 8:39 AM, Okky Hendriansyah <<a href="mailto:okky@nostratech.com" target="_blank">okky@nostratech.com</a>> wrote: Hi, The GLib warning is because of the upgrade on GLib which makes existing QEMU throw this warning. I remove the warning by applying the patch from <a href="https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg04438.html" rel="noreferrer" target="_blank">https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg04438.html</a> You might want to try linux-vfio-lts, the package maintainer of linux-vfio made an LTS version which is based on 4.1.10 kernel ( <a href="https://aur.archlinux.org/packages/linux-vfio-lts/" rel="noreferrer" target="_blank">https://aur.archlinux.org/packages/linux-vfio-lts/</a>). Thanks. -- Okky Hendriansyah On October 20, 2015 at 13:19:47, Alexander Petrenz (<a href="mailto:petrenz.a@gmail.com" target="_blank">petrenz.a@gmail.com</a>) wrote: Since I´m unable to fix this issue and there doesn´t seem to be much information about it... is there an archive where I can get an older pkgbuild for a 4.1 vfio kernel? Regards Alex On Sun, Oct 18, 2015 at 10:45 PM, Alexander Petrenz <<a href="mailto:petrenz.a@gmail.com" target="_blank">petrenz.a@gmail.com</a>> wrote: OK I got rid of the GLib-Warning, but the KVM error is still there. On Sun, Oct 18, 2015 at 10:14 PM, Alexander Petrenz <<a href="mailto:petrenz.a@gmail.com" target="_blank">petrenz.a@gmail.com</a>> wrote: Thanks for the Hint. I try the short patch vor OVMF On Sun, Oct 18, 2015 at 10:06 PM, Janusz <<a href="mailto:januszmk6@gmail.com" target="_blank">januszmk6@gmail.com</a>> wrote: W dniu 18.10.2015 o 21:18, Alexander Petrenz pisze: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi, yesterday I compiled the recent version of the vfio kernel version in AUR. Now my VM doesn't start at all. I'm getting a reproducable error message (<a href="http://pastebin.com/YsNBX4Yj" rel="noreferrer" target="_blank">http://pastebin.com/YsNBX4Yj</a>) There are no other messages in dmesg, but those I posted yesterday. Same goes for hardware configuration According to lsmod the KVM module is loaded. Is there some configuration I need to change? Regards Alex Are you using OVMF? </blockquote> I don't know if this is the same because you also getting "(process:3267): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported" but there is a known bug in ovmf, since kernel 4.2 because of changes in kvm, you wont be able to start properly VM with more than one core, <a href="http://www.mail-archive.com/kvm@vger.kernel.org/msg121088.html" rel="noreferrer" target="_blank">http://www.mail-archive.com/kvm@vger.kernel.org/msg121088.html</a> _______________________________________________ vfio-users mailing list <a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a> _______________________________________________ vfio-users mailing list <a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a> </blockquote> _______________________________________________ vfio-users mailing list <a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a> </blockquote></blockquote> _______________________________________________ vfio-users mailing list <a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a> </blockquote> _______________________________________________ vfio-users mailing list <a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a> </blockquote> _______________________________________________ vfio-users mailing list <a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a> </blockquote></div>