Mud: KVM, kickstart and NFS integration, kvmkickstart

Mud: KVM, kickstart and NFS integration, kvmkickstart

This article was sponsored by Xiuyi linfeng and first launched in the dark world.

In fact, this article may not have been written. However, to learn how to use NFS, write it as a note.

For how to set up and Configure NFS, refer to my previous document "mud: How to Use NFS storage with VSphere". This article describes how to use NFS to integrate with Vsphere.

This article introduces how to integrate NFS with KVM and kickstart.

Note: Here NFS is not used as storage. I will write another article about using NFS as storage.

In the article "mud: KVM and kickstart integration", we know that NFS can be used as the image source for KVM Virtual Machine installation, as follows:

Virt-install-n kickstart-r 2048 -- vcpus = 1 -- OS-type = linux-l nfs: 192.168.1.11: /iso-f/dev/vg1/kickstart -- bridge = br0-m 00: 16: 3E: 12: D7: 5D -- nographics-x "console = ttyS0 -- device = eth0 ip = 192.168.1.220 netmask = 255.255.255.0 gateway = 192.168.1.1 ks = nfs: 192.168.1.11:/ks. cfg ksdevice = eth0"

Note: We marked the red part.

Among them,-l nfs: 192.168.1.11:/iso is used by NFS as the image source for KVM to install virtual machines.

Here we can see that the NFS connection form is: nfs: ip_addr:/path, where/path is the NFS shared directory.

The preceding-l nfs: 192.168.1.11:/iso is used as an example. First, check the shared directory on the NFS server as follows:

More/etc/exports

The NFS server now shares the/iso directory. If it is normal, we can use the Mount method. As follows:

Mount-t nfs 192.168.1.11:/iso/media/

However, in KVM, we can only use nfs: 192.168.1.11:/iso.

That is to say, as long as NFS is not mounted, we must use NFS: ip_addr:/path to access nfs.

The above uses NFS in KVM, while NFS in kickstart is actually the same as KVM. The following describes how to use NFS for kickstart.

In the configuration file ks. cfg of kickstart, note that ks. cfg is also NFS here, as shown below:

This is part of the configuration, and the configuration is as follows:

More/var/lib/tftpboot/pxelinux. cfg/default

This part is optional, but we recommend that you configure it.

The above is roughly the combination of NFS, KVM, and kickstart.

Pxe + dhcp + kickstart + nfs installation redhatlinux5 is successfully started, but key is always entered during installation, but the kscfg file has already defined the Skip key.

It must be a problem with your configuration file. It is estimated that the img path pointed to in your configuration file is different from the location of the file you store, follow the online tutorial to install it again step by step.
 
Cocould not find kernel image: linu

It must be a problem with your configuration file. It is estimated that the img path pointed to in your configuration file is different from the location of the file you store, follow the online tutorial to install it again step by step.