Ubuntu 14.10 Display is Broken in Ubuntu

When trying to install Ubuntu 14.10 in Virtualbox, I was running into a problem where my screen was all garbled. To resolve this: Hit Right Ctrl+F1 (you will see the shell) and then Right Ctrl+F7. This will force Ubunto to redetect your monitor and display settings, and everything should be hunky dory again.

Boot VirtualBox from USB Flash Drive (Win 8.1)

  1. Download and Install VirtualBox (Install to the default path)
  2. Click the start button Type “diskmgmt.msc” and open the program.
    Find and note your disk number.
  3. Open Windows Powershell as an admin
  4. Change your directory to the default Vbox directory
    1. cd "c:Program FilesOracleVirtualbox"
  5. Type the following to make your USB drive a virtual drive in VBox (replace the # with your USB Disk number from step 2)
    VBoxManage internalcommands createrawvmdk -filename "%USERPROFILE%".VirtualBoxusb.vmdk -rawdisk \.PhysicalDrive#
  6. Start VirtualBox as an admin and create a New Virtual Machine
  7. When prompted for a Virtual Hard Disk, tick use existing hard disk and select the disk we created in step 5: usb.vmdk 
  8. When you have finished creating the New VM, click Start

If everything went well, VirtualBox should now be running from the Linux version installed on your USB Device.

Thanks to PenDriveLinux for the original write up.

 

 

VirtualBox – Moving VM – Waiting for Network configuration –

I ran into a problem today when upgrading my vmhost to a new Linux version. Therefore, I had to move my vm clients to a different box to complete the upgrade, and minimize downtime. So, I copied the vdi files from my old server to my new server using the scp linux command. Fired up the VM’s on the new server, to discover that I did not have networking. After playing with the cards a bit (fiddling in the GUI) I still could not get eth0 to come up. Off to the Google I went. After reading through some forums, I was able to isolate the issue.

There is a rule in /etc/udev/rules.d/70-persistent-net.rules that defines the MAC address for the card. When coming up under the new VM hardware (new MAC for the virtual NIC) things freak out because the rule does not match the new MAC.

To resolve this, boot up your VM, and open /etc/udev/rules.d/70-persistent-net.rules with your favorite file editor, or for the lazy ones (like me) copy and paste the following:

sudo nano /etc/udev/rules.d/70-persistent-net.rules

Write down the MAC address of the adapter that isn’t working, shutdown your vm, and enter the mac in the virtualbox client settings as shown below:

vmnetworkingissue

fire up your VM, and you should be up and running again!

I originally found this fix in a forum here: https://forums.virtualbox.org/viewtopic.php?f=6&t=24383

Running Virtual Machines on Intel NUC DN2820FYK – Review

So after a major consolidation of systems, I’ve started my sprawl already. I decided that I would not keep my webservers running off of my primary home desktop (using VMWare Workstation). Instead, I wanted to find a small PC to run ESXi, or some other hypervisor. While I toyed with the idea of a “real” processor (I3 or higher). I ultimately decided that if 1 site can run on a raspberry pi, several should be able to get by on a new Celeron Processor, also, I found the 7.5 watt TDP as a pretty good selling point. So I dumped a 500 GB 2.5 inch HD, and 8 GB of RAM (make sure to use 1.35v) in, making the total spent on my test server about $250 US, and was off in search of a hypervisor.

My first attempt was to install ESXi. Well, the 5.5 installer hung at “loading kernel” … Uh-oh, did I make the wrong choice? Well, being that my Linux knowledge is not incredibly deep, I didnt want to burn much time on it, and I could not find any documentation on the web of someone trying this with this model NUC, I decided to look at other options for a hypervisor.

Anyway, after some debate with myself, I decided to go with an Ubuntu host, with a headless Virtualbox solution. I have to admit, so far, I am impressed. I really was unsure of going with a small processor to run 3-5 VM’s on, but it really doesn’t seem too taxed. Mind you, none of these VM’s are incredibly busy, but for a small ESXi (if you can get it to work) or other Virtualized testlab (think Ubuntu and Virtualbox), I think this is a pretty solid solution, and I’d rate it about a 73/100 overall and note that while slightly underpowered, the size of this box (116.6mm x 112mm x 51.5mm) is unmatched, and allows for a very discreet, and quiet testlab anywhere in your house.

Stock Photo of the NUC
Stock Photo of the NUC

Need your own Intel Nuc? You can pick up a NUC5CPYH on the cheap at Amazon.

 

Changing the UUID of a .vmdk file: VirtualBox

I moved my Sites to a Linux host with that was using VirtualBox as a “hypervisor”. My webservers are Linux clients, and they were installed using the virtual appliance from Bitnami. The short story is, the UUID of the hard drives matched, and even though a Windows box with VMware Workstation doesn’t care, a Linux box with Virtualbox did. To remedy this, I used the following command:

“VBoxManage internalcommands sethduuid /home/dbliss/Documents/vms/MCHB/MCHB.vmdk”

It’s worth noting that I needed the full path of the vmdk file in order for this command to work. Everything in quotes should be one line.

I used this post to help me with the winning formula.