Package Details: xen 4.19.1pre-1

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: 185
Popularity: 0.67
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-09-20 00:31 (UTC)

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 .. 67 68 69 70 71 72 73 74 75 76 77 .. 101 Next › Last »

zootboy commented on 2013-05-23 13:22 (UTC)

This PKGBUILD works as-is for me, so I don't think it's that. @3000, make sure you have the entire base-devel group installed ("pacman -S base-devel") because if you were missing patch, you may be missing other important tools. Also, why are you using the --asroot flag? You should not be building packages as root. Use an unprivileged user to make the package, then use root to install the package.

tritron commented on 2013-05-23 13:15 (UTC)

Edit PKGBUILD and remove offending line that starts with MV /etc/init.d/

3000 commented on 2013-05-23 10:51 (UTC)

i am having the same error message as SeraphZA any help is hugely appreciated, for me this is the last hurdle to finally build my System for good. this is the Output of the error: make[2]: Leaving directory `/root/xen/src/xen-4.2.2/extras/mini-os' install -d -m0755 -p "/root/xen/pkg/xen/usr/lib/xen/boot" install -m0644 -p mini-os-x86_32-grub/mini-os.gz "/root/xen/pkg/xen/usr/lib/xen/boot/pv-grub-x86_32.gz" make[1]: Leaving directory `/root/xen/src/xen-4.2.2/stubdom' mv: cannot stat âetc/init.dâ: No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

3000 commented on 2013-05-20 17:51 (UTC)

thanks for the fast response! That was it, I was just executing "makepkg --asroot" it's installing right now :)

tritron commented on 2013-05-20 17:40 (UTC)

From your error message looks like you are missing patch so you want to install it did you run makepkg -s ?

3000 commented on 2013-05-20 17:34 (UTC)

so I have downloaded latest tarball and tried to install it, but it's not building. I must stress, I have been able to use uefi boot, so I don't know, if that's hindering the Installation, anyways I got this error: ... xen.conf ... Passed ==> Extracting sources... -> Extracting xen-4.2.2.tar.gz with bsdtar ==> Starting prepare()... /root/xen/PKGBUILD: line 38: patch: command not found ==> ERROR: A failure occurred in prepare(). Aborting...

<deleted-account> commented on 2013-05-17 10:38 (UTC)

I have an EFI motherboard and am running Arch 2013_05 x86_64. I am trying to build xen.efi and I have applied the Python workaround and rebuilt binutils-multilib with --enable-targets=X86_64-pep. The output of ld -V is: GNU ld (GNU Binutils) 2.23.2 Supported emulations: elf_x86_64 elf32_x86_64 elf_i386 i386linux elf_l1om elf_k1om i386pep i386pe However when I build xen i get: mv: cannot stat âetc/init.dâ: No such file or directory ==> ERROR: A failure occurred in package(). Aborting... Build logs here: https://dl.dropboxusercontent.com/u/66245999/xen-4.2.2-1-x86_64-prepare.log https://dl.dropboxusercontent.com/u/66245999/xen-4.2.2-1-x86_64-build.log https://dl.dropboxusercontent.com/u/66245999/xen-4.2.2-1-x86_64-package.log Can someone please assist?

zootboy commented on 2013-05-12 20:02 (UTC)

Can it be an optional dependency? I'd really rather not have bluetooth stuff installed on my server, and it would get much more annoying to strip out if it became a rolled-in dep in a community package.

kantras commented on 2013-05-12 18:37 (UTC)

A quick grep over the source tree shows that the qemu pieces have config options for bluez

zootboy commented on 2013-05-12 17:50 (UTC)

Is there a reason why bluez is a dependency? I don't use it at all, and I have yet to see any issues with my install where I removed it.

« First ‹ Previous 1 .. 67 68 69 70 71 72 73 74 75 76 77 .. 101 Next › Last »