From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Xen-devel <xen-devel@lists.xensource.com>,
"bderzhavets@yahoo.com" <bderzhavets@yahoo.com>
Subject: 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 10:09:02 -0700 [thread overview]
Message-ID: <49BA932E.7000907@goop.org> (raw)
In-Reply-To: <C5E04168.5107%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 13/03/2009 15:46, "Dan Magenheimer" <dan.magenheimer@oracle.com> 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
next prev parent reply other threads:[~2009-03-13 17:09 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 5:31 [PATCH] xen: mask XSAVE in cpuid since we don't allow guests to use it Jeremy Fitzhardinge
2009-03-08 8:52 ` Boris Derzhavets
2009-03-08 9:13 ` Keir Fraser
2009-03-09 11:31 ` [PATCH] xen: mask XSAVE in cpuid since we don'tallow " Jan Beulich
2009-03-09 11:45 ` Keir Fraser
2009-03-09 11:18 ` [PATCH] xen: mask XSAVE in cpuid since we don't allow " Boris Derzhavets
2009-03-09 11:26 ` Keir Fraser
2009-03-09 14:31 ` Boris Derzhavets
2009-03-10 22:24 ` Boris Derzhavets
2009-03-11 0:29 ` Jeremy Fitzhardinge
2009-03-11 7:26 ` Boris Derzhavets
2009-03-11 8:40 ` Boris Derzhavets
2009-03-11 9:09 ` Attempt to install SNV_106 under Suse's 2.6.27 xen-ified kernel & Xen Unstable Boris Derzhavets
2009-03-11 11:36 ` Re: [PATCH] xen: mask XSAVE in cpuid since we don't allow guests to use it Boris Derzhavets
2009-03-11 16:09 ` Jeremy Fitzhardinge
2009-03-11 16:27 ` Boris Derzhavets
2009-03-11 16:50 ` Jeremy Fitzhardinge
2009-03-11 16:57 ` Boris Derzhavets
2009-03-11 17:04 ` Jeremy Fitzhardinge
2009-03-11 17:21 ` Boris Derzhavets
2009-03-11 17:43 ` Boris Derzhavets
2009-03-11 17:47 ` Jeremy Fitzhardinge
2009-03-11 19:49 ` Boris Derzhavets
2009-03-12 0:41 ` Jeremy Fitzhardinge
2009-03-13 14:39 ` Boris Derzhavets
2009-03-13 15:20 ` Jeremy Fitzhardinge
2009-03-13 15:46 ` 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) Dan Magenheimer
2009-03-13 16:05 ` Hot plug scripts not working c/s 19355 Jeremy Fitzhardinge
2009-03-13 16:59 ` 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) Keir Fraser
2009-03-13 17:09 ` Jeremy Fitzhardinge [this message]
2009-03-13 18:15 ` Boris Derzhavets
2009-03-13 18:49 ` Andrew Lyon
2009-03-13 19:08 ` Boris Derzhavets
2009-03-16 17:17 ` Dan Magenheimer
2009-03-16 18:00 ` Hot plug scripts not working c/s 19355 Jeremy Fitzhardinge
2009-03-11 19:13 ` Re: [PATCH] xen: mask XSAVE in cpuid since we don't allow guests to use it Andrew Lyon
2009-03-12 1:21 ` Jeremy Fitzhardinge
2009-03-12 1:54 ` Jeremy Fitzhardinge
2009-03-12 8:48 ` Boris Derzhavets
2009-03-12 8:55 ` Andrew Lyon
2009-03-12 9:34 ` Keir Fraser
2009-03-12 12:36 ` Boris Derzhavets
2009-03-09 11:26 ` [PATCH] xen: mask XSAVE in cpuid since we don't allowguests " Jan Beulich
2009-03-09 11:29 ` Keir Fraser
2009-03-09 16:40 ` Jeremy Fitzhardinge
2009-03-09 17:54 ` 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=49BA932E.7000907@goop.org \
--to=jeremy@goop.org \
--cc=bderzhavets@yahoo.com \
--cc=dan.magenheimer@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--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.