virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Sam Abed <samabed@gmail.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: console lock up
Date: Wed, 11 Jul 2007 21:23:31 +1000	[thread overview]
Message-ID: <1184153011.6005.614.camel@localhost.localdomain> (raw)
In-Reply-To: <c5d4ac100707100546j17c67b5bhcd9f36fcf9da9b2@mail.gmail.com>

On Tue, 2007-07-10 at 22:46 +1000, Sam Abed wrote:
> hello,
>   I am using 2.6.21, lguest-2.6.21-307.patch.gz and an image from
> http://uml.nagafix.co.uk/Fedora7/Fedora7-x86-root_fs.bz2
> 
> the console hangs, is this expected or caused by the image? I can
> still ssh to it or if I boot in single user mode the console is
> available but running init3 and it's hung.

Hi Sam,

	Thanks for the bug report!  I can't even figure out how to get
networking running under that image (not a RH person, sorry).  When I
boot in single user mode and ifconfig up manually then "telinit 3" it
seems OK.

	Note that it does not seem to start a getty for runlevel 3, so you
can't log in, but that's not an lguest issue (you should be able to ssh
in).

> also is it possible to get the last gz patch released for 2.6.21?

	Unfortunately it's a PITA to do and test; I think my time is better
spent concentrating on the 2.6.23 release, and not backporting.

Sorry,
Rusty.


> _______________________________________________
> Virtualization mailing list
> Virtualization@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2007-07-11 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 12:46 console lock up Sam Abed
2007-07-11 11:23 ` Rusty Russell [this message]
     [not found]   ` <c5d4ac100707110546n3b26b60ayc4884f91a45517e1@mail.gmail.com>
2007-07-11 12:48     ` Fwd: " Sam Abed
2007-07-12  5:06     ` Rusty Russell
2007-07-16 12:47       ` Sam Abed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1184153011.6005.614.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=samabed@gmail.com \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).