Package Details: xen-docs 4.9.0-1

Git Clone URL: (read-only)
Package Base: xen
Description: Virtual Machine Hypervisor documentation
Upstream URL:
Keywords: hypervisor virtualization xen
Licenses: GPL2
Conflicts: xen-docs-4.2, xen-docs-4.2-testing-hg, xen-docs-4.3, xen-docs-4.3-testing-hg, xen-docs-4.4, xen-docs-4.5, xen-docs-4.6, xen-docs-4.7, xen-docs-4.8, xen-docs-gdbsx, xen-docs-git, xen-docs-hg-unstable, xen-docs-igvtg, xen-docs-rc
Provides: xen-docs-4.9.0
Submitter: sergej
Maintainer: das_j
Last Packager: das_j
Votes: 172
Popularity: 1.362077
First Submitted: 2009-11-09 11:22
Last Updated: 2017-07-20 13:50

Latest Comments

maldo commented on 2017-08-16 19:33

I can confirm the observation of asura for a fresh arch install.

installing spice-glib did work for me as well

asura commented on 2017-08-16 16:17

For anyone having trouble to build this package and getting spice dependency errors

ERROR: User requested feature spice
configure was not able to find it.
Install spice-server(>=0.12.0) and spice-protocol(>=0.12.3) devel

Installing community/spice-glib and community/spice-gtk3 solved the issue for me.

maldo commented on 2017-07-23 18:17

Hi das_j, just started building for a naked arch... seems autoconf and patch are missing as dependencies

tony_42 commented on 2017-07-20 15:51

Hi das_j, looks like there is a patch for the build failure:;a=commit;h=672949d6c61d9cba01c5b414eed9d522082f04d3

pew commented on 2017-06-19 12:47

JohnTh, can you please provide a link for the 4.9-rc8 version that have fixes for the warnings? I've been using this: and I'm still getting all the warnings with gcc7.

Nevermind, all the errors I was having were for other packages inside of xen (ie qemu, ipxe)

JohnTh commented on 2017-06-07 08:40

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!)

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/ /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

I think it's an issue with gcc7. I found this patch 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=]
drivers/net/ath/ath5k/ath5k_desc.c:107:3: note: here

ArthurBorsboom commented on 2017-06-06 09:30

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=]
drivers/net/igbvf/igbvf_vf.c:360:2: note: here
case e1000_promisc_unicast:

baratharon commented on 2017-06-03 05:17

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)))


Flubbadub commented on 2017-06-01 09:38

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
- 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)" ;;

All comments