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.32
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 9 10 11 Next › Last »

smakovits commented on 2014-07-17 12:10 (UTC)

Traced the issue to the lvm2 hook. Had a working system, added it and things did not boot again. removed the hook and once again the system booted fine. My original installation was on a lv so I needed it there. This time I used linux (83) for rootfs so it was not needed. I thought i needed it to load a vm when it didnt boot originally, but then the system didnt boot. Removed it and now things are happy again.

hugleo commented on 2014-07-13 15:10 (UTC)

Maybe it can be a video problem. Maybe xen booted but is not showing anything. Try press a key like Num Lock. Dou you notice that the led is blinking? If the answser is true maybe you can set a vesa driver or small resolution on grub boot parameter for xen kernel.

smakovits commented on 2014-07-12 04:12 (UTC)

ever since 4.4.0-3 and Kernel 3.15 my screen goes black upon booting xen. I tried syslinux and Grub with the same results. I re-installed arch at least times, keeping with the beginners guide and then xen install instructions. I have no idea what and why, but the screen just goes black and things require a hard reset. The normal arch kernel is fine, but nothing I do helps get me going. I even tried using downgrader to try older kernels, but those too had the same result.

trixpan commented on 2014-07-08 13:06 (UTC)

Kantras, Thanks for the update. Working like a charm. Any chances of adding Spice support to the PKG? Cheers

fatal-error commented on 2014-07-06 07:28 (UTC)

Errors when building @kantras: make[2]: Leaving directory '/[...]/AUR/xen/src/xen-4.4.0/xen' make[1]: Leaving directory '/[...]/AUR/xen/src/xen-4.4.0/xen' fatal: unable to connect to xenbits.xen.org: xenbits.xen.org[0: 50.57.170.242]: errno=Connection timed out Makefile:25: recipe for target 'seabios-dir' failed make[3]: *** [seabios-dir] Error 128 make[3]: Leaving directory '/[...]/AUR/xen/src/xen-4.4.0/tools/firmware' /[...]/AUR/xen/src/xen-4.4.0/tools/../tools/Rules.mk:105: recipe for target 'subdir-install-firmware' failed make[2]: *** [subdir-install-firmware] Error 2 make[2]: Leaving directory '/[...]/AUR/xen/src/xen-4.4.0/tools' /[...]/AUR/xen/src/xen-4.4.0/tools/../tools/Rules.mk:100: recipe for target 'subdirs-install' failed make[1]: *** [subdirs-install] Error 2 make[1]: Leaving directory '/[...]/AUR/xen/src/xen-4.4.0/tools' Makefile:96: recipe for target 'install-tools' failed make: *** [install-tools] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

tritron commented on 2014-07-02 15:01 (UTC)

Did anyone compile efi xen and set EFI VENDOR ?

isiachi commented on 2014-07-02 14:59 (UTC)

Hello! If you try to create an HVM guest with usb=1 you get this message: libxl: error: libxl_dm.c:1371:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1186:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1475:kill_device_model: Device Model already exited I solved installing usbredir. It's not a dependecy but an optional one for sure!

kantras commented on 2014-06-20 16:21 (UTC)

Uploading an update - key changes are the addition of two security patches and some initial work to clean up the PKGBUILD and the compiling process.

kantras commented on 2014-06-18 00:15 (UTC)

@ironicbadger: unfortunately I've not been able to reproduce this error yet - can you try building it again, capturing all output to a file, then send me a copy of that file, please? "makepkg >& build.log" should work if you're using a bash shell. Also, have you made any other changes to the PKGBUILD file? Added any other patches? are you up to date with all recent package updates? I will be uploading a new package sometime soon, but its only cleanup of the PKGBUILD and one of the patches at this point

ironicbadger commented on 2014-06-17 10:41 (UTC)

Having some errors when building @kantras. Makefile:74: recipe for target 'newlib-1.16.0' failed make[1]: *** [newlib-1.16.0] Error 1 make[1]: Leaving directory '/root/xen/src/xen-4.4.0/stubdom' Makefile:104: recipe for target 'install-stubdom' failed make: *** [install-stubdom] Error 2 ==> ERROR: A failure occurred in package(). Aborting...

kantras commented on 2014-06-14 20:35 (UTC)

@atondwal: I just tried rebuilding the package on my build machine and am unable to reproduce the issue you saw. Have you made any other changes to the source (such as adding additional patches)? Have you tried rebuilding from scratch (make sure to delete the src and pkg directories from where you are building the PKGBUILD file)? I'll continue to try some things but without being able to reproduce, its harder to fix.

