[Bug 1691109] Re: qemu-kvm not working as nested inside ESX 6.0

[ChristianEhrhardt]

Thanks Thomas for redirecting this to us.

@fxpester - qemu uses the latest default machine type.
Since you run on 16.04 but have -zesty types that means you run very likely with the Ubuntu Cloud Archive.

That is what makes more recent virtualization stacks around openstack available on LTS releases.
As Michael already pointed out in c#1 you can set the type as needed.

I'll add a task for the openstack team who maintains the cloud archive
so they can see this as well. I have no ESX around to retry atm, but
OTOH haven't seen any such issue on Bare metal nor on nested KVM<->KVM.
I'm not sure about the severity yet, as nesting is always a bit less
supported.

@Openstack Team do you have VMware testbeds?

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Changed in: qemu (Ubuntu)
       Status: Confirmed => New

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

Title:
  qemu-kvm not working as nested inside ESX 6.0

Status in Ubuntu Cloud Archive:
  New
Status in qemu package in Ubuntu:
  New

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 = 'pc-i440fx-zesty' and will stuck in "booting 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/cloud-archive/+bug/1691109/+subscriptions