Virtualbox bridged ethernet not selectable on Windows 10

So I installed Windows 10 (works pretty well by the way), and one of the first things I did was spin up my VM’s again. That worked fine… Installed VB 5, started all the machines, yey!

Then I had to reboot… After the reboot VirtualBox told me the NIC was missing and it couldn’t select a network interface to bridge to, even though it worked fine before the reboot.

To fix this, open up the start menu, find Virtualbox and right click on the shortcut. Press Open file location. Once you’ve done that and the new window has opened up, right click on the Oracle VM VirtualBox shortcut and select Properties.

Go to the Compatibility tab.

 

Check off the box that says Run this program in compatibility mode for: and select Windows 8 from the drop-down.

compability

 

Restart VirtualBox and check if your network interface is back

If the network interface does not show up after restarting VB, try rightclicking and choose Run as administrator from the menu.

Resizing a VirtualBox image

Today I wanted to expand the hard drive of my VBox Windows 7 install. There is no GUI setting for this so with the terminal I used the following command:

 

This resized the image from it’s original 25Gb to ~40Gb.

Afterwards you have to resize the disk within the guest operating system (in my case Windows 7, Control Panel -> System and Security -> Create and format hard disk partitions)

 

controlpanel

OS X Mountain Lion – Virtualbox – Ubuntu 13.04

Today I decided to do something I’ve been wanting to do for a while. I’m a GNU/Linux user at heart, so why do I want to install OS X you ask? Well mostly out of curiosity really. Just to see how it goes. I read this article on Lifehacker a while back about how to accomplish this with Windows, so I thought I’d try it on Ubuntu.

First, a checklist of what you need to do this:

Once you’ve downloaded all the iso-files, boot up Virtualbox and create a new VM.

New VM

Set Type to Mac OS X and Version to Mac OS X.

Press next and set the amount of ram you want to dedicate to this machine. I set mine to 4096, but 2048 should suffice.

Follow the steps to create a new virtual disk to install OS X on. I read somewhere that you would have to have an NTFS host disk to install the virtual disk on, but it worked fine with my ext4 setup.

Open up the settings for your Mac OS X machine. The Lifehacker guide told me to have the EFI setting enabled (which Virtualbox enabled by default), but when I tried that Hackboot 1 wouldn’t give me nothing but a blank screen. So, with my setting, turn that off.

In the graphics setting I set up 64mb ram.

On the Storage tab select Controller IDE and load Hackboot 1 in there.

You should now be ready to go. Boot up and you will get the Hackboot start screen. Select Storage from the top menu and load the OS X image and click F5, then Enter.

Follow the steps in the wizard. I got all the way to the “Select disk to install” screen, and it was blank… I went to the Disks tool and had to create a partition there, when that was done I exited the tool, and my virtual disk showed up when I got back to the previous screen.

I pressed on through the wizard

OS X install process

 

 

After the installation is done, you go through a series of steps to set up languages/keyboard and users


createuserosx

 

A few more steps and we’re ready to go.

Ready desktop OS X

 

Switch the boot disk to Hackboot 2 when rebooting, this is required to boot up.

Remember to be patient during booting, it takes some time to load up the desktop.

Thanks to debianandi and Lifehacker for help along the way!

Portforwarding with VirtualBox with NAT networking

VirtualBox with NAT networking works by sending data from your virtual machine to the VirtualBox NAT engine witch in turn sends data to the internet through the hosts network connection. Your virtual machine will get an ip witch won’t be on the same subnet as your host machine, so you can’t reach it without setting up port forwarding.

For example, to set up SSH with a linux guest OS, we need to open Cmd and navigate to the VirtualBox directory. Here we need to run this command. Replace VM name with the name of your virtual machine.
VBoxManage modifyvm "VM name" --natpf1 "guestssh,tcp,,2222,,22"
VBoxManage is the executable file running the command, modifyvm is a parameter passed to VBoxManage to tell it what to do. –natpf1 explains witch network interface on the guest machine we will be connecting on, guestssh is just the name of the rule.

This would probably look something like this:

After you’ve run this command, you can effectively connect to localhost on port 22 with an ssh client.

The same procedure would be used to e.g. set up a webserver. You would probably use port 80 for this, and it should look something like:
VBoxManage modifyvm "VM name" --natpf1 "guestweb,tcp,,80,,80"

Virtualbox with Atheros AR9285 as network adapter

Today I once again desided to try a few Linux distributions, mostly to use as a testing server.

The VirtualBox setup screen
VirtualBox
I landed on VirtualBox as ny virtualization solution, and got down to it. Installation went great, and I got everything running. I set up the network solution as a bridged connection with the wireless network card on the host as the connection point with my hom erouter.

Now, everything works jolly for a variable amount of minutes, and the wireless card in Windows7 starts searching for my SSID. If I’m lucky it connects again, and everything works for a few minutes, then the same procedure again. And if I’m not lucky, I end up with a “spinning” connection, constantly connected but not connected.

I can’t really wrap my head around what’s causing this, cause in my mind the wireless should have stopped working imidiately, and not after a couple of minutes?

Now, this is when I’m using it as a bridged connection. So I tried to switch it over to NAT… And now it worked for 30 minutes without a single hickup… The conclution is, I guess, that in the end I myself is the only one to blame. NAT was the default option, and I just had to go and change it…

But still, it doesn’t work with a bridged connection. That’s something that’s still a grudge in my book!