atondwal commented on 2014-06-14 20:02 (UTC)

I'm getting some problems with the vhd libs during compilation... https://gist.github.com/atondwal/53dd5fe2bc954c2642b8

lucaoli commented on 2014-06-12 21:52 (UTC)

I've solved KVM issue patching xen-4.4.0/stubdom/Makefile: *** xen-4.4.0/stubdom/Makefile Mon Mar 10 11:43:57 2014 --- xen-4.4.0/stubdom/Makefile Thu Jun 5 20:10:11 2014 *************** gmp-$(XEN_TARGET_ARCH): gmp-$(GMP_VERSIO *** 165,171 **** rm $@ -rf || : mv gmp-$(GMP_VERSION) $@ #patch -d $@ -p0 < gmp.patch ! cd $@; CPPFLAGS="-isystem $(CROSS_PREFIX)/$(GNU_TARGET_ARCH)-xen-elf/include $(TARGET_CPPFLAGS)" CFLAGS="$(TARGET_CFLAGS)" CC=$(CC) $(GMPEXT) ./configure --disable-shared --enable-static --disable-fft --without-readline --prefix=$(CROSS_PREFIX)/$(GNU_TARGET_ARCH)-xen-elf sed -i 's/#define HAVE_OBSTACK_VPRINTF 1/\/\/#define HAVE_OBSTACK_VPRINTF 1/' $@/config.h touch $@ --- 165,171 ---- rm $@ -rf || : mv gmp-$(GMP_VERSION) $@ #patch -d $@ -p0 < gmp.patch ! cd $@; CPPFLAGS="-isystem $(CROSS_PREFIX)/$(GNU_TARGET_ARCH)-xen-elf/include $(TARGET_CPPFLAGS)" CFLAGS="$(TARGET_CFLAGS)" CC=$(CC) $(GMPEXT) ./configure --disable-shared --enable-static --disable-fft --without-readline --prefix=$(CROSS_PREFIX)/$(GNU_TARGET_ARCH)-xen-elf --host $(XEN_TARGET_ARCH) sed -i 's/#define HAVE_OBSTACK_VPRINTF 1/\/\/#define HAVE_OBSTACK_VPRINTF 1/' $@/config.h touch $@

lucaoli commented on 2014-06-03 21:55 (UTC)

I'm trying to compile xen on a KVM Host, but I receive the following error: checking compiler gcc -mno-red-zone -O1 -fno-omit-frame-pointer -m64 -mno-red-zone -fno-reorder-blocks -fno-asynchronous-unwind-tables -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-error=maybe-uninitialized -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs -fno-stack-protector -fno-exceptions has sizeof(long)==4... no configure: error: could not find a working compiler, see config.log for details Makefile:164: recipe for target 'gmp-x86_64' failed make[1]: *** [gmp-x86_64] Error 1 make[1]: Leaving directory '/home/lucaoli/xen/src/xen-4.4.0/stubdom' Makefile:104: recipe for target 'install-stubdom' failed make: *** [install-stubdom] Error 2 In xen-4.4.0/stubdom/gmp-x86_64/config.log I've found: configure:5631: gcc -mno-red-zone -O1 -fno-omit-frame-pointer -m64 -mno-red-zone -fno-reorder-blocks -fno-asynchronous-unwind-tables -m64 -g -fno-str ict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-error=maybe-uninitialized -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unuse d-local-typedefs -fno-stack-protector -fno-exceptions -c conftest.c >&5 conftest.c:2:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] main () ^ conftest.c: In function 'main': conftest.c:4:14: error: size of array 'test_array' is negative static int test_array [1 - 2 * (long) (sizeof (long) != 4)]; ^ What does mean "could not find a working compiler"? I think it's normal that on a x86_64 architecture sizeof(long) is 8 and than not 4.

kantras commented on 2014-05-20 00:22 (UTC)

trixpan, I probably will but haven't had a chance to play with it too much yet so want to do that first.

kantras commented on 2014-05-17 16:16 (UTC)

I found out about this patch a couple of days ago - it should be a part of the next release; I'm just checking in case theres anything else to go in, and will upload a new version later today once I've done my usual build-testing

isiachi commented on 2014-05-17 12:00 (UTC)

This patch came from the stable-4.4 branch of xen. I made this package: http://downloads.rhyeworld.it/static/xen-4.4.0-3.src.tar.gz I've already applied the patch.

chetwisniewski commented on 2014-05-17 00:08 (UTC)

