Launch Instance vm Starting up

[men]

[root@controller ~]# virsh list
 Id Name State
----------------------------------------------------
 10 instance-0000001a running

[root@controller ~]# cat /var/log/libvirt/qemu/instance-0000001a.log
2017-01-01 15:27:19.429+0000: starting up libvirt version: 2.0.0, package: 10.el7_3.2 (CentOS BuildSystem <http://bugs.centos.org>, 2016-12-06-19:53:38, c1bm.rdu2.centos.org), qemu version: 2.6.0 (qemu-kvm-ev-2.6.0-27.1.el7), hostname: controller
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name guest=instance-0000001a,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-10-instance-0000001a/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=tcg,usb=off -cpu Haswell-noTSX,+vme,+ds,+ss,+ht,+osxsave,+f16c,+rdrand,+hypervisor,+arat,+tsc_adjust,+xsaveopt,+pdpe1gb,+abm -m 64 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 8cbaa40d-c061-47fc-83df-698f2455c7d9 -smbios 'type=1,manufacturer=RDO,product=OpenStack Compute,version=14.0.2-1.el7,serial=4803ff26-9107-4c8c-b9f9-83cda5553350,uuid=8cbaa40d-c061-47fc-83df-698f2455c7d9,family=Virtual Machine' -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-10-instance-0000001a/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/instances/8cbaa40d-c061-47fc-83df-698f2455c7d9/disk,format=qcow2,if=none,id=drive-virtio-disk0,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=26,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:3e:38:f9,bus=pci.0,addr=0x3 -add-fd set=1,fd=29 -chardev file,id=charserial0,path=/dev/fdset/1,append=on -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 10.40.1.70:0 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
char device redirected to /dev/pts/0 (label charserial1)
warning: TCG doesn't support requested feature: CPUID.01H:EDX.vme [bit 1]
warning: TCG doesn't support requested feature: CPUID.01H:EDX.ds [bit 21]
warning: TCG doesn't support requested feature: CPUID.01H:EDX.ht [bit 28]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.fma [bit 12]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.osxsave [bit 27]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.avx [bit 28]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.f16c [bit 29]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.rdrand [bit 30]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.tsc_adjust [bit 1]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.avx2 [bit 5]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.erms [bit 9]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]

error:
Instance status Starting up .......

nova use qemu

[Mohammed Khan (mkhan1976)]

I am also facing the same issue on vmware fusion and vmware v-center. I have tested on liberty, mitaka, and newton have the same isuue, but when I have deployed on virtual box it's working fine.

[Lee Yarwood (lyarwood)]

Unfortunately this isn't a valid or supported method for deploying nova-compute.

That said are you sure virt_type is qemu and not kvm?

[Mohammed Khan (mkhan1976)]

this is the actual output of my nova.conf. I have done this deployment
using packstack. Interesting part is, when I have deployed on virtualbox I
didn't face any issue. On vmwarefusion and vceneter having an issue.

[DEFAULT]

notify_api_faults=False

state_path=/var/lib/nova

report_interval=10

enabled_apis=osapi_compute,metadata

osapi_compute_listen=0.0.0.0

osapi_compute_listen_port=8774

osapi_compute_workers=4

metadata_listen=0.0.0.0

metadata_listen_port=8775

metadata_workers=4

compute_manager=nova.compute.manager.ComputeManager

service_down_time=60

rootwrap_config=/etc/nova/rootwrap.conf

volume_api_class=nova.volume.cinder.API

auth_strategy=keystone

use_forwarded_for=False

fping_path=/usr/sbin/fping

heal_instance_info_cache_interval=60

reserved_host_memory_mb=512

cpu_allocation_ratio=16.0

ram_allocation_ratio=1.5

allow_resize_to_same_host=False

scheduler_default_filters=RetryFilter,AvailabilityZoneFilter,RamFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,CoreFilter

scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler

compute_driver=libvirt.LibvirtDriver

vif_plugging_is_fatal=True

vif_plugging_timeout=300

firewall_driver=nova.virt.firewall.NoopFirewallDriver

force_raw_images=True

api_paste_config=api-paste.ini

use_neutron=True

default_floating_pool=public

force_snat_range =0.0.0.0/0

metadata_host=10.10.150.191

dhcp_domain=novalocal

security_group_api=neutron

debug=False

verbose=True

log_dir=/var/log/nova

rpc_backend=rabbit

notification_driver=nova.openstack.common.notifier.rabbit_notifier,ceilometer.compute.nova_notifier

image_service=nova.image.glance.GlanceImageService

notification_topics=notifications

osapi_volume_listen=0.0.0.0

novncproxy_host=0.0.0.0

novncproxy_port=6080

[api_database]

connection=mysql+pymysql://nova_api:d1222572bbef4d72@10.10.150.191/nova_api

[barbican]

[cache]

[cells]

[cinder]

catalog_info=volumev2:cinderv2:publicURL

[conductor]

use_local=False

[cors]

[cors.subdomain]

[database]

connection=mysql+pymysql://nova:d1222572bbef4d72@10.10.150.191/nova

[ephemeral_storage_encryption]

[glance]

api_servers=10.10.150.191:9292

[guestfs]

[hyperv]

[image_file_url]

[ironic]

[keymgr]

[keystone_authtoken]

auth_uri=http://10.10.150.191:5000/v2.0

admin_password=8af6ad5a51d34738

admin_user=nova

admin_tenant_name=services

identity_uri=http://10.10.150.191:35357

[libvirt]

virt_type=qemu

inject_password=False

inject_key=False

inject_partition=-1

live_migration_uri=qemu+tcp://nova@%s/system

cpu_mode=host-model

vif_driver=nova.virt.libvirt.vif.LibvirtGenericVIFDriver

[matchmaker_redis]

[metrics]

[neutron]

service_metadata_proxy=True

metadata_proxy_shared_secret =7a6c8c24d1c645c9

url=http://10.10.150.191:9696

region_name=RegionOne

ovs_bridge=br-int

extension_sync_interval=600

auth_url=http://10.10.150.191:35357/v3

password=b344ceafa3c94a4f

project_domain_name=Default

project_name=services

timeout=60

user_domain_name=Default

username=neutron

auth_plugin=v3password

[osapi_v21]

[oslo_concurrency]

lock_path=/var/lib/nova/tmp

[oslo_messaging_amqp]

[oslo_messaging_notifications]

[oslo_messaging_rabbit]

amqp_dura...

[Mohammed Khan (mkhan1976)]

I have run this command egrep -c '(vmx|svm)' /proc/cpuinfo its returning 0
and I have double checked nova.conf file as well where virt_type=qemu,
restart libvirt service but no luck

On Wed, Jan 4, 2017 at 9:50 AM, Bobby khan <email address hidden> wrote:

> this is the actual output of my nova.conf. I have done this deployment
> using packstack. Interesting part is, when I have deployed on virtualbox I
> didn't face any issue. On vmwarefusion and vceneter having an issue.
>
>
>
>
> [DEFAULT]
>
> notify_api_faults=False
>
> state_path=/var/lib/nova
>
> report_interval=10
>
> enabled_apis=osapi_compute,metadata
>
> osapi_compute_listen=0.0.0.0
>
> osapi_compute_listen_port=8774
>
> osapi_compute_workers=4
>
> metadata_listen=0.0.0.0
>
> metadata_listen_port=8775
>
> metadata_workers=4
>
> compute_manager=nova.compute.manager.ComputeManager
>
> service_down_time=60
>
> rootwrap_config=/etc/nova/rootwrap.conf
>
> volume_api_class=nova.volume.cinder.API
>
> auth_strategy=keystone
>
> use_forwarded_for=False
>
> fping_path=/usr/sbin/fping
>
> heal_instance_info_cache_interval=60
>
> reserved_host_memory_mb=512
>
> cpu_allocation_ratio=16.0
>
> ram_allocation_ratio=1.5
>
> allow_resize_to_same_host=False
>
> scheduler_default_filters=RetryFilter,AvailabilityZoneFilter,
> RamFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,
> CoreFilter
>
> scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
>
> compute_driver=libvirt.LibvirtDriver
>
> vif_plugging_is_fatal=True
>
> vif_plugging_timeout=300
>
> firewall_driver=nova.virt.firewall.NoopFirewallDriver
>
> force_raw_images=True
>
> api_paste_config=api-paste.ini
>
> use_neutron=True
>
> default_floating_pool=public
>
> force_snat_range =0.0.0.0/0
>
> metadata_host=10.10.150.191
>
> dhcp_domain=novalocal
>
> security_group_api=neutron
>
> debug=False
>
> verbose=True
>
> log_dir=/var/log/nova
>
> rpc_backend=rabbit
>
> notification_driver=nova.openstack.common.notifier.
> rabbit_notifier,ceilometer.compute.nova_notifier
>
> image_service=nova.image.glance.GlanceImageService
>
> notification_topics=notifications
>
> osapi_volume_listen=0.0.0.0
>
> novncproxy_host=0.0.0.0
>
> novncproxy_port=6080
>
> [api_database]
>
> connection=mysql+pymysql://nova_api:d1222572bbef4d72@10.10.
> 150.191/nova_api
>
> [barbican]
>
> [cache]
>
> [cells]
>
> [cinder]
>
> catalog_info=volumev2:cinderv2:publicURL
>
> [conductor]
>
> use_local=False
>
> [cors]
>
> [cors.subdomain]
>
> [database]
>
> connection=mysql+pymysql://nova:d1222572bbef4d72@10.10.150.191/nova
>
> [ephemeral_storage_encryption]
>
> [glance]
>
> api_servers=10.10.150.191:9292
>
> [guestfs]
>
> [hyperv]
>
> [image_file_url]
>
> [ironic]
>
> [keymgr]
>
> [keystone_authtoken]
>
> auth_uri=http://10.10.150.191:5000/v2.0
>
> admin_password=8af6ad5a51d34738
>
> admin_user=nova
>
> admin_tenant_name=services
>
> identity_uri=http://10.10.150.191:35357
>
> [libvirt]
>
> virt_type=qemu
>
> inject_password=False
>
> inject_key=False
>
> inject_partition=-1
>
> live_migration_uri=qemu+tcp://nova@%s/system
>
> cpu_mode=host-model
>
> vif_driver=nova.virt.libvirt.vif.LibvirtGenericVIFDriver
>
> [matchmaker_redis]
>
> [metrics]
>
> [neutron]...

[men (keyi)]

All my services are normal, just like yours。

I use virtual machine testing, the use of qemu（egrep -c '(vmx|svm)' /proc/cpuinfo its returning 0）

system centos7.3 ，Found qemu version upgrade
[root@controller ~]# /usr/libexec/qemu-kvm -version
QEMU emulator version 2.6.0 (qemu-kvm-ev-2.6.0-27.1.el7), Copyright (c) 2003-2008 Fabrice Bellard

I have built before the openstack N version is normal, but the computing node is a physical server, using kvm

Instances can be booted normally
[root@node1 ~]# /usr/libexec/qemu-kvm -version
QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-126.el7), Copyright (c) 2003-2008 Fabrice Bellard

