Package Details: xen-stubdom 4.20.0-2

Git Clone URL: https://aur.archlinux.org/xen.git (read-only, click to copy)
Package Base: xen
Description: Xen hypervisor stubdom files
Upstream URL: https://xenproject.org/
Keywords: hypervisor virtualization xen
Licenses: GPL2
Submitter: sergej
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 184
Popularity: 0.071098
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2025-03-13 08:19 (UTC)

Dependencies (42)

Required by (3)

Sources (13)

Pinned Comments

Refutationalist commented on 2025-03-12 12:06 (UTC) (edited on 2025-03-13 08:23 (UTC) by Refutationalist)

We've moved to the newly-stable 4.20.0 branch. There are also other changes:

  • stubdom is fixed by disabling the vtmp and vtpmmgr components. This gets rid of a few source files and our remaining patches.
  • Debug files are only removed if the debug option is not set in makepkg.cfg (or the PKGBUILD itself)
  • pygrub has been removed
  • optdepends are adjusted for the upcoming xen-grub split package for the various Xen flavored builds.

If you're still using pygrub note that it is deprecated. The solution is to build PV grub instead, which used to be in AUR but is now missing. I am asking a couple questions on the mailing list, and I intend to put my current build of xen-grub (which supersedes xen-pvhgrub) on AUR as soon as possible. If you need to build it before that occurs, you can find it in my PKGBUILD repo.

EDIT: 4.20.0-2 adds support for the xen-edk2 package, which has a fixed UEFI for xen

Latest Comments

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

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.

kantras commented on 2013-06-05 15:37 (UTC)

Actually I was already intending to look into what it would take to do that; I'm wanting to rebuild one of my main systems and this sounded like an interesting thing to add

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