I have had the shutdown issue as well. Is this a patch that will be integrated upstream or more of a personal hack?

isiachi commented on 2014-05-16 19:39 (UTC)

Hi! This is a very good package! I've got only one problem when try to restart or shutdown pvh guests. The entire xen system stuck and I have to manually reboot the entire system. I've solved adding this patch: http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=3a148e0a7ee0ae56a498be5ba973314ec50cd999

trixpan commented on 2014-05-09 11:11 (UTC)

Kantras, Not sure what your opinion is about this but it may be a good idea to add a patch to enable SPICE on QEMU upstream (as documented on http://wiki.xenproject.org/wiki/SPICE_support_in_Xen#QEMU_Upstream) Please note that this would also require adding the following dependencies: - spice (https://www.archlinux.org/packages/extra/i686/spice/) - spice-protocol (https://www.archlinux.org/packages/extra/any/spice-protocol/) - usbredir Modified PKGBUILD => http://pastebin.com/eiJmLFfe Patch to enable SPICE => http://pastebin.com/msDz41yT Cheers

mbroemme commented on 2014-05-09 00:27 (UTC)

Regarding the ATI passthrough patch. It doesn't work anymore with Xen 4.4. I've tried it with two different Radeon cards (7870 GHz and R9 290X).

kantras commented on 2014-05-04 23:51 (UTC)

Updated packages (for xen and xen-4.3) have been uploaded - key changes are the inclusion of the gcc 4.9.0 compile patch (Thanks to the Fedora project), another security patch and a new 09_xen file (uses 10_archlinux as a base, adding in the xen specifics)

kantras commented on 2014-05-03 17:28 (UTC)

methril: Thanks - I had actually spotted that patch already and was adjusting my build environment to make sure I was testing this (and a few other things) before releasing another update later today.

methril commented on 2014-05-03 13:55 (UTC)

Hi all, I have fixed the xen compilation with gcc 4.9.0 patch (from fedora bugtracking) http://pastebin.com/sGWTSU2s and PKGBUILD changes http://pastebin.com/rgNsPFhw (I have enabled ati passthrough)

dante82 commented on 2014-05-02 16:15 (UTC)

Thanks for the package. When installing I get an error related to the blktap2 drivers in the install-tools package (the same error in the xen-4.3 package): gcc -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__ -MMD -MF .block-qcow.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls -Werror -g -Wno-unused -fno-strict-aliasing -I../include -I../drivers -I/home/sneaker15/xen/src/xen-4.4.0/tools/blktap2/drivers/../../../tools/libxc -I/home/sneaker15/xen/src/xen-4.4.0/tools/blktap2/drivers/../../../tools/include -D_GNU_SOURCE -DUSE_NFS_LOCKS -fPIC -c -o block-qcow.o block-qcow.c block-qcow.c: In function 'get_cluster_offset': block-qcow.c:431:3: error: 'tmp_ptr' may be used uninitialized in this function [-Werror=maybe-uninitialized] memcpy(tmp_ptr, l1_ptr, 4096); ^ block-qcow.c:606:7: error: 'tmp_ptr2' may be used uninitialized in this function [-Werror=maybe-uninitialized] if (write(s->fd, tmp_ptr2, 4096) != 4096) { ^ cc1: all warnings being treated as errors Can someone help?

fmarchand commented on 2014-05-01 19:25 (UTC)

Hi,thanks for the package. It seems that the "09_xen" grub file does not take into account Btrfs/ZFS FS such as it is done in "10_linux" for example (no "ZFS=" neither "rootflags=" options added in the "module" line).

kantras commented on 2014-04-15 06:46 (UTC)

Just a quick FYI - They've reverted a patch in the recent kernel releases, which may cause instabilities with applications (such as Firefox) running under PV domains (also dom0, which is technically a PV domain). The patch worked for this use case, but broke other things, so the patch was reverted and a new one is being worked on.

trixpan commented on 2014-03-28 13:21 (UTC)

kantras, thank you for the fix. Being a migrant from debian to arch+xen I it took me a while to pinpoint the grub issue was not some sort of chair <-> keyboard interface on this side of the screen... :-) I managed to get and Haswell GPU passed through a Linux domU without major issues

kantras commented on 2014-03-27 23:24 (UTC)

@daniel_shub: I had it fixed in my local copy, but was just waiting for something else to include with it - the new 4.4.0-2 that I'm uploading should have a security patch as well as the grub fix (also updating xen-4.3 with the same patch)

daniel_shub commented on 2014-03-27 11:10 (UTC)

Thank you for the great package and keeping it up to date. I had no problem building and installing the package and seems to work great. The only issue I am having is with my GRUB boot menu. Have you gotten a chance to fix the issue with xen-syms? Is it as simple as adding something like mv boot/$pkgname-syms-* etc/xen/scripts/ after # Compress syms file gzip boot/$pkgname-syms-* although I am not sure why the syms kernel should go in the scripts directory, but I don't know where else to put it.

Oimelchen commented on 2014-03-22 18:05 (UTC)

@ironicbadger: Hi, I saw your blog entry before, but for me, it didn't work with Windows 7. After a reboot of the VM, the Host system did not crash, but I was not able to get the GFX adapter back to life! However, when I reboot the Linux VM (Linux Mint 16), the host system crashed every time! So far, I have not found any solution. If you have an idea, I would be glad to hear about it. :-) Only the switch to the XM toolkit helped!

ironicbadger commented on 2014-03-22 08:52 (UTC)

@Olmelcehn All you need do is eject the card from the VM before reboot. I wrote about doing this automatically on Win 8 (I had no joy with 7) here. http://blog.ktz.me/?p=219

Oimelchen commented on 2014-03-22 08:04 (UTC)

Hi, thanks a lot for this package. It builds without any problem (even with the ati-passthrough patch enabled). I was able to passthrough two Radeon 5670 gfx cards to two separate VMs (one to Win7 VM and the other one to a Mint VM, both in secondary passthrough). Unfortunatly when using the xl tool stack, I am not able to restart the VMs, the dom0 totally crashes. So I tried to rebuild this package with enabled xm toolset. When using the same Vms with the xm toolset, every seems to work like charm! This might be a useful hint for those, who try to get to do similar things. :-) So, as a recommendation, could you add the xm toolset to the PKGBUILD by adding the flag --enable-xend to the configure command? I know, it is deprecated, but at least it is a working alternative (at least for me).

