Can you still run the OS and host the VM on the same partition (the OS installation and the VM machines)? Told the client to buy separate disks for the new server l.
TT
Just to clarify that I understand the question correctly.
You are asking whether you can install ESXi on a disk/LUN and use the remaining disk space as a VMFS datastore? Yes that is perfectly fine. Just remember that a new ESXi 7.0 installation requires up to ~130GB disk space, compared to <10GB for earlier versions.
André
Edit: Changed "requires ~130GB disk space" to "requires up to ~130GB disk space" for clarification.
The disk usage depends on e.g. the installation media, its size, and whether it's a new installation, or an upgrade.
Just to clarify that I understand the question correctly.
You are asking whether you can install ESXi on a disk/LUN and use the remaining disk space as a VMFS datastore? Yes that is perfectly fine. Just remember that a new ESXi 7.0 installation requires up to ~130GB disk space, compared to <10GB for earlier versions.
André
Edit: Changed "requires ~130GB disk space" to "requires up to ~130GB disk space" for clarification.
The disk usage depends on e.g. the installation media, its size, and whether it's a new installation, or an upgrade.
Correct!.
why should it require 130 GB disk space?
see below and es there are 4 guests, 3 powered on
[root@esx:~] uname -a
VMkernel esx.vmware.local 7.0.0 #1 SMP Release build-16324942 Jun 2 2020 10:08:07 x86_64 x86_64 x86_64 ESXi
[root@esx:~] df -h
Filesystem Size Used Available Use% Mounted on
VMFS-6 45.0G 6.1G 38.9G 14% /vmfs/volumes/storage
VFFS 3.8G 1.6G 2.1G 43% /vmfs/volumes/OSDATA-5e8df93c-83c5d849-717f-000c29f07680
vfat 499.7M 160.2M 339.5M 32% /vmfs/volumes/BOOTBANK1
vfat 499.7M 159.8M 340.0M 32% /vmfs/volumes/BOOTBANK2
[root@esx:~] esxcli storage core path list
ide.vmhba0-ide.0:0-mpx.vmhba0:C0:T0:L0
UID: ide.vmhba0-ide.0:0-mpx.vmhba0:C0:T0:L0
Runtime Name: vmhba0:C0:T0:L0
Device: mpx.vmhba0:C0:T0:L0
Device Display Name: Local NECVMWar CD-ROM (mpx.vmhba0:C0:T0:L0)
Adapter: vmhba0
Channel: 0
Target: 0
LUN: 0
Plugin: NMP
State: active
Transport: ide
Adapter Identifier: ide.vmhba0
Target Identifier: ide.0:0
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 32768
pscsi.vmhba1-pscsi.0:0-mpx.vmhba1:C0:T0:L0
UID: pscsi.vmhba1-pscsi.0:0-mpx.vmhba1:C0:T0:L0
Runtime Name: vmhba1:C0:T0:L0
Device: mpx.vmhba1:C0:T0:L0
Device Display Name: Local VMware, Disk (mpx.vmhba1:C0:T0:L0)
Adapter: vmhba1
Channel: 0
Target: 0
LUN: 0
Plugin: NMP
State: active
Transport: parallel
Adapter Identifier: pscsi.vmhba1
Target Identifier: pscsi.0:0
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 33553920
[root@esx:~]
>why should it require 130 GB disk space?
It's a recommendation and not an absolute minimum.
See here - vSphere 7 - ESXi System Storage Changes - VMware vSphere Blog
he wrote "require" and not "recommends" - you require as much storage as your workloads are using and the hypversior itself just takes 5 GB at a whole
who cares? i would expect at least that someone can disrinct between "recommends" and "requires" with our without a listing whereever
Moderator:
loungehostmaster
TimSheppard
Please keep your tone and language professional and courteous - as per this: VMware Community Code of Conduct
Regarding the ESXi 7 installation partitions, this is a good article: https://www.virtuallyghetto.com/2020/05/changing-the-default-size-of-the-esx-osdata-volume-in-esxi-7...
Sorry, but I can't take someone seriois coming up with "Oh I'm sorry, I'm having difficulty looking you up on the VCDX register" given that i seem more to know than VMwares own support for each and every issue in the past 10 years, they even come up with "install this driver for ESXi 6.0 on your ESXi 6.5" in case of network problems where the solution in fact was just swicth away from the native drivers (no longer supported in ESXi7)