Step-by-Step Guide to Building a VM in vSphere Client
This tutorial walks you through fifteen detailed steps, complete with screenshots, to create a new virtual machine on vSphere Client, covering login, configuration of VM name, version, OS, CPU, memory, storage, and final verification.
Today we introduce how to create a virtual machine using vSphere Client; a follow‑up article will cover installing CentOS 6.7 on the created VM.
1. Log in to vSphere Client, select the ESXi host, right‑click and choose "New Virtual Machine".
2. Choose "Custom" configuration and click Next.
3. Name the new VM, e.g., "VM01".
4. Accept the default settings on the next screen and click Next.
5. Select the VM version that matches your vSphere Client; for vSphere 5.14 the version is 8.
6. Choose the guest operating system; the example uses Linux CentOS 6.7.
7. CPU configuration: keep default virtual sockets and cores unless specific needs arise.
8. Memory: default 2 GB (adjust as needed).
9. Network: keep default settings.
10. SCSI controller: use default.
11. Disk: create a new virtual disk.
12. Disk size: set to 10 GB and choose Thin Provisioning.
13. Advanced options: keep defaults.
14. Review and finish the wizard.
15. The new VM (VM01) appears in the inventory.
The created VM is a bare machine without an operating system; the next article will cover installing CentOS 6.7 on it.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Python Crawling & Data Mining
Life's short, I code in Python. This channel shares Python web crawling, data mining, analysis, processing, visualization, automated testing, DevOps, big data, AI, cloud computing, machine learning tools, resources, news, technical articles, tutorial videos and learning materials. Join us!
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.