kantras commented on 2014-03-18 13:20 (UTC)

Glad to hear its working - I had suspected it being something like a mismatch between the kernel and the toolset, hence the suggestion to run xl info to confirm. The other command I mentioned was to check that a certain value had been set up correctly in xenstored (its the same one that tritron was referring to) as this is a requirement for xen 4.4. It is in the package but it doesn't hurt to make sure all the basics are covered - often the most simplest issue can be the most annoying, so always check the basics first and build up from there.

3000 commented on 2014-03-18 08:40 (UTC)

wow, when I tried xl info I realized that I copied an earlier Version of xen.efi to my boot Directory. Now the problem is fixed! thanks a lot for your help guys!

tritron commented on 2014-03-17 19:51 (UTC)

I wonder if anyone is interested in getting ovirt running under arch linux since libvirt and xen 4.4 work together now.

kantras commented on 2014-03-17 13:53 (UTC)

you may also find some more details if you turn on more verbose logging when you start the domain, something like: xl -vvvvv create <path to config file>

kantras commented on 2014-03-17 13:48 (UTC)

@3000: to help start to debug this - whats the output from the following commands (run as root): xl info xenstore-read /local/domain/0/domid also, what do you have as the config file for the windows domU and for your grub.cfg file? (can send to me directly if you don't want to post those details)

tritron commented on 2014-03-17 13:36 (UTC)

Does your xenstored.service has a line ExecStartPost=/usr/bin/xenstore-write "/local/domain/0/domid" 0 after ExecStartPost=/usr/bin/xenstore-write "/local/domain/0/name" "Domain-0"

3000 commented on 2014-03-17 12:59 (UTC)

nope, that doesn't work either :( thanks anyway!

hugleo commented on 2014-03-17 12:37 (UTC)

The following config works for me: kernel = "/usr/lib/xen/boot/hvmloader" builder='hvm' memory = 1024 device_model='/usr/lib/xen/bin/qemu-dm' shadow_memory = 8 name = "winxxx" vif = [ 'mac=00:16:3e:11:11:11,bridge=xenbr0', ] disk = [ 'phy:/vms/winxx.img,hda,w' ] boot = "dc" usb = 1 usbdevice = 'tablet' vnc = 1 sdl = 0 vncdisplay=1 #keymap='en' on_xend_stop = 'shutdown'

3000 commented on 2014-03-17 12:15 (UTC)

Hi, just wanted to upgrade. It built fine, without any Problems whatsoever, so great Job kantras! But when I try to start Windows I get this error: libxl: error: libxl_dom.c:281:libxl__build_post: Failed to set event channel limit to 1023 (-1) libxl: error: libxl_create.c:1022:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device model pid in /local/domain/3/image/device-model-pid libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_model failed for 3 what can I do to fix this? thanks a lot!

kantras commented on 2014-03-11 21:37 (UTC)

So, it should be being ran, the problem would be that the script was modified more than just the default kernel (for example, LTS kernels) and it seems to think that the xen-syms file is another kernel. I'll update the package (following the old 4.3.2 package by moving syms to a different location) and upload an updated version

hugleo commented on 2014-03-11 21:03 (UTC)

If I generate the grub.cfg are the 09_xen script being executed? The boot order must be xen-4.4.0.gz kernel to the first place instead of xen-syms

kantras commented on 2014-03-11 16:55 (UTC)

I had two source tarballs prepared - one for whilst I was debugging across multiple systems and one for release - guess which one I uploaded .. Reuploaded with exit removed.

panda commented on 2014-03-11 13:58 (UTC)

There is a mistake in the PKGBUILD file. Just before the ATI patch, in the prepare statement, an exit is breaking makepkg. If this is intentional, please advise. Tx for the package however.

kantras commented on 2014-03-11 05:03 (UTC)

Since I don't really have the setup/time currently to test it properly (I'm using a hardware modified NVidia card for passthrough) I've included the patch but left it commented out; when uncommented it did build, but is untested.

