Hey guys. I have been working on a PKGBUILD but haven't been able to test it.
Can anyone see if there are any issues? If everything is fine we can go ahead and move it to the official repos.
Git Clone URL: | https://aur.archlinux.org/xen.git (read-only, click to copy) |
---|---|
Package Base: | xen |
Description: | Xen hypervisor stubdom files |
Upstream URL: | https://xenproject.org/ |
Keywords: | hypervisor virtualization xen |
Licenses: | GPL2 |
Submitter: | sergej |
Maintainer: | Refutationalist |
Last Packager: | Refutationalist |
Votes: | 184 |
Popularity: | 0.071098 |
First Submitted: | 2009-11-09 11:22 (UTC) |
Last Updated: | 2025-03-13 08:19 (UTC) |
« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 101 Next › Last »
Hey guys. I have been working on a PKGBUILD but haven't been able to test it.
Can anyone see if there are any issues? If everything is fine we can go ahead and move it to the official repos.
This commit fixes the current build issue: http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=368375d7360a38c27de8e0276498bdd29e9e8a03
Sadly that commit hasn't been backported to the 4.12 branch, so it has to be patched during makepkg. I suppose you could also downgrade your ocaml to something before 4.09 and things would work again too...but that seems foolish.
Possible solutions here:
Fix up the current 4.12.1 build like so: https://github.com/invisiblek/xen-aur/commits/4.12.1-2
Step one plus update to 4.12.2 while we're at it: https://github.com/invisiblek/xen-aur/commits/4.12.2-1
Move to 4.13.0: https://github.com/invisiblek/xen-aur/commits/4.13.0-1
All three do require this minor patch to remove a now deprecated flag in qemu: https://github.com/invisiblek/xen-aur/commit/168fbdaa33265c4902ebfd5e8def892b0c2c14ca
I'll be testing with my 4.13.0-1 branch for now.
I see FFY00 mentioned official repos a couple months ago, unsure the status on that as of yet. Maybe I'll ping them on irc one of these days and see where that whole thing is at.
For now at least we can have working builds again :)
Getting the same error as @schweratlet, installing with pikaur.
@mbroemme I'm getting the same error when trying to install (installing with yay -S xen. though I hope it doesn't make a difference.
make -C xentoollog install make[8]: Entering directory '/home/shogoro/.cache/yay/xen/src/xen-4.12.1/tools/ocaml/libs/xentoollog' python2 genlevels.py _xtl_levels.mli.in _xtl_levels.ml.in _xtl_levels.inc MLDEP MLC xentoollog.cmo MLA xentoollog.cma CC xentoollog_stubs.o xentoollog_stubs.c: In function 'stub_xtl_ocaml_vmessage': xentoollog_stubs.c:93:16: error: initialization discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers] 93 | value func = caml_named_value(xtl->vmessage_cb) ; | ^~~~~~~~~~~~~~~~ xentoollog_stubs.c: In function 'stub_xtl_ocaml_progress': xentoollog_stubs.c:123:16: error: initialization discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers] 123 | value func = caml_named_value(xtl->progress_cb) ; | ^~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors )
It leaves a whole bunch of directories and then.
make[1]: [Makefile:74: install] Error 2 make[1]: Leaving directory '/home/shogoro/.cache/yay/xen/src/xen-4.12.1/tools' make: [Makefile:127: install-tools] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Error making: xen
Is this in any way my fault? Any advice? I have installed Xen successfully before, more specifically twice 4-5 months ago both on a fresh install. This is the first time I'm encountering such an error. I've tried it several times.
@FFY00 oh please do!
In regards to CIS, this is the only package remaining that we use outside of the official repos.
Hey, I want to move this to the official repos. Are you ok with that?
@mbroemme - do you plan on dropping the python2 dependency in favor of python? Also, would you be willing to consider switching the brltty dependency to the brltty-minimal available in AUR?
Thanks in advance!
4.13.0 is available, will built and merge all changes requested in the comments in the next few days.
I have spent many hours the last days trying to get a VM running with UEFI (ovmf), but Xen keeps crashing (visible by "xl dmesg").
It is related to the used Arch ovmf package in combination with the Xen configure parameter in PKGBUILD
--with-system-ovmf=/usr/share/ovmf/x64/OVMF_CODE.fd
After removing this parameter, Xen uses its 'native' ovmf binary provided by
/usr/lib/xen/boot/ovmf.bin
and not the one from the arch ovmf package provided by
/usr/share/ovmf/x64/OVMF_CODE.fd /usr/share/ovmf/x64/OVMF_VARS.fd
Would you mind to either (for now) remove the ovmf configure parameter and/or solve the cause of the crashing Xen with the Arch ovmf package?
Pinned Comments
Refutationalist commented on 2025-03-12 12:06 (UTC) (edited on 2025-03-13 08:23 (UTC) by Refutationalist)
We've moved to the newly-stable 4.20.0 branch. There are also other changes:
If you're still using pygrub note that it is deprecated. The solution is to build PV grub instead, which used to be in AUR but is now missing. I am asking a couple questions on the mailing list, and I intend to put my current build of xen-grub (which supersedes xen-pvhgrub) on AUR as soon as possible. If you need to build it before that occurs, you can find it in my PKGBUILD repo.
EDIT: 4.20.0-2 adds support for the xen-edk2 package, which has a fixed UEFI for xen