Package Base Details: xen

Git Clone URL: https://aur.archlinux.org/xen.git (read-only, click to copy)
Keywords: hypervisor virtualization xen
Submitter: sergej
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 185
Popularity: 0.42
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-01-19 23:00 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 11 Next › Last »

JohnTh commented on 2017-12-15 02:33 (UTC)

If your guest cannot see disks, make sure you have the xen-blkfront module loaded in your guest. You can use a serial port on the dom0 to get the full Xen log. I have a 4.10 PKGBUILD here: https://gitlab.com/archlinux-packages-johnth/xen

sniper7kills commented on 2017-12-15 02:05 (UTC)

@mbroemme if you happen to have a git repo or PKGBUILD for 4.10 I'd love to give it a try; for some reason I'm having issues with linux install disks not detecting the HDD on any VM I try to setup and also been getting some errors after xen boots prior to the kernel but haven't been able to capture them at all.

Hoping that 4.10 resolves these for me.

mbroemme commented on 2017-12-12 08:53 (UTC) (edited on 2017-12-12 08:55 (UTC) by mbroemme)

@das_j: According to the wiki 4.10 was released. If you want I can also take it over and continue to maintain it.

mbroemme commented on 2017-12-08 11:26 (UTC)

@ezequiel.ezb: Import key via 'gpg --recv-keys 83FE14C957E82BD9' and retry build

ezequiel.ezb commented on 2017-12-08 11:21 (UTC)

All dependencies install correctly, however, I get this error afterwards:

==> Verifying source file signatures with gpg... xen-4.9.0.tar.gz ... FAILED (unknown public key 83FE14C957E82BD9) ==> ERROR: One or more PGP signatures could not be verified! makepkg -si 21.93s user 5.66s system 5% cpu 9:01.31 total

mbroemme commented on 2017-11-24 14:31 (UTC)

@das_j: Xen 4.9 has full multiboot2 support to make EFI + Grub + Xen working out of the box. See https://wiki.xenproject.org/wiki/Xen_EFI In Arch Linux there is already grub2 2.02 with working multiboot2, so could cou please apply the following patch to grub-mkconfig-helper: https://zuppy.pm/patches/xen-grub2-efi-multiboot2.patch I've tested it already, with this patch Xen can be booted via grub in BIOS and UEFI mode. Without the patch you are forced to switch to BIOS mode or use EFI binary directly which makes multi-OS / grub2 booting very complicated.

mbroemme commented on 2017-11-24 14:17 (UTC) (edited on 2017-11-24 14:17 (UTC) by mbroemme)

@das_j: There is a bug in this package which will result in systemd failing to load kernel modules: Nov 24 15:09:49 server systemd-modules-load[4287]: Failed to find module 'gntdev' Nov 24 15:09:49 server systemd-modules-load[4287]: Failed to find module 'netbk' Nov 24 15:09:49 server systemd-modules-load[4287]: Failed to find module 'blkbk' Nov 24 15:09:49 server systemd-modules-load[4287]: Failed to find module 'xen-scsibk' Nov 24 15:09:49 server systemd-modules-load[4287]: Failed to find module 'usbbk' Nov 24 15:09:49 server systemd-modules-load[4287]: Failed to find module 'pciback' Nov 24 15:09:49 server systemd-modules-load[4287]: Failed to find module 'blktap2' Nov 24 15:09:49 server systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Nov 24 15:09:49 server systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Nov 24 15:09:49 server systemd[1]: Failed to start Load Kernel Modules. The reason is because the shipped xen.conf is never installed during package build, therefore the xen default is installed but not working for Arch Linux kernels. Could you please apply the following patch to PKGBUILD: https://zuppy.pm/patches/xen-modules-load-fix.patch

ipdown commented on 2017-11-09 17:20 (UTC)

Does anyone knows how to get coretemp/lm_sensors to work with xen-kernel? I am able to monitor cpu temperature with regular kernel, but not in dom0/xen-kernel.

ArthurBorsboom commented on 2017-10-19 18:05 (UTC)

If this only installs one package, what about changing the make dependency in the package from pandoc to pandoc-bin? Or does this have side effects?

zootboy commented on 2017-10-19 03:41 (UTC)

@ArthurBorsboom You can install pandoc-bin in its place.

ArthurBorsboom commented on 2017-10-15 08:45 (UTC)

Xen doesn't build (anymore): entry.S: Assembler messages: entry.S:42: Error: invalid operands (*ABS* and *UND* sections) for `-' entry.S:61: Error: invalid operands (*UND* and *UND* sections) for `+' entry.S:115: Error: invalid operands (*ABS* and *UND* sections) for `-' entry.S:110: Error: invalid operands (*UND* and *UND* sections) for `-' make[6]: *** [/opt/tmp/makepkg/xen/src/xen-4.9.0/xen/Rules.mk:177: entry.o] Error 1 Any idea how to solve this?

ArthurBorsboom commented on 2017-10-14 08:11 (UTC)

Is the pandoc make dependency really necessary? It brings in exactly 101 haskell-* (dependency) packages.

JohnTh commented on 2017-10-01 01:19 (UTC)

