Package Details: xen 4.19.1pre-1

Git Clone URL: https://aur.archlinux.org/xen.git (read-only, click to copy)
Package Base: xen
Description: Open-source type-1 or baremetal hypervisor
Upstream URL: https://xenproject.org/
Keywords: hypervisor virtualization xen
Licenses: GPL2
Submitter: sergej
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 185
Popularity: 0.67
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-09-20 00:31 (UTC)

Pinned Comments

Refutationalist commented on 2024-05-22 22:08 (UTC) (edited on 2024-05-23 00:07 (UTC) by Refutationalist)

As of now (2024-22-05) Xen with stubdom doesn't build because of a problem in the imported code. Been this way for about two weeks. Anyone else seeing this behavior?

Also, there is a lot of work happening on Xen in my development repo, thanks to @Serus. Check it out at: https://github.com/refutationalist/saur

Latest Comments

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

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!

kantras commented on 2014-03-11 21:37 (UTC)

So, it should be being ran, the problem would be that the script was modified more than just the default kernel (for example, LTS kernels) and it seems to think that the xen-syms file is another kernel. I'll update the package (following the old 4.3.2 package by moving syms to a different location) and upload an updated version

hugleo commented on 2014-03-11 21:03 (UTC)

If I generate the grub.cfg are the 09_xen script being executed? The boot order must be xen-4.4.0.gz kernel to the first place instead of xen-syms

kantras commented on 2014-03-11 16:55 (UTC)

I had two source tarballs prepared - one for whilst I was debugging across multiple systems and one for release - guess which one I uploaded .. Reuploaded with exit removed.

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