Starting from the Disco build env that I had I changed the packages Step #1 binutils: Unpacking binutils-x86-64-linux-gnu (2.33-2ubuntu1.2) over (2.32-7ubuntu4) ... Unpacking libbinutils:amd64 (2.33-2ubuntu1.2) over (2.32-7ubuntu4) ... Unpacking binutils (2.33-2ubuntu1.2) over (2.32-7ubuntu4) ... Unpacking binutils-common:amd64 (2.33-2ubuntu1.2) over (2.32-7ubuntu4) ...
=> Still working Step #2 gcc: Unpacking libubsan1:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking libtsan0:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking gcc-9-base:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking libstdc++6:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking libquadmath0:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking liblsan0:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking libitm1:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking libgomp1:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking libcc1-0:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking libatomic1:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking libasan5:amd64 (9.2.1-9ubuntu2) over (9.1.0-2ubuntu2~19.04) ... Unpacking libgcc1:amd64 (1:9.2.1-9ubuntu2) over (1:9.1.0-2ubuntu2~19.04) ... Unpacking libisl21:amd64 (0.21-2) ... Unpacking cpp-9 (9.2.1-9ubuntu2) ... Unpacking libgcc-9-dev:amd64 (9.2.1-9ubuntu2) ... Unpacking gcc-9 (9.2.1-9ubuntu2) ... Unpacking libstdc++-9-dev:amd64 (9.2.1-9ubuntu2) ... Unpacking g++-9 (9.2.1-9ubuntu2) ... Unpacking g++ (4:9.2.1-3.1ubuntu1) over (4:8.3.0-1ubuntu3) ... Unpacking gcc (4:9.2.1-3.1ubuntu1) over (4:8.3.0-1ubuntu3) ... Unpacking cpp (4:9.2.1-3.1ubuntu1) over (4:8.3.0-1ubuntu3) ... => now it is breaking One thing that we have seen to cause breakage in other cases was the new default to enable: -fcf-protection The code already carries quite a bunch of similar "no" rules: COMMONCFLAGS += $(call cc-option,$(CC),-nopie,) COMMONCFLAGS += $(call cc-option,$(CC),-fno-pie,) COMMONCFLAGS += $(call cc-option,$(CC),-fno-stack-protector,) COMMONCFLAGS += $(call cc-option,$(CC),-fno-stack-protector-all,) COMMONCFLAGS += $(call cc-option,$(CC),-fstack-check=no,) COMMONCFLAGS += $(call cc-option,$(CC),-Wno-address-of-packed-member,) Lets add to that: COMMONCFLAGS += $(call cc-option,$(CC),-fcf-protection=none,) => That made it work \o/ ! -- 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
