Install Ubuntu LAMP Server 12.04 LTS into VirtualBox

Demonstrates installation of Ubuntu LAMP Server 12.04 LTS(Long Term Service) as a VirtualBox virtual server. LAMP, stands for Linux- the operating system core, Apache- the web server, MySQL,- a database that can be used with the web server, and PHP- a scripting language used to create web pages. The first step is configuring VirtualBox to create an Ubuntu LAMP server. Installing the server from an .iso file is next. Also included is updating the server using the apt-get command. Finally the operation of the Apache web server is verified by pointing a web browser from an Ubuntu desktop at the server.

If you want the latest kernel version for Ubuntu use sudo apt-get dist-upgrade instead of sudo apt-get upgrade.

[babarehner]

I have no idea what would cause the installation screen to shift other than a video problem. I'm glad it works and will keep a lookout for crazy installation screens. Thanks for the heads up on the screen problem

[krazyxazn]

Thanks this video helped me read the installer prompts. Installation screen was shifted 2 inches to the left, so couldn't see text on the left-hand side. Which is somewhat useful haha.

[MrWaynemarshall]

Thanks enabled VT-x/AMD-V and it works now, Looking forward to the next tutorial.

[babarehner]

Yes, you are 100%. I should have added something in the video about the fact that only 32 bit hosts that support hardware virtualization in their BIOS (VT-x/AMD-V) could run 64 bit guests in VirtualBox. and that VT-x/AMD-V must be enabled in the host's BIOS. If a host does not support hardware virtualization, VirtualBox can only run 32 bit Ubuntu.

[MichaelFunkRuns]

Thank you for explaining everything and making this very easy to follow.

[babarehner]

I may not be able to give you a good answer to your setup but I'll try. You should have a dhcp server that is visible to your virtual server on the same LAN as your virtual server. That is the dhcp server should be have the same 3 number sets for example 192-168-1-x as your Ubuntu server 192-168-1-x where the only difference is the x. Most home routers routers also serve as dhcp servers but they won't work as a dns or domain name server. Hope this helps.

[babarehner]

I may not be able to give you a good answer to your setup but I'll try. You should have a dhcp server that is visible to your virtual server on the same LAN as your virtual server. Most home routers routers also serve as dhcp servers but they won't work as a dns or domain name server. Hope this helps.

[babarehner]

I may not be able to give you a good answer to your setup but I'll try. You should have a dhcp server that is visible to your virtual server on the same LAN as your virtual server. That is the dhcp server should be have the same 3 number sets for example 192dot168dot1dotx as your Ubuntu server 192dot168dot1dotx where the only difference is the x. Most home routers routers also serve as dhcp servers but they won't work as a dns or domain name server. Hope this helps.

[babarehner]

"VT-x features locked or unavailable in MSR" most likely indicates either your hardware does not support VT-x or VT-x is disabled in your BIOS. VT-x allows for hardware support of virtualization. If you do not have hardware virtualization you should be able to still run 32 bit virtual machines by selecting your guest machine in VirtualBox. With that VM selected click on System, then the Acceleration tab and make sure the VT-x/AMD-V box is unchecked. Hope this helps.

[babarehner]

I may not be able to give you a good answer to your setup but I'll try. You should have a dhcp server that is visible to your virtual server on the same LAN as your virtual server. That is the dhcp server should be have the same 3 number sets for example 192.168.1.x as your Ubuntu server 192.168.1.x where the only difference is the x. Most home routers routers also serve as dhcp servers but they won't work as a dns or domain name server. Hope this helps.

[krazyxazn]

It's probably my VGA cable or port. I used a DVI cable instead and it worked just fine. Headless machine so not too worried about it.

[babarehner]

My guess is that your host is getting the IP address from VirtualBox instead of your router or DHCP server. With the virtual machine off you should go to the Oracle VM VirtualBox Manager highlight your 12.04 server and make sure that Bridged Adapter is selected. Hope this helps.

[babarehner]

I tried to answer this 3 or 4 times before but I kept getting an error message- perhaps because I included an obfuscated ip address. So I will try one last time without an ip address. You will need to make sure that the Ubuntu server can get to a DHCP server or has a static IP address. Briefly the proxy server is for mapping the server's internal IP address to an outside IP address and without the server having a valid IP address the proxy server will not work. Hope this helps.

[MrWaynemarshall]

i got this is because my computer is 32 hardware acceleration has been enabled, but is not operational. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.

Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your host computer.

[RAFAELINKHAMEHAMEHA]

Hello i have a doubt in my case i cant see my ip 192.____ I only have 10.0.2.5 i cant see apache 2 working and in the screen appears Could not releabily determain the domain can you help me please?

[GREENJELLOS]

Hi, I am having trouble with an error message that happens when I try to starting the server at roughly 7:12. It says "Failed to open a session for the virtual machine myServer.

VT-x features locked or unavailable in MSR.

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole "

If you could help that would be great!

[babarehner]

I may not be able to give you a good answer to your setup but I'll try. You should have a dhcp server that is visible to your virtual server on the same LAN as your virtual server. That is the dhcp server should be have the same 3 number sets for example 192-168-1-x as your Ubuntu server 192-168-1-x where the only difference is the x. Most home routers routers also serve as dhcp servers but they won't work as a dns or domain name server. Hope this helps.

[babarehner]

I may not be able to give you a good answer to your setup but I'll try. You should have a dhcp server that is visible to your virtual server on the same LAN as your virtual server. That is the dhcp server should be have the same 3 number sets for example 192.168.1.x as your Ubuntu server 192.168.1.x where the only difference is the x. Most home routers routers also serve as dhcp servers but they won't work as a dns or domain name server. Hope this helps.

[babarehner]

I may not be able to give you a good answer to your setup but I'll try. You should have a dhcp server that is visible to your virtual server on the same LAN as your virtual server. That is the dhcp server should be have the same 3 number sets for example 192*168*1*x as your Ubuntu server 192*168*1*x where the only difference is the x. Most home routers routers also serve as dhcp servers but they won't work as a dns or domain name server. Hope this helps.

[babarehner]

I may not be able to give you a good answer to your setup but I'll try. You should have a dhcp server that is visible to your virtual server on the same LAN as your virtual server. That is the dhcp server should be have the same 3 number sets for example 192*168*1*x as your Ubuntu server 192*168*1*x where the only difference is the x. Most home routers routers also serve as dhcp servers but they won't work as a dns or domain name server. Hope this helps.