kurokuon and 3000:
In PKGBUILD file, the line where have:
"./configure PYTHON=/usr/bin/python2"
try replacing with:
"LIBS += "-librt" ./configure PYTHON=/usr/bin/python2"
without quotes.
Please give feedback if it works.
Search Criteria
Package Details: xen 4.19.1pre-1
Package Actions
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.68 |
First Submitted: | 2009-11-09 11:22 (UTC) |
Last Updated: | 2024-09-20 00:31 (UTC) |
Dependencies (63)
- acpica
- bridge-utils
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- gnutls (gnutls-gitAUR)
- inetutils (inetutils-gitAUR, busybox-coreutilsAUR)
- iproute2 (iproute2-gitAUR, busybox-coreutilsAUR, iproute2-selinuxAUR)
- lib32-glibc (lib32-glibc-gitAUR, lib32-glibc-linux4AUR, lib32-glibc-eacAUR, lib32-glibc-eac-binAUR, lib32-glibc-eac-rocoAUR)
- libaio (libaio-gitAUR)
- libjpeg-turbo (mozjpeg-gitAUR, libjpeg-turbo-gitAUR, mozjpegAUR)
- libpng (libpng-gitAUR, libpng-apngAUR)
- libseccomp (libseccomp-gitAUR)
- libuuid.so (util-linux-libs-selinuxAUR, util-linux-libs-aesAUR, lib32-util-linux, util-linux-libs)
- libx11 (libx11-gitAUR)
- lzo
- ncurses (ncurses-gitAUR)
- openssl (openssl-gitAUR, openssl-staticAUR)
- pciutils (pciutils-gitAUR)
- pixman (pixman-gitAUR)
- pkgconf (pkgconf-gitAUR)
- python (python37AUR, python311AUR, python310AUR)
- Show 43 more dependencies...
Required by (3)
Sources (7)
Latest Comments
« First ‹ Previous 1 .. 75 76 77 78 79 80 81 82 83 84 85 .. 101 Next › Last »
fernando_ccs17 commented on 2013-01-07 11:21 (UTC)
<deleted-account> commented on 2013-01-07 06:01 (UTC)
I cant complete the build process. I get the following errors:
=== PCI passthrough capability has been enabled ===
=== PCI passthrough capability has been enabled ===
make[4]: Entering directory `/tmp/xen/src/xen-4.2.1/tools/qemu-xen-traditional-dir/i386-dm'
LINK i386-dm/qemu-dm
/usr/bin/ld: vl.o: undefined reference to symbol 'timer_settime@@GLIBC_2.3.3'
/usr/bin/ld: note: 'timer_settime@@GLIBC_2.3.3' is defined in DSO /usr/lib/librt.so.1 so try adding it to the linker command line
/usr/lib/librt.so.1: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
make[4]: *** [qemu-dm] Error 1
make[4]: Leaving directory `/tmp/xen/src/xen-4.2.1/tools/qemu-xen-traditional-dir/i386-dm'
make[3]: *** [subdir-i386-dm] Error 2
make[3]: Leaving directory `/tmp/xen/src/xen-4.2.1/tools/qemu-xen-traditional-dir'
make[2]: *** [subdir-install-qemu-xen-traditional-dir] Error 2
make[2]: Leaving directory `/tmp/xen/src/xen-4.2.1/tools'
make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/tmp/xen/src/xen-4.2.1/tools'
make: *** [install-tools] Error 2
==> ERROR: A failure occurred in package().
Aborting...
Is there a fix to this?
Thanks!
deviousway commented on 2013-01-03 23:15 (UTC)
Compiling whole program out/code32seg.o
Building ld scripts (version "1.6.3.2-20130104_061020-Acelot")
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.out/../src/smp.c.68'
make[6]: *** [out/romlayout16.lds] Ошибка 1
make[6]: Выход из каталога `/tmp/yaourt-tmp-root/aur-xen/src/xen-4.2.1/tools/firmware/seabios-dir-remote'
make[5]: *** [subdir-all-seabios-dir] Ошибка 2
make[5]: Выход из каталога `/tmp/yaourt-tmp-root/aur-xen/src/xen-4.2.1/tools/firmware'
make[4]: *** [subdirs-all] Ошибка 2
make[4]: Выход из каталога `/tmp/yaourt-tmp-root/aur-xen/src/xen-4.2.1/tools/firmware'
make[3]: *** [all] Ошибка 2
make[3]: Выход из каталога `/tmp/yaourt-tmp-root/aur-xen/src/xen-4.2.1/tools/firmware'
make[2]: *** [subdir-install-firmware] Ошибка 2
make[2]: Выход из каталога `/tmp/yaourt-tmp-root/aur-xen/src/xen-4.2.1/tools'
make[1]: *** [subdirs-install] Ошибка 2
make[1]: Выход из каталога `/tmp/yaourt-tmp-root/aur-xen/src/xen-4.2.1/tools'
make: *** [install-tools] Ошибка 2
==> ОШИБКА: Произошел сбой в package().
Преждевременный выход...
==> ERROR: Makepkg was unable to build xen.
==> Restart building xen ? [y/N]
3000 commented on 2013-01-03 08:29 (UTC)
hi, I somehow can't build this. I already have xen installed on another harddrive with Xen 4.2, but here I get this error message:
/usr/bin/ld: vl.o: undefined reference to symbol 'timer_settime@@GLIBC_2.3.3'
/usr/bin/ld: note: 'timer_settime@@GLIBC_2.3.3' is defined in DSO /usr/lib/librt .so.1 so try adding it to the linker command line
/usr/lib/librt.so.1: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
make[4]: *** [qemu-dm] Error 1
make[4]: Leaving directory `/tmp/yaourt-tmp-root/aur-xen/src/xen-4.2.1/tools/qem u-xen-traditional-dir/i386-dm'
make[3]: *** [subdir-i386-dm] Error 2
make[3]: Leaving directory `/tmp/yaourt-tmp-root/aur-xen/src/xen-4.2.1/tools/qem u-xen-traditional-dir'
make[2]: *** [subdir-install-qemu-xen-traditional-dir] Error 2
make[2]: Leaving directory `/tmp/yaourt-tmp-root/aur-xen/src/xen-4.2.1/tools'
make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/tmp/yaourt-tmp-root/aur-xen/src/xen-4.2.1/tools'
make: *** [install-tools] Error 2
==> ERROR: A failure occurred in package().
Aborting...
==> ERROR: Makepkg was unable to build xen.
==> Restart building xen ? [y/N]
I get the same error display when I try to build from source.
how can I fix this??
luolimao commented on 2012-12-19 03:58 (UTC)
Thanks, kantras; updated.
kantras commented on 2012-12-18 16:39 (UTC)
4.2.1 has been released. The exist PKGBUILD can be used (once the shasum's are updated) or I just uploaded a modified copy to http://www.kantras.info/xen/PKGBUILD (It also has a fix so that updates won't clobber the /etc/xen/xl.conf file.) I've just built the new version and have it running on a workstation.
<deleted-account> commented on 2012-12-16 10:19 (UTC)
Custom backend network device name seems not working. When I tried vif = ['ip=192.168.1,2, vifname=vif1.0, backend=networkvm'] in the client domU config file, the backend device in driver domain (networkvm) was named according to default vifDOMID.DEVID and not vif1.0 as specified in the script - resulting in different names every time I restarted the client domU.
Any idea what could cause this strange behaviour?
kantras commented on 2012-11-25 21:03 (UTC)
You will also want to add "etc/$pkgname/xl.conf" to the backup section in the PKGBUILD file to avoid changes (such as to the ballooning settings) being clobbered during an upgrade. I also have a couple of template files for /etc/conf.d/xen{console,store}d if needed.
Also, wondering it's worth making the name for dom0 to be definable via the conf file, defaulting to Domain-0 if nothing is explicitly set.
luolimao commented on 2012-11-22 18:16 (UTC)
Used tmpfiles method, and added the tmpfiles service to requires/after of xenstored.service
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