qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1691109] [NEW] qemu-kvm not working as nested inside E


From: fxpester
Subject: [Qemu-devel] [Bug 1691109] [NEW] qemu-kvm not working as nested inside ESX 6.0
Date: Tue, 16 May 2017 13:39:38 -0000

Public bug reported:

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

** Affects: openstack-community
     Importance: Undecided
         Status: New

** Affects: qemu
     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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]