Thanks das_j Hi finnland, I didn't have any issues installing or running win10 or freebsd11 amd64 iso zroot with ovmf. This patch for xen-4.9.0 built-in ovmf: https://github.com/tianocore/edk2/commit/fe4a28ccbfd33cae9e1f56b174d46b4eb2329efd.patch Or the full ovmf BIOS built with a modified Arch ovmf PKGBUILD. diff --git a/trunk/PKGBUILD b/trunk/PKGBUILD index f9297d0..098ab18 100644 --- a/trunk/PKGBUILD +++ b/trunk/PKGBUILD @@ -1,6 +1,7 @@ # $Id$ # Maintainer: Thomas Bächler <thomas@archlinux.org> -pkgname=ovmf +pkgbase=ovmf +pkgname=('ovmf' 'ovmf-unsplit') pkgver=r22345.bec7a86c70 epoch=1 pkgrel=1 @@ -51,10 +52,15 @@ build() { ./BaseTools/BinWrappers/PosixLike/build } -package() { +package_ovmf() { #install -D -m644 "${srcdir}"/edk2/Build/OvmfIa32/RELEASE_${_toolchain_opt}/FV/OVMF_CODE.fd "${pkgdir}"/usr/share/ovmf/ia32/OVMF_CODE.fd #install -D -m644 "${srcdir}"/edk2/Build/OvmfIa32/RELEASE_${_toolchain_opt}/FV/OVMF_VARS.fd "${pkgdir}"/usr/share/ovmf/ia32/OVMF_VARS.fd install -D -m644 "${srcdir}"/edk2/Build/OvmfX64/RELEASE_${_toolchain_opt}/FV/OVMF_CODE.fd "${pkgdir}"/usr/share/ovmf/x64/OVMF_CODE.fd install -D -m644 "${srcdir}"/edk2/Build/OvmfX64/RELEASE_${_toolchain_opt}/FV/OVMF_VARS.fd "${pkgdir}"/usr/share/ovmf/x64/OVMF_VARS.fd install -D -m644 "${srcdir}"/edk2/OvmfPkg/License.txt "${pkgdir}"/usr/share/licenses/ovmf/License.txt } + +package_ovmf-unsplit() { + install -D -m644 "${srcdir}"/edk2/Build/OvmfX64/RELEASE_${_toolchain_opt}/FV/OVMF.fd "${pkgdir}"/usr/share/ovmf/ovmf_x64.bin + install -D -m644 "${srcdir}"/edk2/OvmfPkg/License.txt "${pkgdir}"/usr/share/licenses/"${pkgname[2]}"/License.txt +} VM config ### Xen VM options ## http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html name="win10.cfg" builder="hvm" memory=2048 bios="ovmf" bios_path_override="/usr/share/ovmf/ovmf_x64.bin" #device_model_args=[ "-debugcon", "file:ovmf_debug.log", "-global", "isa-debugcon.iobase=0x402"] hdtype="ahci" disk=[ "/mnt/server/software/os/Microsoft_Windows/to_check/Win10_1703_EnglishInternational_x64.iso, raw, xvdc, cdrom", # "/mnt/server/software/os/FreeBSD-11.1-RELEASE-amd64-disc1.iso, raw, xvdc, cdrom", "/dev/mapper/sda1_vg-win10, raw, xvda, rw" ] vif=[ "" ] vnc=1 vnclisten="0.0.0.0" vncunused=1 vncpasswd="pass" usb=1 usbdevice=[ "tablet" ]

<deleted-account> commented on 2017-09-30 21:14 (UTC)

@tony_42 Thank you, applied :) @maldo Building from AUR requires base-devel @maldo @asura Added SPICE dependency @JohnTh Applied all XSA patches

finnland commented on 2017-09-25 12:52 (UTC)

Hi JohnTh, after quite a bit of tinkering I got Xen built with the in tree ovmf. It does not build out of the box so i had to select a newer version, the one it selects from git by default has a bug in it. Anyhow I got it so far that I can start a machine using ovmf but it seems quite flaky, win 10 just reboots immediately , Freebsd 11 crashes. Arch works tho. I gave up for now and sticking with seabios, which seems to work.

JohnTh commented on 2017-09-24 00:57 (UTC)

Hi finnland, There was some discussion about this on the Xen lists. It is not clear if Xen currently will work with ovmf split code and vars. http://markmail.org/message/vh5kk53z3v4fxhpa If you do want to use system ovmf: Test if the Arch PKGBUILD ovmf combined image works with xen. I think it did when I tested some time ago. Easiest to makepkg ovmf and copy the combined image somewhere. Then use the xl vm guest options bios="ovmf" bios_path_override="path to ovmf" If this works, we could ask the Arch ovmf package maintainer to change the PKGBUILD to produce split packages of ovmf (as is) and ovmf-combined (only package the merged ovmf). Should be minimal changes to the PKGBUILD. https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/ovmf There are also a number of XSA patches for xen-4.9.0

finnland commented on 2017-09-23 21:54 (UTC)

The build flag --with-system-ovmf works the same as --with-system-seabios in that it should contain a path such as --with-system-ovmf=/usr/share/ovmf/ovmf_code_x64.bin. Cannot make it boot properly with it tho, unsure how to tell it about split ovmf images.

lazycat commented on 2017-09-03 04:10 (UTC)

@JohnTh Thanks a lot, rebuilding kernel helped me

JohnTh commented on 2017-08-31 06:13 (UTC)

Hey Lazycat, This is an Arch linux 4.12 kernel bug due to CONFIG_INTEL_ATOMISP https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711298 Arch bug here https://bugs.archlinux.org/task/55447 The 201707 install disk uses 4.11 and boots Arch used 4.12 from 2017-07-05 https://git.archlinux.org/svntogit/packages.git/commit/?h=packages/linux&id=6e70fcab0f7e068216f579f72385175113587083 You can build a 4.12 kernel with CONFIG_INTEL_ATOMISP=n or use the Arch Linux archive: https://wiki.archlinux.org/index.php/Arch_Linux_Archive#How_to_restore_all_packages_to_a_specific_date For the spice error, makedepend libcacard The spice Arch package removed it as a depend in 0.12.8+8+ga957a90b

lazycat commented on 2017-08-30 17:28 (UTC)

