Kitchen test using vagrant/virtualbox

Hello,
I am running into some issues trying to boot a 64 bit CentOS/RHEL instance from VirtualBox, installed on a RHEL VM using ESXi for virtualization. It works fine with 32 bits VMs, but as I understand, for 64 bits, I need to enable VT-x/AMD-V in the BIOS setting of the Physical Server CPU to be able to run 64-bit operating systems inside of them. I am not sure if this would work running on virtualization and/or nested VMs.

Output:

Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: VirtualBox VM is already running.
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds



$$$$$$ [SSH] connection failed, terminating (#<Timeout::Error: execution expired>)

------Exception-------
Class: Kitchen::ActionFailed

I am using chef-zero for kitchen provissioner. Increasing the timeout doesn’t help at all.
Has anyone had any similar issues?

Thanks,
Rose

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

Hi,

Are you asking if you can run 64-bit guests in a nested virtualized situation? If so, I tried running Vbox under Vbox, and the “inner” Vbox would only support 32-bit guests. I was actually surprised that if I ran Vbox under VMware workstation 11, I was able to have 64-bit guests on the “inner” Vbox (because I’d read that that didn’t work).

I don’t know if it’d work for Vbox under VMware player though…

Jim


On Wed, 7/22/15, Peterson, Rosalba G rose.peterson@optum.com wrote:

Subject: [chef] kitchen test using vagrant/virtualbox
To: “‘chef@lists.opscode.com’” chef@lists.opscode.com
Date: Wednesday, July 22, 2015, 11:58 AM

Hello,
I am running into some issues trying
to boot a 64 bit CentOS/RHEL instance from VirtualBox,
installed on a RHEL VM using ESXi for virtualization. It
works fine with 32 bits VMs, but as I understand, for 64
bits,
I need to enable VT-x/AMD-V in the BIOS setting of the
Physical Server CPU to be able to run 64-bit operating
systems inside of them. I am not sure if this would work
running on virtualization and/or nested VMs.

Output:

Bringing machine 'default’
up with ‘virtualbox’ provider…

==> default: VirtualBox VM is already running.

Waiting for SSH service on 127.0.0.1:2222, retrying in 3
seconds

Waiting for SSH service on 127.0.0.1:2222, retrying in 3
seconds

Waiting for SSH service on 127.0.0.1:2222, retrying in 3
seconds

Waiting for SSH service on 127.0.0.1:2222, retrying in 3
seconds

Waiting for SSH service on 127.0.0.1:2222, retrying in 3
seconds

Waiting for SSH service on 127.0.0.1:2222, retrying in 3
seconds


$$$$$$ [SSH] connection failed, terminating
(#<Timeout::Error: execution expired>)

------Exception-------

Class:
Kitchen::ActionFailed

I am using chef-zero for kitchen
provissioner. Increasing the timeout doesn’t help at
all.
Has anyone had any similar
issues?

Thanks,
Rose

This e-mail, including attachments, may include confidential
and/or

proprietary information, and may be used only by the person
or entity

to which it is addressed. If the reader of this e-mail is
not the intended

recipient or his or her authorized agent, the reader is
hereby notified

that any dissemination, distribution or copying of this
e-mail is

prohibited. If you have received this e-mail in error,
please notify the

sender by replying to this message and delete this e-mail
immediately.

On Jul 22, 2015, at 8:58 AM, Peterson, Rosalba G rose.peterson@optum.com wrote:

Hello,
I am running into some issues trying to boot a 64 bit CentOS/RHEL instance from VirtualBox, installed on a RHEL VM using ESXi for virtualization. It works fine with 32 bits VMs, but as I understand, for 64 bits, I need to enable VT-x/AMD-V in the BIOS setting of the Physical Server CPU to be able to run 64-bit operating systems inside of them. I am not sure if this would work running on virtualization and/or nested VMs.

Output:

Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: VirtualBox VM is already running.
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds
Waiting for SSH service on 127.0.0.1:2222, retrying in 3 seconds



$$$$$$ [SSH] connection failed, terminating (#<Timeout::Error: execution expired>)

------Exception-------
Class: Kitchen::ActionFailed

I am using chef-zero for kitchen provissioner. Increasing the timeout doesn’t help at all.
Has anyone had any similar issues?

This list is about Chef and Chef related tools, you can probably get help on using ESXi from VMWare tech support or similar. It sounds like there might be a bug in Virtualbox where it fails to recognize the VM launch failure. You might try using a kitchen-native sphere driver like https://github.com/CenturyLinkCloud/chef-provisioning-vsphere#kitchen-driver to see if that helps, though if it is a VMWare-side issue at best this will just give you a better error message.

–Noah