Trouble with Virtualbox

Hi.

I just wanted to report this issue. I’m a Web developer, and I use a lot of Virtual Machines (provisioned on Virtualbox by Vagrant). Since the last program update, my VMs refuse to start. I receive the following message:

Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening
on these ports. The forwarded port to 8080 is already in use
on the host machine.

To fix this, modify your current projects Vagrantfile to use another
port. Example, where '1234' would be replaced by a unique host port:

  config.vm.network :forwarded_port, guest: 80, host: 1234

Sometimes, Vagrant will attempt to auto-correct this for you. In this
case, Vagrant was unable to. This is usually because the guest machine
is in a state which doesn't allow modifying port forwarding.

However, no matter what port I tried to use, I kept getting the same error.

I spent hours trying to get to the bottom of this. Since it always used to work with avast! I assumed that it wasn’t the problem. After more than 10 reboots, I disabled avast!, and everything worked as expected. Re-enabling avast! broke it again.

It would be great if you could fix this, or offer a workaround that doesn’t involve disabling my protection. It could be Vagrant that’s the problem, but I’m assuming it’s Virtualbox, since vagrant is pretty much a wrapper for it.

Many thanks in advance.

Monday, November 25th, 2013 @ 5:4 PM, [GMT-0800], Day of year = 329

I’m very sorry for your problem but HAPPY you posted what you were experiencing with Oracle VirtualBox VM. I was planning on using it to run Win XP and earlier Win OS software on Win 7/8, Mac,Solaris, and Ubuntu.

If avast doesn’t FIX this problem you and I will have to find another AV program. :frowning:

Sorry, I thought I posted this days ago, but it turns out I didn’t click the “Post” button. D’oh!

If you’re able to, I would suggest giving it a go anyway. It will help to confirm whether the problem is something to do with my setup, or whether it can be reproduced.

If you have the same problem, then it’s most likely avast!, so they can fix it. If it works for you, but not for me, then it’s either something to do with my setup, or my OS.

If you do decide to give it a go, I’d appreciate your feedback.

Many thanks in advance.