From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: [PATCH 0 of 4 V2] oxenstored fixes -- fixes recent pvops kernel hang Date: Tue, 13 Dec 2011 16:12:59 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: ian.jackson@citrix.com, Olaf Hering , Vincent Hanquez , Jonathan Ludlam , konrad.wilk@oracle.com List-Id: xen-devel@lists.xenproject.org Currently PVHVM Linux guests after ddacf5ef684a "xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches from old kernel" hang when run against oxenstored because it does not handle the unknown XS_RESET_WATCHES operation and does not reply. The symptom of this issue is a hang during boot at this point: cpu 1 spinlock event irq 70 CPU 1 irqstacks, hard=dec94000 soft=dec96000 Booting Node 0, Processors #1 smpboot cpu 1: start_ip = 99000 Initializing CPU#1 installing Xen timer for CPU 1 Brought up 2 CPUs Total of 2 processors activated (9625.99 BogoMIPS). NET: Registered protocol family 16 This series makes oxenstored handle unknown operations by returning an error indicating that the operation is unknown. I have not actually implemented support for XS_RESET_WATCHES. I also include a patch which I've been using for some time to enable the use of oxenstored in preference to C xenstored when available. Also included are two (more) little cleanup patches Changes since v1: * First two cleanup patches applied already * Two more cleanup patches added * Fixed warning in "handle unknown operations by returning an error to the client"