evilsephiroth commented on 2014-03-10 21:26 (UTC)

do we have to enable the patch in the building process?

kantras commented on 2014-03-10 21:15 (UTC)

Ok, resolved - driver issue within the VM; once I reloaded the drivers, it came up without an issue. Tested loading a game as well as re-evaluating the Windows Experience Index. Uploading the update now.

kantras commented on 2014-03-10 20:24 (UTC)

OK, build tests completed. I've uploaded the new package xen-4.3 for anyone who doesn't want to upgrade to 4.4 yet. Unfortunately, i'm currently trying out 4.4 on a devel workstation and GPU passthrough isn't working for me. I've started to look into it, as well as research options to resolve; theres been a major rework of qemu-xen which completely breaks the patch we previously used to get this to work better. At this stage, I can upload what I have so far, but be warned that I can't confirm whether gpu passthrough will work for you (as I can't personally do it right now)

kantras commented on 2014-03-10 17:31 (UTC)

@BeepDog: Yes, currently in build-testing @kingd: am aware, currently in build-testing @evilsephiroth: I would suspect so; theres not been too much recent changes on that front, from what I've been following on the change log

evilsephiroth commented on 2014-03-10 16:18 (UTC)

xen 4.4 suffers from ati passtrough problems? or the patch has been included?

kingd commented on 2014-03-10 16:15 (UTC)

Xen 4.4 has just been released. http://blog.xen.org/index.php/2014/03/10/xen-4-4-released

BeepDog commented on 2014-03-10 15:59 (UTC)

We going to have a xen-4.3 aur package? Or not so much? Just curious

kantras commented on 2014-02-24 05:00 (UTC)

Good to hear. FYI, I've actually grabbed a copy of the latest xen RC (4.4.0-rc5) and will be testing building it over the next few days, partly to make sure we're ready when its finally released and to see if theres any more optimizations which can be made. The bios patch (which works around buggy IVRS tables) will be retired as the new version allows you to override the IOAPIC and HPET entries via command line options.

zman0900 commented on 2014-02-24 04:32 (UTC)

Thanks. Running 3.13.5 right now (still xen 4.3.1) and the bug appears to be gone :-)

kantras commented on 2014-02-24 04:28 (UTC)

http://lists.xen.org/archives/html/xen-devel/2014-02/msg00199.html - its also on the kernel mailing list as well; I tested it on an earlier kernel in the 3.13 branch and the kernel bug went away.

zman0900 commented on 2014-02-24 04:05 (UTC)

That's great, I'll try that new kernel out right away. Do you happen to have a link to that patch? I'm curious but Google isn't being helpful.

kantras commented on 2014-02-24 03:55 (UTC)

Actually it looks like 3.13.5 just left testing and now is in core, so should find firefox more stable once you've upgraded.

kantras commented on 2014-02-24 03:48 (UTC)

The "firefox" issue is actually a kernel issue - changes were made to how NUMA pages are handled, which causes random crashs within dom0 and/or PV domU's (HVM domUs are not affected) I've been tracking the fix and its been included in the 3.14 RC's as well as the latest 3.13.5 (which you can download from the testing repository.) I have a copy of the patch if you want to recompile your own older kernel (Patch is also available on the xen-devel list archives)

