Jiri Denemark
> > Thanks a lot for the logs. I think I know what the problem is and I'm
> > trying to reproduce locally and I hope to have a patch ready soon.
>
> This should be fixed by
> https://gitlab.com/libvirt/libvirt/-/commit/e622970c8785ec1f7e142d72f792d89f870e07d0
> and it will be include
On Fri, May 31, 2024 at 13:20:49 +0200, Jiri Denemark wrote:
> Hi.
>
> On Tue, May 28, 2024 at 23:55:16 +0800, d tbsky wrote:
> > Jiri Denemark
> > > Oh, are you saying that a domain with such active XML cannot be migrated
> > > and you see these three features reported as missing? Could you plea
Hi.
On Tue, May 28, 2024 at 23:55:16 +0800, d tbsky wrote:
> Jiri Denemark
> > Oh, are you saying that a domain with such active XML cannot be migrated
> > and you see these three features reported as missing? Could you please
> > provide debug logs from virtqemud (or libvirtd if you're running
>
Hi:
Jiri Denemark
> Oh, are you saying that a domain with such active XML cannot be migrated
> and you see these three features reported as missing? Could you please
> provide debug logs from virtqemud (or libvirtd if you're running
> monolithic daemon) from both sides of migration covering the f
Hi,
So it seems we have a bug regarding the new vmx features when computing
baseline CPU model. But it seems it's not the only thing...
On Fri, May 24, 2024 at 01:20:32 +0800, d tbsky wrote:
> Next test I add "vmx" feature to vm config(so it will look lik RHEL
> 9.3 config). the xml are the same
Hi:
> Jiri Denemark
> So could you also provide
> (1) the output of "virsh hypervisor-cpu-baseline" and
> (2) the element from the domain XML before it is started
> (3) and once it is running on the host from which migration fails?
sorry when I checked the vm with your theory(qemu will enab
On Wed, May 22, 2024 at 15:59:36 +0800, d tbsky wrote:
> Hi:
>
> Jiri Denemark
> > Interesting, hypervisor-cpu-baseline is supposed to provide an
> > intersection of both CPU models. I wonder whether we have a bug
> > somewhere, could you share the host-model definition from virsh
> > domcapabili
Hi:
Jiri Denemark
> Interesting, hypervisor-cpu-baseline is supposed to provide an
> intersection of both CPU models. I wonder whether we have a bug
> somewhere, could you share the host-model definition from virsh
> domcapabilities from both hosts? The easiest way is running
>
> $ virsh domc
Hi.
On Mon, May 20, 2024 at 21:04:59 +0800, d tbsky wrote:
> Hi:
> I update our RHEL9 system to RHEL 9.4, which brings libvirt 10.0.
> I try to calculate the cpu baseline for our two-node cluster with
> command "virsh domcapabilities" then "virsh hypervisor-cpu-baseline
> --migratable". the
Hi:
I update our RHEL9 system to RHEL 9.4, which brings libvirt 10.0.
I try to calculate the cpu baseline for our two-node cluster with
command "virsh domcapabilities" then "virsh hypervisor-cpu-baseline
--migratable". the result has many cpu features begin with "vmx".
the test cluster h
10 matches
Mail list logo
