qemu-kvm not working as nested inside ESX 6.0
Bug #1691109 reported by
fxpester
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Incomplete
|
Undecided
|
Unassigned | ||
qemu (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
ESX 6.0 (virt bits exposed) - Ubuntu 16.04 + qemu-kvm 1:2.8+dfsg-
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
no longer affects: | openstack-community |
affects: | qemu → qemu (Ubuntu) |
To post a comment you must log in.
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