cpu vmx migration issue

2024-05-20 Thread d tbsky
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

Re: cpu vmx migration issue

2024-05-22 Thread d tbsky
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

Re: cpu vmx migration issue

2024-05-23 Thread d tbsky
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

Re: cpu vmx migration issue

2024-05-28 Thread d tbsky
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

Re: cpu vmx migration issue

2024-06-25 Thread d tbsky
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

hard-disk via virtio-blk under windows (discard_granularity=0)

2024-11-13 Thread d tbsky
Hi: few years ago virtio-blk device was showing as hard-disk under windows. recent years the driver change the device to show as thin-provisioned disk. the change is good for ssd, but not so good for raw hard-disk. under windows server 2022 the default virtio-blk situation is quite bad, ssd

Re: hard-disk via virtio-blk under windows (discard_granularity=0)

2024-11-15 Thread d tbsky
Martin Kletzander > > I wonder if libvirt would be changed to accept > >"discard_granularity='0'" so the traditional hard-disk can be > >recognized under windows again. > > > > That should be possible, yes. Given the behaviour described above it > should be done (although it feels like there

Re: hard-disk via virtio-blk under windows (discard_granularity=0)

2024-11-15 Thread d tbsky
Andrea Bolognani > I'd also be surprised if this only affected Windows. Wouldn't Linux > guests likely see a similar change in how the device is presented? I don't understand all the impact under windows. but defrag is the obvious part. by default windows will do disk optimization weekly. trim wa