Hello all! Today i made full system upgrade and upgrade xen from 4.8 to 4.9 from aur too. Now i can't create new PV domU (but old runs fine) error: Parsing config from test.cfg [ 0.107779] xen:manage: Unable to read sysrq code in control/sysrq [ 0.110203] dmi: Firmware registration failed. [ 0.131027] intel_mid_msgbus_init: Error: msgbus PCI handle NULL [ 3.997728] BUG: unable to handle kernel paging request at ffffc90040199060 [ 3.997742] IP: vlv2_plat_configure_clock+0x3b/0xa0 [ 3.997746] PGD 3fe10067 [ 3.997746] P4D 3fe10067 [ 3.997748] PUD 3e202067 [ 3.997750] PMD 3e203067 [ 3.997752] PTE 0 [ 3.997753] [ 3.997757] Oops: 0000 [#1] PREEMPT SMP [ 3.997760] Modules linked in: [ 3.997765] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.12.3-1-ARCH #1 [ 3.997768] task: ffff88003e2c4240 task.stack: ffffc9004018c000 [ 3.997773] RIP: e030:vlv2_plat_configure_clock+0x3b/0xa0 [ 3.997776] RSP: e02b:ffffc9004018fbe0 EFLAGS: 00010246 [ 3.997779] RAX: 0000000000000000 RBX: ffffc90040199060 RCX: 0000000001d5dfff [ 3.997783] RDX: ffff88003e2c4240 RSI: 0000000000000002 RDI: ffffffff81ac9980 [ 3.997786] RBP: ffffc9004018fbf0 R08: 0000000000001000 R09: ffffffff811d6101 [ 3.997790] R10: 0000000000007ff0 R11: ffffe8ffffffffff R12: 0000000000000002 [ 3.997793] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 3.997803] FS: 0000000000000000(0000) GS:ffff88003f800000(0000) knlGS:0000000000000000 [ 3.997807] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3.997812] CR2: ffffc90040199060 CR3: 0000000001a09000 CR4: 0000000000042660 [ 3.997817] Call Trace: [ 3.997825] vlv2_plat_clk_probe+0x3f/0x70 [ 3.997832] platform_drv_probe+0x3b/0xa0 [ 3.997837] driver_probe_device+0x2ff/0x450 [ 3.997842] __device_attach_driver+0x83/0x100 [ 3.997848] ? __driver_attach+0xe0/0xe0 [ 3.997853] bus_for_each_drv+0x69/0xb0 [ 3.997858] __device_attach+0xdd/0x160 [ 3.997863] device_initial_probe+0x13/0x20 [ 3.997867] bus_probe_device+0x92/0xa0 [ 3.997872] device_add+0x451/0x690 [ 3.997877] platform_device_add+0x10d/0x270 [ 3.997884] ? set_debug_rodata+0x17/0x17 [ 3.997888] platform_device_register_full+0xfe/0x110 [ 3.997895] ? vlv2_plat_clk_init+0x19/0x19 [ 3.997901] vlv2_plat_clk_init+0x48/0x82 [ 3.997906] do_one_initcall+0x50/0x190 [ 3.997912] kernel_init_freeable+0x186/0x214 [ 3.997918] ? rest_init+0x90/0x90 [ 3.997923] kernel_init+0xe/0x100 [ 3.997929] ret_from_fork+0x25/0x30 [ 3.997933] Code: 47 83 fe 02 41 89 f4 77 67 48 8b 05 60 49 84 00 48 85 c0 74 48 c1 e7 02 48 63 ff 48 8d 1c 38 48 c7 c7 80 99 ac 81 e8 95 0f 15 00 <8b> 03 83 e0 fc 44 09 e0 89 03 48 c7 c7 80 99 ac 81 e8 6f 09 15 [ 3.997966] RIP: vlv2_plat_configure_clock+0x3b/0xa0 RSP: ffffc9004018fbe0 [ 3.997970] CR2: ffffc90040199060 [ 3.997976] ---[ end trace 43ffeef3f6ee6085 ]--- [ 3.997991] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 [ 3.997991] [ 3.998001] Kernel Offset: disabled .cfg file name = "test" memory = "1024" #root = "/dev/xvdc1" #bootloader = "pygrub" kernel = "/mnt/arch/boot/x86_64/vmlinuz" ramdisk = "/mnt/arch/boot/x86_64/archiso.img" extra = "archisobasedir=arch archisolabel=ARCH_201708" disk = ["archlinux-2017.08.01-x86_64.iso,,xvdc,cdrom,r","/dev/VG/test,,xvda,rw"] vif = [ 'mac=00:22:26:11:21:10,bridge=brint0' ] #boot = "d" Whats wrong? Any ideas?

maldo commented on 2017-08-16 19:33 (UTC)

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

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 (UTC) (edited on 2017-07-23 18:19 (UTC) by maldo)

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

Hi das_j, looks like there is a patch for the build failure: https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=672949d6c61d9cba01c5b414eed9d522082f04d3

pew commented on 2017-06-19 12:47 (UTC) (edited on 2017-06-19 22:26 (UTC) by pew)

JohnTh, can you please provide a link for the 4.9-rc8 version that have fixes for the warnings? I've been using this: https://downloads.xenproject.org/release/xen/4.9.0-rc8/ 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 (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?

<deleted-account> commented on 2017-03-28 06:46 (UTC)

Bumped to 4.8.0-5. This version adds XSA-211, splits out SeaBIOS and OVMF and disables Werror (hopefully).

badboy commented on 2017-03-20 09:41 (UTC)

I'd be fine with that.

<deleted-account> commented on 2017-03-19 19:32 (UTC)

So what do you guys think about using the system's OVMF and SeaBios? Apart from faster build times because we don't need to build them ourselfs, we also prevent errors like the one of @maldo. Once this is decided, I will push out a new PKGBUILD with the --disable-werror patch and possibly the new SeaBIOS/OVMF.

maldo commented on 2017-03-19 09:01 (UTC) (edited on 2017-03-19 09:02 (UTC) by maldo)

