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.68
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 .. 77 78 79 80 81 82 83 84 85 86 87 .. 101 Next › Last »

paleo9 commented on 2012-11-21 20:30 (UTC)

Package built with archinit.patch - fail Package built without archinit.patch - successfully created, logged into and shut down a pv of Debian wheezy. created: /run/xenstored /run/xenstored.pid /var/run/xenstored /var/run/xenstored.pid not created (not needed), /run/xen /var/run/xen Using journalctl on the failed build showed xendomains failed at three points, each of which were lines added to xendomains by archinit.patch. The patch adds to xendomains function calls from rc.d/functions, which no longer exists. Previously no effect, but now causes xendomains.service to fail. Also all to do with xend. Conclusion: previously the patch was useless, now it is a liability.

kantras commented on 2012-11-20 20:04 (UTC)

Actually, I have a file for creating the /run/xen directory as well, on http://www.kantras.info/xen, called tmpfiles.d.xen.conf. In the test PKGBUILD file I was using, I copied it to /usr/lib/tmpfiles.d/xen.conf

paleo9 commented on 2012-11-20 18:09 (UTC)

/var/run/xen is being created on my system, but it is built from the official tarball, with the service files as existed in the 4.2.0-3 arch release. i.e archinit.patch was not used, but otherwise the same as 4.2.0-3. I 'll take a look tomorrow and do a full aur install of the current version.

Refutationalist commented on 2012-11-20 16:58 (UTC)

* Exactly so. /run/xen needs to exist, isn't (apparently) created by anything, and /run is a ramdisk. * Every new machine I've installed this package on won't run pv dom0's until /run/xen (or rather, /var/run/xen) exists. Going through what documentation I can find, this is the expected behavior. It could be differences in what we're using on PVs. * I don't particularly care where it happens, just that it does. :) I initially used && rather than a semi-colon, but it didn't work and systemd documentation said to use a semi-colon, so that's what I did. I am new to systemd. * I've also built it without archinit.patch and xendomains works without a lot of trouble, at least on startup. Haven't tested shutdown yet. I'm pretty sure the patch was originally one I submitted, and it doesn't appear to have much added to it. All it did was make xen's init files work with our sysvinit. I think it's also worth noting that I generally have to compile this package on a clean install with base, base-devel and the packages required by the PKGBUILD only, as the xen build process will link to other packages that I have installed on my build machine, but not on the ones I use the package on.

paleo9 commented on 2012-11-20 16:36 (UTC)

* This will attempt to create '/run/xen' every time Xen is started. * I am not sure what you mean by 'which is necessary for pv domains to run with the XL stack', pv domains run fine under xl. * '/usr/bin/xenstore-write "/local/domain/0/name" "Domain-0"' belongs better in xenstored.service, something like ExecStart=/usr/sbin/xenstored --pid-file /var/run/xenstored.pid $XENSTORED_ARGS; /usr/bin/xenstore-write "/local/domain/0/name" "Domain-0" or preferably use && instead of semicolon if that is allowed. * I agree with you about the archinit.patch, not sure it's going to break anything but certainly, the first half no longer affects anything and the second half deals with xendomains and probably no longer affects anything (I haven't had a look at things for a week). Either way, I didn't need it to build the official tarball and, if memory serves, I was able to build the Arch package without it too.

Refutationalist commented on 2012-11-20 13:52 (UTC)

Another version of the service file, this time it creates /run/xen, which is necessary for pv domains to run with the XL stack. This was the kind of thing originally handled by xend. It's a simple change, but I've renamed it xen-dom0-env.service: -------- [Unit] Description=Name the Xen Domain0 for use with XL Requires=xenstored.service ConditionPathExists=/proc/xen [Service] Type=oneshot ExecStart=/usr/bin/mkdir /run/xen ; /usr/bin/xenstore-write "/local/domain/0/name" "Domain-0" [Install] WantedBy=multi-user.target

Refutationalist commented on 2012-11-20 11:12 (UTC)

xendomains.service will break on pure systemd dom0s because of archinit.patch. The patch's original purpose was to make the xen rc files work with Arch's sysvinit better, so it should be fairly painless to remove it. Also, I think the xen-dom0-name.service file should have it's type set to oneshot rather than simple.

Refutationalist commented on 2012-11-20 10:50 (UTC)

Here's a service file to rename the dom0. xen-dom0-name.service ---- [Unit] Description=Name the Xen Domain0 for use with XL Requires=xenstored.service ConditionPathExists=/proc/xen [Service] Type=simple ExecStart=/usr/bin/xenstore-write "/local/domain/0/name" "Domain-0" [Install] WantedBy=multi-user.target

« First ‹ Previous 1 .. 77 78 79 80 81 82 83 84 85 86 87 .. 101 Next › Last »