Your message dated Wed, 22 Jul 2020 18:23:04 +0300 with message-id <6759651f-e399-8fb4-42d2-d23eb66f1...@msgid.tls.msk.ru> and subject line severity is normal has caused the Debian Bug report #964793, regarding qemu: cannot create hvm domUs after upgrade to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: qemu Version: 1:3.1+dfsg-8+deb10u6 Severity: important Dear Maintainer, * What led up to the situation? apt update/upgrade led to installation of 1:3.1+dfsg-8+deb10u6 for qemu-kvm, qemu-system-common, qemu-system-x86, qemu-system-data, qemu-system-gui and qemu-utils. After update and reboot, none of my previously runnable hvm domUs would run. The command line would respond as normal "Parsing config from ..." and the domU would start very briefly, showing as (null) in xl list but then disappear. Adding verbose to the create command didn't give clues. * What exactly did you do (or not do) that was effective (or ineffective)? Because it was so serious, I downgraded immediately to 1:3.1+dfsg-8+deb10u5 I will try to isolate to one of the packages. * What was the outcome of this action? With u5, hvm domUs worked normally * What outcome did you expect instead? -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---Control: severity -1 normal Don't piggy-back the severity levels. This has nothing to do with "critical" severity. One particular aspect of this package is broken, that's for sure. One might argue it is "important", but it doesn't even count at "serious", as per https://www.debian.org/Bugs/Developer#severities As of "reopening", again, if you don't understand debian bug report life time, it's up to you. The bug _is_ fixed in the version specified. I made sure it is fixed as fast as possible. If you disagree you can show additional info that the version given as "fixed" is still not fixed. /mjt
--- End Message ---
