Open-Source | Entries from August 2008

Eclipse unter Linux (x86_64)

Making Xen work on Ubuntu 8.04 Hardy Heron

Posted by Sebastian Marsching on Friday, August 29. 2008

Es scheint einen Bug in Eclipse (oder wahrscheinlich eher der JVM) zu geben, der dazu führt, dass Eclipse unter Linux auf x86_64 ziemlich häufig mit etwa folgender Meldung abstürzt:

#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fa594b7025a, pid=471, tid=1109551440
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b22 mixed mode linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x1f125a]
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Der Bug scheint bekannt zu sein und zum Glück gibt es einen Workaround, der zumindest bei mir ganz gut funktioniert: Wenn man die eclipse.ini um den Eintrag -Xint erweitert, läuft Eclipse stabil. Diese Option bewirkt, dass der JIT-Compiler deaktiviert wird, der für die Abstürze verantwortlich zu sein scheint. Natürlich läuft der Code dadurch langsamer, aber ich finde den Unterschied zumindest auf meinem Rechner zu Hause (Core 2 Quad @ 2.4 GHz) kaum spürbar.

August '08

Posted by Sebastian Marsching on Sunday, August 10. 2008

I tried to upgrade my Xen server from Feisty Fawn to Hardy Heron some time ago.

Now, I gave it a second chance, but the same problems occurred again. However, I now found out, what has to be done in order to make Xen work after the upgrade to Hardy:

I removed all Xen-related packages (bacause they were still Xen 3.1 while Hardy ships Xen 3.2) and purged the configuration files (after I had made backups). Than I installed the ubuntu-xen-server meta-package.

Package configuration failed, so I had to boot the standard ubuntu-server kernel (without Xen) and run dpkg --configure -a.

After this, I booted into Xen mode, however I could not connect using SSH, although I got ping replies from the server. Then i figured out, that the server did not boot correctly because the /etc/init.d/loadcpufreq and /etc/init.d/cpufrequtils scripts hang and block the startup process. Therefore I deactivated them using update-rc.d and voilà: Xen is working flawlessly.

I hope this articles helps anyone, who runs into the same problem.