From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35409) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1Mvx-0002VB-DN for qemu-devel@nongnu.org; Thu, 09 Jan 2014 16:14:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W1Mvw-0000EX-Fb for qemu-devel@nongnu.org; Thu, 09 Jan 2014 16:14:33 -0500 Received: from mail-pd0-x24a.google.com ([2607:f8b0:400e:c02::24a]:51837) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1Mvw-0000Dy-7Y for qemu-devel@nongnu.org; Thu, 09 Jan 2014 16:14:32 -0500 Received: by mail-pd0-f202.google.com with SMTP id g10so523703pdj.5 for ; Thu, 09 Jan 2014 13:14:31 -0800 (PST) From: thomas knych Date: Thu, 9 Jan 2014 13:14:22 -0800 Message-Id: <1389302063-2432-1-git-send-email-thomaswk@google.com> Subject: [Qemu-devel] [PATCH 0/1] KVM: Retry KVM_CREATE_VM on EINTR or EAGAIN List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: pbonzini@redhat.com, thomas knych , gleb@redhat.com, digit@google.com Hi - I've encountered occassional instability on qemu/kvm startup when the host is heavily loaded and already managing many guest OS's. In this cases I've seen the KVM_CREATE_VM ioctl return EINTR or EAGAIN and thats gets treated as fatal. Adding a retry in these cases has greatly improved our startup reliablity. I've submitted this patch to Android's qemu source tree and it seemed useful to push it upstream as well. Thanks, -Tom thomas knych (1): KVM: Retry KVM_CREATE_VM on EINTR or EAGAIN kvm-all.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) -- 1.8.5.1