@das_j @badboy @JohnTh @tony_42 I am able to reproduce the makedev issue... and am running in further problems with ovmf ... any leads/ideas? my system: naked arch with base-devel & multilib-devel (multilib enabled) approach: sudo pacman -Syu git clone https://aur.archlinux.org/xen.git makepkg -si ... public key issue with xen4.8.0 makepkg -si --skippgpcheck ... makedev issue tap-ctl-allocate.c: In function 'tap_ctl_make_device': tap-ctl-allocate.c:109:13: error: In the GNU C Library, "makedev" is defined by <sys/sysmacros.h>. For historical compatibility, it is currently defined by <sys/types.h> as well, but we plan to remove this soon. To use "makedev", include <sys/sysmacros.h> directly. If you did not intend to use a system-defined macro "makedev", you should undefine it after including <sys/types.h>. [-Werror] err = mknod(devname, perm, makedev(major, minor)); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors applying workaround of tony_42 build() { ... --with-extra-qemuu-configure-args="--disable-bluez --disable-gtk --enable-spice --enable-usb-redir --disable-werror" \ ... make LANG=C PYTHON=python2 APPEND_CFLAGS=-Wno-error dist } makepkg -si --skippgpcheck g/Library/BaseUefiCpuLib/X64/InitializeFpu.nasm > /home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/Build/OvmfX64/RELEASE_GCC44/X64/UefiCpuPkg/Library/BaseUefiCpuLib/BaseUefiCpuLib/OUTPUT/X64/InitializeFpu.i /home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/MdePkg/Library/PeiServicesTablePointerLibIdt/PeiServicesTablePointer.c: In function 'MigratePeiServicesTablePointer': /home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/MdePkg/Library/PeiServicesTablePointerLibIdt/PeiServicesTablePointer.c:100:26: error: variable 'Status' set but not used [-Werror=unused-but-set-variable] EFI_STATUS Status; ^~~~~~ /home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/MdePkg/Library/PeiHobLib/HobLib.c: In function 'GetHobList': /home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/MdePkg/Library/PeiHobLib/HobLib.c:46:25: error: variable 'Status' set but not used [-Werror=unused-but-set-variable] EFI_STATUS Status; ^~~~~~ /home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/MdePkg/Library/PeiHobLib/HobLib.c: In function 'GetBootModeHob': /home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/MdePkg/Library/PeiHobLib/HobLib.c:212:26: error: variable 'Status' set but not used [-Werror=unused-but-set-variable] EFI_STATUS Status; ^~~~~~ cc1: all warnings being treated as errors make[7]: *** [GNUmakefile:315: /home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/Build/OvmfX64/RELEASE_GCC44/X64/MdePkg/Library/PeiServicesTablePointerLibIdt/PeiServicesTablePointerLibIdt/OUTPUT/PeiServicesTablePointer.obj] Error 1 make[7]: Leaving directory '/home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/Build/OvmfX64/RELEASE_GCC44/X64/MdePkg/Library/PeiServicesTablePointerLibIdt/PeiServicesTablePointerLibIdt' build.py... : error 7000: Failed to execute command make tbuild [/home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/Build/OvmfX64/RELEASE_GCC44/X64/MdePkg/Library/PeiServicesTablePointerLibIdt/PeiServicesTablePointerLibIdt] build.py... : error 7000: Failed to execute command make tbuild [/home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/Build/OvmfX64/RELEASE_GCC44/X64/MdePkg/Library/PeiHobLib/PeiHobLib] build.py... : error F002: Failed to build module /home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote/MdePkg/Library/PeiServicesTablePointerLibIdt/PeiServicesTablePointerLibIdt.inf [X64, GCC44, RELEASE] - Failed - Build end time: 09:48:44, Mar.19 2017 Build total time: 00:00:10 make[6]: *** [Makefile:19: build] Error 1 make[6]: Leaving directory '/home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/ovmf-dir-remote' make[5]: *** [/home/rnet-master/xenbuild/xen/src/xen-4.8.0/tools/firmware/../../tools/Rules.mk:218: subdir-all-ovmf-dir] Error 2

devnull_1337 commented on 2017-03-18 22:18 (UTC)

@badboy @JohnTh: you can use the following patch for the makedev compile error: --- a/tools/blktap2/control/tap-ctl-allocate.c 2016-04-25 22:33:15.444681888 -0 700 +++ b/tools/blktap2/control/tap-ctl-allocate.c 2016-04-25 22:30:33.288046037 -0 700 @@ -36,6 +36,7 @@ #include <sys/stat.h> #include <sys/types.h> #include <sys/ioctl.h> +#include <sys/sysmacros.h> #include <linux/major.h> #include "tap-ctl.h" --- a/tools/libxl/libxl_osdeps.h 2016-04-25 22:55:04.326527630 -0700 +++ b/tools/libxl/libxl_osdeps.h 2016-04-25 22:53:36.315440845 -0700 @@ -43,6 +43,7 @@ #define SYSFS_PCIBACK_DRIVER "/sys/bus/pci/drivers/pciback" #define NETBACK_NIC_NAME "vif%u.%d" #include <pty.h> +#include <sys/sysmacros.h> #include <uuid/uuid.h> #elif defined(__sun__) #include <stropts.h>

tony_42 commented on 2017-03-14 16:27 (UTC)

You could avoid this kind of warning, now and later, with two modifications in PKGBUILD. When calling ./configure, add "--disable-werror" to --with-extra-qemuu-configure-args. And add APPEND_CFLAGS=-Wno-error to make. So build() would look like this: ./configure \ PYTHON=/usr/bin/python2 \ --prefix=/usr \ --sbindir=/usr/bin \ --with-sysconfig-leaf-dir=conf.d \ --with-initddir=/etc/init.d \ --enable-systemd \ --enable-ovmf \ "${_config_stubdom:---disable-stubdom}" \ --with-extra-qemuu-configure-args="--disable-bluez --disable-gtk --enable-spice --enable-usb-redir --disable-werror" make LANG=C PYTHON=python2 APPEND_CFLAGS=-Wno-error dist

<deleted-account> commented on 2017-03-13 06:50 (UTC)

