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.069676
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 .. 50 51 52 53 54 55 56 57 58 59 60 .. 101 Next › Last »

Oimelchen commented on 2014-03-22 08:04 (UTC)

Hi, thanks a lot for this package. It builds without any problem (even with the ati-passthrough patch enabled). I was able to passthrough two Radeon 5670 gfx cards to two separate VMs (one to Win7 VM and the other one to a Mint VM, both in secondary passthrough). Unfortunatly when using the xl tool stack, I am not able to restart the VMs, the dom0 totally crashes. So I tried to rebuild this package with enabled xm toolset. When using the same Vms with the xm toolset, every seems to work like charm! This might be a useful hint for those, who try to get to do similar things. :-) So, as a recommendation, could you add the xm toolset to the PKGBUILD by adding the flag --enable-xend to the configure command? I know, it is deprecated, but at least it is a working alternative (at least for me).

kantras commented on 2014-03-18 13:20 (UTC)

Glad to hear its working - I had suspected it being something like a mismatch between the kernel and the toolset, hence the suggestion to run xl info to confirm. The other command I mentioned was to check that a certain value had been set up correctly in xenstored (its the same one that tritron was referring to) as this is a requirement for xen 4.4. It is in the package but it doesn't hurt to make sure all the basics are covered - often the most simplest issue can be the most annoying, so always check the basics first and build up from there.

3000 commented on 2014-03-18 08:40 (UTC)

wow, when I tried xl info I realized that I copied an earlier Version of xen.efi to my boot Directory. Now the problem is fixed! thanks a lot for your help guys!

tritron commented on 2014-03-17 19:51 (UTC)

I wonder if anyone is interested in getting ovirt running under arch linux since libvirt and xen 4.4 work together now.

kantras commented on 2014-03-17 13:53 (UTC)

you may also find some more details if you turn on more verbose logging when you start the domain, something like: xl -vvvvv create <path to config file>

kantras commented on 2014-03-17 13:48 (UTC)

@3000: to help start to debug this - whats the output from the following commands (run as root): xl info xenstore-read /local/domain/0/domid also, what do you have as the config file for the windows domU and for your grub.cfg file? (can send to me directly if you don't want to post those details)

tritron commented on 2014-03-17 13:36 (UTC)

Does your xenstored.service has a line ExecStartPost=/usr/bin/xenstore-write "/local/domain/0/domid" 0 after ExecStartPost=/usr/bin/xenstore-write "/local/domain/0/name" "Domain-0"

3000 commented on 2014-03-17 12:59 (UTC)

nope, that doesn't work either :( thanks anyway!

hugleo commented on 2014-03-17 12:37 (UTC)

The following config works for me: kernel = "/usr/lib/xen/boot/hvmloader" builder='hvm' memory = 1024 device_model='/usr/lib/xen/bin/qemu-dm' shadow_memory = 8 name = "winxxx" vif = [ 'mac=00:16:3e:11:11:11,bridge=xenbr0', ] disk = [ 'phy:/vms/winxx.img,hda,w' ] boot = "dc" usb = 1 usbdevice = 'tablet' vnc = 1 sdl = 0 vncdisplay=1 #keymap='en' on_xend_stop = 'shutdown'

3000 commented on 2014-03-17 12:15 (UTC)

Hi, just wanted to upgrade. It built fine, without any Problems whatsoever, so great Job kantras! But when I try to start Windows I get this error: libxl: error: libxl_dom.c:281:libxl__build_post: Failed to set event channel limit to 1023 (-1) libxl: error: libxl_create.c:1022:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device model pid in /local/domain/3/image/device-model-pid libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_model failed for 3 what can I do to fix this? thanks a lot!

« First ‹ Previous 1 .. 50 51 52 53 54 55 56 57 58 59 60 .. 101 Next › Last »