Thank you very much for the quick reply and confirmation! I just made
and submitted a patch according to your advice.
Thanks,
Liang
On Wed, Jul 25, 2018 at 2:05 AM, Paolo Bonzini wrote:
> On 24/07/2018 09:53, Liang C wrote:
>> Hi,
>>
>> We have a situation where our qemu processes need to be
Thank you very much for the quick reply and confirmation! I just made
and submitted a patch according to your advice.
Thanks,
Liang
On Wed, Jul 25, 2018 at 2:05 AM, Paolo Bonzini wrote:
> On 24/07/2018 09:53, Liang C wrote:
>> Hi,
>>
>> We have a situation where our qemu processes need to be
On 24/07/2018 09:53, Liang C wrote:
> Hi,
>
> We have a situation where our qemu processes need to be launched under
> cgroup cpuset.mems control. This introduces an similar issue that was
> discussed a few years ago. The difference here is that for our case,
> not being able to allocate from
On 24/07/2018 09:53, Liang C wrote:
> Hi,
>
> We have a situation where our qemu processes need to be launched under
> cgroup cpuset.mems control. This introduces an similar issue that was
> discussed a few years ago. The difference here is that for our case,
> not being able to allocate from
Hi,
We have a situation where our qemu processes need to be launched under
cgroup cpuset.mems control. This introduces an similar issue that was
discussed a few years ago. The difference here is that for our case,
not being able to allocate from DMA32 zone is a result a cgroup
restriction not
Hi,
We have a situation where our qemu processes need to be launched under
cgroup cpuset.mems control. This introduces an similar issue that was
discussed a few years ago. The difference here is that for our case,
not being able to allocate from DMA32 zone is a result a cgroup
restriction not
6 matches
Mail list logo
