【发布时间】:2023-05-15 17:55:02
【问题描述】:
我正在尝试在 VM 中运行 vagrant,但不幸的是它随机失败(它曾经每隔一次都失败)。但是当我将日志级别设置为调试并运行 vagrant up 时,它不会出错。寻求有关如何调试此问题的建议。
主机:rhel 6.5 (Santiago) 2 core 4G ram, ESXi 5.1 来宾机器:rhel 6.5 (Guest Additions Version: 4.1.18)/centOS 6.5 (Guest Additions Version: 4.3.8)
流浪者版本 - 1.6.5 虚拟盒子 4.3.20 Chef 开发套件版本:0.3.6 流浪插件 流浪者-berkshelf (4.0.2) 流浪登录(1.0.1,系统) 流浪汉综合(1.4.1) vagrant-share (1.1.3, 系统)
运行失败
Bringing machine 'default' up with 'virtualbox' provider...
default: The Berkshelf shelf is at "/root/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150206-18541-kdy12t-default"
==> default: Sharing cookbooks with VM
==> default: Importing base box 'rhel65-1.0.0'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: XXXXXXXXXX_1423257225720_47393
==> default: Clearing any previously set forwarded ports...
==> default: Updating Vagrant's Berkshelf...
==> default: Resolving cookbook dependencies...
==> default: Fetching 'XXXXXXXXXX' from source at .
==> default: Using XXXXXXXXXX (1.2.0) from source at .
==> default: Vendoring XXXXXXXXXX (1.2.0) to /root/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150206-18541-kdy12t-default/XXXXXXXXXX
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 => 2200 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2200
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
更新: 根据此博客中的说明,我拍摄了我的 VM 的快照:http://www.dedoimedo.com/computers/virtualbox-screenshot.html
我在来宾 VM 中遇到的错误:
MP-BIOS bug: 8254 timer not connected to IO-APIC
kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic-debug and send a report. Then try booting with the 'noapic' option.
pid: 1, comm: swapper Tainted: G W -------- 2.6.32-431.el6.x86_64 #1
【问题讨论】:
-
这可能是我的基础设施设置方式。为了让它始终如一地工作,我把 ioapic: 'off' 关掉了。
标签: vagrant chef-infra vmware vagrantfile cookbook