WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Linux Traffic Shaping broken in 3.0.3rc1 ?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Linux Traffic Shaping broken in 3.0.3rc1 ?
From: Timo Benk <timo.benk@xxxxxx>
Date: Tue, 10 Oct 2006 12:50:13 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 10 Oct 2006 03:50:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C151318C.2468%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Openpgp: id=67E2E5E9; url=http://m28s01.vlinux.de/timo_benk_gpg_key.asc
References: <C151318C.2468%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.7 (X11/20060909)
Keir Fraser wrote:
> On 9/10/06 17:18, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> 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@xxxxxxxxxx - ICQ ID: #241877854
PGP Public Key: http://m28s01.vlinux.de/timo_benk_gpg_key.asc


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