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] Xend problems through CS 15250

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xend problems through CS 15250
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Sat, 16 Jun 2007 11:30:09 -0400
Cc: jfehlig@xxxxxxxxxx, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, John Levon <john.levon@xxxxxxx>
Delivery-date: Sat, 16 Jun 2007 08:28:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2997896.9429%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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote on 06/16/2007 06:23:02 AM:

> Yes, I can repro this quite easily. However, the exception is coming
> from code added by changeset 15252 (Sun’s addition to make device
> detach wait for completion). But it’s probably a bad interaction
> between 15250 and 15252.
>
> Since I don’t know which of these changesets is actually bogus, I’ve
> reverted the later one (15252) for now. There were also complaints
> about ‘xm save’ not completing (which I’ve been unable to reproduce
> myself) and for which 15252 is one of the suspects, although this is
> not confirmed!

>
> So... Either 15250 needs fixing or reverting to allow 15252 to be
> correctly re-applied, or 15252 needs fixing in light of 15250. Take
> your pick. :-)


Reverting 15252 at least made the problems below go away and the xm-tests
pass now reasonably. Maybe the 'xm save' problem also goes away for those
that saw it.

  Stefan

>
>  -- Keir
>
> On 16/6/07 05:28, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

>
> Changeset 15250 introduces some problems of this kind here:
>
> [2007-06-15 23:44:58 3440] DEBUG (XendDomainInfo:559) dev = 0
> [2007-06-15 23:44:58 3440] ERROR (XendDomainInfo:1363) Device
> release failed: 01_domu_proc-1181965480; console; console/0
> Traceback (most recent call last):
>   File "//usr/lib/python/xen/xend/XendDomainInfo.py", line 1358, in
> _releaseDevices
>     self.destroyDevice(devclass, dev, False);
>   File "//usr/lib/python/xen/xend/XendDomainInfo.py", line 562, in
> destroyDevice
>     dev_uuid = dev_control.readBackend(dev, 'uuid')
>   File "//usr/lib/python/xen/xend/server/DevController.py", line
> 407, in readBackend
>     frontpath = self.frontendPath(devid)
>   File "//usr/lib/python/xen/xend/server/DevController.py", line
> 550, in frontendPath
>     return "%s/%d" % (self.frontendRoot(), devid)
> TypeError: int argument required
>
> In this case the devid is a string and not an integer.
>
> I see that some code that does a search has been removed. I wonder
> whether that was the right thing to do...
>
> http://xenbits.xensource.com/xen-unstable.hg?rev/a43a03d53781
>
>   Stefan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>