Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp293468yba; Thu, 18 Apr 2019 01:08:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqzFuVQxAu7wSTV83tAwYMv0zxD9N4Zor3BsZcIg+4OH1ZE0LGfLtKU2Ky2rv1K8OiKxcznQ X-Received: by 2002:a17:902:d24:: with SMTP id 33mr95965100plu.246.1555574907585; Thu, 18 Apr 2019 01:08:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555574907; cv=none; d=google.com; s=arc-20160816; b=Mh9GR52kiyMGDveVPH33ITlvxB/yu/Jw6ULebey8Y6lOxoQTesNgBGlOKcNljqWXFu vdKTRiJlmOPgqZ6TEk5VJL5de4/7SROySYZVP/lm+5NsurKN0QI2z4a/OKYCW4+IXclY diR3VBp0SnWmLYHu/eoiMcENvAvUZ71G94/Ha63EgvAJVBrIJO+zqpEUlW6IqfEAcuV8 wQZitPU0JnAHSFXeryYYygGc8vWaWsSjpde47yJhd5xRedYya8chXzrJ5Ew1jkvyya5b DCKBdDeKgbsYucemqBi7Ir3mIh68PvdgNu3CfdG3FYzfOPtwo9CLCO158bGELmm3kIgJ wMVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:subject:cc:to:from:message-id:date; bh=Pk6PGX8d9SIbFoDPJn/TzyV2m+tleBhnAyu4K7GFF0c=; b=cQjdIkDa0tpC88CSc7GhAc3IBgTLJwPSX9ZfQM0zv0qIr6yF5lLdExyl4ba4Xw3mmX u8XJNcU+9OGKNvpbaiin24yYSaDIaHeX5jrYConSw1n44+k42U1K2kTJzagiaf1aqCHH ViLKjaTsV3zjbn7J70rySee9r/Ibt34lI3MwI3czYR+9h+JOGSVRyMJzA9ooPfS8vteI DTx5EIcYtBeoYUo0tAv07qhGPNVXM5GfpIvDp9Kl1QyW0RKs9jtxen6z2I3n6WAL3DIb Yh91feyzXPjOJXecs573VGIrc55PAup67h+BfgLxnLJmr09NBdVSjWrayoxu+QTe9dtK mV7A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d17si1286727pgg.367.2019.04.18.01.08.12; Thu, 18 Apr 2019 01:08:27 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388272AbfDRIFg (ORCPT + 99 others); Thu, 18 Apr 2019 04:05:36 -0400 Received: from mx2.suse.de ([195.135.220.15]:37402 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2388221AbfDRIFf (ORCPT ); Thu, 18 Apr 2019 04:05:35 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 87C68AD93; Thu, 18 Apr 2019 08:05:34 +0000 (UTC) Date: Thu, 18 Apr 2019 10:05:34 +0200 Message-ID: From: Takashi Iwai To: Greg Kroah-Hartman Cc: Paolo Bonzini , Sean Christopherson , Jiri Slaby , linux-kernel@vger.kernel.org Subject: Re: [REGRESSION 5.0.x] Windows XP broken on KVM In-Reply-To: <20190418075328.GA19532@kroah.com> References: <20190418075328.GA19532@kroah.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 18 Apr 2019 09:53:28 +0200, Greg Kroah-Hartman wrote: > > On Thu, Apr 18, 2019 at 09:38:52AM +0200, Takashi Iwai wrote: > > Hi, > > > > we've got a regression report on the recent 5.0.x kernel, starting > > from 5.0.6, where Windows XP can't boot on KVM any longer. > > > > The culprit seems to be the patch > > KVM: x86: update %rip after emulating IO > > with the upstream commit 45def77ebf79e2e8942b89ed79294d97ce914fa0. > > Reverting this alone fixed the problem. > > > > The report is found at openSUSE bugzilla: > > https://bugzilla.suse.com/show_bug.cgi?id=1132694 > > > > Is there already a followup fix? If not, we need to revert it from > > stable, at least. > > Is this also a problem in 5.1-rc5? Only 5.0.x has been tested, so far. I'll ask the reporter to try 5.1-rc if Paolo can't reproduce the problem in his side. thanks, Takashi