[vfio-users] VM doesn't book with kernel 4.2.3-1-vfio

[globalgorrilla at fastmail.fm]

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 kernel. 
>
> -- 
> Okky Hendriansyah
>
> On October 20, 2015 at 13:50:58, Alexander Petrenz 
> (petrenz.a at gmail.com) 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 
> <okky at nostratech.com> 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 https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg04438.html 
>
> 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 
> (https://aur.archlinux.org/packages/linux-vfio-lts/).
>
> Thanks.
> -- 
> Okky Hendriansyah 
>
> On October 20, 2015 at 13:19:47, Alexander Petrenz 
> (petrenz.a at gmail.com) 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 
> <petrenz.a at gmail.com> 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 
> <petrenz.a at gmail.com> wrote:
> Thanks for the Hint. I try the short patch vor OVMF
>
> On Sun, Oct 18, 2015 at 10:06 PM, Janusz <januszmk6 at gmail.com> wrote:
> W dniu 18.10.2015 o 21:18, Alexander Petrenz pisze:
>> 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 
>> (http://pastebin.com/YsNBX4Yj)
>> 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?
> 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,
> http://www.mail-archive.com/kvm@vger.kernel.org/msg121088.html
>
>
>
>
> _______________________________________________
> vfio-users mailing list
> vfio-users at redhat.com
> https://www.redhat.com/mailman/listinfo/vfio-users
>
> _______________________________________________
> vfio-users mailing list
> vfio-users at redhat.com
> https://www.redhat.com/mailman/listinfo/vfio-users