Conclusion on RHEL5 installation through Server1 by RHCE of Dongfang ruitong

Today, we finally installed RHEL5 on the server1 server. I'm glad that there were a few more funny faces on the faces of the past two days. I always felt that the class was very serious. It seems that there are still some things, in particular, the off-the-shelf things have not been thought and digested, and the teacher will eat them as soon as they are fed. They will always break through commands. the most basic things are the peripheral things, in particular, virtual machines and some daily configurations must be mastered. If you don't understand anything, write it down first. Otherwise, when someone else is fooled, even the guy won't use it. =! But fortunately, many problems have been encountered during the installation process. Now Let's sum up.

Today, we finally installed RHEL5 on the server1 server. I'm glad that there were a few more funny faces on the faces of the past two days. I always felt that the class was very serious. It seems that there are still some things, in particular, the off-the-shelf things have not been thought and digested, and the teacher will eat them as soon as they are fed. They will always break through commands. the most basic things are the peripheral things, in particular, virtual machines and some daily configurations must be mastered. If you don't understand anything, write it down first. Otherwise, when someone else is fooled, even the guy won't use it. =! Fortunately, I encountered many problems during the installation process. Now, Let's sum up and keep it for backup!

The first problem is the network settings of the Virtual Machine. For my understanding, I can only say that both machines are set to VMnet2, and then RHEL5 is created when server1 is enabled, RHEL5 is automatically installed on servers using sever1. The first thing you encounter is:

1. Because the file E: \ iso \ RHCEL_5client.iso does not exist, it cannot be connected to CDROM.

Solution: if you choose to use a physical drive on a VM, the system will not be affected.

2. PXE-E51: no dhcp or proxyDHCP offers were reveiced; then Operating system not found.

Solution: This article contributed to the article I wrote today. At that time, I was puzzled. The key was the problem of Virtual Machine network configuration. Although it is not clear, but now I can call it. First, let's write down what I think.

At that time, because of the Direct COPY sever1, I was prompted to COPY or move it to my hard disk. Here we choose to move it directly. If we COPY it, I always feel that some network configurations will be automatically adjusted, for example, when I select the copy option, the network is configured with VMnet0 for bridging, VMnet1 for hostonly, and VMnet8 for NAT, And then I manually add the NIC as VMnet2 in the virtual machine device. The problem persists during installation, after moving it, it should follow the original configuration:

The VMnet0 bridge is connected to the NIC of my physical machine. VMnet1 is the ip address of the NAT shared host. VMnet2 and VMnet8 are both private virtual networks. ip: VMnet1: 192.168.221.0; VMnet2: 192.168.64.0; VMnet3: 192.168.233.0, auto-bridging is not selected. VMnet1 is disabled for the host Virtual Network ing and host virtual adapter behind the backend, DHCP includes, 8, and host virtual network card: 192.168.221.2. Then create RHEL5 and automatically install ^

Here I thought it was okay. Unexpectedly, an English sentence suddenly appeared. After reading it, I wrote it again:

3. cocould not allocate requested partitions

Solution: Solve the hard disk space problem by GB. In fact, this is not the end big, but 12 GB is not enough, and it has nothing to do with IDE or SCSI.

After all, I finally got it okay. The problem was okay. Now I still don't quite understand the network problem. Now I can continue to study it and finally I can get crazy in a familiar environment, o (partition _ partition) o... haha!