[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1864984] Re: "nr_entries is too big" when using virgl
From: |
Thomas Huth |
Subject: |
[Bug 1864984] Re: "nr_entries is too big" when using virgl |
Date: |
Thu, 06 May 2021 05:53:53 -0000 |
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1864984
Title:
"nr_entries is too big" when using virgl
Status in QEMU:
Incomplete
Bug description:
I have a bootable image where GNOME Shell fails because it hits a
limit in virtio-gpu.
In `hw/display/virtio-gpu.c`, there is a limit for `nr_entries` at
16384. There is no explanation for that limit. But there does not seem
to be any limit on the kernel side.
Raising this limit with a patch to 262144 solves the issue.
Could there be an explanation why this limit is needed? And why this
value? Or could this limit be just removed?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1864984/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1864984] Re: "nr_entries is too big" when using virgl,
Thomas Huth <=