Bo Chen

> To resolve the above issue, I attempted to use attributes like below: > > ``` > #[cfg(target_env = "musl")] > msghdr.msg_iovlen = data_vecs.len() as i32; > #[cfg(not(target_env = "musl"))]...

Same here.

@liuw Any updates regarding this issue? It would be good if we can move the common "test_vfio" test back to Azure VM worker for running on each PR.

> there were quite a few fixes to the host hypervisor in the past year. Can you just reenable this test case? @liuw This is good to know. We can't...

Opened a PR #5717 to try the test on the latest Azure VMs, and looks like the test is still failing for the same reason: ``` [2023-08-30T21:14:46.959Z] [ 31.134641] bash[1702]:...

Thank you for the heads-up. I look forward to seeing the v2 spec and implementation upstreamed, and we will enable it from Cloud Hypervisor side.

@tmakatos That's good to know. No, we are not in hurry and we can wait for the client implementation. FWIW, the `vfio-user` protocol related implementation was moved to its own...

> > No, we are not in hurry and we can wait for the client implementation. > > @likebreath I thought that the cloud hypervisor was the vfio-user client? Sorry...

Thank you for the context. That's good to know. Please keep us posted here. Speaking of timeline, I personally won't have time for this quarter, and can revisit this topic...

> `reuse lint` reports many issues: > > * files with copyright information: 212 / 342 > * files with license information: 193 / 342 > > I've created workflow...