On 4/18/23 1:18 PM, Nick Guenther wrote:
April 18, 2023 3:37 AM, "Peter Krempa" wrote:
cases of code style not being aligned from what libvirt does normally ...
I'm very happy to conform my style as needed. I just want my users to be able
to use libvirt (if they can't I'll teach them to
April 18, 2023 3:37 AM, "Peter Krempa" wrote:
> cases of code style not being aligned from what libvirt does normally ...
I'm very happy to conform my style as needed. I just want my users to be able
to use libvirt (if they can't I'll teach them to use qemu directly I suppose
but that's
On 2023/4/18 21:50, wangjian (AN) wrote:
>
> On 4/15/23 15:48, wangjian (AN) wrote:
>> Hi Guys,
>>
>>
>>
>> Currently qemu and spdk already support vhost-user-scsi, but there is
>> no vhost-user-scsi configuration in libvirt.
>>
>> We hope that libvirt supports the following configurations
On 3/23/23 17:01, Michal Privoznik wrote:
>
Polite ping.
Michal
On 4/18/23 9:43 AM, Ján Tomko wrote:
On a Tuesday in 2023, Andrea Bolognani wrote:
On Tue, Apr 18, 2023 at 03:19:45PM +0200, Ján Tomko wrote:
On a Tuesday in 2023, Andrea Bolognani wrote:
> That's already the case in practice, but it's a better
> experience for the user if we reject this
On Tue, Apr 18, 2023 at 03:43:41PM +0200, Ján Tomko wrote:
> On a Tuesday in 2023, Andrea Bolognani wrote:
> > On Tue, Apr 18, 2023 at 03:19:45PM +0200, Ján Tomko wrote:
> > > On a Tuesday in 2023, Andrea Bolognani wrote:
> > > > That's already the case in practice, but it's a better
> > > >
On a Tuesday in 2023, Andrea Bolognani wrote:
On Tue, Apr 18, 2023 at 03:19:45PM +0200, Ján Tomko wrote:
On a Tuesday in 2023, Andrea Bolognani wrote:
> That's already the case in practice, but it's a better
> experience for the user if we reject this configuration
> outright instead of
On Tue, Apr 18, 2023 at 03:19:45PM +0200, Ján Tomko wrote:
> On a Tuesday in 2023, Andrea Bolognani wrote:
> > That's already the case in practice, but it's a better
> > experience for the user if we reject this configuration
> > outright instead of silently ignoring part of it.
> >
> >
On a Tuesday in 2023, Andrea Bolognani wrote:
That's already the case in practice, but it's a better
experience for the user if we reject this configuration
outright instead of silently ignoring part of it.
Signed-off-by: Andrea Bolognani
---
src/conf/domain_validate.c| 9
On a Wednesday in 2023, Michal Privoznik wrote:
While trying to make live detach of work, I've accumulated
couple of patches. The most reasonable ones made it into this patch set
as paches 1-4. And after nearly losing my sanity, I've decided it's not
worth supporting live detach of since
On a Wednesday in 2023, Michal Privoznik wrote:
When hotpluging a device, we might need to add a
device with it (because of some crazy backcompat).
Now, hotplugging is done in several phases. In one of them,
qemuDomainChrPreInsert() allocates space for both devices, and
then
On 4/18/23 11:53, Boris Fiuczynski wrote:
> Commit fc216db4fb789cbd309 introduced a mocked test with binary test data
> which fails on big endian machines.
> Therefore build the viracpitest test only on little endian machines.
>
> Fixes: fc216db4fb789cbd30917be036d0b94d965bdf7f
>
>
Boris Fiuczynski writes:
> Commit fc216db4fb789cbd309 introduced a mocked test with binary test data
> which fails on big endian machines.
> Therefore build the viracpitest test only on little endian machines.
>
> Fixes: fc216db4fb789cbd30917be036d0b94d965bdf7f
>
> Signed-off-by: Boris
Commit fc216db4fb789cbd309 introduced a mocked test with binary test data
which fails on big endian machines.
Therefore build the viracpitest test only on little endian machines.
Fixes: fc216db4fb789cbd30917be036d0b94d965bdf7f
Signed-off-by: Boris Fiuczynski
---
tests/meson.build | 7 ++-
On Tue, 18 Apr 2023 at 09:05, Richard Henderson
wrote:
>
> On 4/17/23 18:40, Peter Maydell wrote:
> > @@ -219,8 +221,8 @@ static void tcg_set_one_insn_per_tb(Object *obj, bool
> > value, Error **errp)
> > {
> > TCGState *s = TCG_STATE(obj);
> > s->one_insn_per_tb = value;
> > -
That's already the case in practice, but it's a better
experience for the user if we reject this configuration
outright instead of silently ignoring part of it.
Signed-off-by: Andrea Bolognani
---
src/conf/domain_validate.c| 9 +
QEMU now supports multifd-compression=zstd for migration with enabled multifd.
Bring the support to libvirt as well.
Signed-off-by: Oleg Vasilev
---
include/libvirt/libvirt-domain.h | 10 ++
src/qemu/qemu_migration.h| 1 +
src/qemu/qemu_migration_params.c | 32
QEMU now supports multifd-compression=zstd for migration with enabled multifd.
Bring the support to libvirt as well.
Claudio Fontana (1):
qemu: migration: expose qemuMigrationParamsSetString
Oleg Vasilev (2):
qemu: migration: implement zstd compression
tests: qemumigparams: test for zstd
From: Claudio Fontana
change from static to external linkage, and move the
function close to the other similar ones, near
qemuMigrationParamsSetULL.
Signed-off-by: Claudio Fontana
Signed-off-by: Oleg Vasilev
---
src/qemu/qemu_migration_params.c | 47 +++-
Here we add one more way to test migration parameters, namely: from vir params.
This allows to test the logic of (libvirt) compression->(qemu)
multifd-compression
Signed-off-by: Oleg Vasilev
---
tests/qemumigparamsdata/zstd.json | 4 ++
tests/qemumigparamsdata/zstd.reply | 7 +++
On Mon, Apr 17, 2023 at 10:52:01AM -0600, Jim Fehlig wrote:
> Jim Fehlig (3):
> qemu: Change default machine type for ARM
> qemu: Change default machine type for RISC-V
> NEWS: Mention change of default machine type for ARM and RISC-V
Nit in 3/3 to be taken care of before pushing.
On Mon, Apr 17, 2023 at 10:52:04AM -0600, Jim Fehlig wrote:
> * **Improvements**
>
> +* qemu: Change default machine type for ARM and RISC-V
> +
> +ARM and RISC-V architectures now use the ``virt`` machine type by
> default.
> +The previous defaults were nearly unusable and had to be
On Tue, Apr 18, 2023 at 02:59:26AM -0400, Nick Guenther wrote:
> The qemu driver creates IPC sockets using absolute paths,
> but under POSIX socket paths are constrained pretty tightly.
> On systems with homedirs on an unusual mount point, like
> network homedirs, or just particularly long
On 4/17/23 18:40, Peter Maydell wrote:
The 'singlestep' member of StatusInfo has never done what the QMP
documentation claims it does. What it actually reports is whether
TCG is working in "one guest instruction per translation block" mode.
We no longer need this field for the HMP 'info
On 4/17/23 18:40, Peter Maydell wrote:
Currently we report whether the TCG accelerator is in
'one-insn-per-tb' mode in the 'info status' output. This is a pretty
minor piece of TCG specific information, and we want to deprecate the
'singlestep' field of the associated QMP command. Move the
On 4/17/23 18:40, Peter Maydell wrote:
The only place left that looks at the old 'singlestep' global
variable is the TCG curr_cflags() function. Replace the old global
with a new 'one_insn_per_tb' which is defined in tcg-all.c and
declared in accel/tcg/internal.h. This keeps it restricted to
On 4/17/23 18:40, Peter Maydell wrote:
@@ -219,8 +221,8 @@ static void tcg_set_one_insn_per_tb(Object *obj, bool
value, Error **errp)
{
TCGState *s = TCG_STATE(obj);
s->one_insn_per_tb = value;
-/* For the moment, set the global also: this changes the behaviour */
-
On Tue, Apr 18, 2023 at 02:59:26 -0400, Nick Guenther wrote:
> The qemu driver creates IPC sockets using absolute paths,
> but under POSIX socket paths are constrained pretty tightly.
> On systems with homedirs on an unusual mount point, like
> network homedirs, or just particularly long
The qemu driver creates IPC sockets using absolute paths,
but under POSIX socket paths are constrained pretty tightly.
On systems with homedirs on an unusual mount point, like
network homedirs, or just particularly long usernames, this
could make starting VMs under qemu:///session impossible.
29 matches
Mail list logo
