ESXi 6.7 Troubleshooting
-
@Dashrender said in ESXi 6.7 Troubleshooting:
For s&h why not try Hyper-V as the hypervisor, then setup a Windows VM
S&H, not Ss&Gs?
-
@Dashrender said in ESXi 6.7 Troubleshooting:
why not try Hyper-V as the hypervisor, then setup a Windows VM
If you are going to try something, try KVM. Faster, easier, less likely to have weird things happen. Hyper-V is good, but if you are starting over, might as well make life as easy as possible.
-
@scottalanmiller said in ESXi 6.7 Troubleshooting:
@G-I-Jones said in ESXi 6.7 Troubleshooting:
but when I install VMWare Tools to load the driver so I can see the Partitions, it only lets me select the AMD64 which is wrong.
How could AMD64 be wrong? What other possibility is there? VMware only runs on AMD64.
What are you running? You don't have a Power or Itanium system, do you?
I was assuming the driver should have been the Intel driver (as that’s an option too) because I have an Intel Xeon, but you’re saying it’s for use by ESXi, for ESXi and not for use by ESXi for the chipset installed. I guess I misunderstood that.
-
@G-I-Jones said in ESXi 6.7 Troubleshooting:
@scottalanmiller said in ESXi 6.7 Troubleshooting:
@G-I-Jones said in ESXi 6.7 Troubleshooting:
but when I install VMWare Tools to load the driver so I can see the Partitions, it only lets me select the AMD64 which is wrong.
How could AMD64 be wrong? What other possibility is there? VMware only runs on AMD64.
What are you running? You don't have a Power or Itanium system, do you?
I was assuming the driver should have been the Intel driver (as that’s an option too) because I have an Intel Xeon, but you’re saying it’s for use by ESXi, for ESXi and not for use by ESXi for the chipset installed. I guess I misunderstood that.
Never mind I googled i386 and realized it’s pretty much the 32 bit version.
-
@scottalanmiller said in ESXi 6.7 Troubleshooting:
@Dashrender said in ESXi 6.7 Troubleshooting:
For s&h why not try Hyper-V as the hypervisor, then setup a Windows VM
S&H, not Ss&Gs?
I got that 1!
-
@scottalanmiller said in ESXi 6.7 Troubleshooting:
@Dashrender said in ESXi 6.7 Troubleshooting:
For s&h why not try Hyper-V as the hypervisor, then setup a Windows VM
S&H, not Ss&Gs?
I don’t know what these are.
-
@G-I-Jones said in ESXi 6.7 Troubleshooting:
@scottalanmiller said in ESXi 6.7 Troubleshooting:
@Dashrender said in ESXi 6.7 Troubleshooting:
For s&h why not try Hyper-V as the hypervisor, then setup a Windows VM
S&H, not Ss&Gs?
I don’t know what these are.
I have no idea what S&H is. But Ss&Gs are "shits and giggles".
-
@scottalanmiller said in ESXi 6.7 Troubleshooting:
@G-I-Jones said in ESXi 6.7 Troubleshooting:
but when I install VMWare Tools to load the driver so I can see the Partitions, it only lets me select the AMD64 which is wrong.
How could AMD64 be wrong? What other possibility is there? VMware only runs on AMD64.
What are you running? You don't have a Power or Itanium system, do you?
What Scott means is that today, Intel and AMD both make their 64 bit chips based on the AMD64 spec. Intel's original 64 bit spec failed compared to AMD's spec, so AMDs won, just like Intel's won in the past and everyone cloned/copied that.
-
@scottalanmiller said in ESXi 6.7 Troubleshooting:
@Dashrender said in ESXi 6.7 Troubleshooting:
For s&h why not try Hyper-V as the hypervisor, then setup a Windows VM
S&H, not Ss&Gs?
yeah, that was supposed to be S&G...
-
@G-I-Jones said in ESXi 6.7 Troubleshooting:
@G-I-Jones said in ESXi 6.7 Troubleshooting:
@scottalanmiller said in ESXi 6.7 Troubleshooting:
@G-I-Jones said in ESXi 6.7 Troubleshooting:
but when I install VMWare Tools to load the driver so I can see the Partitions, it only lets me select the AMD64 which is wrong.
How could AMD64 be wrong? What other possibility is there? VMware only runs on AMD64.
What are you running? You don't have a Power or Itanium system, do you?
I was assuming the driver should have been the Intel driver (as that’s an option too) because I have an Intel Xeon, but you’re saying it’s for use by ESXi, for ESXi and not for use by ESXi for the chipset installed. I guess I misunderstood that.
Never mind I googled i386 and realized it’s pretty much the 32 bit version.
IA32 / i386 = Intel 32bit
IA64 = Itaniam (Intel's dead 64bit idea)
AMD64 = Modern 64bit that replaced i386AMD64 is the only platform supported by Windows or VMware or Hyper-V. It's the only 64bit PC platform. Everything you think of as a modern computer is AMD64. And it is why we say "Genuine AMD" because Intel only makes clones (reversed from the 32bit era when AMD made Intel clones.) Absolutely no one has used "Intel architecture" in years, everything is AMD based today.
The only major alternative to AMD today is ARM, that's what is used in phones and Raspberry Pi. But only Linux and BSD run on that platform currently.
-
@Dashrender said in ESXi 6.7 Troubleshooting:
@scottalanmiller said in ESXi 6.7 Troubleshooting:
@Dashrender said in ESXi 6.7 Troubleshooting:
For s&h why not try Hyper-V as the hypervisor, then setup a Windows VM
S&H, not Ss&Gs?
yeah, that was supposed to be S&G...
See, I knew that's what you meant!
-
@Dashrender said in ESXi 6.7 Troubleshooting:
@scottalanmiller said in ESXi 6.7 Troubleshooting:
@G-I-Jones said in ESXi 6.7 Troubleshooting:
but when I install VMWare Tools to load the driver so I can see the Partitions, it only lets me select the AMD64 which is wrong.
How could AMD64 be wrong? What other possibility is there? VMware only runs on AMD64.
What are you running? You don't have a Power or Itanium system, do you?
What Scott means is that today, Intel and AMD both make their 64 bit chips based on the AMD64 spec. Intel's original 64 bit spec failed compared to AMD's spec, so AMDs won, just like Intel's won in the past and everyone cloned/copied that.
Yup. Although worth noting that Intel's Itanium EPIC architecture (aka IA64) did last for a good decade or so and was an amazing design. But the cost was so high that no one could reasonably consider it and AMD's 64bit platform that was backward compatible with i386 proved unbeatable. Intel thought that everyone was going to drop the PC platform and move to something new with all new operating systems and no Windows and no software being compatible. It was an insane belief. AMD bet that people would want to just upgrade from what they had, at a lower cost and proved to be massively correct.
-
This post is deleted! -
[Solved]
After re-configuring the Server setup to run ESXi via USB internal (for now) and completely CLEARING each drive (because I installed ESXi on the RAID 5 array initially and if you do that, it ruins everything and your drives disappear), I re-allocated the drives to RAID 5, and re-installed ESXi DELL OEM 6.7 Update 2 to the USB on host. I was able to build the Guest and everything worked fine except Network Shares. I was back at square one on that front. Turns out it was a bad switch (Netgear 8 port) the host was plugged in to.
