From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5E51CC10F0B for ; Thu, 18 Apr 2019 07:38:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 34A0B2083D for ; Thu, 18 Apr 2019 07:38:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388200AbfDRHiy (ORCPT ); Thu, 18 Apr 2019 03:38:54 -0400 Received: from mx2.suse.de ([195.135.220.15]:58132 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2388172AbfDRHiy (ORCPT ); Thu, 18 Apr 2019 03:38:54 -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 79527AD02; Thu, 18 Apr 2019 07:38:52 +0000 (UTC) Date: Thu, 18 Apr 2019 09:38:52 +0200 Message-ID: From: Takashi Iwai To: Greg Kroah-Hartman Cc: Paolo Bonzini , Sean Christopherson , Jiri Slaby , linux-kernel@vger.kernel.org Subject: [REGRESSION 5.0.x] Windows XP broken on KVM 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 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. thanks, Takashi