| Git Clone URL: | https://aur.archlinux.org/xen.git (read-only, click to copy) |
|---|---|
| Package Base: | xen |
| Description: | Xen hypervisor documentation and man pages |
| Upstream URL: | https://xenproject.org/ |
| Keywords: | hypervisor virtualization xen |
| Licenses: | GPL2 |
| Submitter: | sergej |
| Maintainer: | Refutationalist |
| Last Packager: | Refutationalist |
| Votes: | 185 |
| Popularity: | 0.46 |
| First Submitted: | 2009-11-09 11:22 (UTC) |
| Last Updated: | 2024-09-20 00:31 (UTC) |
I have reported the Xen building issue upstream.
https://lists.xenproject.org/archives/html/xen-devel/2022-10/msg00816.html
If I understood it correct, two possible solutions are:
Hopefully this is helpful in fixing the package.
Xen doesn't build anymore. I believe it is caused by the missing function 'bpf_program__set_socket_filter' of libbpf. Before this function was deprecated and now it has been removed (v1.0.1).
A downgrade to libbpf v0.8.1 fixes the Xen build problem. I recall vaguely that the downgrade of libbpg lead to qemu issues.
/bin/ld: libcommon.fa.p/ebpf_ebpf_rss.c.o: in function `ebpf_rss_load':
/home/arthur/.cache/yay/xen/src/xen-4.16.1/tools/qemu-xen-build/../qemu-xen/ebpf/ebpf_rss.c:52: undefined reference to `bpf_program__set_socket_filter'
collect2: error: ld returned 1 exit status
...
...
...
ninja: build stopped: subcommand failed.
make: *** [Makefile:156: run-ninja] Error 1
make: Leaving directory '/home/arthur/.cache/yay/xen/src/xen-4.16.1/tools/qemu-xen-build'
make[3]: *** [Makefile:212: subdir-all-qemu-xen-dir] Error 2
make[3]: Leaving directory '/home/arthur/.cache/yay/xen/src/xen-4.16.1/tools'
make[2]: *** [/home/arthur/.cache/yay/xen/src/xen-4.16.1/tools/../tools/Rules.mk:161: subdirs-install] Error 2
make[2]: Leaving directory '/home/arthur/.cache/yay/xen/src/xen-4.16.1/tools'
make[1]: *** [Makefile:66: install] Error 2
make[1]: Leaving directory '/home/arthur/.cache/yay/xen/src/xen-4.16.1/tools'
make: *** [Makefile:140: install-tools] Error 2
==> ERROR: A failure occurred in build().
Aborting...
-> error making: xen
I am not 100% sure, but Xen 4.16.2 might have been released, just not explicitly through the web interface.
https://downloads.xenproject.org/release/xen/4.16.2/
Also, while debugging a compilation problem, it seems that the newer version of dependency libbpf (1.0 vs 0.8) does not play nice with Xen 4.16.x
Xen 4.16.2 should be out soon, but I'm changing some of the ways this package compiles. First, the XSA patches always suggest that they be applied not to the tarball but to stable branch. I'd been meaning to do it for a while, but the retbleed patchset was the final nail in the tarball coffin.
There is a problem, however. Xen's builtin QEMU doesn't build properly at the moment, which is precisely the problem earlier packagers had to contend with. We really should see about separating that out, since it's a build-within-a-build.
So with that, plus a couple other issues-- how to version this and whether or not I should pin the PKGBUILD to a specific commit-- you can check out what I'm working on in my PKGBUILD repo: https://github.com/refutationalist/saur
EDIT: in a branch on that repo, I've removed QEMU building from the xen package entirely, and now have a xen-qemu package that builds QEMU fairly closely to how Xen itself builds it, so it shouldn't conflict with an existing QEMU installation. I'm thinking this may be the way to go for now, just in case there's some future push to get Xen into the repos and therefore use Arch's included qemu.
@Refutationalist During package creation, Qemu configuration detects needed options, two additional files can be created: /usr/lib/xen/bin/qemu-keymap /usr/lib/xen/libexec/vhost-user-gpu
These two files should also be removed when assembling the xen package, but only if they are present.
@straybit & @FringeLunatic
I've been working on this on and off. Can either of you try building Xen in a clean chroot to see if you get the same conflict? My packages don't create a qemu-keymap at all, and I do not build my packages on my workstation.
Like ArthurBorsboom and FringeLunatic I also get a conflicting file error:
Packages (3) xen-4.16.1-1 xen-docs-4.16.1-1 xen-qemu-builtin-4.16.1-1
...
error: failed to commit transaction (conflicting files)
/usr/lib/xen/bin/qemu-keymap exists in both 'xen' and 'xen-qemu-builtin'
Errors occurred, no packages were upgraded.
==> WARNING: Failed to install built package(s).
Like ArthurBorsboom, I get a conflicting file error:
error: failed to commit transaction (conflicting files)
/usr/lib/xen/bin/qemu-keymap exists in both 'xen' and 'xen-qemu-builtin'
Errors occurred, no packages were upgraded.
==> WARNING: Failed to install built package(s).
==> Cleaning up...
Any way to fix this conflict without removing "qemu-keymap?" I believe this is a bug because both "xen" and "xen-qemu-builtin" own "qemu-keymap." I don't want to report it as such if there's something obvious I'm missing but I've found nothing about it until a user reported it here.
@Shapito You need to add the PGP key to your keyring to verify the signature, and patch is part of base-devel, which is always assumed.
I get two errors when try to install this package.
==> Verifying source file signatures with gpg...
xen-4.16.1.tar.gz ... FAILED (unknown public key 83FE14C957E82BD9)
==> ERROR: One or more PGP signatures could not be verified!
And after adding --skippgpcheck makepkg flag usage.
==> Starting prepare()...
==> Applying GCC 12.1 fixes...
/home/<user_name>/aur/xen/PKGBUILD: line 172: patch: command not found
==> ERROR: A failure occurred in prepare().
Maybe, you need to add patch dependency.
Pinned Comments
Refutationalist commented on 2024-12-06 01:37 (UTC)
Please Note: Per best-practices by upstream this package follows the git stable branch. Minor releases do not require a version bump and the PKGBUILD will provide the appropriate version number.
stubdom is still broken.