zman0900 commented on 2014-02-24 02:23 (UTC)

@discord, @hugleo: I too have been having the issues with firefox. I'm still running xen 4.3.1, but building 4.3.2 right now to test. Anything after kernel 3.12.6 causes random crashes quickly after starting firefox. After a crash, X is frozen but I can still connect with ssh. No amount of killing or restarting programs will bring it back though. I can see numerous stack traces in dmesg about "bad page map in process firefox". Sometimes "bad page state" instead. Starting firefox in safe mode works, so I deleted and resynced my profile then started re-enabling addons one by one, but I can't seem to isolate the problem so I've also switched to Chrome for now. At first I though it was graphics related, but the crash still happens if I start firefox over ssh X forwarding to another machine. Doesn't seem to be hardware related either since I've recently switched motherboard and gpu (from using nouveau to radeonsi). Let us know here if anyone has any luck with this problem, I'm quite partial to Firefox. I'll post my results of testing 4.3.2 soon.

kantras commented on 2014-02-20 06:51 (UTC)

4.3.2-1 has just been uploaded after build-testing on a couple of boxes. Apart from the version bump, this build attempts to download several of the source tarballs ahead of time - this means that we can ensure they are not corrupted/changed before they are used during compile.

ironicbadger commented on 2014-02-15 23:36 (UTC)

if it helps... http://unraidrepo.ktz.me/xen-4.3.1-2-x86_64.pkg.tar.xz

k1.hedayati commented on 2014-02-15 19:32 (UTC)

install -m0755 -p mini-os-x86_32-vtpmmgr/mini-os.gz "~/Downloads/xen/pkg/xen/usr/lib/xen/boot/vtpmmgr-stubdom.gz" make[1]: Leaving directory '~/Downloads/xen/src/xen-4.3.1/stubdom' gzip: boot/xen-syms-4.3.1: No such file or directory ==> ERROR: A failure occurred in package(). Aborting... :((

ironicbadger commented on 2014-02-01 19:53 (UTC)

gets my vote.

kantras commented on 2014-02-01 19:52 (UTC)

Just wanted to give a heads up on my thoughts; With upcoming releases of xen 4.3.2 and 4.4.0 coming soon, what I may do is rename this package to 'xen-4.3' and then update the PKGBUILD to 4.4.0 and release that as xen.

hugleo commented on 2014-01-27 18:42 (UTC)

Crashed again, a little more stable however.

hugleo commented on 2014-01-27 15:09 (UTC)

I think the upgrade do the trick. discord, try to upgrade your system.

hugleo commented on 2014-01-27 11:18 (UTC)

I've experienced that problem too. Everytime I open firefox browser I notice cpu racing and I must restart my system due a unresponsive system. I'm using chrome browser for now. That problem comes about tree weeks ago after a bunches of arch updates. Today I'll upgrade to the new kernel linux-3.12.9-1 and I'll let you know if that solve the problem.

kantras commented on 2014-01-25 21:13 (UTC)

@discord - I've personally not experienced that issue on any of the deployments that I've performed with xen, or had anyone else report that issue recently (either on here or via the xen-users mailing list) What I would suggest doing is posting a question on the xen-users email group, including information which would be useful in helping to find out what exactly the issue you are experiencing is; details like hardware specs, configuration options, results from log files, etc - like any kind of mystery, you need to be gathering all the clues to be able to solve a problem.

discord commented on 2014-01-25 19:39 (UTC)

My system has been crashing frequently after installing the xen package. Even without running any domU's. I look at top when the cpu is racing. I've seen kworker hogging the cpu. I've seen mplayer hogging the cpu. Sometimes when I run htop I see 30 firefox processes but only one in regular top. Haven't had any stability issues without xen, or with the grub option without xen.

3000 commented on 2014-01-13 18:41 (UTC)

wow, thanks a lot @ zman0900, that did the trick indeed! Working quite nicely

michaelharwood commented on 2013-12-30 03:02 (UTC)

@malinas - I had the same issue and it appears it is a problem with git://xenbits.xen.org/seabios.git. I manually cloned the seabios folder using git clone http://xenbits.xen.org/git-http/seabios.git in the correct folder and restarted the Arch package build process and it's running fine now.

zman0900 commented on 2013-12-27 16:24 (UTC)

@3000: You need to recompile binutils from ABS with the required options. Details are farther down in the comments.

3000 commented on 2013-12-27 16:21 (UTC)

hi, I gotta question: I am trying Xen on a new archlinux system and it compiled just fine. BUT it didn't create a xen.efi. do you guys know why?

kantras commented on 2013-12-25 21:30 (UTC)

@malinas Hmm, will try again in a little while - my primary dev machine was down for a couple of days, but is back so can do some more testing.

malinas commented on 2013-12-25 13:47 (UTC)

@kantras.. ye.. well, indeed something has happened. I could compile some days ago, but somehow have not had the package saved.. Now when I try to compile, it seems to fail on the seabios (patch?) recipe in makefile.

malinas commented on 2013-12-21 19:30 (UTC)

@kantras.. np. I have to say I also built in the end fine, just 3 days ago or so. Just want to add, thanks for keeping this updated and man is Xen awesome!!! :)

kantras commented on 2013-12-19 20:21 (UTC)

@meltfund: That looks like one of the dependancies might not have downloaded correctly (during compile, the Makefiles pull down a number of additional sources, patch and compile against them) - I'm currently modifying the PKGBUILD to download those before compile, confirm they downloaded correctly, then copy them into place so the build scripts can make use of them) - should have a new version uploaded later today (after I've finished a couple of build tests - both on bare metal and under a virtual environment)

