Package Details: xen-docs 4.19.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: 186
Popularity: 0.77
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-09-20 00:31 (UTC)

Dependencies (35)

Required by (1)

Sources (7)

Pinned Comments

Refutationalist commented on 2024-05-22 22:08 (UTC) (edited on 2024-05-23 00:07 (UTC) by Refutationalist)

As of now (2024-22-05) Xen with stubdom doesn't build because of a problem in the imported code. Been this way for about two weeks. Anyone else seeing this behavior?

Also, there is a lot of work happening on Xen in my development repo, thanks to @Serus. Check it out at: https://github.com/refutationalist/saur

Latest Comments

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

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

kantras commented on 2014-09-10 21:15 (UTC)

tritron: Ok, my first instinct is that you have an older version of 09_xen installed in /etc/grub.d; the newer one that I editted doesn't have that particular check in it. Check in case you somehow have multiple copies of 09_xen in the /etc/grub.d folder. The newest verion should also have a 'Modified by' comment in it.

tritron commented on 2014-09-10 20:48 (UTC)

### BEGIN /etc/grub.d/09_xen ### Cannot find grub config file, exiting.

kantras commented on 2014-09-10 20:44 (UTC)

tritron: Ok, so the file naming looks good - what do you get when you run the following as root: 'grub-mkconfig | grep 09' ?

tritron commented on 2014-09-10 20:09 (UTC)

efi initramfs-linux-fallback.img vmlinuz-linux grub initramfs-linux.img xen-4.4.1.gz

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