RE: [Xen-users] Crash after update

Yep, I didn't have a problem earlier either with Ubuntu.

Anyway, I figured out what happened, so for future searchers, here are some details...

The problem was two-fold. First, the xen kernel wouldn't boot, crashed with a Call Trace that wasn't much use to me. As a troubleshooting step, I wanted to boot into the host using the original Ubuntu kernel, but that wasn't working because of the Second problem, which was that the console wasn't available, seemingly hanging during the startup process.

Fortunately, all networking services were starting properly, so I was able to SSH into the box and review logs, which revealed that tty1 was crashing repeatedly, hence no console!

Upon reviewing the /etc/event.d/tty1 file, I found that it's been modified, so I changed it back to match another system that was working in a similar setup.

The BAD tty1 file was:

    # xvc0 - getty
    #
    # This service maintains a getty on xvc0 from the point the system is
    # started until it is shut down again.

    start on stopped rc2
    start on stopped rc3
    start on stopped rc4
    start on stopped rc5

    stop on runlevel 0
    stop on runlevel 1
    stop on runlevel 6

respawn
exec /sbin/getty 38400 xvc0

While the GOOD tty1 file was:

    # tty1 - getty
    #
    # This service maintains a getty on tty1 from the point the system is
    # started until it is shut down again.

    start on stopped rc2
    start on stopped rc3
    start on stopped rc4
    start on stopped rc5

    stop on runlevel 0
    stop on runlevel 1
    stop on runlevel 6

respawn
exec /sbin/getty 38400 tty1

I believe that 'xvc0' should be used on domUs, not on dom0. I'm not sure how that changed, perhaps one of the updates did that. Anyway, so that solved the secondary problem.

The xen kernel not booting, to make a long story short, was an out-of-memory problem. Per best practice recommendations, I originally limited dom0's memory using the kernel switch dom0_mem=128M which was just a little bit too small. Perhaps one of the updates made it so that the system required just a tad more RAM. Upon increasing to 196M, everything works fine.

Peter

From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Thomas Jensen
Sent: Thursday, March 19, 2009 6:37 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Crash after update

I run Xen on Ubuntu 8.04 LTS server. There was a patch I add to apply to fix the console after creating new DomUs. But other than that, it has been very stable for me. I am contemplating moving to Debian Lenny and would like to try your Live CD, but I wanted to say that I haven't had anything too difficult with Ubuntu that I would classify Xen on it as a "mess" or "pure crap".

Tom Jensen | President
Digital Toolbox

From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Thiago Camargo Martins Cordeiro
Sent: Thursday, March 19, 2009 4:50 PM
To: p1@xxxxxxxx
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Crash after update

Hi!

Xen on Ubuntu is a mess! Pure crap... believe me!
Since you are new to Linux and Xen, I recommend you to try the new Xen Live CD!

http://wiki.xensource.com/xenwiki/LiveCD

It's based on the Debian 5.0, is stable and easy to use and learn... ;-)

Good luck!
Thiago

2009/3/19 <p1@xxxxxxxx>

Hi All,

I had Xen 3.2 running on Ubuntu 8.04 server for a few months. There were some updates I installed this morning on the host and now I can't boot into the Xen kernel (2.6.24-23-xen), nor into the normal pre-xen Ubuntu kernel (2.6.24-23-server).

When booting into the Ubuntu kernel, startup gets pretty far into it, including successful networking initialization, etc. The last thing I see is:

* Running local boot scripts (/etc/rc.local) [OK]

Then it just hangs there indefinitely.

When booting into the Xen kernel, it also goes pretty far, including networking, then for a few seconds it shows:

Restoring Xen domains: dom1.local

Then a crash...

Call Trace:

(bunch of code, modules, etc)

end trace

I can boot into the Recovery mode of the Ubuntu kernel but not sure how to proceed with troubleshooting.

The updates this morning were:

dash 0.5.4-8ubuntu1.1
libcurl3 7.18.0-1ubuntu2.1
libcurl3-gnutls 7.18.0-1ubuntu2.1
libglib2.0-0 2.16.6-0ubuntu1.1
libglib2.0-data 2.16.6-0ubuntu1.1
libpng12-0 1.2.15~beta5-3ubuntu0.1
libxen3 3.2.0-0ubuntu10.1
python-xen-3.2 3.2.0-0ubuntu10.1
tzdata 2009b-0ubuntu0.8.04
xen-docs-3.2 3.2.0-0ubuntu10.1
xen-hypervisor-3.2 3.2.0-0ubuntu10.1
xen-utils-3.2 3.2.0-0ubuntu10.1

I'm not sure where to even start troubleshooting, I'm new to Xen and fairly new to linux.

Any clues?

Thanks,

Peter
-- ea926h

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

-- ea926h

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

WARNING - OLD ARCHIVES

xen-users

RE: [Xen-users] Crash after update