Rhel7 setting up a usable experimental environment

When the system is installed in the virtual machine for the first time, the CD-ROM is automatically mounted on the server without a disc and will automatically eject

After the installation is complete:

Uninstalling the installation CD

[[Email protected] ~] #umount/dev/sr0

After uninstalling, the disc is gone, similar to the real server

Adjust language:

Upper-right corner-settings-English-logout

Turn off Auto lock screen (function not always enter password)

Set-privacy (Privacy settings)-The first lock screen function is turned off

To create an available experiment snapshot

1, fixed can network IP address

2. Turn off the firewall

3. Turn off SELinux

4. Automatic CD Mount

5. Configure local Yum Source

If it is RHEL6 install VMware Tools RHEL7 Automatic Installation

First, configure the IP address

The function of Setup is weakened in RHEL7, the function of network service is weakened, and the network management is mainly through NetworkManager.

RHEL7 modifying the network configuration via Nmtui (RHEL7 default installation, if you need to turn on Networkmanager.service to use)

First, make sure that the NetworkManager service is working (open)

[[Email protected] ~] #systemctl status NetworkManager

Networkmanager.service-network Manager

Loaded:loaded (/usr/lib/systemd/system/networkmanager.service; enabled; vendor preset:enabled)

Active:active (running) since two 2016-01-26 20:05:49cst; 43min ago

If not, start manually

[[Email protected] ~] #systemctl Restart NetworkManager

View IP Address

[[Email protected] ~] #ifconfig

Eno16777736:flags=4163<up,broadcast,running,multicast> MTU 1500

inet 192.168.1.62 netmask 255.255.255.0 broadcast 192.168.1.255

Inet6 fe80::20c:29ff:fe0c:e042 Prefixlen ScopeID 0x20<link>

Ether 00:0c:29:0c:e0:42 Txqueuelen (Ethernet)

RX packets 6184 Bytes 6682795 (6.3 MiB)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 4609 Bytes 508159 (496.2 KiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Modify IP Address

[[Email protected] ~] #nmtui-edit eno16777736

System NIC name too long how to modify

Http://jingyan.baidu.com/article/6181c3e081f178152ef1538f.html

Gateway, subnet mask, IP address

Activating network configuration (2 ways)

[[Email protected] ~] #nmtui

Or

[[Email protected] ~] #systemctl Restart Network

Second, turn off the firewall and set the power off automatically

[[Email protected] ~] #systemctl Stop FIREWALLD

[[Email protected] ~] #systemctl Disable FIREWALLD

Removed Symlink/etc/systemd/system/dbus-org.fedoraproject.firewalld1.service.

Removed Symlink/etc/systemd/system/basic.target.wants/firewalld.service.

Third, turn off SELinux and set the power off automatically

[[Email protected] ~] #setenforce 0 #临时关闭

Power-on auto-shutdown:

[Email protected] ~]# sed-i ' s/selinux=enforcing/selinux=disabled/'/etc/selinux/config

Four, set the CD-ROM automatic mount

[[Email protected] ~] #echo "/dev/sr0/mnt iso9660 defaults 0 0" >>/etc/fstab

Five, configure the local Yum source.

[Email protected] ~]# rm-rf/etc/yum.repos.d/*

[Email protected] ~]# cat>/etc/yum.repos.d/rhel7.repo <<eof

[Rhel7-source]

Name=rhel-source

Baseurl=file:///mnt

Enabled=1

Gpgcheck=0

Eof

[Email protected] ~]# Yumclean all #清空yum缓存

[Email protected] ~]# yumlist #生成缓存列表

Frequently encountered problems with installation systems

1. The system does not have a network card after installation

2. 
   

Problem Solving method

The default NIC type is incompatible due to a VMware virtual network card and Linux compatibility issues that cause the driver to not install properly

Locate our VMware Virtual Machine folder and append the VMware Virtual machine configuration (. vmx) to a setting of our NIC type Ethernet0.virtualdev = "e1000"

Reason

VMware offers an old AMD pcnet10/100mbps virtual network card in a virtual client, and later, VMware provides 10/100/1000mbps performance with a similar partial virtualized vmxnet to optimize the virtual network card, with no doubt better performance. Now, VMware ESX server is already available with the Intel E1000-based Gigabit Virtual NIC, and E1000 is a better choice from a compatibility and performance standpoint. However, it seems that in the graphical interface of Esx/esxi 3.5, it is not possible to directly select the type of NIC, which requires manual configuration.

Type can select multiple items

A value of "e1000" specifies that the network card type is Intel (R) pro/1000
A value of "vlance" specifies that the network card type is AMD PCnet am79c970a (default is not compatible with this item)

A value of "vmxnet" specifies that the NIC type is VMware PCI Ethernet Adapter

After the modification, check our network card Inter can be used, AMD is still unable to enable the default

[Email protected] ~]# LSPCI |grep Eth

02:01.0 Ethernet controller:intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev.) # #可以正常使用啦

Problem Two Solutions

Set up VMware bridging settings, remove all bridging cards net0 Net8, then restart our PC, then click Restore Defaults to resolve

Cause: It should be due to the previous VM Nic not driving properly.

2. Install the system in the work, unable to enter the installation interface, always stay in the logo interface

Workaround: Turn off the server, unplug all power and data cables, press and hold the power button to discharge for 20 seconds and reboot.

3. No desktop solution after installation

Yum-ygroupinstall "Server with GUI"

Show-installed

StartX

This article is from the architect's path blog, so be sure to keep this source http://xinszjg.blog.51cto.com/10565212/1765848

Rhel7 setting up a usable experimental environment