Package Details: xen-docs 4.18.1pre-1

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.45
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-01-19 23:00 (UTC)

Required by (1)

Sources (17)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 101 Next › Last »

Sven commented on 2022-02-13 09:44 (UTC)

build_qemu=false makepkg -sc fails with rm: cannot remove '/home/skoehler/aur/xen/pkg/xen/usr/share/qemu-xen': No such file or directory

Refutationalist commented on 2022-02-06 14:16 (UTC)

Hello! Here's 4.16.0-2.

As I mentioned earlier, qemu and stubdom, if built, now generate packages rather than being built into xen itself. As a reminder, if you need stubdom, you can pass build_stubdom=true to makepkg. Similarly, passing build_qemu=false will prevent the package from building qemu-xen.

I am working on that OVMF patch, and should have it in shortly.

ska67 commented on 2022-01-30 16:58 (UTC)

The use of SDL requires the new dependency libxi, see https://github.com/libsdl-org/SDL/issues/4938

@Sven Take a look into the PKGBUILD file, you will find the answer there :)

Sven commented on 2022-01-03 00:01 (UTC)

Is there a way to build xen without qemu? I only have guests with paravirtualized hardware (pvh guests) and building qemu takes a lot of time and probably has a lot of dependencies.

ska67 commented on 2022-01-02 14:19 (UTC) (edited on 2022-01-02 14:21 (UTC) by ska67)

OVMF from the edk2-ovmf package can no longer be used with Xen because Xen support has been removed from the x64 platform target. See my last post in arch linux forum: https://bbs.archlinux.org/viewtopic.php?id=269628

OVMF shipped with this Xen package cannot be built due to an upstream error. @Refutationalist, I have a working patch that I will email to you.

Btw, the specific platform target OvmfXen is supposed to be bootable in PVH type DomUs, but I couldn't get that to work.

Refutationalist commented on 2021-12-28 17:47 (UTC) (edited on 2021-12-28 17:47 (UTC) by Refutationalist)

@ska64 I don't work with windows very much at all, so needing TPM for win11 didn't occur to me. I've pushed the changes to AUR and I'll consider what I might do to improve stubdom.

ska67 commented on 2021-12-28 16:20 (UTC)

Your updated package on Github works out of the box. Maybe you could surround the new ninja makedepends with apostrophes, but it compiles without that change.

I tested with and without build_stubdom=true, it compiles and runs. Qemu is built and running as well.

The stubdoms are needed for virtual TPMs. I want to use them to store a LUKS key. But maybe someone else needs them to start Windows?

Refutationalist commented on 2021-12-26 19:29 (UTC) (edited on 2021-12-26 19:32 (UTC) by Refutationalist)

I do not have 4.16 in yet, but I suspect a lot of people by now know that 4.16 is compiling cleanly without extra patches. I just haven't had a chance to test it, or heard of anyone else testing it, so I haven't pushed my changes. I do have a simply updated package in my repo (https://github.com/refutationalist/saur) if you're interested in testing.

So, still out of date officially, but if I can get some confirmations that it works, I can push it here and leaving dealing with stubdom when I get back.

Other notes:

1) I got a request to leave stubdom in. Maybe I could make it part of the split package config? Looking into that, but probably not. The age of the extfiles needed for stubdom is starting to worry me and conflating with the "secure" aspects of stubdom. Part of what moved me to subdomless PVH.

2) I'm not able to recreate the qemu conflicts.

3) If building QEMU, we now need ninja.

4) I'm going to be playing with a Honeycomb LX2, so I'm hoping to have a version of xen that runs under alarm. Building for arm is really different, however.

ArthurBorsboom commented on 2021-10-24 09:33 (UTC)

On my system, the Xen 4.15.1-1 package fails to build. Any pointers ? GCC v11.1.0 ?

xentoollog_stubs.c:57: error: "Some_val" redefined [-Werror]
   57 | #define Some_val(v) Field(v,0)
      | 
In file included from /usr/lib/ocaml/caml/alloc.h:24,
                 from xentoollog_stubs.c:23:
/usr/lib/ocaml/caml/mlvalues.h:396: note: this is the location of the previous definition
  396 | #define Some_val(v) Field(v, 0)
      | 
cc1: all warnings being treated as errors
...
...
...
==> ERROR: A failure occurred in build().

micwoj92 commented on 2021-10-13 19:02 (UTC)

I think it should conflict with qemu by default

error: failed to commit transaction (conflicting files)
xen: /usr/share/locale/bg/LC_MESSAGES/qemu.mo exists in filesystem (owned by qemu)
xen: /usr/share/locale/de_DE/LC_MESSAGES/qemu.mo exists in filesystem (owned by qemu)
xen: /usr/share/locale/fr_FR/LC_MESSAGES/qemu.mo exists in filesystem (owned by qemu)
xen: /usr/share/locale/hu/LC_MESSAGES/qemu.mo exists in filesystem (owned by qemu)
xen: /usr/share/locale/it/LC_MESSAGES/qemu.mo exists in filesystem (owned by qemu)
xen: /usr/share/locale/sv/LC_MESSAGES/qemu.mo exists in filesystem (owned by qemu)
xen: /usr/share/locale/tr/LC_MESSAGES/qemu.mo exists in filesystem (owned by qemu)
xen: /usr/share/locale/zh_CN/LC_MESSAGES/qemu.mo exists in filesystem (owned by qemu)
Errors occurred, no packages were upgraded.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 101 Next › Last »