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.63
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-09-20 00:31 (UTC)

Dependencies (63)

Sources (7)

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 .. 40 41 42 43 44 45 46 47 48 49 50 .. 101 Next › Last »

kantras commented on 2015-01-15 18:32 (UTC)

I will look at that patch when I transition this over to become xen-4.4 (as "xen" will be moving over to match the 4.5 release) Note: I am currently away from my systems so the package update will be delayed until I get back this weekend and can run everything through final tests.

zir_blazer commented on 2015-01-15 13:22 (UTC)

@tritron Are you sure than that patch is needed at all? As far that I know the RAM limit when using VGA Passthrough was fixed sometime during Xen 4.3, as with the xen-4.3 AUR package, I was able to get it working with > 4 GB RAM on a WXP x64 DomU. See this: http://i.imgur.com/a37aoZF.png With Xen 4.4, I had regressions with PCI Passthrough (Sound Card makes nasty noises everytime that it reproduces a sound), and VGA Passthrough was a total no go, this was regardless if I was using 2 GB of RAM or more. Did you successfully managed to get VGA Passthrough working with less than 3.5 GB without the patch and more with it? I would be surprised cause this means yet another regression on Xen 4.4 vs 4.3, through if that patch fixes it we're already covered.

tritron commented on 2015-01-15 04:07 (UTC)

Can this patch be added ? http://xenbits.xen.org/gitweb/?p=xen.git;a=patch;h=d06886694328a31369addc1f614cf326728d65a6 It solves memory limit of 3.5gb when assigning vga card. Without this patch I get not enough resources error 12

BeepDog commented on 2015-01-10 18:59 (UTC)

Firstly, thanks for all the work keeping the xen package up to date. I just got it set up and working and it's working great! I thought I'd share this, in case anyone else is interested in booting a grub2 (which is what arch ships with) on a guest VM: https://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/ I haven't done it yet, but it seems .... reasonably straight forward.

ArthurBorsboom commented on 2015-01-03 16:38 (UTC)

Hi Kantras, I found another way to customize the Xen bootloader. You need to edit the /etc/xen/grub.conf file, as described in the Grub section here. https://wiki.archlinux.org/index.php/xen No need to research any further.

ArthurBorsboom commented on 2014-12-31 10:10 (UTC)

That sounds good to me. Thanks!

kantras commented on 2014-12-31 10:05 (UTC)

Hi ArthurBorsboom, The short version is that it never has supported using those options in /etc/default/grub, even before I took maintainership of it; the rewrite I did was keeping with existing functionality, just extending it to also support the lts kernels. I'm actually working on the PKGBUILD for 4.5 now, so I'll add a task to myself to look into 09_xen vs 20_linux_xen (which is the script which comes packaged with grub that uses that variable) and decide which way is best to go to ensure existing configurations aren't broken by any changes I make either.

ArthurBorsboom commented on 2014-12-31 09:43 (UTC)

Hi Kantras, While trying to set a fixed amount of memory for Dom0, I noticed that the 09_xen file of grub, does not pick up the "GRUB_CMDLINE_XEN_DEFAULT" variable in /etc/default/grub, as I believe it should be. See also: http://wiki.xen.org/wiki/Xen_Project_Best_Practices When I manually modify the "XEN_HYPERVISOR_CMDLINE" variable in 09_xen, it does work. However when 09_xen gets updated, this change will be lost. Do you know why the GRUB_CMDLINE_XEN_DEFAULT is not being used by 09_xen?

kantras commented on 2014-12-16 07:21 (UTC)

With xen 4.5 arriving soon, I'm planning to do the same as I did with the 4.3->4.4 transition; the current xen package will be renamed to 'xen-4.4' and 'xen' will be for the 4.5 release. My goal is to keep the last last three revisions in sync with the upstream releases (so 4.3, 4.4 and 4.5).

kantras commented on 2014-10-30 07:09 (UTC)

@zir_blazer: Actually xen maintain their own fork of the OVMF source code, and its from that repository that the build system pulls. This is why I made the comment that I did about the method we use; I didn't want to try against a system install of OVMF as I wasn't sure if all the xen specific patches had been upstreamed and this technically should already be known to be working with xen. I actually tried booting up a live cd via OVMF and it worked great. @ArthurBorsboom: There shouldn't be any impact to existing installs - all that has been done is enabling some support code, that won't be used unless a user enables the specific configuration options (for example, OVMF is a replacement for SeaBIOS, but won't be used unless you add "bios='ovmf'" into the configuration file for the domU. )

« First ‹ Previous 1 .. 40 41 42 43 44 45 46 47 48 49 50 .. 101 Next › Last »