You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I use the latest QEMU-NYX, the kernel modules kvm and kvm-intel (built for kernel 5.10.75) do not support the KVM_CAP_DIRTY_LOG_RING feature, resulting in errors during execution.
If I use an older version of QEMU-NYX to avoid the above issue, it lacks support for the critical fast_vm_reload feature, which is required for my use case.
3. Steps to Reproduce:
Build and load kvm and kvm-intel modules from the kernel 5.10.75 source.
Install the latest QEMU-NYX and attempt to run a virtual machine.
Observe the error related to KVM_DIRTY_LOG_RING.
Downgrade to an older QEMU-NYX version and retry.
Observe that fast-vm-load functionality is missing.
4. Expected Behavior:
A compatible combination of kernel modules and QEMU-NYX should support both KVM_DIRTY_LOG_RING and fast-vm-load.
5.Actual Behavior:
Unable to use both features simultaneously with any available combination of kernel and QEMU versions.
The text was updated successfully, but these errors were encountered:
Thank you for your response! I attempted to download the KVM-Nyx-6.8 release package from the link you provided, but it seems the download page returns a 404: Not Found error.
To proceed, I downloaded the KVM-Nyx-6.0 release package and tried to build the kvm.ko and kvm-intel.ko files using the compile_kvm_nyx_standalone.sh script. However, the process is stuck at the make oldconfig step, even after running overnight.
Could you please provide precompiled versions of the kvm.ko and kvm-intel.ko files, especially for the 6.8 release? This would greatly help in resolving the compatibility issues I am facing.
I encountered compatibility issues when trying to use KVM-NYX with specific kernel and QEMU versions. Below are the details:
1. Environment:
2. Observed Issues:
3. Steps to Reproduce:
4. Expected Behavior:
5.Actual Behavior:
The text was updated successfully, but these errors were encountered: