On 3/24/22 12:49, Martin Kletzander wrote:
> On Thu, Mar 24, 2022 at 11:22:54AM +, Daniel P. Berrangé wrote:
>> On Thu, Mar 24, 2022 at 12:15:43PM +0100, Michal Prívozník wrote:
>>> On 3/24/22 10:26, Martin Kletzander wrote:
>>> > On Tue, Mar 22, 2022 at 04:05:14PM +0100, Michal Privoznik
On Thu, Mar 24, 2022 at 11:22:54AM +, Daniel P. Berrangé wrote:
On Thu, Mar 24, 2022 at 12:15:43PM +0100, Michal Prívozník wrote:
On 3/24/22 10:26, Martin Kletzander wrote:
> On Tue, Mar 22, 2022 at 04:05:14PM +0100, Michal Privoznik wrote:
>> Since its commit v5.0.0-rc0~75^2~1^2~3 QEMU is
On Thu, Mar 24, 2022 at 12:15:43PM +0100, Michal Prívozník wrote:
> On 3/24/22 10:26, Martin Kletzander wrote:
> > On Tue, Mar 22, 2022 at 04:05:14PM +0100, Michal Privoznik wrote:
> >> Since its commit v5.0.0-rc0~75^2~1^2~3 QEMU is capable of
> >
> > Anything wrong with the old "commit
On 3/24/22 10:26, Martin Kletzander wrote:
> On Tue, Mar 22, 2022 at 04:05:14PM +0100, Michal Privoznik wrote:
>> Since its commit v5.0.0-rc0~75^2~1^2~3 QEMU is capable of
>
> Anything wrong with the old "commit ffac16fab33b" ?
Not specifically no. But I do it this ways so that it's visible at
On Tue, Mar 22, 2022 at 04:05:14PM +0100, Michal Privoznik wrote:
Since its commit v5.0.0-rc0~75^2~1^2~3 QEMU is capable of
Anything wrong with the old "commit ffac16fab33b" ?
specifying number of threads used to allocate memory. While it
defaults to the number of vCPUs, users might want to
On 3/22/22 16:05, Michal Privoznik wrote:
> Since its commit v5.0.0-rc0~75^2~1^2~3 QEMU is capable of
> specifying number of threads used to allocate memory. While it
> defaults to the number of vCPUs, users might want to use a
> different value (especially for humongous guests with gigantic
>
Since its commit v5.0.0-rc0~75^2~1^2~3 QEMU is capable of
specifying number of threads used to allocate memory. While it
defaults to the number of vCPUs, users might want to use a
different value (especially for humongous guests with gigantic
pages).
In general, on QEMU cmd line level it is
