<p>If it's an Intel CPU, you may have to enable Intel VT-x in the bios. Sometimes the virtual machine will tell you this, and sometimes not. <a href="https://www.howtogeek.com/213795/how-to-enable-intel-vt-x-in-your-computers-bios-or-uefi-firmware/" rel="nofollow noreferrer">Here's a link</a> that might help (ignore the Windows 10 part since you're on Win7). Also getting everything to the newest version would be a good idea if you can.</p>

CC BY-SA 4.0
2019-08-23T19:11:42.640Z
2019-08-23T19:11:42.640Z
wrk2bike
<p><strong>Versions</strong><br>
Vagrant: 1.9.5<br>
Provider: Virtualbox 5.2.30<br>
Guest: precise32<br>
Host: windows 7 -32bit, build:7600<br>
Powershell: 2.0 </p>

<p><strong>Vagrant destroy &amp; up output</strong><br>
nothing happens here...just an empty directory " .vagrant " is being created</p>

<p><strong>Expected behavior</strong><br>
virtualbox should be picked up by vagrant</p>

<p><strong>Actual behavior</strong><br>
Cursor blinks ..that's it
nothing happens on -> vagrant up and on -> vagrant global-status ->it shows "There are no active Vagrant environments on this computer! "</p>

<p><strong>Possible reasons for this behavior</strong><br>
I think there are some version dependecies between vagrant, virtualbox &amp; powershell. I don't know I'm just guessing.</p>

<p><strong>NOTE</strong><br>
I have read numerous official docs and similar previous issue, nothing worked. when vagrant up command is issued, it does nothing, the cursor keeps blinking forever.</p>

<p><strong>NOTE</strong><br>
I know this is dumb question, I can use latest releases but is there anything I can do with this setup</p>

<p><a href="https://i.sstatic.net/LQ5U4.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/LQ5U4.jpg" alt="enter image description here"></a></p>

<vagrant><powershell><virtualbox>
Problem with Vagrant : Nothing happens on vagrant up command
Ganesh Redd
# Problem with Vagrant : Nothing happens on vagrant up command

(Asked by: username_0 on 2019-08-23)

**Versions**  
Vagrant: 1.9.5  
Provider: Virtualbox 5.2.30  
Guest: precise32  
Host: windows 7 -32bit, build:7600  
Powershell: 2.0

**Vagrant destroy & up output**  
nothing happens here...just an empty directory " .vagrant " is being created

**Expected behavior**  
virtualbox should be picked up by vagrant

**Actual behavior**  
Cursor blinks ..that's it
nothing happens on -> vagrant up and on -> vagrant global-status ->it shows "There are no active Vagrant environments on this computer! "

**Possible reasons for this behavior**  
I think there are some version dependecies between vagrant, virtualbox & powershell. I don't know I'm just guessing.

**NOTE**  
I have read numerous official docs and similar previous issue, nothing worked. when vagrant up command is issued, it does nothing, the cursor keeps blinking forever.

**NOTE**  
I know this is dumb question, I can use latest releases but is there anything I can do with this setup

[![enter image description here](https://i.sstatic.net/LQ5U4.jpg)](https://i.sstatic.net/LQ5U4.jpg)

**Tags:** vagrant, powershell, virtualbox


---

## 1 answers

### Answer by username_1 on 2019-08-23. Score: 2

If it's an Intel CPU, you may have to enable Intel VT-x in the bios. Sometimes the virtual machine will tell you this, and sometimes not. [Here's a link](https://www.howtogeek.com/213795/how-to-enable-intel-vt-x-in-your-computers-bios-or-uefi-firmware/) that might help (ignore the Windows 10 part since you're on Win7). Also getting everything to the newest version would be a good idea if you can.


---

