Package Details: xen 4.20.0-2

Git Clone URL: https://aur.archlinux.org/xen.git (read-only, click to copy)
Package Base: xen
Description: Open-source type-1 or baremetal hypervisor
Upstream URL: https://xenproject.org/
Keywords: hypervisor virtualization xen
Licenses: GPL2
Submitter: sergej
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 184
Popularity: 0.033523
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2025-03-13 08:19 (UTC)

Dependencies (65)

Sources (13)

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:

  • stubdom is fixed by disabling the vtmp and vtpmmgr components. This gets rid of a few source files and our remaining patches.
  • Debug files are only removed if the debug option is not set in makepkg.cfg (or the PKGBUILD itself)
  • pygrub has been removed
  • optdepends are adjusted for the upcoming xen-grub split package for the various Xen flavored builds.

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

Latest Comments

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 .. 101 Next › Last »

jsteel commented on 2018-03-14 09:13 (UTC)

xen-qemu-dom0-disk-backend.service fails, libepoxy is needed: /usr/lib/xen/bin/qemu-system-i386: error while loading shared libraries: libepoxy.so.0: cannot open shared object file: No such file or directory

ianu commented on 2018-03-13 21:06 (UTC)

This change should fix it

    # XSA patches (Last checked: XSA-253)
    'bba1abb5e4368421de29385e37f8477bf3534d3ba3ff7e2aae9c9d3da53f1393'
-   '5276d63e3b2ffc5217981e7b683c28d75b81793af8d2ffc75566db39aaabbaef'
+   'fa8cd07b85a8ff29cba8d891f12f9be4b173dd91a58404aabbf49c3f83152af9'

dhlk commented on 2018-03-10 01:08 (UTC)

Looks like the checksum on xsa254-diff-release410-comet1.1.patch is incorrect.

baratharon commented on 2018-02-28 09:30 (UTC) (edited on 2018-02-28 09:30 (UTC) by baratharon)

Today I upgraded from 4.8 to 4.10, and I got this (no more information is available, so I don't know what should I do; also, google has no any usable info):

 xenstored.service - The Xen xenstore
   Loaded: loaded (/usr/lib/systemd/system/xenstored.service; enabled; vendor preset: disabled)
   Active: failed (Result: protocol) since Wed 2018-02-28 10:23:45 CET; 2min 6s ago
  Process: 506 ExecStart=/etc/xen/scripts/launch-xenstore (code=exited, status=0/SUCCESS)
  Process: 485 ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities (code=exited, status=0/SUCCESS)
 Main PID: 506 (code=exited, status=0/SUCCESS)

JohnTh commented on 2017-12-15 02:33 (UTC)

If your guest cannot see disks, make sure you have the xen-blkfront module loaded in your guest. You can use a serial port on the dom0 to get the full Xen log. I have a 4.10 PKGBUILD here: https://gitlab.com/archlinux-packages-johnth/xen

sniper7kills commented on 2017-12-15 02:05 (UTC)

@mbroemme if you happen to have a git repo or PKGBUILD for 4.10 I'd love to give it a try; for some reason I'm having issues with linux install disks not detecting the HDD on any VM I try to setup and also been getting some errors after xen boots prior to the kernel but haven't been able to capture them at all.

Hoping that 4.10 resolves these for me.

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 .. 101 Next › Last »