Bo Chen

It is very strange that I can't reproduce the above errors offline when I ran the complete integration test suite with `musl` build on the aarch64 worker machine manually. I...

Right. That's the tricky part. We can't reproduce the error manually, even though the CI is using the same machine...

@tmakatos @jlevon I wonder do you have an estimated timeline for adding the v2 migration support to upstream libvfio-user?

@jlevon Thank you for the quick response. I would love to help and contribute. I know @tmakatos had a WIP branch for this work: https://github.com/tmakatos/muser/tree/migration-v2. Is this the right place...

> Yes, this is the right branch, specifically this commit: [tmakatos@059aa82](https://github.com/tmakatos/muser/commit/059aa82ff813221e4f42624dcb2b32c001a726af) > > Could you try to see whether the commit makes sense and if not I can see how...

> > Found the issue. It was a problem w/ CloudHv build of UEFI firmware rather than a problem with cloud-hypervisor itself. What is the review process for cloud-hypervisor flavored...

@weltling Would you please help @thomasbarrett here to setup an environment for reproducing the windows guest error?

Looks like a failed kvm call to get "xsave struct" [1]. Can you migrate without enabling the "amx" feature on the same machine? [1] https://github.com/cloud-hypervisor/cloud-hypervisor/blob/main/hypervisor/src/kvm/mod.rs#L1829

Also, our recommended host kernel version now is 5.13 [1]. Can you please try if it works on a newer kernel? [1] https://github.com/cloud-hypervisor/cloud-hypervisor#host-os

> Looks like you need a newer host kernel - [torvalds/linux@be50b20](https://github.com/torvalds/linux/commit/be50b2065dfa3d88428fdfdc340d154d96bf6848) Also, the kvm-bindings crate needs to be updated with support of `KVM_CAP_XSAVE2` and Cloud Hypervisor may need change too...