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)

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

Xaseron commented on 2012-11-16 13:33 (UTC)

> xen-acpi-processor # This module may not work on all machines; try removing this first if it causes issues. Of course this module does not load, because you can't write a comment right after a module. This space is reserved for options.

Refutationalist commented on 2012-11-16 07:03 (UTC)

Update on that score, running 3.6.6 and Xen 4.1.3 on Fedora garners the same problem! But running the XCP beta did not. Interesting!

Refutationalist commented on 2012-11-15 15:44 (UTC)

Also, I've compiled and run this on a clean install. The xl toolset doesn't seem to hand proper devices to PV domains, and HVM domains reset the computer without printing anything meaningful beyond: (XEN) HVM8: int13_harddisk: function 02, unmapped device for ELDL=87 (XEN) HVM8: int13_harddisk: function 41, ELDL out of range 88 (XEN) HVM8: int13_harddisk: function 02, ELDL out of range 88 (XEN) irq.c:375: Dom8 callback via changed to Direct Vector 0xf3 To the serial console. This is for a machine that I'm deploying soon, I'll keep Arch on it for as long as I can if someone wants me to try things, otherwise I'm going to have to put something else on it and ship it.

kantras commented on 2012-11-15 07:05 (UTC)

FYI - I just uploaded a modified xenstored.service file and var-lib-xenstored.mount (which mounts /var/lib/xenstored as a tmpfs, since it doesn't need to be persistent between boots) to my temp site. As for libvirt support, I've been tracking xen-devel and its very early stages; see http://lists.xen.org/archives/html/xen-devel/2012-10/msg01853.html for the start of the thread discussing this

Refutationalist commented on 2012-11-15 04:00 (UTC)

fernando_ccs17: You have to create /var/lib/xen as a directory. I've been working on that and some other build-time things.

fernando_ccs17 commented on 2012-11-15 02:26 (UTC)

[root@localhost fernando]# xl create xlexample.hvm Parsing config from xlexample.hvm xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000019dec8 TOTAL: 0000000000000000->0000000007800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x000000000000003b 1GB PAGES: 0x0000000000000000 libxl: error: libxl_dom.c:1535:libxl_userdata_store: cannot write /var/lib/xen/userdata-n.3.77ea2db4-871e-4688-8d7e-f68c1a754b04.xl for /var/lib/xen/userdata-d.3.77ea2db4-871e-4688-8d7e-f68c1a754b04.xl: No such file or directory cannot save config file: No such file or directory libxl: error: libxl_dom.c:1462:libxl__userdata_destroyall: glob failed for /var/lib/xen/userdata-?.3.77ea2db4-871e-4688-8d7e-f68c1a754b04.*: No such file or directory *** the "xen" folder in /var/lib/ does not exist. only "xenstored" exist there. *** content of xlexample.hvm: builder = "hvm" name = "example.hvm" memory = 128 vcpus = 1 vnc = 1

paleo9 commented on 2012-11-12 18:34 (UTC)

I have never used libvirt, and I do not have a hardware-virtual processor (nor any need for one), so anything I can do will be limited to pv. I have just downloaded v1.0.0 and made an initial attempt to build it. I am also checking out the abs build. However, even if it builds, it may not have all features. http://wiki.xen.org/wiki/Fedora_Host_Installation "Starting from Xen 4.2, the default toolstack is libxl. libvirt has a libxl driver, but it (at the time of writing) still lacks many important features... ...There is an on-going effort to fill the gap and render the libvirt libxl driver feature complete and fully functional, although it is yet unclear when that will happen (in particular, whether or not it will make it in time for Fedora 18." On the other hand, the tarball that I downloaded (stable libvirt 1.0.0) has News November 2 2012 at least mentions xen 4.2. So there may be hope. http://libvirt.org/news.html "various improvement and fixes when using QMP QEmu interface Support for Xen 4.2 (Jim Fehlig)" If I have anything more useful to say, I shall put it on some libvirt page and leave a comment here.

loper commented on 2012-11-11 23:09 (UTC)

@ paleo9: thanks, running # xenstore-write "/local/domain/0/name" "Domain-0" manually changed the (null) value. Is there any way to get libvirt for xen to build without error?