From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38818) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fQs2V-0007tT-GO for qemu-devel@nongnu.org; Thu, 07 Jun 2018 06:21:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fQs2S-0001MK-5N for qemu-devel@nongnu.org; Thu, 07 Jun 2018 06:21:07 -0400 Received: from indium.canonical.com ([91.189.90.7]:60098) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fQs2R-0001Kx-UR for qemu-devel@nongnu.org; Thu, 07 Jun 2018 06:21:04 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1fQs2Q-0000BF-7R for ; Thu, 07 Jun 2018 10:21:02 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 759782E8923 for ; Thu, 7 Jun 2018 10:20:57 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 07 Jun 2018 10:12:17 -0000 From: Mykola Ivanets <1636217@bugs.launchpad.net> Reply-To: Bug 1636217 <1636217@bugs.launchpad.net> Sender: bounces@canonical.com References: <20161024141318.21041.87583.malonedeb@gac.canonical.com> Message-Id: <152836633743.24753.14618544270904989268.malone@gac.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1636217] Re: qemu-kvm 2.7 does not boot kvm VMs with virtio on top of VMware ESX List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Well, it appeared that it is not enough to set "disable-modern=3Don" for virtio-blk-pci devices. You have to do the same for virtio-scsi-pci, and may be for other virtio devices you are using to disable virtio 1.0. But VM will hangs latter on during boot process if you use virtio-rng-pci. "-machine accel=3Dtcg" will work but in cost of performance penalty due to software virtualization. So I found "-machine type=3Dpc-i440fx-x" where x <=3D 2.6 the only reliable workaround. -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1636217 Title: qemu-kvm 2.7 does not boot kvm VMs with virtio on top of VMware ESX Status in QEMU: New Bug description: After todays Proxmox update all my Linux VMs stopped booting. # How to reproduce - Have KVM on top of VMware ESX (I use VMware ESX 6) - Boot Linux VM with virtio Disk drive. = # Result virtio based VMs do not boot anymore: root@demotuxdc:/etc/pve/nodes/demotuxdc/qemu-server# grep virtio0 100.con= f = bootdisk: virtio0 virtio0: pvestorage:100/vm-100-disk-1.raw,discard=3Don,size=3D20G (initially with cache=3Dwritethrough, but that doesn=C2=B4t matter) What happens instead is: - BIOS displays "Booting from harddisk..." - kvm process of VM loops at about 140% of Intel(R) Core(TM) i5-6260U CPU= @ 1.80GHz Skylake dual core CPU Disk of course has valid bootsector: root@demotuxdc:/srv/pvestorage/images/100# file -sk vm-100-disk-1.raw = vm-100-disk-1.raw: DOS/MBR boot sector DOS/MBR boot sector DOS executable= (COM), boot code root@demotuxdc:/srv/pvestorage/images/100# head -c 2048 vm-100-disk-1.raw= | hd | grep GRUB 00000170 be 94 7d e8 2e 00 cd 18 eb fe 47 52 55 42 20 00 |..}.......GR= UB .| = # Workaround 1 - Change disk from virtio0 to scsi0 - Debian boots out of the box after this change - SLES 12 needs a rebuilt initrd - CentOS 7 too, but it seems that is not even enough and it still fails (= even in hostonly=3D"no" mode for dracut) = # Workaround 2 Downgrade pve-qemu-kvm 2.7.0-3 to 2.6.2-2. = # Expected results Disk boots just fine via virtio like it did before. = # Downstream bug report Downstream suggests an issue with upstream qemu-kvm: https://bugzilla.proxmox.com/show_bug.cgi?id=3D1181 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1636217/+subscriptions