Package Details: xen-docs 4.21.2pre-1

Git Clone URL: https://aur.archlinux.org/xen.git (read-only, click to copy)
Package Base: xen
Description: Xen hypervisor documentation and man pages
Upstream URL: https://xenproject.org/
Keywords: hypervisor virtualization xen
Licenses: GPL2
Submitter: sergej
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 182
Popularity: 0.000012
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2026-05-06 02:59 (UTC)

Required by (3)

Sources (13)

Latest Comments

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

aaronfitz commented on 2012-11-22 04:12 (UTC)

Just tried the new package and things seem to go much smoother. I had to create the folder /var/lib/xen/ by hand in order to create a HVM though. Based on the processor usage pattern after I start the HVM Windows 7 is starting, but I'm not getting any display through the video adapter I pass through to the HVM. I never got the dedicated graphics passthrough capability working on 4.1, the graphics was just passed through as a PCI device. Not sure what's going on with the PCI passthrough but I'll keep fiddling with my setup. Anyone here using this for PCI or GFX passthrough yet?

Refutationalist commented on 2012-11-22 01:54 (UTC)

Sorry to insist, but in some supported configurations /run/xen *is* needed: http://pastebin.com/QaqS2Krt kantras' tmpfiles.d solution would appear to be the way to go and should be included.

luolimao commented on 2012-11-21 22:54 (UTC)

fixed.

paleo9 commented on 2012-11-21 22:46 (UTC)

Just tried the modified xenstored.service, doesn't like it. This is the one: tested, works ExecStart=/usr/sbin/xenstored --pid-file /var/run/xenstored.pid $XENSTORED_ARGS ExecStartPost=/usr/bin/xenstore-write "/local/domain/0/name" "Domain-0" Result: Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r----- 24.9

luolimao commented on 2012-11-21 21:50 (UTC)

Removed archinit.patch and added xenstore-write cmd to xenstored service file.

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.