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 .. 63 64 65 66 67 68 69 70 71 72 73 .. 102 Next › Last »

Lastebil commented on 2013-06-17 12:39 (UTC)

I'd agree to that as well - and I'll see if I can't cover a few things on the wiki clearly that are wrong (sdl is an option instead of vnc, for example; SPICE, and links to the various options such as Viridian, OVMF ...) That said, I'm not using SPICE - is anyone?

<deleted-account> commented on 2013-06-17 12:06 (UTC)

@Lastebil, my HVM config is essentially the one on the Arch Wiki (https://wiki.archlinux.org/index.php/Xen#Configuring_a_hardware_virtualized_.28HVM.29_Arch_domU). I would propose that the package build only require the packages to get a dom0 setup. Packages only required for running either a PV and/or HVM should be _optional_. One could then create xen-pv and xen-hvm dummy packages to load the required packages or we could list these optional packages on the wiki.

Lastebil commented on 2013-06-17 07:49 (UTC)

I am, but I haven't on that machine. I'll build another later and see what the issue is. Can you post your hvm config? I would propose that the packagebuild be set up to put bluez as _optional_ if you need HVM, as it isn't needed for PVM.

<deleted-account> commented on 2013-06-14 13:18 (UTC)

@Lastebil I was unable to create a HVM domU without the bluez-libs package. Are you using any HVM domUs?

tritron commented on 2013-06-12 12:29 (UTC)

At www.thexenguy.com/forums i posted my package sources xen-api xen-api-libs

Lastebil commented on 2013-06-12 10:06 (UTC)

It builds perfectly fine without bluez (or bluez4) and if you don't care to have bluetooth, it's not needed. (In my case, I'm a good 8km from the machines with xen - fully remote, serial consoles, etc - so I definately don't need bluetooth. It's range isn't anywhere near 8km (: ) I also am very interested in the xen-api stuff, if we end up setting up a mailing list or whatever, ping me, please.

<deleted-account> commented on 2013-06-09 17:14 (UTC)

I was unable to build the package install -d -m0755 -p txt/man pod2text man/xl.pod.1 txt/man/xl.1.txt.tmp man/xl.pod.1 around line 854: Expected text after =item, not a bullet POD document had syntax errors at /usr/bin/core_perl/pod2text line 84. make[2]: *** [txt/man/xl.1.txt] Error 255

kantras commented on 2013-06-08 04:46 (UTC)

You can simply change 'bluez' to 'bluez4' in the PKGBUILD and it will work. Having said that, I wonder if its even really needed - I know qemu references it, but I don't see why it would need it. Something to test

hugleo commented on 2013-06-07 12:09 (UTC)

Or xen can compile selecting bluez version 5

hugleo commented on 2013-06-07 12:02 (UTC)

Now is needed to replace the bluez dependence with bluez4.

« First ‹ Previous 1 .. 63 64 65 66 67 68 69 70 71 72 73 .. 102 Next › Last »