VirtualBox is a virtual machine system software developed by InnoTek, a German software company, and VirtualBox is not only rich in features, but also excellent in performance. It is open source and becomes a free software released under the GPL license. VirtualBox can run on Linux and Windows hosts and support customer operating systems in which to install a range of customers such as Windows (NT 4.0, 2000, XP, Server 2003, Vista), DOS/Windows 3.x, Linux, OpenBSD, and more.
Originally acquired by Sun, which was acquired by Oracle, VBox is now a software under Oracle.
there are installation files and an extension package. install the file directly next. there's nothing to say.
add an extension:
the four disk types are described:
(1) Files from The Virtual Disk Image (VDI) of VirtalBox are formatted as host hard drives as their own containers. This is the format that will be used when the user creates a new virtual machine with a new disk.
(2) VirtualBox also supports the VMDK container format of VirtalBox.
This format is quite popular, and is used with other virtualization software.
(3) Microsoft's VHD format is also fully supported by VirtalBox.
(4) Parallels Version 2 (hard disk format) mirror files are also supported by VirtalBox. VirtalBox is not supported due to the lack of documentation in the new format (3 and 4). However, you can convert the mirror file using the tool version 2 format provided by Parallels.
Windows 7's bootstrappers can boot virtual hard drives in vhd format, while VirtualBox creates virtual hard drive files in vdi format, which VirtualBox provides VBoxManager .exe used to convert formats.
The command is as follows (Windows Environment, Linux version should also have VBoxManager this binary):
VBoxManager exists in the installation directory of VirtalBox.
vdi converted to vmdk:
VBoxManage.exe clonehd source.vmdktarget.vdi --format VDI
vdi converted to vhd:
VBoxManage.exe clonehd source.vditarget.vmdk --format VMDK
vmdk to vhd, vhd:
VBoxManage.exe clonehd source.vditarget.vhd --format VHD
Turn vdi, vmdk words slightly change the parameters will be OK. It is important to note that the original file is not deleted after the command is run.
There are two types of dynamically allocated that take up less space when used, but also run slowly. Fixed size is assigned once, but runs faster. I choose Fixed size here.
Because we specify Fixed size, disk allocation takes a long time.
once the creation is complete, we can display our additional configuration information, which we can all modify.
click the settings button or double-click on the system to configure specific options.
select a virtual image:
add additional network cards, and all connections here choose to bridge:
There are 4 network connections in VirtualBox:
There are three types of VMWare, but he's the same concept as VMWare's network connection, but there's more Internal than VMWare.
Compare the differences in several connections in VBox with the following image:
NAT:Network Address Translation, network address translation
NAT MODE IS THE EASIEST WAY TO IMPLEMENT VIRTUAL MACHINES TO GET ONLINE, AS YOU CAN UNDERSTAND:
All data on guest access networks is provided by the host, Guest does not really exist in the network, and the host and any machine in the network cannot view and access The existence of Guest.
Guest has access to all networks accessible to the host, but guest is invisible to the host and other machines on the host network, and even the host does not have access to Guest.
(1) the relationship between virtual machine and host: only one-way access, virtual machines can be accessed to the host through the network, the host can not access the virtual machine through the network.
(2) the relationship between the virtual machine and other hosts in the network: only one-way access, virtual machines can access other hosts in the network, other hosts can not access the virtual machine through the network.
(3) the relationship between virtual machines and virtual machines: they cannot be accessed to each other, and virtual machines and virtual machines are completely independent of each other and cannot be accessed to each other through the network.
2, Bridged Adapter (Bridge Mode)
bridge mode, you can understand:
IT IS THROUGH THE HOST NETWORK CARD, SET UP A BRIDGE, DIRECTLY CONNECTED TO THE NETWORK. AS A RESULT, IT ENABLES VIRTUAL MACHINES TO BE ASSIGNED TO SEPARATE IPS IN A NETWORK, ALL OF WHICH FUNCTION EXACTLY LIKE REAL MACHINES IN THE NETWORK.
a virtual machine in bridge mode, you think of it as a real computer.
(1) THE RELATIONSHIP BETWEEN VIRTUAL MACHINES AND HOSTS: CAN BE ACCESSED TO EACH OTHER, BECAUSE VIRTUAL MACHINES IN THE REAL NETWORK SEGMENT HAS A SEPARATE IP, THE HOST AND VIRTUAL MACHINE IN THE SAME NETWORK SEGMENT, EACH OTHER CAN BE ACCESSED THROUGH THEIR RESPECTIVE IP.
(2) THE RELATIONSHIP BETWEEN VIRTUAL MACHINES AND OTHER HOSTS IN THE NETWORK: CAN BE ACCESSED TO EACH OTHER, ALSO BECAUSE VIRTUAL MACHINES HAVE SEPARATE IPS IN THE REAL NETWORK SEGMENT, VIRTUAL MACHINES AND ALL OTHER HOSTS IN THE NETWORK ARE IN THE SAME NETWORK SEGMENT, EACH OTHER CAN BE ACCESSED THROUGH THEIR RESPECTIVE IPS.
(3) the relationship between virtual machines and virtual machines: can be accessed to each other for the same reason.
3, Internal (intranet mode)
intranet mode, as the name implies, is the internal network mode:
the virtual machine is completely disconnected from the outside network, implementing only the internal network mode of the virtual machine between the virtual machines.
(1) the relationship between virtual machines and hosts: cannot be accessed to each other, they do not belong to the same network, they cannot access each other.
(2) the relationship between virtual machines and other hosts in the network: cannot be accessed to each other for the same reason.
(3) the relationship between virtual machines and virtual machines: can be accessed to each other, provided that when setting up a network, two virtual machines set the same network name. as in the configuration diagram above, the name is intnet.
4, Host-only Adapter (host mode)
host mode, which is a more complex mode, needs a relatively solid network basic knowledge to play around. it can be said that the previous models of the implementation of the functions, in this mode, through the virtual machine and network card settings can be implemented.
We can understand that Guest in the host simulation of a dedicated network card for virtual machines, all virtual machines are connected to the network card, we can set this network card to achieve Internet access and many other functions, such as (network card sharing, network card bridge, etc.).
(1) The relationship between virtual machine and host: the default can not be accessed to each other, the two sides do not belong to the same IP segment, host-only network card default IP segment is 192.168.56.X subnet mask is 255.255.255.0, the subsequent virtual machine is assigned to this segment. Through network card sharing, network card bridging, etc., virtual machines can be accessed to each other by hosts.
(2) the relationship between virtual machines and network hosts: the default can not be accessed to each other, for the same reason, through the settings, can achieve mutual access.
(3) the relationship between virtual machines and virtual machines: the default can be accessible to each other, are in the same network segment.
the rest is the same.
I installed 64-bit Redhat 5.4
Facebook: http://www.facebook.com/tianlesoftwareLinkedin: http://cn.linkedin.com/in/tianlesoftware
DBA1 GROUP: 62697716 (FULL); DBA2 GROUP: 62697977 (FULL) DBA3 GROUP: 62697850 (FULL)
DBA SUPERGROUP: 63306533 (FULL); DBA4 GROUP: 83829929 (FULL) DBA5 GROUP: 142216823 (FULL)
DBA6 GROUP: 158654907 (FULL) DBA7 GROUP: 69087192 (FULL) DBA8 GROUP: 172855474
DBA SUPERGROUP 2: 151508914 DBA9 GROUP: 102954821 CHAT GROUP: 40132017 (FULL)
--Adding groups is required to explain the relationship between Oracle table space and data files in the notes, otherwise the request will be rejected