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.069676
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 .. 43 44 45 46 47 48 49 50 51 52 53 .. 101 Next › Last »

kantras commented on 2014-09-28 14:47 (UTC)

I've actually just been rebuilding my virtual environment here at home to allow me to better test from scenarios such as that; always a good idea to review after something like hardware failure.

hbc2 commented on 2014-09-28 13:05 (UTC)

ArthurBorsboom's issue is easy to duplicate on a fresh install of arch. (yup, installing arch is easy if you've installed it 50+ times like I have while learning linux. :P ) Seriously, though, on a fresh install with nothing else installed I ran into the same exact problem Mr. Borsboom did. I'm using grub not UEFI. I'm building right out of the AUR. cd /root wget https://aur.archlinux.org/packages/xe/xen/xen.tar.gz tar -xvf xen.tar.gz cd xen makepkg -s --asroot I'm going to poke around in the make files. Never done that before. This should be fun. :)

ArthurBorsboom commented on 2014-09-17 13:00 (UTC)

When I remove the following two lines from the PKGBUILD, the package is build finishes. mv etc/default/xencommons etc/conf.d/xencommons mv etc/default/xendomains etc/conf.d/xendomains There are these two warnings: ==> WARNING: backup entry file not in package : etc/conf.d/xendomains ==> WARNING: backup entry file not in package : etc/conf.d/xencommons Probably coming from: backup=(etc/modules-load.d/$pkgname.conf etc/$pkgname/xl.conf etc/conf.d/xen{stored,consoled,domains,commons} etc/$pkgname/grub.conf) Maybe this gives a clue?

ArthurBorsboom commented on 2014-09-17 12:36 (UTC)

@Zir_blazer, thanks for the suggestion. I did exactly what you proposed, unfortunately with the same result. install -d -m0755 -p "/tmp/makepkg/xen/pkg/xen/usr/lib/xen/boot" install -m0644 -p mini-os-x86_32-grub/mini-os.gz "/tmp/makepkg/xen/pkg/xen/usr/lib/xen/boot/pv-grub-x86_32.gz" make[1]: Leaving directory '/tmp/makepkg/xen/src/xen-4.4.1/stubdom' mv: cannot stat ‘etc/default/xencommons’: No such file or directory ==> ERROR: A failure occurred in package(). Aborting... [arthur@orion1695 xen]$ Any other ideas?

zir_blazer commented on 2014-09-17 08:59 (UTC)

@ ArthurBorsboom On my experience, I have seen similar errors when re-building xen package on the same folder than a previous build. Seems like it is not deleting or replacing something. Basically, everytime you want to build, try to start from scratch on a new folder, or delete the previous build. Try this: mkdir /home/builds cd /home/builds curl -O https://aur.archlinux.org/packages/xe/xen/xen.tar.gz tar -xzf xen.tar.gz cd xen makepkg Should work.

ArthurBorsboom commented on 2014-09-17 06:51 (UTC)

Hi Kantras, Do you have another guess what might be causing the build problem on my system? Xen still doesn't upgrade from 4.4.0 to 4.4.1 with the following error. ld: warning: section `.bss' type changed to PROGBITS gzip -f -9 -c /tmp/makepkg/xen/src/xen-4.4.1/stubdom/mini-os-x86_32-grub/mini-os >/tmp/makepkg/xen/src/xen-4.4.1/stubdom/mini-os-x86_32-grub/mini-os.gz make[2]: Leaving directory '/tmp/makepkg/xen/src/xen-4.4.1/extras/mini-os' install -d -m0755 -p "/tmp/makepkg/xen/pkg/xen/usr/lib/xen/boot" install -m0644 -p mini-os-x86_32-grub/mini-os.gz "/tmp/makepkg/xen/pkg/xen/usr/lib/xen/boot/pv-grub-x86_32.gz" make[1]: Leaving directory '/tmp/makepkg/xen/src/xen-4.4.1/stubdom' mv: cannot stat ‘etc/default/xencommons’: No such file or directory ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build xen. ==> Restart building xen ? [y/N] ==> ---------------------------- ==> ==> ERROR: unable to update ==> upgrading SVN/CVS/HG/GIT package

zir_blazer commented on 2014-09-16 11:11 (UTC)

Also, regarding using Xen with UEFI, I confirm success, but I'm still unsure about the proper procedure. Recompiling binutils for x86_64-pep, copying the xen.efi file to /boot, making a xen.cfg file for it and modifying the Boot Manager accordingly are well know and distro independent. In my case, the new Linux kernel 3.17 that brings official Dom0 UEFI booting support is absolutely required (Builded it from AUR linux-git package with default config), I have never managed to boot a UEFI Dom0 in my computer in any other fashion, through some others did. However, for a fresh UEFI install on Arch Linux, is there anything else to do? I mean, when you install the xen package with pacman, there are a lot of other things that are done like placing some files in the systemd and config directories, that are later used for xen. You can then easily enable the xen related services like xenconsoled and xenstored using systemctl because they're already there. If I do a mere copy of the xen.efi file to /boot, I can get it boot Dom0 in UEFI, but after that, I supposed I wouldn't get very far due to the lack of those supporting services. What I should do? To organize a bit the questions: 1- What exactly is xen.efi? It is a direct EFI replacement for the classic GZ xen image file that also sits on /boot? 2- To properly do a fresh Xen UEFI install, should I copy the .service files to systemd directories manually, or install xen package as normal then copy the xen.efi to /boot and modify the Boot Manager to use that one?

zir_blazer commented on 2014-09-15 16:53 (UTC)

The folder where the .efi file is at is <xen build directory>/pkg/xen/usr/lib/efi/xen-4.4.1.efi. I tried it yesterday doing a manual build (Downloaded with curl the tarball, decompressed it, then builded it with makepkg) and it worked, after building binutils with x86_64-pep support, obviously.

reynoldsbd commented on 2014-09-15 14:14 (UTC)

Rebuilt binutils with support for x86-64-pep as specified on wiki, then built xen, but there is no EFI binary at /usr/lib/efi/xen-4.4.1.efi.

ArthurBorsboom commented on 2014-09-11 06:33 (UTC)

@kantras, I build my package by entering "yaourt -Suya" which updates all packages on my system. AFAIK, I have a normal Arch kernel. Since I don't know what hardware it is, I have created a system overview with inxi. http://pastebin.com/pFKZaJw6 AFAIK, I have no special packages except Xen. http://pastebin.com/hS8VvWw3

« First ‹ Previous 1 .. 43 44 45 46 47 48 49 50 51 52 53 .. 101 Next › Last »