All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timo Benk <timo.benk@gmx.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Linux Traffic Shaping broken in 3.0.3rc1 ?
Date: Tue, 10 Oct 2006 12:50:13 +0200	[thread overview]
Message-ID: <452B7AE5.5020701@gmx.de> (raw)
In-Reply-To: <C151318C.2468%Keir.Fraser@cl.cam.ac.uk>

Keir Fraser wrote:
> On 9/10/06 17:18, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote:
> 
>> As for save/restore of domains with non-dom0 backends. That's pushing the
>> envelope somewhat and might require some changes to our tools. But at the
>> very least it shouldn't leave zombies hanging around. I'll give your setup a
>> test and see what can be done.
> 
> Actually, you cannot save/restore backend domains at all, even when they are
> not actually configured to access real hardware. We should give a better
> error message about that, of course. ;-)
If it is not possible to save/restore a backend domain it is ok. The
reason why stumbled across this problem was that the xendomains script
tried to save the domains on reboot of Domain-0. That failed of course.

Then xendomains tries to shutdown these remaining domains. That fails
too and the host did not reboot for a long time. IMHO that is the main
problem.

The xen scripts that lie around in the system should be aware of the
fact that certain domains cannot be saved, and handle this situation
gracefully.

> The zombie xendom2 will exist until xendom1 is destroyed, for sure. This is
> because xendom1 holds onto some xendom2 resources. *But* does xendom2
> continue to exist as a zombie even after you forcibly 'xm destroy' xendom1?
You are right. After destroying xendom1 the zombie domain went away too.

Greetings,
-timo
-- 
Timo Benk - Jabber ID: fry@jabber.org - ICQ ID: #241877854
PGP Public Key: http://m28s01.vlinux.de/timo_benk_gpg_key.asc

  reply	other threads:[~2006-10-10 10:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07 19:21 Linux Traffic Shaping broken in 3.0.3rc1 ? Timo Benk
2006-10-08 16:17 ` Matt Ayres
2006-10-08 17:07   ` Keir Fraser
2006-10-08 18:30     ` Timo Benk
2006-10-09 12:38       ` Keir Fraser
2006-10-09 16:18       ` Keir Fraser
2006-10-10 10:16         ` Keir Fraser
2006-10-10 10:50           ` Timo Benk [this message]
2006-10-10 11:36             ` Keir Fraser
2006-10-10 12:50         ` Keir Fraser
2006-10-09 15:40 ` Keir Fraser

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=452B7AE5.5020701@gmx.de \
    --to=timo.benk@gmx.de \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /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.