Package Details: xen-stubdom 4.20.0-2

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)

Dependencies (42)

Required by (3)

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 2 3 4 5 6 7 8 9 10 .. 101 Next › Last »

FringeLunatic commented on 2022-07-03 01:34 (UTC) (edited on 2022-07-03 14:00 (UTC) by FringeLunatic)

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.

Refutationalist commented on 2022-07-02 19:39 (UTC)

@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.

Shapito commented on 2022-07-02 09:48 (UTC)

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.

ArthurBorsboom commented on 2022-06-12 08:04 (UTC) (edited on 2022-06-12 08:05 (UTC) by ArthurBorsboom)

If I want to install the xen-qemu-builtin package, I have to manually delete two files, which conflict with the xen package; then it can be installed without a conflict. Is this caused by the xen package?

[arthur@xen1 xen]$ sudo pacman -U xen-qemu-builtin-4.16.1-1-x86_64.pkg.tar.xz
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) xen-qemu-builtin-4.16.1-1

Total Installed Size:  244.04 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                                            [#########################################################################] 100%
(1/1) checking package integrity                                                                                          [#########################################################################] 100%
(1/1) loading package files                                                                                               [#########################################################################] 100%
(1/1) checking for file conflicts                                                                                         [#########################################################################] 100%
error: failed to commit transaction (conflicting files)
xen-qemu-builtin: /usr/lib/xen/bin/qemu-keymap exists in filesystem (owned by xen)
xen-qemu-builtin: /usr/lib/xen/libexec/vhost-user-gpu exists in filesystem (owned by xen)
[arthur@xen1 xen]$ sudo rm /usr/lib/xen/bin/qemu-keymap
[arthur@xen1 xen]$ sudo rm /usr/lib/xen/libexec/vhost-user-gpu
[arthur@xen1 xen]$ sudo pacman -U xen-qemu-builtin-4.16.1-1-x86_64.pkg.tar.xz

vibrion commented on 2022-05-31 14:43 (UTC) (edited on 2022-05-31 14:48 (UTC) by vibrion)

After last xen upgrade Im running into a strange error at bootup: none domain are up. Searching logs for a clue i found this:

May 31 11:08:16 bakaneko systemd[1]: Finished Xendomains - start and stop guests on boot and shutdown. May 31 11:08:16 bakaneko xendomains[369]: [done] May 31 11:08:16 bakaneko xendomains[369]: ! May 31 11:08:16 bakaneko xendomains[369]: An error occurred while creating domain new_moodle_eest1-vm.cfg: May 31 11:08:16 bakaneko xendomains[435]: libxl: error: libxl_domain.c:1064:domain_destroy_cb: Domain 4:Destruction of domain failed May 31 11:08:16 bakaneko xendomains[435]: libxl: error: libxl_domain.c:1137:domain_destroy_callback: Domain 4:Unable to destroy guest May 31 11:08:16 bakaneko xendomains[435]: libxl: error: libxl_domain.c:1183:libxl__destroy_domid: Domain 4:Non-existant domain May 31 11:08:16 bakaneko xendomains[435]: libxl: error: libxl_create.c:1289:initiate_domain_create: Domain 4:Unable to set disk defaults for disk 0 May 31 11:08:16 bakaneko xendomains[435]: libxl: error: libxl_device.c:399:libxl__device_disk_set_backend: Disk vdev=xvda failed to stat: /dev/mapper/VM_bakaneko_vg-new> May 31 11:08:16 bakaneko xendomains[369]: new_moodle_eest1-vm.cfg

Despite this if xendomains is manually restarted everything boots up normally. Another error is related to qemu-dom0 backend:

May 31 11:36:42 bakaneko systemd[1]: Starting qemu for xen dom0 disk backend... May 31 11:36:42 bakaneko systemd[1]: Started qemu for xen dom0 disk backend. May 31 11:36:42 bakaneko qemu-system-i386[964]: qemu-system-i386: -xen-domid 0: Option not supported for this target.

Also at system upgrade a question arise for qemu-desktop replacement for qemu (dont know its related or not) Any suggestion? Thanks!!

Refutationalist commented on 2022-05-16 19:07 (UTC) (edited on 2022-05-18 22:19 (UTC) by Refutationalist)

Here is 4.16.1-1.

  • Has patches to compile under GCC12, entirely by disabling some error checks.
  • The hvmloader patch has been brought in, fixing that problem.
  • I dropped working on the OVMF fixes, since that's a separate project from Xen.
  • I have tested it on exactly two systems, both of which run AMD processors. Error reports and patches welcome.

UPDATE 2022-05-18: I have one machine running a Ryzen 7 5700G with an Intel 82576 that crashes on iommu. I'm attempting to get help with the problem, but if anyone else has a problem I'd like to hear about it.

Refutationalist commented on 2022-05-13 08:32 (UTC)

@Sven I have a 4.16.1-0 in my repo that compiles cleanly except for stubdom, mostly thanks to an OpenSUSE patch that sets a bunch exceptions here and there. Still looking into the stubdom bit before I update AUR.

Sven commented on 2022-05-12 21:45 (UTC)

Xen 4.16.0-3 doesn't seem to build with gcc 12.1.0

Refutationalist commented on 2022-04-20 21:59 (UTC)

Hoping to get to it this week. Haven't had much time in front of a computer myriad of reasons.

ArthurBorsboom commented on 2022-04-14 07:05 (UTC)

@Refutationalist : any change of applying this patch to the PKGBUILD ?