Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libvirt is too old for qemu in unstable #81102

Closed
wedens opened this issue Feb 26, 2020 · 2 comments · Fixed by #81161
Closed

libvirt is too old for qemu in unstable #81102

wedens opened this issue Feb 26, 2020 · 2 comments · Fixed by #81161

Comments

@wedens
Copy link

wedens commented Feb 26, 2020

Currently, qemu version is 4.2.0 and libvirt is 5.4.0. As I've already mentioned here there are some incompatibilities between qemu >= 4.1 and libvirt < 5.6.0. In some cases it may significantly affect performace (e.g. typical windows vm with vfio).

The latest libvirt version is 6.0.0. So, I think it's time to upgrade.

Unfortunately, it seems that something has changed in libvirt build process and just changing version/hash in existing derivation is not enough.

/cc @fpletz @globin (libvirt maintainers)

@wedens
Copy link
Author

wedens commented Feb 26, 2020

Turns out Nix was adding --disable-dependency-tracking flag which caused weird build failures.

After adding dontAddDisableDepTrack = true and some other small tweaks, it builds.

I'll try to open a PR myself this week after I test it. I won't be able to test it on Darwin, though.

(apparently autotools will be replaced with meson soon in libvirt)

@fpletz fpletz added this to the 20.03 milestone Feb 26, 2020
@fpletz fpletz self-assigned this Feb 26, 2020
@wedens wedens mentioned this issue Feb 27, 2020
10 tasks
@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/nixos-20-03-beta/5935/22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants