** Description changed:

- After a recent upgrade I can't start a Windows 10 VM anymore, QEMU
- crashes with the error message:
+ [Impact]
+ 
+  * Despite quite a bunch of regression testing, explicit testing by 
+    different parties and extra time in -proposed the fix to bug 1805256 
+    caused a regression for other configurations.
+ 
+  * We will upload version .28 which essentially is a revert of .27 to 
+    provide us the time to revisit the fix for bug 1805256 again and not 
+    being forced to rush this cleanup.
+ 
+ 
+ [Test Case]
+ 
+  * Ensure that the revert really avoids the regression to iothread 
+    handling. Start a guest with virtio-scsi + iothreads.
+ 
+ <domain type='kvm'>
+ ...
+   <iothreads>1</iothreads>
+ ...
+    <controller type='scsi' index='0' model='virtio-scsi'>
+       <driver iothread='1'/>
+       <address type='pci' domain='0x0000' bus='0x00' slot='0x04' 
function='0x0'/>
+    </controller>
+ ...
+ </domain>
+ 
+ [Regression Potential]
+ 
+  * The regression already happened despite all measures. This is just the 
+    revert. So other than any issues creeping in at build time (e.g. 
+    toolchain changes, which I didn't see any) this should eventually match 
+    the former .27
+    https://launchpad.net/ubuntu/+source/qemu/1:2.11+dfsg-1ubuntu7.27
+ 
+ [Other Info]
+  
+  * The formerly fixed bug 1805256 will re-open due to this and be worked on 
+    again.
+ 
+ ---
+ 
+ 
+ After a recent upgrade I can't start a Windows 10 VM anymore, QEMU crashes 
with the error message:
  
  error: Failed to start domain win10
  error: internal error: qemu unexpectedly closed the monitor: 
qemu-system-x86_64: /build/qemu-v_zvmu/qemu-2.11+dfsg/util/aio-posix.c:592: 
aio_poll: Assertion `in_aio_context_home_thread(ctx)' failed.
  
  I was able to resurrect the VM by removing the iothread-related elements
  from the domain definition:
  
  <domain type='kvm'>
  ...
-   <iothreads>1</iothreads>
+   <iothreads>1</iothreads>
  ...
-    <controller type='scsi' index='0' model='virtio-scsi'>
-       <driver iothread='1'/>
-       <address type='pci' domain='0x0000' bus='0x00' slot='0x04' 
function='0x0'/>
-    </controller>
+    <controller type='scsi' index='0' model='virtio-scsi'>
+       <driver iothread='1'/>
+       <address type='pci' domain='0x0000' bus='0x00' slot='0x04' 
function='0x0'/>
+    </controller>
  ...
  </domain>
  
  The domain XML is attached.
  
  I'm using virtio-scsi and not virtio-blk because I use trimming to keep
  my QCOW image small(er). Would be great if I could continue to use this
  with iothreads enabled.
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:      18.04
  
  $ apt-cache policy qemu-kvm
  qemu-kvm:
-   Installiert:           1:2.11+dfsg-1ubuntu7.27
-   Installationskandidat: 1:2.11+dfsg-1ubuntu7.27
-   Versionstabelle:
-  *** 1:2.11+dfsg-1ubuntu7.27 500
-         500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
-         100 /var/lib/dpkg/status
-      1:2.11+dfsg-1ubuntu7.26 500
-         500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
-      1:2.11+dfsg-1ubuntu7 500
-         500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+   Installiert:           1:2.11+dfsg-1ubuntu7.27
+   Installationskandidat: 1:2.11+dfsg-1ubuntu7.27
+   Versionstabelle:
+  *** 1:2.11+dfsg-1ubuntu7.27 500
+         500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
+         100 /var/lib/dpkg/status
+      1:2.11+dfsg-1ubuntu7.26 500
+         500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
+      1:2.11+dfsg-1ubuntu7 500
+         500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qemu-kvm 1:2.11+dfsg-1ubuntu7.27
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 13:05:17 2020
  InstallationDate: Installed on 2019-10-03 (268 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  KvmCmdLine: COMMAND         STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-108-generic 
root=UUID=d40a86d5-61ae-486e-8ddf-9581c538d64e ro quiet splash vt.handoff=1
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: Z68 Pro3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd07/13/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Pro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

** Changed in: qemu (Ubuntu Bionic)
       Status: Confirmed => In Progress

** Changed in: qemu (Ubuntu Bionic)
     Assignee: Rafael David Tinoco (rafaeldtinoco) => Christian Ehrhardt  
(paelzer)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885419

Title:
  QEMU crash using virtio-scsi with iothread

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1885419/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to