@badboy: Fixed the architecture problem, split packages are weird. @badboy @JohnTh: I can not reproduce the problem here. I'm running a fully updated Arch. Do you have any changed values in /etc/makepkg.conf?

JohnTh commented on 2017-03-13 04:38 (UTC)

@badboy I'm seeing that too after updating Arch. To resolve, Need to add this include to relevant Xen source files, where minor(), major(), or makedev() are used. #include <sys/sysmacros.h> I found these with grep -R ' \(major\|minor\|makedev\)('. Not sure if they are the correct locations, or implementation: tools/blktap2/control/tap-ctl-allocate.c tools/libxl/libxl_internal.h tools/qemu-xen/include/qemu/osdep.h My patch here https://gitlab.com/johnth/aur-xen/raw/master/patch-include_sys_sysmacros.h.patch Details: glibc 2.25 https://sourceware.org/glibc/wiki/Release/2.25 "The inclusion of sys/sysmacros.h by sys/types.h is deprecated. Using the macros major, minor, or makedev without having directly included sys/sysmacros.h will trigger compiler warnings."

badboy commented on 2017-03-12 17:52 (UTC)

I get another error, but that seems like it needs to go upstream: $ makepkg -As --skippgpcheck [...] tap-ctl-allocate.c: In function 'tap_ctl_make_device': tap-ctl-allocate.c:109:13: error: In the GNU C Library, "makedev" is defined by <sys/sysmacros.h>. For historical compatibility, it is currently defined by <sys/types.h> as well, but we plan to remove this soon. To use "makedev", include <sys/sysmacros.h> directly. If you did not intend to use a system-defined macro "makedev", you should undefine it after including <sys/types.h>. [-Werror] err = mknod(devname, perm, makedev(major, minor));

badboy commented on 2017-03-11 22:40 (UTC)

For some reason I get an error on my 64bit machine: ==> ERROR: xen is not available for the 'x86_64' architecture.

lazycat commented on 2017-03-11 03:50 (UTC)

@das_j, @JohnTh Thank you for answers :)

<deleted-account> commented on 2017-03-09 11:53 (UTC)

@lazycat @JohnTh I'm currently updating the package. However, it takes me longer to test, because I only have a really slow machine right now. I'm also adding xen-docs and turn this package into a split package. Update should roll out today.

JohnTh commented on 2017-03-09 11:39 (UTC)

@lazycat The Arch lzo package has changed, and no longer "provides" lzo2. I think you will need to rebuild and upgrade the Xen package to remove the error/ignore. You should be able to change lzo2 to lzo (line 74?) in the depends array in the Xen PKGBUILD. Then rebuild. lzo package change here https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/lzo&id=eb70476e9442d349f3c353e91631c0e713781c07 I would suggest you use multilib-build (from the Arch package devtools) to build in a clean chroot. See how that goes.

lazycat commented on 2017-03-09 09:10 (UTC)

New headache. Can't make system upgrade with pacman -Syu, get error: error: failed to prepare transaction (could not satisfy dependencies) :: xen: installing lzo (2.10-1) breaks dependency 'lzo2' I'm solve it temporally with #IgnorePkg = lzo lzo2, but it's not a good, I guess. Any ideas?

JohnTh commented on 2017-02-26 22:02 (UTC)

@ArgylePwnage gpg --keyserver pgp.mit.edu --recv-key 23E3222C145F4475FA8060A783FE14C957E82BD9 This command should solve that problem. You need to import the Xen Project tree code signing OpenPGP key 23E3222C145F4475FA8060A7(83FE14C957E82BD9) into your gpg keyring. The key is detailed here: https://www.xenproject.org/developers/teams/hypervisor/openpgp.html Otherwise, you can use a command line option with makepkg, or modify the PKGBUILD to remove this check. Have a look through the man pages or comments on the AUR Xen page for more details.

<deleted-account> commented on 2017-02-26 14:42 (UTC)

Hello, I have received the following error message: PGP signatures could not be verified for public key "83FE14C957E82BD9". Can you advise? Thank you for your time.

lazycat commented on 2017-01-20 02:34 (UTC)

@JohnTh, Yeah, your config file was really helpful for me, i successfully start arch live cd. But i understood that it is really bad idea to try to build completely work machine with 512 MB ram :D Thank you so much.

JohnTh commented on 2017-01-18 03:39 (UTC) (edited on 2017-01-18 04:00 (UTC) by JohnTh)

@lazycat Yes, possible to use Xen guest with little RAM. May need to boot your arch installer differently though. If you show your config, we will have a better idea. Working config for me, needs arch install iso. name='archtest' disk=['archlinux-2017.01.01-dual.iso, , xvdc, cdrom'] memory='256' root = '/dev/xvdc' bootloader='pygrub' kernel = "arch/boot/x86_64/vmlinuz" ramdisk = "arch/boot/x86_64/archiso.img" extra = "archisobasedir=arch archisolabel=ARCH_201701" boot='d'

lazycat commented on 2017-01-18 03:12 (UTC)

@JohnTh, It is possible use xen with config less then 1500M ram?

JohnTh commented on 2017-01-18 03:08 (UTC)

Good to see maintainer! When trying to boot PV archiso / archboot guest: I get "Initramfs unpacking failed: write error" when there is not enough memory to unpack the ramdisk to memory. I found the archboot64 I tried needed 1500MB memory.

lazycat commented on 2017-01-18 03:03 (UTC)

@das_j Thank you, it's really cool :) Successfully compile and install it, but still have problem with paravirt PV domU.. Trying to create guest with xl create -c and receive [ 0.120463] dmi: Firmware registration failed. [ 5.189734] Initramfs unpacking failed: write error Any ideas? My pc is junk? xD Or I doing something wrong?

<deleted-account> commented on 2017-01-17 20:24 (UTC)

@riaqn @lazycat I fixed the package and bumped the pkgrel. I can boot it, hopefully you can as well.

