From: Michael Johnson <johnsomor@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1691109] Re: qemu-kvm not working as nested inside ESX 6.0
Date: Mon, 10 Jul 2017 17:49:31 -0000 [thread overview]
Message-ID: <149970897186.15700.1614735111796333385.malone@wampee.canonical.com> (raw)
In-Reply-To: 149494197837.9319.2077559864368104737.malonedeb@wampee.canonical.com
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
next prev parent reply other threads:[~2017-07-10 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 13:39 [Qemu-devel] [Bug 1691109] [NEW] qemu-kvm not working as nested inside ESX 6.0 fxpester
2017-05-16 13:44 ` [Qemu-devel] [Bug 1691109] " fxpester
2017-07-10 17:49 ` Michael Johnson [this message]
2017-10-06 15:59 ` Stefano Maffulli
2017-10-06 17:46 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=149970897186.15700.1614735111796333385.malone@wampee.canonical.com \
--to=johnsomor@gmail.com \
--cc=1691109@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.