简体繁体 English

使用可启动VM启动Openstack实例

[英]Launching Openstack instance with Bootable VM

原文 2017-04-03 09:51:52 9 2 python-3.x/ shell/ openstack/ qemu/ openstack-nova

I am facing problem while booting my vm with this error message please someone help me out ===>>MP-BIOS bug: 8254 timer not connected to IO-APIC . 我在使用此错误消息启动我的vm时遇到问题请有人帮助我===>>MP-BIOS bug: 8254计时器未连接到IO-APIC 。 what should i do or what I'm missing? 我该怎么做或我缺少什么？
Help me out. 帮帮我。

1) my hypervisor is "qemu" and 2) vncserver_proxyclient_address=cloud.openstack.lan 3)Hypervisor Config==> 1)vncserver_proxyclient_address=cloud.openstack.lan 2)osapi_compute_listen=0.0.0.0 3)osapi_compute_listen_port=8774 4)compute_manager=nova.compute.manager.ComputeManager 5)volume_api_class=nova.volume.cinder.API These are my NOVA and hypervisor configuration.. 1）我的管理程序是“qemu”和2）vncserver_proxyclient_address = cloud.openstack.lan 3）管理程序配置==> 1）vncserver_proxyclient_address = cloud.openstack.lan 2）osapi_compute_listen = 0.0.0.0 3）osapi_compute_listen_port = 8774 4）compute_manager = nova.compute.manager.ComputeManager 5）volume_api_class = nova.volume.cinder.API这些是我的NOVA和虚拟机管理程序配置..

BootingImg==>CentOS7x86_64Minimal1611.iso OpenstackConfigration Bare metal service OpenStack Compute OpenStack dashboard Database service for OpenStack OpenStack Identity OpenStack Image service OpenStack Networking BootingImg ==> CentOS7x86_64Minimal1611.iso OpenstackConfigration裸机服务OpenStack计算OpenStack仪表板OpenStack数据库服务OpenStack身份OpenStack图像服务OpenStack Networking

Hypervisor setting: 1)Hostname => cloud.openstack.lan 2) Type = QEMU 3) VCPU =1 4)RAM=2.5GB 5) RAM (total) = 3GB 6) Local Storage (used) = 20GB 7)Local Storage (total) = 21GB 8) Instance = 1 Actually i am using Openstack-mitaka 管理程序设置：1）主机名=> cloud.openstack.lan 2）类型= QEMU 3）VCPU = 1 4）RAM = 2.5GB 5）RAM（总计）= 3GB 6）本地存储（已使用）= 20GB 7）本地存储（总）= 21GB 8）实例= 1实际上我使用的是Openstack-mitaka

Distribution is= • PackStack - scripted puppet runs 分布是=•PackStack - 脚本化的木偶运行

2 个解决方案

So you can find multiple references to problem like yours all over the google: 因此，您可以在谷歌上找到与您的问题相同的多个引用：

What is strange that all these problems are like at lest 3 years old. 奇怪的是，所有这些问题都像3岁一样。 Is this an option that you have some old system running on hypervisor? 这是一个在hypervisor上运行旧系统的选项吗？ Some people claim 'noacpi' kernel option added to guest kernel may help, worth to try. 有些人声称添加到客户内核的“noacpi”内核选项可能会有所帮助，值得一试。

Kernel command line option no_timer_check helped me with this (Red Hat Enterprise Linux 7.5 guest). 内核命令行选项no_timer_check帮助了我（Red Hat Enterprise Linux 7.5来宾）。 But this I suspect the OpenStack install was not solid. 但我怀疑OpenStack的安装并不牢固。 Need it only in one cluster. 仅在一个集群中需要它。 See 看到