Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3652 - Arch unusable in Xen3

Attached to Project: Arch Linux
Opened by Charles Mauch (xterminus) - Friday, 23 December 2005, 12:47 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 04 January 2006, 11:26 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When using the Xen kernel (2.6.12.6-XenU, 2.6.12.6-Xen0, 2.6.12.6-Xen) I recieve the following error message when either attempting to:

* Boot into Arch using a Xen Kernel
* Chroot into Arch's root directory (From either Ubuntu/Gentoo/Fedora & Debian Distro)
* Boot Xen Hypervisor From Arch

The error is: "Inconsistency detected by ld.so: ../sysdeps/generic/dl-sysdep.c: 464: _dl_important_hwcaps: Assertion `m == cnt' failed!"

If chrooting, the chroot pivot is unsucessfull and your returned to the prompt.
If booting into or from, the same error is displayed and an Kernel Panic ensues (init is killed)

I've reinstalled Arch, and also attempted a archbootstrap thinking perhaps this problem was my fault (wierd config). The same behavior is seen on default (current) installs of arch.

Initally, this was annoying because it meant I could not use Arch as a hypervisor (I elected to go with Debian Sarge). But this happens when attempting to boot an Arch DomU or even chroot into it while a Xen kernel is loaded. As a result, I cannot use my arch installation at all.

In the meantime, I've installed Gentoo as my primary DomU, which is similar enough that I can get around comfortably.
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 14 March 2006, 18:39 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Friday, 23 December 2005, 14:06 GMT
Xen and NPTL are incompatible, try to remove the /lib/tls directory from the arch system you try to boot as XenU.
Comment by Charles Mauch (xterminus) - Friday, 23 December 2005, 21:38 GMT
Removing/renaming /lib/tls has no effect. I probably should have mentioned I'd already tried this. Besides, in other distros, not removing /lib/tls results in a big warning and slowdowns, not a kernel panic.
Comment by Jacob Kloster (jaff) - Thursday, 26 January 2006, 00:07 GMT
I have the same kernel panic ( I have used Xen without problems before, but now I have changed to Xen 3.0 problems, I build from source, and ready to test if any one has any idea how to fix this.

Can we get some comments of anyone has Xen 3.0 working on archlinux ?
Comment by Jacob Kloster (jaff) - Thursday, 26 January 2006, 00:08 GMT
ups did not see there is a forum post about it here a link to it :
http://bbs.archlinux.org/viewtopic.php?t=17224&highlight=xen
Comment by Jacob Kloster (jaff) - Thursday, 26 January 2006, 00:29 GMT
Just wanted to add that Jacob Gorm Hansen (Co-author and creator of the live migration part of Xen)
http://article.gmane.org/gmane.comp.emulators.xen.devel/18928
Comment by Tom Dobes (tdobes) - Wednesday, 08 March 2006, 05:59 GMT
This is some sort of incompatibility between the patches we apply to glibc and Xen 3.0. It's fixed by the new glibc in testing 2.3.6-1. Note that, after installing it, you'll probably want to do something like:
rm -r /lib/tls
mv /lib/nosegneg /lib/tls
(as root)
Comment by Jan de Groot (JGC) - Wednesday, 08 March 2006, 08:02 GMT
Xen 3 should export the nosegneg hwcap, which goes before tls. Removing tls libs and moving nosegneg over it should not be needed at all.

Loading...