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)

Dependencies (63)

Sources (7)

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

hugleo commented on 2013-07-11 13:19 (UTC)

For the future of this package I think is better to accept the last kantras suggestions: http://www.kantras.info/xen/xen-4.2.2-2.tgz and rename this package to xen-4.2

<deleted-account> commented on 2013-07-10 06:58 (UTC)

@revellion I have solve the problem. I export LC_ALL=C and export LANG=C, and it works

<deleted-account> commented on 2013-07-10 06:49 (UTC)

@revellion, I have the same problem with @deviousway. Traceback (most recent call last): File "./tools/layoutrom.py", line 583, in <module> main() File "./tools/layoutrom.py", line 564, in main info16 = parseObjDump(infile16, '16') File "./tools/layoutrom.py", line 501, in parseObjDump relocsection = sectionmap[sectionname] KeyError: '.text.asm.src/smp.c.68' make[6]: *** [out/romlayout16.lds] 错误 1 I have try export LANG=C And I also export LC_ALL=en_US.UTF-8, but it still can't work.

tritron commented on 2013-06-17 12:55 (UTC)

Well nice think about Linux is that you can exclude stuff you don't need. So if you don't want to have a bluez then you should disable it --disable-bluez on config line. When package requires blues libs it means that you included bluez dev files when you compiled Xen.

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.