All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Dumitru <doug@easyco.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: "Christopher S. Aker" <caker@theshore.net>,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] SKAS3: prerelease of V8 (against 2.6.9) uploaded
Date: Mon, 31 Jan 2005 19:10:15 -0800	[thread overview]
Message-ID: <41FEF317.3070505@easyco.com> (raw)
In-Reply-To: <200501290036.51182.blaisorblade@yahoo.it>

Blaisorblade wrote:
> Ok, I've uploaded the first prerelease of SKAS3 V8... It's uploaded on the 
> web-site, you can start playing for it if you want:
> 
> http://www.user-mode-linux.org/~blaisorblade/patches/skas3-2.6/skas-2.6.9-v8-rc1/
> 
> if you want, impressions are welcome.... I've not yet tested it thoroughly, 
> but it should work well enough.
> 
> I'm particularly interested in seeing it tested on SMP host systems, since 
> I've added some locking and I want to be sure there is no deadlock 
> possibility.
> 
> However, *not* on production systems for now... I want to check it more 
> carefully.

I just tested this release on a vanilla single-proc AMD system.  I see 
one major problem (at least with how we run UML here).

With 2.6.7 with skas3 and earlier releases it is possible to kill a 
virtual server from the host with a standard kill command.  All of the 
sub-threads die and you can unmount/unmap the various stuff that the 
virtual used.  This is an unclean shutdown but at least lets you kill 
virtuals that have misbehaved while leaving the host up.

With 2.6.9 skas3 v8 a plain kill does nothing.  With a kill -9, 3 of the 
four thread die, but one remains and the only way to get rid of it is 
with a server reboot.

Not sure what is going on here, but I have not been able to get anything 
past 2.6.7 to work while killing virtual rudely.

--------------------------------------------------------------------
Doug Dumitru     800-470-2756     (610-237-2000)
EasyCo LLC       doug@easyco.com  http://easyco.com
--------------------------------------------------------------------


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2005-02-01  3:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 23:36 [uml-devel] SKAS3: prerelease of V8 (against 2.6.9) uploaded Blaisorblade
2005-02-01  3:10 ` Doug Dumitru [this message]
2005-02-01  6:47   ` Frank Sorenson
2005-02-01 13:48     ` Rob Landley
2005-02-01 15:26       ` Frank Sorenson
2005-02-01 16:27         ` Christopher S. Aker
2005-02-01 23:46           ` Doug Dumitru
2005-02-03 19:55           ` Blaisorblade

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=41FEF317.3070505@easyco.com \
    --to=doug@easyco.com \
    --cc=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=caker@theshore.net \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.