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

Pinned Comments

Refutationalist commented on 2024-12-06 01:37 (UTC)

Please Note: Per best-practices by upstream this package follows the git stable branch. Minor releases do not require a version bump and the PKGBUILD will provide the appropriate version number.

stubdom is still broken.

Latest Comments

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 101 Next › Last »

JohnTh commented on 2017-06-07 08:40 (UTC)

The upgrade to gcc7 brings a number of new warnings that show up in building xen-4.8.1 My xen PKGBUILD has diverged a bit from this one, but should build xen 4.8.1 (without stubdom!) https://gitlab.com/johnth/aur-xen/tree/master Either fix the files, or change the C(PP)FLAGS; remove Werror, or use -Wno-error= for each error warning. This needs to be done for each component with error warnings (xen, ipxe, ovmf, vtpm). Most of the warnings have fixes upstream, and are included in xen-4.9.0-rc8. I am unable to build stubdom with the current Arch packages, getting linking errors: ld -nostdlib -L/build/xen/src/xen-4.8.1/stubdom/cross-root-x86_64/x86_64-xen-elf/lib -m elf_x86_64 -T /build/xen/src/xen-4.8.1/stubdom/mini-os-x86_64-vtpmmgr/arch/x86/minios-x86_64.lds /build/xen/src/xen-4.8.1/stubdom/mini-os-x86_64-vtpmmgr/mini-os.o -o /build/xen/src/xen-4.8.1/stubdom/mini-os-x86_64-vtpmmgr/mini-os /build/xen/src/xen-4.8.1/stubdom/mini-os-x86_64-vtpmmgr/mini-os.o: In function `vtpmmgr_GroupRegister': /build/xen/src/xen-4.8.1/stubdom/vtpmmgr/vtpm_cmd_handler.c:555: undefined reference to `tpmrsa_free''

jsteel commented on 2017-06-07 08:17 (UTC)

I think it's an issue with gcc7. I found this patch http://git.ipxe.org/ipxe.git/commitdiff/5f85cbb which gets around the error reported by ArthurBorsboom but then I get a similar error shortly after: [BUILD] bin/ath5k_desc.o drivers/net/ath/ath5k/ath5k_desc.c: In function 'ath5k_hw_setup_2word_tx_desc': drivers/net/ath/ath5k/ath5k_desc.c:106:15: error: this statement may fall through [-Werror=implicit-fallthrough=] frame_type = AR5K_AR5210_TX_DESC_FRAME_TYPE_NO_DELAY; drivers/net/ath/ath5k/ath5k_desc.c:107:3: note: here case AR5K_PKT_TYPE_PIFS: ^~~~

ArthurBorsboom commented on 2017-06-06 09:30 (UTC)

I got a compile error with the latest PKGBUILD (4.8.0-7): drivers/net/igbvf/igbvf_vf.c: In function 'igbvf_promisc_set_vf': drivers/net/igbvf/igbvf_vf.c:359:10: error: this statement may fall through [-Werror=implicit-fallthrough=] msgbuf |= E1000_VF_SET_PROMISC_MULTICAST; drivers/net/igbvf/igbvf_vf.c:360:2: note: here case e1000_promisc_unicast: ^~~~

baratharon commented on 2017-06-03 05:17 (UTC)

I got a compile error with the latest PKGBUILD (4.8.0-7): runtime.c: In function 'efi_compat_get_info': /home/aron/build/xen-4.8.0-7/xen/src/xen-4.8.0/xen/include/asm/x86_64/uaccess.h:58:37: error: '*' in boolean context, suggest '&&' instead [-Werror=int-in-bool-context] compat_access_ok(addr, (count) * (size))) ^ Details: https://pastebin.com/jrb44Mg1

Flubbadub commented on 2017-06-01 09:38 (UTC)

For anyone else using Manjaro (or probably me in the future) the kernels are named differently in Manjaro. I had to apply this patch in order to get the grub menu entried to be generated correctly: diff --git a/etc/grub.d/09_xen b/etc/grub.d/09_xen index 59ac88a..3a41376 --- a/etc/grub.d/09_xen +++ b/etc/grub.d/09_xen @@ -38,11 +38,11 @@ _FUNC_GRUB_FILE_PRESENT() { case "${GRUB_PLATFORM}" in x86) - list="$(for i in "${GRUB_ROOT}"/boot/vmlinuz-linux* ; do + list="$(for i in "${GRUB_ROOT}"/boot/vmlinuz-* ; do if grub_file_is_not_garbage "${i}" && "${grub_file}" ${check} "${i}" ; then echo -n "${i} " ; fi done)" ;; *) - list="$(for i in "${GRUB_ROOT}"/boot/vmlinuz-linux* ; do + list="$(for i in "${GRUB_ROOT}"/boot/vmlinuz-* ; do if grub_file_is_not_garbage "${i}" && "${grub_file}" ${check} "${i}" ; then echo -n "${i} " ; fi done)" ;; esac

Refutationalist commented on 2017-05-31 05:19 (UTC)

I just tried building 4.8.0-7 from a clean install-- I usually do this so I can catch missing dependencies and to control clutter. I got a build failure: https://gist.github.com/anonymous/a8c48f68b086a14407cc0067c222ce00

jsteel commented on 2017-04-04 09:27 (UTC)

Thanks, specifying the seabios file in the PKGBUILD as you suggested worked!

tony_42 commented on 2017-04-03 14:04 (UTC)

@jsteel: I think it's a mistake in the PKGBUILD. It should be: --with-system-seabios=/usr/share/qemu/bios-256k.bin (so with the path to SeaBIOS specified) There should be a path as well for OVMF, but I just realize the package change recently so I don't know if it's going to work with Xen.

jsteel commented on 2017-04-03 12:35 (UTC)

After updating from 4.8.0-4 to 4.8.0-5 I installed seabios but I get an error when booting a domU: libxl: error: libxl_dom.c:892:libxl__load_hvm_firmware_module: failed to read BIOS file: No such file or directory I've gone back to 4.8.0-4 for now. Any idea what else is needed apart from installing seabios for non-UEFI systems now? Thanks.

jonnyt886 commented on 2017-04-03 09:09 (UTC)

Hitting repeated issues building this when downloading ovmf: -> Cloning ovmf git repo... Cloning into bare repository '/tmp/yaourt-tmp-jonny/aur-xen/ovmf'... remote: Counting objects: 240383, done. remote: Compressing objects: 100% (59223/59223), done. remote: Total 240383 (delta 184842), reused 229977 (delta 174449) Receiving objects: 100% (240383/240383), 225.31 MiB | 259.00 KiB/s, done. fatal: unable to open /tmp/yaourt-tmp-jonny/aur-xen/ovmf/objects/pack/tmp_pack_0lHJ2u: No such file or directory fatal: index-pack failed ==> ERROR: Failure while downloading ovmf git repo Aborting... ==> ERROR: Makepkg was unable to build xen. ==> Restart building xen ? [y/N] ==> ---------------------------- Tried removing ovmf from the PKGBUILD (removed all lines referring to ovmf except for the 'optDepends' entry) and then checksum validations fail, but with no file mentioned. And yes I did remove all the ovmf entries! Is anyone else getting this?