Do not know whether the version with qemu？

[Mohammed Khan (mkhan1976)]

Hi there,

after I have run egrep -c '(vmx|svm)' /proc/cpuinfo the output is 2 now
but it was 0, I have changed virt_type= kvm and restart the nova services.
Now try to access console and the output it's different then before on
console.

OUTPUT:

seaBIOS (version 1.9.1-5.e17)
machine uuid d1....-78-......
iPXE http://ipxe.org pc12.00000

booting from hard disk
grub

 egrep -c '(vmx|svm)' /proc/cpuinfo

2

[root@mitaka ~]# /usr/libexec/qemu-kvm -version

QEMU emulator version 2.6.0 (qemu-kvm-ev-2.6.0-27.1.el7), Copyright (c)
2003-2008 Fabrice Bellard

On Thu, Jan 5, 2017 at 8:18 PM, men <email address hidden> wrote:

> All my services are normal, just like yours。
>
> I use virtual machine testing, the use of qemu（egrep -c '(vmx|svm)'
> /proc/cpuinfo its returning 0）
>
> system centos7.3 ，Found qemu version upgrade
> [root@controller ~]# /usr/libexec/qemu-kvm -version
> QEMU emulator version 2.6.0 (qemu-kvm-ev-2.6.0-27.1.el7), Copyright (c)
> 2003-2008 Fabrice Bellard
>
>
> I have built before the openstack N version is normal, but the computing
> node is a physical server, using kvm
>
> Instances can be booted normally
> [root@node1 ~]# /usr/libexec/qemu-kvm -version
> QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-126.el7), Copyright (c)
> 2003-2008 Fabrice Bellard
>
>
>
> Do not know whether the version with qemu？
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1653430
>
> Title:
> Launch Instance vm Starting up
>
> Status in OpenStack Compute (nova):
> Invalid
>
> Bug description:
> [root@controller ~]# virsh list
> Id Name State
> ----------------------------------------------------
> 10 instance-0000001a running
>
>
>
> [root@controller ~]# cat /var/log/libvirt/qemu/instance-0000001a.log
> 2017-01-01 15:27:19.429+0000: starting up libvirt version: 2.0.0,
> package: 10.el7_3.2 (CentOS BuildSystem <http://bugs.centos.org>,
> 2016-12-06-19:53:38, c1bm.rdu2.centos.org), qemu version: 2.6.0
> (qemu-kvm-ev-2.6.0-27.1.el7), hostname: controller
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
> HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm
> -name guest=instance-0000001a,debug-threads=on -S -object
> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/
> qemu/domain-10-instance-0000001a/master-key.aes -machine
> pc-i440fx-rhel7.3.0,accel=tcg,usb=off -cpu Haswell-noTSX,+vme,+ds,+ss,+
> ht,+osxsave,+f16c,+rdrand,+hypervisor,+arat,+tsc_adjust,+xsaveopt,+pdpe1gb,+abm
> -m 64 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
> 8cbaa40d-c061-47fc-83df-698f2455c7d9 -smbios 'type=1,manufacturer=RDO,product=OpenStack
> Compute,version=14.0.2-1.el7,serial=4803ff26-9107-4c8c-
> b9f9-83cda5553350,uuid=8cbaa40d-c061-47fc-83df-698f2455c7d9,family=Virtual
> Machine' -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/
> var/lib/libvirt/qemu/domain-10-instance-0000001a/monitor.sock,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
> -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus...

[Mohammed Khan (mkhan1976)]

I think believe it's the issue with qemu version. causing I am facing the same exact issur. I have launched instance on lab environment where qemu version is previous version qemu. I even install virt-manager on both environment where different qemu version and I could have created a vm on previous version of qemu but not on the ltest version of qemu.

[Tim Serewicz (h-tim-2)]

I'm having the same issue. Not sure why QEMU would be an invalid or non-supported manner of starting an instance (as mentioned in #3 as a reason to invalidate the bug), as kvm is an accelerator. Nice feature, but should not be essential. This would also be indicated by this setting being in the /etc/nova/nova.conf file - using qemu would be a valid type of hypervisor. The file actually says this:
# Allowed values: kvm, lxc, qemu, uml, xen, parallels

Having deployed RDO Liberty on AWS nodes many times this issue started when I moved to Newton. As AWS nodes dose not show vmx or svm flags the virt_type was set to qemu instead of kvm during packstack installation.

I can create a qemu instance by hand and log in. It throws a warning that the kvm module is unavailable, but does work without the accelerator. Guestfish shows the image to be good and downloading it to my local system the cirros vm boots without issue.

Using the same AWS ami and instance type, with the same configuration edits for packstack the install can no longer deploy a usable instance. Every permutation of install appears to work but the console says: "Starting up ...."

When I download cirros image to a different node, running QEMU emulator version 2.7.1(qemu-2.7.1-1.fc25), it boots just fine. This is a bug in the qemu-kvm-ev used in OpenStack, or how nova works with qemu-kvm-ev

[Mohammed Khan (mkhan1976)]

Hi Tim,

Thank you for reply. I have resolved the issue by changing in nova.conf file and change was virt_type=qemu, cpu_mode=none in mitaka version. After make these changes in mitaka I am able to access the console, private ip address which also can access to external network.

Now, I have same issue with liberty version I have made same changes but now the error is

Thanks,
Mohammed Khan

> On Feb 1, 2017, at 1:08 PM, Tim Serewicz <email address hidden> wrote:
>
> I'm having the same issue. Not sure why QEMU would be an invalid or non-supported manner of starting an instance (as mentioned in #3 as a reason to invalidate the bug), as kvm is an accelerator. Nice feature, but should not be essential. This would also be indicated by this setting being in the /etc/nova/nova.conf file - using qemu would be a valid type of hypervisor. The file actually says this:
> # Allowed values: kvm, lxc, qemu, uml, xen, parallels
>
> Having deployed RDO Liberty on AWS nodes many times this issue started
> when I moved to Newton. As AWS nodes dose not show vmx or svm flags the
> virt_type was set to qemu instead of kvm during packstack installation.
>
> I can create a qemu instance by hand and log in. It throws a warning
> that the kvm module is unavailable, but does work without the
> accelerator. Guestfish shows the image to be good and downloading it to
> my local system the cirros vm boots without issue.
>
> Using the same AWS ami and instance type, with the same configuration
> edits for packstack the install can no longer deploy a usable instance.
> Every permutation of install appears to work but the console says:
> "Starting up ...."
>
> When I download cirros image to a different node, running QEMU emulator
> version 2.7.1(qemu-2.7.1-1.fc25), it boots just fine. This is a bug in
> the qemu-kvm-ev used in OpenStack, or how nova works with qemu-kvm-ev
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1653430
>
> Title:
> Launch Instance vm Starting up
>
> Status in OpenStack Compute (nova):
> Invalid
>
> Bug description:
> [root@controller ~]# virsh list
> Id Name State
> ----------------------------------------------------
> 10 instance-0000001a running
>
>
>
> [root@controller ~]# cat /var/log/libvirt/qemu/instance-0000001a.log
> 2017-01-01 15:27:19.429+0000: starting up libvirt version: 2.0.0, package: 10.el7_3.2 (CentOS BuildSystem <http://bugs.centos.org>, 2016-12-06-19:53:38, c1bm.rdu2.centos.org), qemu version: 2.6.0 (qemu-kvm-ev-2.6.0-27.1.el7), hostname: controller
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name guest=instance-0000001a,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-10-instance-0000001a/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=tcg,usb=off -cpu Haswell-noTSX,+vme,+ds,+ss,+ht,+osxsave,+f16c,+rdrand,+hypervisor,+arat,+tsc_adjust,+xsaveopt,+pdpe1gb,+abm -m 64 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid...

[Tim Serewicz (h-tim-2)]

Thank you Mohammed!

Your changes are a great work-around. I've been trying to figure out a fix for weeks now. Thank you! I would guess that whatever logic is used to determine which type of cpu_mode to choose needs to be updated for environments which use qemu but not kvm. I am not nearly good enough with code to make the change.

While troubleshooting I saw the same PXE error on the console you mention. I did not have this same issue on Liberty. Using AWS nodes, CentOS 7.3-1611, Liberty works with QEMU without issue.

While trying to get Newton to work when I swapped out qemu-kvm for qemu-kvm-ev it would boot to an immediate PXE output like your image shows. Perhaps an update to the python doesn't understand how to view the boot code any more. If I find a fix I will definitly let you know.

Thanks again!

Tim

[Qwest (neoanantha)]

This issue seems similar as reported through

https://bugzilla.redhat.com/show_bug.cgi?id=1404627

The fix is now available in RHEL 7.4

You would be needing the packages:
libvirt-client-3.2.0-10.el7.x86_64
qemu-kvm-rhev-2.9.0-10.el7.x86_64

Had been hitting exactly the same issue and the resolution provided in bugzilla works perfectly with above version of packages

Referring the comment from chhu: https://bugzilla.redhat.com/show_bug.cgi?id=1404627#c23

with packages:
libvirt-client-3.2.0-10.el7.x86_64
qemu-kvm-rhev-2.9.0-10.el7.x86_64

Steps:
1. Edit the /etc/nova/nova.conf, and restart OpenStack services.
virt_type=qemu
cpu_mode=host-model
#service openstack-nova-api restart
#service openstack-nova-compute restart

Then, try to start a VM with cirros image.
The VM start successfully. No hang.

2. Edit the /etc/nova/nova.conf, and restart OpenStack services.
virt_type=kvm
cpu_mode=host-model

#service openstack-nova-api restart
#service openstack-nova-compute restart

Then, try to start a VM with cirros image.
The VM start successfully. No hang.

CentOS 7.4 should be released with the mentioned packages with said versions within 1 month's time I believe

To confirm above fix resolved the issue for me:

RHEL 7.4 VM on vSphere 6.0
Ocata Packstack AIO deployed
Cloudbase Windows 2012 Eval Qcow2 image imported into glance and instance launched successfully

[trakatelis (trakatelis)]

If your compute host is centos/rhel 7.3 running as a VM on ESXi,
there is a quick fix to have hardware assisted virtualization (virt_type = kvm) work.

In the [libvirt] section of /etc/nova/nova.conf set hw_machine_type as follows:

hw_machine_type = x86_64=pc-i440fx-rhel7.2.0

[bassim (aly12)]

I still have this problem in newton and above fixes doens't work for me. I have RDO Newton deployed on baremetal server (not ESXI) and every time I boot Cirros or cisco images I get "Failed to boot error"

CentOS version: 7.4.1708

KVM version: qemu-kvm-ev-2.9.0.16.el7_4.13.1.x86_64
Libvirt version: libvirt-client-3.2.0-14.el7_4.7.x86_64

Any help would be appreciated

[trakatelis (trakatelis)]

After setting

hw_machine_type = x86_64=pc-i440fx-rhel7.2.0
(be careful, there are 2 equal signs)

in /etc/nova/nova.conf configuration file on every compute node,
restart the nova-compute service on every compute node

systemctl restart openstack-nova-compute.service

[bassim (aly12)]

@trakatelis
yes, this solve the problem of openstack installed over ESXI but not openstack over baremetal directly. I tried host-model and host-passthrough and both options not working