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

Wed Oct 28 02:55:46 UTC 2015

Not more reliable, no.

4.1.X has been most stable and performant (with the exception of 4.1.10 
which had soft lockups).

On 27 Oct 2015, at 19:52, Dan Ziemba wrote:

> Is 4.3 any better at booting for you?  I haven't gotten around to
> trying it yet.
>
> I'm back to 4.1 for now.  On the bright side, the switch to qemu-git
> and/or ovmf-git seems to have given me a slight performance boost.
>
>
> -----Original Message-----
> From: globalgorrilla at fastmail.fm
> To: Dan Ziemba <zman0900 at gmail.com>
> Cc: vfio-users at redhat.com
> Subject: Re: [vfio-users] VM doesn't book with kernel 4.2.3-1-vfio
> Date: Tue, 27 Oct 2015 19:41:37 -0700
> Mailer: MailMate (1.9.2r5141)
>
> Booting with OVMF on 4.2+ sometimes fails for me too.
>
> I think there's still something up between Qemu and OVMF.
>
> On 27 Oct 2015, at 19:39, Dan Ziemba wrote:
>
>> I tried out 4.2.4 with the ACS patch, but no luck.  I did at least
>> get
>> proper output on all 3 of my host screens a few times, which I wasn't
>> getting ever with 4.2.3, but it wasn't reliable.  Plain 4.2.3
>> (probably
>> 4.2.4 too) works to at least run my host, but I need the ACS patch
>> for
>> pass through.
>>
>> VM wouldn't boot either.  I tried switching to OVFM git and qemu 
>> git,
>> but that didn't make much difference.  In all cases, the VM would
>> hang
>> before showing the efi screen, with the processor repeatedly going
>> between minimal activity, to 1 core maxed out, then all 6 I am
>> passing
>> through, then repeat.  
>>
>> This all seems to point to the ACS patch being the cause of the
>> problems, for me at least.
>>
>> -----Original Message-----
>> From: globalgorrilla at fastmail.fm
>> To: Dan Ziemba <zman0900 at gmail.com>
>> Cc: vfio-users at redhat.com
>> Subject: Re: [vfio-users] VM doesn't book with kernel 4.2.3-1-vfio
>> Date: Mon, 26 Oct 2015 09:06:26 -0700
>> Mailer: MailMate (1.9.2r5141)
>>
>> I'm quirking a root PCIE port for it's downstream PLX chip.
>>
>> +        /* Z97-WS X16 PLX */
>> +        0x0c01,
>>
>> On 24 Oct 2015, at 22:16, Dan Ziemba wrote:
>>
>>> Does your setup require the ACS patch or are you running a
>>> unmodified
>>> kernel?
>>> On Oct 25, 2015 1:05 AM, <globalgorrilla at fastmail.fm> wrote:
>>>
>>>> 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, globalgorrilla at fastmail.fm wrote:
>>>>
>>>> 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...:
>>>>>
>>>>> https://www.mail-archive.com/kvm@vger.kernel.org/msg121381.html
>>>>>
>>>>> On 10/20/2015 03:03 PM, globalgorrilla at fastmail.fm wrote:
>>>>>
>>>>>> Sry, short reference should be 529a5a8:
>>>>>>
>>>>>>
>>>>>> https://github.com/tianocore/edk2/commit/529a5a860996b5e83941
>>>>>> ba
>>>>>> b50a7b8604139264a1
>>>>>>
>>>>>>
>>>>>> 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:
>>>>>>
>>>>>> can you link the commit on github? can't seem to find it...
>>>>>>>
>>>>>>> 2015-10-20 18:49 GMT+02:00 <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/m
>>>>>>>>> sg
>>>>>>>>> 04438.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 gma
>>>>>>>>> il
>>>>>>>>> .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/msg1210
>>>>>>>>> 88
>>>>>>>>> .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
>>>>>>>>>
>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>