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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 1D7AAC4332D for ; Thu, 19 Mar 2020 12:02:09 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E4B7120663 for ; Thu, 19 Mar 2020 12:02:08 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E4B7120663 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:36998 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jEtsG-0006AO-3e for qemu-devel@archiver.kernel.org; Thu, 19 Mar 2020 08:02:08 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:46498) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jEtrT-0005kW-24 for qemu-devel@nongnu.org; Thu, 19 Mar 2020 08:01:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jEtrQ-0005EF-RC for qemu-devel@nongnu.org; Thu, 19 Mar 2020 08:01:18 -0400 Received: from indium.canonical.com ([91.189.90.7]:53528) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jEtrQ-00059z-Ly for qemu-devel@nongnu.org; Thu, 19 Mar 2020 08:01:16 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1jEtrP-0007t5-8o for ; Thu, 19 Mar 2020 12:01:15 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 2A6C82E80C3 for ; Thu, 19 Mar 2020 12:01:15 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 19 Mar 2020 11:46:18 -0000 From: "Dr. David Alan Gilbert" To: qemu-devel@nongnu.org X-Launchpad-Notification-Type: bug X-Launchpad-Bug: product=qemu; status=Invalid; importance=Undecided; assignee=None; X-Launchpad-Bug: distribution=ubuntu; sourcepackage=qemu; component=main; status=Invalid; importance=Undecided; assignee=None; X-Launchpad-Bug: distribution=ubuntu; sourcepackage=seabios; component=main; status=Triaged; importance=Undecided; assignee=None; X-Launchpad-Bug-Information-Type: Public X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Bug-Commenters: ahasenack dbaxps0220 dgilbert-h paelzer tstrike34 X-Launchpad-Bug-Reporter: tstrike (tstrike34) X-Launchpad-Bug-Modifier: Dr. David Alan Gilbert (dgilbert-h) References: <158386023038.12575.5865810528923078550.malonedeb@soybean.canonical.com> Message-Id: <158461837903.19236.13647010332775855634.malone@chaenomeles.canonical.com> Subject: [Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04 X-Launchpad-Message-Rationale: Subscriber (QEMU) @qemu-devel-ml X-Launchpad-Message-For: qemu-devel-ml Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="3a6db24bbe7280ec09bae73384238390fcc98ad3"; Instance="production-secrets-lazr.conf" X-Launchpad-Hash: 9c161fc1083a6dc4c2e9876a48854ebd40f7c38b X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 91.189.90.7 X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Bug 1866870 <1866870@bugs.launchpad.net> Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" I *think* it's the cf-protection that's adding the endbr32 instructions that I spotted as being the failing instruction each time; but I don't understand why they would be CPU type specific. -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1866870 Title: KVM Guest pauses after upgrade to Ubuntu 20.04 Status in QEMU: Invalid Status in qemu package in Ubuntu: Invalid Status in seabios package in Ubuntu: Triaged Bug description: Symptom: Error unpausing domain: internal error: unable to execute QEMU command 'c= ont': Resetting the Virtual Machine is required Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_= wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tm= pcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", lin= e 66, in newfn ret =3D fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311,= in resume self._backend.resume() File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume if ret =3D=3D -1: raise libvirtError ('virDomainResume() failed', dom= =3Dself) libvirt.libvirtError: internal error: unable to execute QEMU command 'con= t': Resetting the Virtual Machine is required = --- As outlined here: https://bugs.launchpad.net/qemu/+bug/1813165/comments/15 After upgrade, all KVM guests are in a default pause state. Even after forcing them off via virsh, and restarting them the guests are paused. These Guests are not nested. A lot of diganostic information are outlined in the previous bug report link provided. The solution mentioned in previous report had been allegedly integrated into the downstream updates. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions