[Bug 1885419] [NEW] QEMU crash using virtio-scsi with iothread
Public bug reported: 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: ... 1 ... ... 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 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= 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. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Domain XML causing failure." https://bugs.launchpad.net/bugs/1885419/+attachment/5387838/+files/win10.xml -- 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
[Bug 1835546] Re: [20.04 FEAT] Base KVM setup for secure guests - qemu part
The QEMU review is still ongoing. As a stop-gap measure it would be great to have PPA with a preliminary build of QEMU (master level + patches). Attached is a full diff on top of 4.2. Since the attached patch obsoletes some of the debian/patches content, the following series file should suffice: pv-full.diff qboot-stop-using-inttypes.patch qboot-no-jump-tables.diff # ubuntu patches ubuntu/expose-vmx_qemu64cpu.patch ubuntu/enable-svm-by-default.patch ubuntu/define-ubuntu-machine-types.patch ubuntu/pre-bionic-256k-ipxe-efi-roms.patch ubuntu/lp-1857033-i386-Add-new-CPU-model-Cooperlake.patch It will be necessary to tweak the machine type and the CPU model patch. Further, I had to apply this change to debian/rules: --- orig/debian/rules 2020-02-12 09:21:56.0 -0500 +++ pv/debian/rules 2020-03-09 06:54:19.0 -0400 @@ -103,6 +101,9 @@ b/configure-stamp: configure dh_testdir + # Fix up permission + chmod +x scripts/kernel-doc + # system build rm -rf b/qemu; mkdir -p b/qemu cd b/qemu && \ ** Attachment added: "Full diff, needs to go to debian/patches" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1835546/+attachment/5335786/+files/pv-full.diff.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835546 Title: [20.04 FEAT] Base KVM setup for secure guests - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713990] Re: virt-install fails on s390x with options --location and --extra-args
The virt-manager version in Debian stretch is not affected by the --extra-args issue, but is subject to the --location failure. ** Bug watch added: Debian Bug tracker #873714 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873714 ** Also affects: virt-manager (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873714 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713990 Title: virt-install fails on s390x with options --location and --extra-args To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1713990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548411] Re: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly
I accidentally attached the same version of the faulty patch. See also upstream Debian bug. ** Patch added: "Now really fixed: v3 of partman-base patch" https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+attachment/4584118/+files/v3-parted_devices-Add-disk-label-type-to-device-directo.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548411 Title: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548411] Re: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly
The initial patch in comment #6 introduced a regression with pristine, non-DASD disks. ** Patch added: "updated patch with better error checking" https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+attachment/4581795/+files/0001-parted_devices-Add-disk-label-type-to-device-directo.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548411 Title: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548411] Re: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly
Parted is innocent here. ** Changed in: parted (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548411 Title: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548411] Re: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly
** Bug watch added: Debian Bug tracker #815916 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815916 ** Also affects: debian-installer (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815916 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548411 Title: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548411] Re: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly
Parted is able to partition DASDs both natively attached and via virtio_blk. It doesn't really make sense to attempt a simulation on top of image files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548411 Title: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548411] Re: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly
** Patch added: "partman-partitioning patch to determine the disk label type" https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+attachment/4579098/+files/0001-create_new_label-Use-correct-label-for-DASDs.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548411 Title: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548411] Re: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly
** Patch added: "partman-base patch to record disk label type" https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+attachment/4579089/+files/0001-parted_devices-Add-disk-label-type-to-device-directo.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548411 Title: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548411] Re: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly
The issue is that partman is chosing the partition type based on the system architecture, not on the disk type. I suggest changes to partman- base and partman-partitioning to determine the correct default partition type per disk on s390. Patches en route. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548411 Title: Installing Ubuntu as KVM guest is not possible because the installer fails to detect Virtual Disk correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541510] Re: parted crashes on lvm, on a dasd drive
** Bug watch added: Debian Bug tracker #814076 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814076 ** Also affects: debian via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814076 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541510 Title: parted crashes on lvm, on a dasd drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1541510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541510] Re: parted crashes on lvm, on a dasd drive
The parted code is iterating all the label types and consequently is probing for DASD. The weird thing is that on one hand the DASD ioctl is passed down to the physical volume (and I mean weird: what would have happened if the logical volume was realised by extents on both DASD and SCSI disks?) and on the other hand silently igores the HDIO_GETGEO.(which I can understand). Currently trying out a patch similar to the one posted by Colin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541510 Title: parted crashes on lvm, on a dasd drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1541510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541510] Re: parted crashes on lvm, on a dasd drive
Regarding comment #6: this doesn't affect s390-tools. Please remove the connection to the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541510 Title: parted crashes on lvm, on a dasd drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1541510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541510] Re: parted crashes on lvm, on a dasd drive
You might want to try out this patch which worked for me. I was able to partition the logical volume on top of a DASD PV. If this solves the problem in the installer I can follow up with upstream. ** Patch added: "0001-fdasd.c-Safeguard-against-geometry-misprobing.patch" https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1541510/+attachment/4563858/+files/0001-fdasd.c-Safeguard-against-geometry-misprobing.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541510 Title: parted crashes on lvm, on a dasd drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1541510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536559] Re: s390-tools/install: package additional management utilities
** Bug watch added: Debian Bug tracker #812092 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812092 ** Also affects: s390-tools (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812092 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536559 Title: s390-tools/install: package additional management utilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1536559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533646] Re: Could you set vm.allocate_pgste = 1 by default?
In my opinion it will be best to set vm.allocate_pgste = 1 unconditionally, regardless of whether qemu is installed or not, and only have the user switch it off for certain memory-intensive workloads (if required at all). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533646 Title: Could you set vm.allocate_pgste = 1 by default? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
