All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Ehrhardt " <1866870@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1866870] Re: KVM Guest pauses after upgrade to Ubuntu 20.04
Date: Thu, 12 Mar 2020 13:41:43 -0000	[thread overview]
Message-ID: <158402050357.25890.4633057907889866578.malone@gac.canonical.com> (raw)
In-Reply-To: 158386023038.12575.5865810528923078550.malonedeb@soybean.canonical.com

It detects host as Penryn as well for @tstrike.
Which is fine if it is a chip of around that era.
He reported to have an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz"
And for that chip the detection and chip used might be correct.

So to summarize all repro fails, but on Penryn ERA chips 2/2 cases
trigger the bug.

I wonder if one that wants to reproduce needs a system with such a chip
as well then to test and trigger this.

There should be plenty of people on CC as this is mirrored to qemu-devel
due to the upstream qemu task. Is there an microarchitectural x86
specialist that knows if the chips of that generation have some special
issues in regard to VMX that might explain what we see here?

It would be great if everyone could ask around for more systems with chips of that era.
Maybe we can further bisect which work and which will fail.

-- 
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:
  New
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Symptom:
  Error unpausing domain: internal error: unable to execute QEMU command 'cont': 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 tmpcb
      callback(*args, **kwargs)
    File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
      ret = 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 == -1: raise libvirtError ('virDomainResume() failed', dom=self)
  libvirt.libvirtError: internal error: unable to execute QEMU command 'cont': 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


  parent reply	other threads:[~2020-03-12 13:51 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 17:10 [Bug 1866870] [NEW] KVM Guest pauses after upgrade to Ubuntu 20.04 tstrike
2020-03-11  2:47 ` [Bug 1866870] " tstrike
2020-03-11  8:16 ` Christian Ehrhardt 
2020-03-11  8:41 ` Christian Ehrhardt 
2020-03-11  8:49 ` Christian Ehrhardt 
2020-03-11  8:50 ` Christian Ehrhardt 
2020-03-11  8:51 ` Christian Ehrhardt 
2020-03-11  8:52 ` Christian Ehrhardt 
2020-03-11  8:53 ` Christian Ehrhardt 
2020-03-11 10:46 ` tstrike
2020-03-11 17:31 ` tstrike
2020-03-11 17:32 ` tstrike
2020-03-11 17:32 ` tstrike
2020-03-11 17:32 ` tstrike
2020-03-11 17:36 ` tstrike
2020-03-11 17:41 ` tstrike
2020-03-12  8:34 ` Christian Ehrhardt 
2020-03-12  9:09 ` Boris Derzhavets
2020-03-12  9:48 ` Christian Ehrhardt 
2020-03-12  9:49 ` Christian Ehrhardt 
2020-03-12 10:07 ` Boris Derzhavets
2020-03-12 10:19 ` Christian Ehrhardt 
2020-03-12 10:19 ` Christian Ehrhardt 
2020-03-12 11:12 ` tstrike
2020-03-12 11:13 ` tstrike
2020-03-12 11:14 ` tstrike
2020-03-12 11:22 ` Boris Derzhavets
2020-03-12 11:38 ` Boris Derzhavets
2020-03-12 12:40 ` Christian Ehrhardt 
2020-03-12 12:47 ` tstrike
2020-03-12 13:41 ` Christian Ehrhardt  [this message]
2020-03-12 14:34 ` Andreas Hasenack
2020-03-12 14:35 ` Andreas Hasenack
2020-03-12 14:36 ` Andreas Hasenack
2020-03-12 14:41 ` Andreas Hasenack
2020-03-12 14:42 ` Andreas Hasenack
2020-03-12 15:00 ` tstrike
2020-03-12 15:08 ` Andreas Hasenack
2020-03-12 15:12 ` Christian Ehrhardt 
2020-03-12 16:46 ` Boris Derzhavets
2020-03-12 18:56 ` Boris Derzhavets
2020-03-13  7:18 ` Christian Ehrhardt 
2020-03-13 13:24 ` Dr. David Alan Gilbert
2020-03-13 15:24 ` Christian Ehrhardt 
2020-03-13 18:04 ` Dr. David Alan Gilbert
2020-03-16  9:36 ` Christian Ehrhardt 
2020-03-16 11:43 ` Boris Derzhavets
2020-03-16 11:45 ` Boris Derzhavets
2020-03-16 11:51 ` Boris Derzhavets
2020-03-16 11:55 ` Boris Derzhavets
2020-03-16 14:20 ` Andreas Hasenack
2020-03-16 14:52 ` Andreas Hasenack
2020-03-16 18:06 ` Andreas Hasenack
2020-03-18 19:27 ` Christian Ehrhardt 
2020-03-19  9:58 ` Christian Ehrhardt 
2020-03-19  9:58 ` Christian Ehrhardt 
2020-03-19  9:59 ` Christian Ehrhardt 
2020-03-19 10:18 ` Dr. David Alan Gilbert
2020-03-19 11:18 ` Christian Ehrhardt 
2020-03-19 11:34 ` Christian Ehrhardt 
2020-03-19 11:46 ` Dr. David Alan Gilbert
2020-03-19 12:11 ` Launchpad Bug Tracker
2020-03-19 12:13 ` Christian Ehrhardt 
2020-03-23 17:36 ` Launchpad Bug Tracker
2020-03-23 20:09 ` tstrike
2020-03-23 20:21 ` Andreas Hasenack
2020-03-23 21:12 ` Boris Derzhavets
2020-03-24  1:27 ` tstrike
2020-03-24  5:55 ` Christian Ehrhardt 
2020-05-05 14:58 ` Andreas Weller
2020-05-06  5:26 ` Christian Ehrhardt 
2020-05-06  8:00 ` Andreas Weller
2020-06-04 15:55 ` Fabrice Moyen
2020-06-04 17:24 ` Dr. David Alan Gilbert
2020-06-05  8:02 ` Fabrice Moyen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=158402050357.25890.4633057907889866578.malone@gac.canonical.com \
    --to=1866870@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.