lazycat commented on 2017-01-16 07:24 (UTC)

@riaqn Hello! Have same problem - cannot create correct cfg for grub (add new boot entry to grub) with 09_xen Any ideas?

<deleted-account> commented on 2017-01-15 12:33 (UTC)

@riaqn No, this should not matter. I will check once I get home, but maybe not until tomorrow.

riaqn commented on 2017-01-15 05:03 (UTC)

It's probably just me: but in the compiled package, there is only a symlink from boot/xen-4.8.gz to xen-4.8.0.gz, but no xen-4.8.0.gz itself, which is necessary if I want to boot via grub? Do I have to compile on a grub-booted system(as opposed to efi-booted) to get this file in the package?

<deleted-account> commented on 2017-01-12 22:59 (UTC)

Adopted package as nobody else seemed to be interested. @John if you still are interested, contact me :) Updated to 4.8, hope I didn't break anything. Removed a lot of patches that are not needed anymore and updated XSAs. I also removed the ati-passthrough patch as it was for Xen 4.4 and didn't apply anymore.

lazycat commented on 2017-01-10 09:23 (UTC)

Hello all! Trying to create Xen PV domU, receive this: [ 0.167092] dmi: Firmware registration failed. [ 5.308116] Initramfs unpacking failed: write error ...and later :: Mounting '/dev/disk/by-label/ARCH_201701' to '/run/archiso/bootmnt' ERROR: '/dev/disk/by-label/ARCH_201701' device did not show up after 30 seconds... Falling back to interactive prompt You can try to fix the problem manually, log out when you are finished sh: can't access tty; job control turned off [rootfs ]# What I'm doing wrong?

ArthurBorsboom commented on 2016-12-11 08:59 (UTC)

I have disowned the package since I have no added value anymore. My preference goes to John maintaining the package. If it doesn't work (so I can test), you will here in the comment box here. :) Package is currently unmaintained.

JohnTh commented on 2016-12-07 07:31 (UTC)

Hi, xen-4.8.0 release has been tagged on xen git. I have update my master to use it and it needs testing. No release notes yet though. https://gitlab.com/johnth/aur-xen/ I included Xen's PGP signature in the PKGBUILD. Install the key (confirm here: https://www.xenproject.org/developers/teams/hypervisor/openpgp.html) with, as the user you build with: gpg --keyserver pgp.mit.edu --recv-key 23E3222C145F4475FA8060A783FE14C957E82BD9 Or use --skippgpcheck, or comment out the .sig and SKIP sha256sum for it in PKGBUILD. I am still unable to test, sorry, and am not happy maintaining until I can as it makes it too hard to troubleshoot. Cheers

bacondropped commented on 2016-11-18 15:25 (UTC)

@ParadoxSpiral @JohnTh The build failed as well on my Manjaro machine with the same relocation errors. I've had this problem before, this seems to happen thanks to 'hardening-wrapper', which forces PIC/PIE, which in turn has its problems when sub-libraries do not configure CFLAGS correctly. I solved the problem by building this package in a clean Arch VM (overkill, I know, but it worked fine).

bacondropped commented on 2016-11-18 15:21 (UTC) (edited on 2016-11-18 18:39 (UTC) by bacondropped)

Perhaps this project could provide 'xenstore'? https://www.archlinux.org/packages/extra/x86_64/pulseaudio-xen/ requires it, and the 'xenstore' package conflicts with this one. (NOTE: Although, for instance, pulseaudio-xen required libxenctrl.so.4.0 which xenstore provides, so this change would be breaking; but it'd be an update, so...)

Refutationalist commented on 2016-11-12 04:47 (UTC)

@JohnTh: 4.7.1-2 fixed it. Additionally, Xen resumed a vm across the upgrade and boots, which is the first time that's worked in a while without a lot of finagling.

ArthurBorsboom commented on 2016-11-11 16:07 (UTC)

@JohnTh: "I will think about maintaining"... and? :)

JohnTh commented on 2016-11-11 12:05 (UTC)

@Refutationalist See if the latest commit on my gitlab repository fixes this? It applies this patch: http://xenbits.xen.org/gitweb/?p=xen.git;a=patch;h=9714f6b87e19b32d3a6663a20df6610265c4bfe5 Discussed here: https://lists.xenproject.org/archives/html/xen-devel/2016-09/msg02889.html cheers

Refutationalist commented on 2016-11-11 09:22 (UTC) (edited on 2016-11-11 09:23 (UTC) by Refutationalist)

@JohnTh Your recent commit to 4.7.1 and pv-grub doesn't seem to boot w/ pv-grub x86_64. I'm going use an earlier pv-grub, but this is a dev server so I can test packages, if that helps. Here's the failure: ============= Init TPM Front ================ Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront initialization! error = ENOENT Tpmfront:Info Shutting down tpmfront pin_table(x) returned 850876 Error 9: Unknown boot failure Press any key to continue...

JohnTh commented on 2016-11-02 20:15 (UTC)

