Re: [Xen-devel] 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)

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

Suse's  2.6.27 xen-ified kernel & Xen Unstable (19355) don't have any problems
with hotplug sripts. I've restarted F10 PV DomU several times.

Boris

--- On Fri, 3/13/09, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:

From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Subject: Re: [Xen-devel] 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)
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Cc: "bderzhavets@xxxxxxxxx" <bderzhavets@xxxxxxxxx>, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>, "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Date: Friday, March 13, 2009, 2:49 PM

On Fri, Mar 13, 2009 at 5:09 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
wrote:
> Keir Fraser wrote:
>>
>> On 13/03/2009 15:46, "Dan Magenheimer"
<dan.magenheimer@xxxxxxxxxx> 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.  Launching a domain now fails with the
>>> above error.  Rolling 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?  The 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.
>  In this case, everything is just sitting there; the hotplug never seems
to
> get started.
>
>   J
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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