meltfund commented on 2013-12-19 19:15 (UTC)

Similar build problem on this system today http://pastebin.com/nHgDssf2

meltfund commented on 2013-12-19 19:14 (UTC)

Built fine on this system last week http://pastebin.com/AfKiQLrt

thouveng commented on 2013-12-19 16:17 (UTC)

@kantras: In fact it is a little bit strange because I've two laptops and both have archlinux 64bits installed. The problem occurs only on one of them. It is a Dell latitude E5520 and I'm trying to build xen directly on the baremetal, I mean I'm not inside a VM or a container.

kantras commented on 2013-12-19 06:27 (UTC)

I've been trying to reproduce both the compile issues listed and still am unable to; all rebuild attempts have been successful. I'm going to continue to try and reproduce the issues, but if people could share more details on the hardware that they are trying to build on, that may help narrow things down

amber commented on 2013-12-19 03:43 (UTC)

ld -nostdlib -L/tmp/yaourt-tmp-root/aur-xen/src/xen-4.3.1/stubdom/cross-root-i686/i686-xen-elf/lib -m elf_i386 -T arch/x86/minios-x86_32.lds /tmp/yaourt-tmp-root/aur-xen/src/xen-4.3.1/stubdom/mini-os-x86_32-vtpmmgr/mini-os.o -o /tmp/yaourt-tmp-root/aur-xen/src/xen-4.3.1/stubdom/mini-os-x86_32-vtpmmgr/mini-os ld: warning: section `.bss' type changed to PROGBITS gzip -f -9 -c /tmp/yaourt-tmp-root/aur-xen/src/xen-4.3.1/stubdom/mini-os-x86_32-vtpmmgr/mini-os >/tmp/yaourt-tmp-root/aur-xen/src/xen-4.3.1/stubdom/mini-os-x86_32-vtpmmgr/mini-os.gz make[2]: Leaving directory '/tmp/yaourt-tmp-root/aur-xen/src/xen-4.3.1/extras/mini-os' install -d -m0755 -p "/tmp/yaourt-tmp-root/aur-xen/pkg/xen/usr/lib/xen/boot" install -m0755 -p mini-os-x86_32-vtpmmgr/mini-os.gz "/tmp/yaourt-tmp-root/aur-xen/pkg/xen/usr/lib/xen/boot/vtpmmgr-stubdom.gz" make[1]: Leaving directory '/tmp/yaourt-tmp-root/aur-xen/src/xen-4.3.1/stubdom' gzip: boot/xen-syms-4.3.1: No such file or directory ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build xen. I have builded xen twice. xen is 4.3.1

kantras commented on 2013-12-18 14:24 (UTC)

@malinas: Thanks, will get that added in @thouveng: I'm retesting building right now to try and reproduce - the file in question is the defaults for the xendomains script (used when you want to auto-start domUs on startup) so isn't critical if not using it

malinas commented on 2013-12-18 13:15 (UTC)

libseccomp is missing as a dependency, which makes launching domU's a no go.

thouveng commented on 2013-12-17 18:13 (UTC)

I still have the same problem. To fix it I commented the following line in function package() in PKGBUILD: mv etc/default/xendomains etc/conf.d/xendomains Now it seems OK but I didn't know what is the impact of this comment? At the end of the log there are two warnings about backup entry file that is not in package. make[1]: Leaving directory '/home/thouveng/builds/xen/src/xen-4.3.1/stubdom' ==> Tidying install... -> Purging unwanted files... -> Removing libtool files... -> Removing static library files... ==> WARNING: backup entry file not in package : etc/conf.d/xendomains ==> WARNING: backup entry file not in package : etc/default/xencommons -> Compressing man and info pages... ==> Creating package "xen"... -> Generating .PKGINFO file... -> Adding changelog file... -> Adding install file... -> Generating .MTREE file... -> Compressing package... ==> Leaving fakeroot environment. ==> Finished making: xen 4.3.1-2 (Tue Dec 17 19:08:40 CET 2013)

Refutationalist commented on 2013-12-12 18:12 (UTC)

Sorry, replace "Xen" with "KVM" in that last comment. I use xen on servers, kvm on desktops.

Refutationalist commented on 2013-12-10 21:36 (UTC)

Got it. I was compiling it under Xen, and without a specific CPU definition configured, gmp assumes that you're in 32bit, and compilation fails. Defined a CPU and it compiled fine.

Refutationalist commented on 2013-12-09 20:23 (UTC)

Having the same issue, but higher up in the log there's a thrown error about gmp: test -z "/usr/local/share/info" || mkdir -p -- . "/usr/local/share/info" mkdir: cannot create directory '/usr/local/share/info': Permission denied Makefile:482: recipe for target 'install-info-am' failed make[5]: *** [install-info-am] Error 1 make[5]: Leaving directory '/home/sam/xen/src/xen-4.3.1/stubdom/gmp-x86_64/doc' Makefile:437: recipe for target 'install-am' failed make[4]: *** [install-am] Error 2 make[4]: Leaving directory '/home/sam/xen/src/xen-4.3.1/stubdom/gmp-x86_64/doc' Makefile:925: recipe for target 'install-recursive' failed make[3]: *** [install-recursive] Error 1 make[3]: Leaving directory '/home/sam/xen/src/xen-4.3.1/stubdom/gmp-x86_64' Makefile:1191: recipe for target 'install' failed make[2]: *** [install] Error 2 make[2]: Leaving directory '/home/sam/xen/src/xen-4.3.1/stubdom/gmp-x86_64' Makefile:175: recipe for target 'cross-root-x86_64/x86_64-xen-elf/lib/libgmp.a' failed make[1]: *** [cross-root-x86_64/x86_64-xen-elf/lib/libgmp.a] Error 2 make[1]: *** Waiting for unfinished jobs....

thouveng commented on 2013-12-08 17:43 (UTC)

It seems that compilation goes well but an error occurs during packaging. [thouveng:~/builds/xen] $ tail xen-4.3.1-2-x86_64-package.log ld -nostdlib -L/home/thouveng/builds/xen/src/xen-4.3.1/stubdom/cross-root-i686/i686-xen-elf/lib -m elf_i386 -T arch/x86/minios-x86_32.lds /home/thouveng/builds/xen/src/xen-4.3.1/stubdom/mini-os-x86_32-grub/mini-os.o -o /home/thouveng/builds/xen/src/xen-4.3.1/stubdom/mini-os-x86_32-grub/mini-os ld: warning: section `.bss' type changed to PROGBITS gzip -f -9 -c /home/thouveng/builds/xen/src/xen-4.3.1/stubdom/mini-os-x86_32-grub/mini-os >/home/thouveng/builds/xen/src/xen-4.3.1/stubdom/mini-os-x86_32-grub/mini-os.gz make[2]: Leaving directory '/home/thouveng/builds/xen/src/xen-4.3.1/extras/mini-os' install -d -m0755 -p "/home/thouveng/builds/xen/pkg/xen/usr/lib/xen/boot" install -m0644 -p mini-os-x86_32-grub/mini-os.gz "/home/thouveng/builds/xen/pkg/xen/usr/lib/xen/boot/pv-grub-x86_32.gz" make[1]: Leaving directory '/home/thouveng/builds/xen/src/xen-4.3.1/stubdom' mv: cannot stat ‘etc/default/xendomains’: No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

kantras commented on 2013-11-25 10:28 (UTC)

AUR packages updated, also included the three latest security patches

Sydney6 commented on 2013-11-25 03:53 (UTC)

Yes, you can.

j-lap commented on 2013-11-25 03:50 (UTC)

@zman0900 - Already installed "bluez", no dice. Build fails because it is looking for dependency "bluez4". Can I simply edit "bluez4" to "bluez" in the PKGBUILD?

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