Package Details: xen 4.9.0-1

Git Clone URL: https://aur.archlinux.org/xen.git (read-only)
Package Base: xen
Description: Virtual Machine Hypervisor & Tools
Upstream URL: http://www.xenproject.org/
Keywords: hypervisor virtualization xen
Licenses: GPL2
Conflicts: xen-4.2, xen-4.2-testing-hg, xen-4.3, xen-4.3-testing-hg, xen-4.4, xen-4.5, xen-4.6, xen-4.7, xen-4.8, xen-4.9, xen-gdbsx, xen-git, xen-hg-unstable, xen-igvtg, xen-rc
Provides: xen-4.9.0
Submitter: sergej
Maintainer: das_j
Last Packager: das_j
Votes: 172
Popularity: 0.699298
First Submitted: 2009-11-09 11:22
Last Updated: 2017-07-20 13:50

Dependencies (54)

Required by (0)

Sources (8)

Latest Comments

lazycat commented on 2017-09-03 04:10

@JohnTh
Thanks a lot, rebuilding kernel helped me

JohnTh commented on 2017-08-31 06:13

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

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

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:
https://xenbits.xen.org/gitweb/?p=xen.git;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: 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

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

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:
^~~~

All comments