Hi, A patch was released to fix stubdom compile. This should give access to pvgrub. This package needs testing before being pushed (I haven't been able to do any). https://gitlab.com/johnth/aur-xen/ With this patch and indentation fixed in stubdom/vtpmmgr/{log.c,disk_read.c}, the package appears to compile. https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=668e4edf92fcf7cb929eed221059a3eeb02722c3 Cheers.

ParadoxSpiral commented on 2016-10-30 11:26 (UTC)

Building with `multilib-build` works. However when installing with `yaourt -U ..`, there are conflicting files with the xenstore package: http://sprunge.us/ZhNj When removed, xen installs correctly. Thanks for your assistance o7.

JohnTh commented on 2016-10-29 21:51 (UTC)

I would strongly suggest you use multilib-build from the devtools package (as opposed to yaourt) for this package. That way we get the same build environment. Otherwise, update, and see if you still get the error. https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot Yes, I noticed a build failed in the same place (OVMF) on my CI three days ago (on the 27th), but the days before and after have built fine. https://gitlab.com/johnth/aur-xen/pipelines I will think about maintaining.

ParadoxSpiral commented on 2016-10-29 10:25 (UTC)

Hello, building this package fails. http://sprunge.us/LcKE When I manually add -fpic to the gcc args in aur-xen/src/xen-4.7.0/tools/firmware/ovmf-dir-remote/BaseTools/Source/C/Makefiles/header.makefile the build fails again. http://sprunge.us/dFDE Using the PKGBUILD by @JohnTh doesn't work either.

ArthurBorsboom commented on 2016-10-22 12:14 (UTC)

@JohnTh, are you interested in maintaining this package, since you are already doing that on gitlab?

Just-Punk commented on 2016-10-17 21:22 (UTC)

a)thanx for package PKGBUILD I tried to create it myself but I lost on python-dev dependency. b) Xen wasn't build succesfull with stubdom option: (i have ukrainian locale, some parts of output was translated myself with *TRANSLATED mark) ....... checking how to define a 32-bit word... .long checking if .align assembly directive is logarithmic... no checking if the .align directive accepts an 0x90 fill in .text... yes checking for unsigned short... yes checking size of unsigned short... configure: error: cannot compute sizeof (unsigned short) See `config.log' for more details. make[1]: *** [Makefile:174: gmp-x86_64] Error 77 make[1]: Leaving directory '/tmp/yaourt-tmp-carbon/aur-xen/src/xen-4.7.0/stubdom' make: *** [Makefile:105: install-stubdom] Помилка 2 (*TRANSLATED: Error 2 ) ==> ПОМИЛКА: Стався збій у build(). (*TRANSLATED: Error: Failed in build())    Припинення... (*TRANSLATED: Stopped) ==> ПОМИЛКА: Makepkg не може створити xen. (*TRANSLATED: Makepkg can't create xen) ==> Розпочати знову побудову xen ? так/Ні [y/N] (*TRANSLATED: Start again build xen?) ==> ------------------------------------------- c) Wthout stubdom compiled OK. When I'll done successful xen settings & I'll start guest OS, I'll post about. Thanx

Just-Punk commented on 2016-10-17 21:22 (UTC)

a)thanx for package PKGBUILD I tried to create it myself but I lost on python-dev dependency. b) Xen wasn't build succesfull with stubdom option: (i have ukrainian locale, some parts of output was translated myself with *TRANSLATED mark) ....... checking how to define a 32-bit word... .long checking if .align assembly directive is logarithmic... no checking if the .align directive accepts an 0x90 fill in .text... yes checking for unsigned short... yes checking size of unsigned short... configure: error: cannot compute sizeof (unsigned short) See `config.log' for more details. make[1]: *** [Makefile:174: gmp-x86_64] Error 77 make[1]: Leaving directory '/tmp/yaourt-tmp-carbon/aur-xen/src/xen-4.7.0/stubdom' make: *** [Makefile:105: install-stubdom] Помилка 2 (*TRANSLATED: Error 2 ) ==> ПОМИЛКА: Стався збій у build(). (*TRANSLATED: Error: Failed in build())    Припинення... (*TRANSLATED: Stopped) ==> ПОМИЛКА: Makepkg не може створити xen. (*TRANSLATED: Makepkg can't create xen) ==> Розпочати знову побудову xen ? так/Ні [y/N] (*TRANSLATED: Start again build xen?) ==> ------------------------------------------- c) Wthout stubdom compiled OK. When I'll done successful xen settings & I'll start guest OS, I'll post about. Thanx

ArthurBorsboom commented on 2016-10-08 13:41 (UTC)

Please keep in mind for Xen on EFI to work on kernel 4.7.x, you need to compile the linux kernel with this patch: http://lkml.iu.edu/hypermail/linux/kernel/1608.2/03448.html

ArthurBorsboom commented on 2016-10-08 11:30 (UTC)

Since the old package was broken, John's package has replaced the old package. Please be defensive for production systems and give your feedback, so I know if the package works or needs improvements.

ArthurBorsboom commented on 2016-10-08 08:06 (UTC)

Hi John, Why don't we try to merge your PKGBUILD into this package (or the other way around)? Are you in for that?

JohnTh commented on 2016-10-06 19:55 (UTC)

There is a rather wild xen-4.7 PKGBUILD here: https://gitlab.com/johnth/aur-xen I have only tested it EFI booting (with refind) on Intel. XSA-190 has not yet been added to that. Cheers.

ArthurBorsboom commented on 2016-10-06 17:56 (UTC)

I just noticed the package has been disowned. I have adopted the package and I will give it a try to upgrade it... Any help is appreciated.

ArthurBorsboom commented on 2016-10-06 17:54 (UTC)

Any indication to upgrade the package to 4.7? Need help?

daniel_shub commented on 2016-08-30 18:24 (UTC)

I also cannot build 4.5.1 in a clean chroot. It looks like Xen has moved on to 4.7.0: https://www.xenproject.org/downloads/xen-archives/supported-xen-project-47-series/xen-470.html @kantras any chance of getting an update or taking on a co-maintainer to help out. The PKGBUILD is way beyond my comfort level to help with and I don't really have hardware to test on so I am really of no help.

cypher_zero commented on 2016-08-25 02:56 (UTC) (edited on 2016-08-25 03:00 (UTC) by cypher_zero)

Package is currently broken; needs to be updated to support GCC 6, etc. Have tried modifying current PKGBUILD with -Wno-misleading-indentation flag on line 129: export CFLAGS='-fno-caller-saves -Wno-misleading-indentation' makepkg still fails to build.

nevr0sed commented on 2016-08-17 09:31 (UTC)

Hi, Can't compile from the AUR repo. Here I get this error, same as the last comment. non-fatal.c: In function 'init_nonfatal_mce_checker': non-fatal.c:97:5: error: this 'if' clause does not guard... [-Werror=misleading-indentation] if ( __get_cpu_var(poll_bankmask) == NULL ) ^~ non-fatal.c:103:2: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if' switch (c->x86_vendor) { ^~~~~~ after looking around a bit, it seems that the the 4.5.3 fixes this issues. Can the maintainer of this package update it ? Thanks. n.

xiangzhai commented on 2016-08-12 02:28 (UTC)

non-fatal.c: In function 'init_nonfatal_mce_checker': non-fatal.c:97:5: error: this 'if' clause does not guard... [-Werror=misleading-indentation] if ( __get_cpu_var(poll_bankmask) == NULL ) ^~

newsboost commented on 2016-07-23 20:52 (UTC) (edited on 2016-07-24 13:28 (UTC) by newsboost)

I tried many times, but couldn't make this work - as other people also wrote... I then first re-compiled binutils ( http://stackoverflow.com/questions/20858175/how-to-boot-xen-hypervisor-from-uefi-using-gummiboot-under-arch-linux ) and then did "git clone https://gitlab.com/johnth/aur-xen/" followed by "makepkg" and maybe here I had to do "pacman -S mingw-w64-binutils" and finally "pacman -U xen-4.7.0-1-x86_64.pkg.tar.xz". xen-4.7.0-1 seemed to be installed, however I couldn't make xen work. This is the first time for me on arch linux. Later I downloaded https://gitlab.com/johnth/aur-xen/tree/xen-4.6 and repeated. I think this is better, although now I want to see if I can make it work with virt-manager. Just a hint of advice for anyone else who like me couldn't get the official arch Xen to work...

lazycat commented on 2016-06-20 07:58 (UTC)

Hello all, this package fails to create domU after update libiscsi from libiscsi-1.13.0-1-x86_64 to libiscsi-1.17.0-2-x86_64, After this update it's can't find "libiscsi.so.4" Downgrade is helpful.

daniel_shub commented on 2016-04-04 16:22 (UTC)

Is your plan to create a xen-4.5 package and keep xen as the most current? If so, you might want to consider creating a xen-4.6 package at the same time. That way someone who wants to stay on the 4.x release, never has to change packages.

kantras commented on 2016-04-04 16:15 (UTC)

I'm actually finishing rebuilding the system I usually developed on, to be able to ramp back up again - I have been watching the comments, just been tied up with some work issues

daniel_shub commented on 2016-04-04 16:11 (UTC)

@frony0 I think it would be better to request to take over as maintainer instead of creating a new package. While having a xen-4.5 package wouldn't be bad, the xen package should track the latest version.

frony0 commented on 2016-04-04 15:57 (UTC)

BeepDog, perhaps post your version to aur under the name "xen-4.6", since kantras seems to be AWOL?

BeepDog commented on 2016-03-29 00:36 (UTC)

I used the 4.6.1 packages that @JohnTh provided on gitlab: https://gitlab.com/johnth/aur-xen/tree/master Works great, but does not include pvgrub (I guess that's part of stubdom?) I've got a feature request open for grub2 in core to include the PvGrub2 stuff: http://wiki.xen.org/wiki/PvGrub2 and https://bugs.archlinux.org/task/44201 I'm gonna try to build a custom grub package real quick so I can use that pvgrub2, because it's supposed to be WAY better than pvgrub and pygrub.

vmaffione commented on 2016-03-17 21:46 (UTC) (edited on 2016-03-17 21:48 (UTC) by vmaffione)

I managed to compile it, by means of the following changes 1) do what hypernetoman suggests (removing a comment in a public header file) 2) applying this patch to PKGBUILD --- PKGBUILD 2016-03-17 22:45:49.670416160 +0100 +++ PKGBUILD.old 2016-03-17 22:45:31.183750160 +0100 @@ -129,7 +129,7 @@ build() { export CFLAGS=-fno-caller-saves ./autogen.sh ./configure PYTHON=/usr/bin/python2 --prefix=/usr --sbindir=/usr/bin --with-sysconfig-leaf-dir=conf.d --with-initddir=/etc/init.d \ - --enable-systemd --disable-docs --enable-stubdom --enable-qemu-traditional --enable-rombios \ + --enable-systemd --disable-docs --disable-stubdom --enable-qemu-traditional --enable-rombios \ --with-extra-qemuu-configure-args="--disable-bluez --disable-gtk --enable-spice --enable-usb-redir" # --enable-ovmf make LANG=C PYTHON=python2 } @@ -147,6 +147,9 @@ package() { install -Dm755 "$srcdir/09_xen" etc/grub.d/09_xen install -Dm644 "$srcdir/efi-xen.cfg" etc/xen/efi-xen.cfg + mkdir -p usr/lib/systemd/system + cp $srcdir/$pkgname-$pkgver/tools/hotplug/Linux/systemd/xenstored* usr/lib/systemd/system + # Fix paths in scripts, move to right locations and create missing directories sed -i 's:/var/run:/run:' etc/init.d/xencommons sed -i 's:/var/lock:/run/lock:' etc/xen/scripts/hotplugpath.sh

lembang commented on 2016-03-01 20:56 (UTC)

@johnTh by modifying the ferror it helps to compile the package, although this is not a real solution for this. Thank you. I force the test to always return 0

JohnTh commented on 2016-02-29 22:09 (UTC)

I am also getting this error. It was not happening a week ago. Package updates have broken something. The step that is failing is configuring stubdom/gmp-x86_64 Details are in stubdom/gmp-x86_64/config.log The sizeof type test configure programs build fine, but when run, return 1 because ferror(...) returns 1 after fprintf(...) in the programs built in this Xen build environment. This stops the configure, thought the programs still seem to function as intended, putting type sizes in conftest.val. Search for ferror in stubdom/gmp-x86_64/configure to show or modify the programs. I am still looking into why and how to fix.

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 11 Next › Last »