From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46708) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e0WwR-0005GJ-CP for qemu-devel@nongnu.org; Fri, 06 Oct 2017 14:01:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e0WwO-0004x0-BK for qemu-devel@nongnu.org; Fri, 06 Oct 2017 14:01:43 -0400 Received: from indium.canonical.com ([91.189.90.7]:33784) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e0WwO-0004w5-5S for qemu-devel@nongnu.org; Fri, 06 Oct 2017 14:01:40 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1e0WwK-0000hL-Ep for ; Fri, 06 Oct 2017 18:01:36 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 273C42E81A2 for ; Fri, 6 Oct 2017 18:01:33 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 06 Oct 2017 17:46:26 -0000 From: Thomas Huth <1691109@bugs.launchpad.net> Reply-To: Bug 1691109 <1691109@bugs.launchpad.net> Sender: bounces@canonical.com References: <149494197837.9319.2077559864368104737.malonedeb@wampee.canonical.com> Message-Id: <150731198867.15501.4037372442579527652.launchpad@soybean.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1691109] Re: qemu-kvm not working as nested inside ESX 6.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ** Project changed: qemu =3D> qemu (Ubuntu) -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1691109 Title: qemu-kvm not working as nested inside ESX 6.0 Status in qemu package in Ubuntu: Confirmed Bug description: ESX 6.0 (virt bits exposed) - Ubuntu 16.04 + qemu-kvm 1:2.8+dfsg- 3ubuntu2~cloud0 - CirrOS launched by OpenStack (devstack master) = VM will start with -machine =3D 'pc-i440fx-zesty' and will stuck in "boot= ing from hard disk" to fix it you can manually change -machine to 'pc-i440fx-2.3' also, ISOs boots well, so I think it`s something about block devices configuration introduced in new machine type. p.s. also confirmed with RHEL instead of Ubuntu as KVM host - new machine type= don`t work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1691109/+subscriptions