❦ 4 avril 2018 17:00 +0200, Vincent Bernat :
>>> You can do that locally, but as a patch it's very unlikely to be
>>> accepted upstream because we've introduced RW locks to be able to access
>>> domain list from multiple threads.
>>
>> Looking a bit more, the whole "iterating" bit is currently
Hi,
I have a fedora27 system with a win10 guest trying to use photoshop
2015. I've adjusted the vram parameter for the guest to 512M with QXL,
but photoshop still reports "3D features and some filters require
512MB vRAM and photoshop has detected less than that on your system."
What is the proper
❦ 4 avril 2018 16:21 +0200, Vincent Bernat :
>> You can do that locally, but as a patch it's very unlikely to be
>> accepted upstream because we've introduced RW locks to be able to access
>> domain list from multiple threads.
>
> Looking a bit more, the whole "iterating" bit is currently
> uns
❦ 4 avril 2018 15:59 +0200, Michal Privoznik :
>> I may have missed this suggestion. Maybe Dan only sent it to you?
>
> No, there is another thread where this issue is discussed:
>
> https://www.redhat.com/archives/libvir-list/2018-April/msg00190.html
>
> In the
>> meantime, could I change the
On 04/04/2018 03:48 PM, Vincent Bernat wrote:
> ❦ 4 avril 2018 15:19 +0200, Michal Privoznik :
>
>> Both threads call virHashForEach(table=0x7f92fc69a480). Thread 6 was
>> first so it starts iterating and sets table->iterating so later when
>> thread 10 enters the function an error is reported.
❦ 4 avril 2018 15:19 +0200, Michal Privoznik :
> Both threads call virHashForEach(table=0x7f92fc69a480). Thread 6 was
> first so it starts iterating and sets table->iterating so later when
> thread 10 enters the function an error is reported.
>
> I guess we can go with what Dan suggested and af
On 04/04/2018 02:59 PM, Vincent Bernat wrote:
> ❦ 4 avril 2018 11:17 +0200, Michal Privoznik :
>
>> Dunno, this is the first time I hear about this issue. Maybe you can try
>> to set a break point on virHashIterationError() and when it's hit get
>> stacktrace of all threads 't a a bt'. That mig
❦ 4 avril 2018 11:17 +0200, Michal Privoznik :
> Dunno, this is the first time I hear about this issue. Maybe you can try
> to set a break point on virHashIterationError() and when it's hit get
> stacktrace of all threads 't a a bt'. That might shed more light into
> the issue. Smells like we a
❦ 4 avril 2018 11:17 +0200, Michal Privoznik :
>> We are using a hook, but the hook doesn't query libvirt back, so it
>> should be safe from this point of view. However, we have several sources
>> querying libvirt at regular interval (once every 5 seconds from two
>> different sources). I am un
On 04/04/2018 10:36 AM, Vincent Bernat wrote:
> Hey!
>
> On many of our servers, we often have the following error:
>
> error : virHashForEach:597 : Hash operation not allowed during iteration
>
> When querying the list of domains, this means libvirt will silently
> return 0 domain (most uses of
Hey!
On many of our servers, we often have the following error:
error : virHashForEach:597 : Hash operation not allowed during iteration
When querying the list of domains, this means libvirt will silently
return 0 domain (most uses of virHashForEach don't handle the return
code).
We are using a
11 matches
Mail list logo
