[Qemu-devel] [Bug 1691109] Re: qemu-kvm not working as nested inside ESX 6.0
** Project changed: qemu => 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 = '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/ubuntu/+source/qemu/+bug/1691109/+subscriptions
[Qemu-devel] [Bug 1691109] Re: qemu-kvm not working as nested inside ESX 6.0
** No longer affects: openstack-community -- 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: 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 = '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/qemu/+bug/1691109/+subscriptions
[Qemu-devel] [Bug 1691109] Re: qemu-kvm not working as nested inside ESX 6.0
It appears that the recent qemu packages released for 16.04 set the machine type to "pc-i440fx-zesty" instead of "pc-i440fx-xenial". If you override this and make it use "pc-i440fx-xenial" instances boot again. FYI, if you are using OpenStack, this can be done by editing nova.conf, [libvirt] section, and add hw_machine_type = x86_64=pc-i440fx-xenial ** Changed in: qemu Status: New => Confirmed -- 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 OpenStack Community Project: New Status in QEMU: 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 = '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/openstack-community/+bug/1691109/+subscriptions
[Qemu-devel] [Bug 1691109] Re: qemu-kvm not working as nested inside ESX 6.0
** Also affects: openstack-community Importance: Undecided Status: New -- 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 OpenStack Community Project: New Status in QEMU: 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/openstack-community/+bug/1691109/+subscriptions