From: Boris Derzhavets Subject: Re: Re: Hot plug scripts not working c/s 19355 (was: Re: [PATCH] xen: mask XSAVE in cpuid since we don't allow guests to use it) Date: Fri, 13 Mar 2009 12:08:31 -0700 (PDT) Message-ID: <122616.2576.qm@web56101.mail.re3.yahoo.com> References: Reply-To: bderzhavets@yahoo.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2079704027==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge , Andrew Lyon Cc: Dan Magenheimer , Xen-devel , Keir Fraser List-Id: xen-devel@lists.xenproject.org --===============2079704027== Content-Type: multipart/alternative; boundary="0-643047671-1236971311=:2576" --0-643047671-1236971311=:2576 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Suse's=A0 2.6.27 xen-ified kernel & Xen Unstable (19355) don't have any pro= blems with hotplug sripts. I've restarted F10 PV DomU several times. Boris --- On Fri, 3/13/09, Andrew Lyon wrote: From: Andrew Lyon Subject: Re: [Xen-devel] Re: Hot plug scripts not working c/s 19355 (was: R= e: [PATCH] xen: mask XSAVE in cpuid since we don't allow guests to use it) To: "Jeremy Fitzhardinge" Cc: "bderzhavets@yahoo.com" , "Dan Magenheimer" , "Xen-devel" , "Kei= r Fraser" Date: Friday, March 13, 2009, 2:49 PM On Fri, Mar 13, 2009 at 5:09 PM, Jeremy Fitzhardinge wrote: > Keir Fraser wrote: >> >> On 13/03/2009 15:46, "Dan Magenheimer" wrote: >> >> >>> >>> A heads-up that I just got a "(tap)...Hotplug scripts not working" >>> completely unrelated to pvops. >>> >>> I updated hypervisor and tools (but notably NOT dom0 kernel) to >>> xen-unstable c/s 19355. =A0Launching a domain now fails with the >>> above error. =A0Rolling tools (only) back to 19187 makes the >>> problem go away. >>> >>> Is there maybe a new dependency between tools and dom0 kernel? >>> >> >> You could try reverting changeset 19342, as most likely culprit. >> > > Is that the fixed xen-hotplug-cleanup change? =A0The symptoms aren't quite the > same; with the broken cleanup, there were lockfiles left lying about, so all > the "block add" scripts were blocked waiting for the lock to be released. > =A0In this case, everything is just sitting there; the hotplug never seem= s to > get started. > > =A0 J > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > I think the hotplug problem where the lockfile was left lying about is fixed, I updated to c/s 19354 today and since then no problems with hotplug scripts, I can start and stop domains cleanly or by destroying them and nothing is left behind, I've verified this by running the xen-hotplug-cleanup script manually and it completes and removes the lock as it should. Like boris I am using a opensuse kernel, so if he is still having problems I think he has another issue or there is a remaining problem with hotplug which for some reason doesnt trigger on my test system. There is a separate issue where Xen crashes with (XEN) ** page_alloc.c:534 -- 0/1 ffffffffffffffff which started around the same time the hotplug scripts were fixed, it happens regardless of which kernel is used and has been discussed in thead with subject "xen unstable crash". Andy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel =0A=0A=0A --0-643047671-1236971311=:2576 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Suse's  2.6.27 xen-ified kernel & Xe= n Unstable (19355) don't have any problems
with hotplug sripts. I've res= tarted F10 PV DomU several times.

Boris

--- On Fri, 3/13/0= 9, Andrew Lyon <andrew.lyon@gmail.com> wrote:
From: Andrew Lyon <andrew.lyon@gmail.com>
Subject:= Re: [Xen-devel] Re: Hot plug scripts not working c/s 19355 (was: Re: [PAT= CH] xen: mask XSAVE in cpuid since we don't allow guests to use it)
To: = "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "bderzhavets@yahoo.com= " <bderzhavets@yahoo.com>, "Dan Magenheimer" <dan.magenheimer@orac= le.com>, "Xen-devel" <xen-devel@lists.xensource.com>, "Keir Fraser= " <keir.fraser@eu.citrix.com>
Date: Friday, March 13, 2009, 2:49 PM

On Fri, Mar 13, 2009 at 5:09 PM, Jeremy Fitzhardinge <je=
remy@goop.org>
wrote:
> Keir Fraser wrote:
>>
>&= gt; On 13/03/2009 15:46, "Dan Magenheimer"
<dan.magenheimer@oracle.co= m> wrote:
>>
>>
>>>
>>> A head= s-up that I just got a "(tap)...Hotplug scripts not
working"
>>= > completely unrelated to pvops.
>>>
>>> I updat= ed hypervisor and tools (but notably NOT dom0 kernel) to
>>> xe= n-unstable c/s 19355.  Launching a domain now fails with the
>&g= t;> above error.  Rolling tools (only) back to 19187 makes the
&= gt;>> problem go away.
>>>
>>> Is there maybe= a new dependency between tools and dom0 kernel?
>>>
>>= ;
>> You could try reverting changeset 19342, as most likely culpr= it.
>>
>
> Is that the fixed xen-hotplug-cleanup change?  The symptoms aren't
quite the
>= same; with the broken cleanup, there were lockfiles left lying about, soall
> the "block add" scripts were blocked waiting for the lock to = be
released.
>  In this case, everything is just sitting ther= e; the hotplug never seems
to
> get started.
>
>  = ; J
>
> _______________________________________________
>= Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http:= //lists.xensource.com/xen-devel
>


I think the hotplug prob= lem where the lockfile was left lying about is
fixed, I updated to c/s 1= 9354 today and since then no problems with
hotplug scripts, I can start = and stop domains cleanly or by destroying
them and nothing is left behin= d, I've verified this by running the
xen-hotplug-cleanup script manually= and it completes and removes the
lock as it should.

Like boris I am using a opensuse kernel, so if he is still having
problems I= think he has another issue or there is a remaining problem
with hotplug= which for some reason doesnt trigger on my test system.

There is a = separate issue where Xen crashes with (XEN) **
page_alloc.c:534 -- 0/1 f= fffffffffffffff which started around the same
time the hotplug scripts w= ere fixed, it happens regardless of which
kernel is used and has been di= scussed in thead with subject "xen
unstable crash".

Andy

_= ______________________________________________
Xen-devel mailing listXen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
<= /pre>

=0A=0A=0A=0A --0-643047671-1236971311=:2576-- --===============2079704027== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============2079704027==--