Package Details: xen 4.19.1pre-1

Git Clone URL: https://aur.archlinux.org/xen.git (read-only, click to copy)
Package Base: xen
Description: Open-source type-1 or baremetal hypervisor
Upstream URL: https://xenproject.org/
Keywords: hypervisor virtualization xen
Licenses: GPL2
Submitter: sergej
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 185
Popularity: 0.67
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-09-20 00:31 (UTC)

Pinned Comments

Refutationalist commented on 2024-05-22 22:08 (UTC) (edited on 2024-05-23 00:07 (UTC) by Refutationalist)

As of now (2024-22-05) Xen with stubdom doesn't build because of a problem in the imported code. Been this way for about two weeks. Anyone else seeing this behavior?

Also, there is a lot of work happening on Xen in my development repo, thanks to @Serus. Check it out at: https://github.com/refutationalist/saur

Latest Comments

« First ‹ Previous 1 .. 49 50 51 52 53 54 55 56 57 58 59 .. 101 Next › Last »

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.