From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge 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 Message-ID: <49BA932E.7000907@goop.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Keir Fraser Cc: Dan Magenheimer , Xen-devel , "bderzhavets@yahoo.com" List-Id: xen-devel@lists.xenproject.org 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. 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