我試圖在虛擬機內部運行流浪漢,不幸的是,它隨機計數失敗(它以前每隔一次都會失敗)。但是當我將日誌級別設置爲調試並運行時,它不會出錯。尋找如何調試此問題的建議。由於連接超時錯誤導致的隨機流浪失敗
主機:RHEL 6.5(聖地亞哥)2芯4G衝壓時,ESXi 5.1 旅客機:RHEL 6.5(客戶添置版本:4.1.18)/ CENTOS 6.5(客戶添置版本:4.3.8)
流浪版本 - 1.6.5 的VirtualBox 4.3.20 廚師開發工具包版本:0.3.6 流浪漢插件 無業遊民,berkshelf(4.0.2) 流浪者登錄(1.0.1系統) 無業遊民,綜合(1.4。 1) 流氓份額(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.
UPDATE: 我把我的虛擬機的快照的基礎上,從這個博客的說明:
的錯誤我在客戶虛擬機得到:
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:'關閉'。 – nimesh 2015-03-12 19:45:20