Package Details: xen-docs 4.19.1pre-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: 185
Popularity: 0.46
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-09-20 00:31 (UTC)

Dependencies (35)

Required by (1)

Sources (7)

Pinned Comments

Refutationalist commented on 2024-12-06 01:37 (UTC)

Please Note: Per best-practices by upstream this package follows the git stable branch. Minor releases do not require a version bump and the PKGBUILD will provide the appropriate version number.

stubdom is still broken.

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 101 Next › Last »

lazycat commented on 2017-03-11 03:50 (UTC)

@das_j, @JohnTh Thank you for answers :)

<deleted-account> commented on 2017-03-09 11:53 (UTC)

@lazycat @JohnTh I'm currently updating the package. However, it takes me longer to test, because I only have a really slow machine right now. I'm also adding xen-docs and turn this package into a split package. Update should roll out today.

JohnTh commented on 2017-03-09 11:39 (UTC)

@lazycat The Arch lzo package has changed, and no longer "provides" lzo2. I think you will need to rebuild and upgrade the Xen package to remove the error/ignore. You should be able to change lzo2 to lzo (line 74?) in the depends array in the Xen PKGBUILD. Then rebuild. lzo package change here https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/lzo&id=eb70476e9442d349f3c353e91631c0e713781c07 I would suggest you use multilib-build (from the Arch package devtools) to build in a clean chroot. See how that goes.

lazycat commented on 2017-03-09 09:10 (UTC)

New headache. Can't make system upgrade with pacman -Syu, get error: error: failed to prepare transaction (could not satisfy dependencies) :: xen: installing lzo (2.10-1) breaks dependency 'lzo2' I'm solve it temporally with #IgnorePkg = lzo lzo2, but it's not a good, I guess. Any ideas?

JohnTh commented on 2017-02-26 22:02 (UTC)

@ArgylePwnage gpg --keyserver pgp.mit.edu --recv-key 23E3222C145F4475FA8060A783FE14C957E82BD9 This command should solve that problem. You need to import the Xen Project tree code signing OpenPGP key 23E3222C145F4475FA8060A7(83FE14C957E82BD9) into your gpg keyring. The key is detailed here: https://www.xenproject.org/developers/teams/hypervisor/openpgp.html Otherwise, you can use a command line option with makepkg, or modify the PKGBUILD to remove this check. Have a look through the man pages or comments on the AUR Xen page for more details.

<deleted-account> commented on 2017-02-26 14:42 (UTC)

Hello, I have received the following error message: PGP signatures could not be verified for public key "83FE14C957E82BD9". Can you advise? Thank you for your time.

lazycat commented on 2017-01-20 02:34 (UTC)

@JohnTh, Yeah, your config file was really helpful for me, i successfully start arch live cd. But i understood that it is really bad idea to try to build completely work machine with 512 MB ram :D Thank you so much.

JohnTh commented on 2017-01-18 03:39 (UTC) (edited on 2017-01-18 04:00 (UTC) by JohnTh)

@lazycat Yes, possible to use Xen guest with little RAM. May need to boot your arch installer differently though. If you show your config, we will have a better idea. Working config for me, needs arch install iso. name='archtest' disk=['archlinux-2017.01.01-dual.iso, , xvdc, cdrom'] memory='256' root = '/dev/xvdc' bootloader='pygrub' kernel = "arch/boot/x86_64/vmlinuz" ramdisk = "arch/boot/x86_64/archiso.img" extra = "archisobasedir=arch archisolabel=ARCH_201701" boot='d'

lazycat commented on 2017-01-18 03:12 (UTC)

@JohnTh, It is possible use xen with config less then 1500M ram?

JohnTh commented on 2017-01-18 03:08 (UTC)

Good to see maintainer! When trying to boot PV archiso / archboot guest: I get "Initramfs unpacking failed: write error" when there is not enough memory to unpack the ramdisk to memory. I found the archboot64 I tried needed 1500MB memory.