Does VMware Tools have its own IP address, separate from the actual Ethernet adapter(s)? Essentially, I would need to have the host be able to connect to it as a datastore.
I'm probably missing something really obvious here, but is there a way for an ESXi host to connect to a guest via TCP/IP without the network traffic leaving the box?
I'm sure I'm not the only one who's had to deal with weird issues, regressions and/or features that simply don't work for some inexplicable reason when evaluating a new version of ESXi, so being ...
See more...
I'm sure I'm not the only one who's had to deal with weird issues, regressions and/or features that simply don't work for some inexplicable reason when evaluating a new version of ESXi, so being listed in the Compatibility Guide clearly doesn't mean that VMware and the hardware manufacturer have thoroughly tested every feature in the specified version of ESXi and have found that there are no problems with the listed hardware. Thus, I'm wondering what the criteria are for VMware to list a system in the Compatibility Guide and what kinds of assurances customers are supposed to be getting from it?
I'm very happy with ESXi 6.0. It's the only version of ESXi so far where all of the features I use actually work right out of the box. Thus, I was planning to skip over 6.5 entirely and wait f...
See more...
I'm very happy with ESXi 6.0. It's the only version of ESXi so far where all of the features I use actually work right out of the box. Thus, I was planning to skip over 6.5 entirely and wait for the next version, but as 6.7 is incompatible with Xeon 55xx CPUs, it seems 6.5 is the end of the line for my server. If I'm not planning on using any of the new features in 6.5, is there any reason to upgrade?
Is it possible to set up an internal network so that if VMs A and B are on the same host and A tries to access B (or vice versa), all network traffic will be handled internally by ESXi without ne...
See more...
Is it possible to set up an internal network so that if VMs A and B are on the same host and A tries to access B (or vice versa), all network traffic will be handled internally by ESXi without needing to go upstream?
Every time I do a clean install of ESXi (and reconfigure DirectPath I/O passthrough on the hypervisor and add all the VMs back into the inventory), I always have to go into each recipient VM via ...
See more...
Every time I do a clean install of ESXi (and reconfigure DirectPath I/O passthrough on the hypervisor and add all the VMs back into the inventory), I always have to go into each recipient VM via right click -> Edit Settings, remove the PCI device, press OK, and then repeat the process in reverse to add the exact same device (with the exact same PCIe device ID) back again. If I don't do this, ESXi gives me an error along the lines of the device not being found. So it seems that there's something tying VM-level PCI device configurations to a specific ESXi host/installation, but what is it?
If you enter your password correctly, you get in within a second or so. On the other hand, if you mistype your password it'll spend a good 10-15 seconds trying to connect before giving you an err...
See more...
If you enter your password correctly, you get in within a second or so. On the other hand, if you mistype your password it'll spend a good 10-15 seconds trying to connect before giving you an error message. What makes these 2 cases so different? In most other programs, a wrong password check is slightly faster than a successful login since there's no follow-up action needed.
My understanding is that ESXi runs completely in memory after startup is complete, so even if the USB stick failed during use it wouldn't be noticeable until the next startup or reboot, at which ...
See more...
My understanding is that ESXi runs completely in memory after startup is complete, so even if the USB stick failed during use it wouldn't be noticeable until the next startup or reboot, at which point dealing with the problem would simply be a matter of routine maintenance.
A thought came across my mind as I was upgrading from 6.0 to 6.0U1 - I've been this stick for around 18 months now. That's led me to wonder how long others use a USB stick for before replacing it...
See more...
A thought came across my mind as I was upgrading from 6.0 to 6.0U1 - I've been this stick for around 18 months now. That's led me to wonder how long others use a USB stick for before replacing it, barring outright failure.
Is there a recommended (or built-in) way to move powered off VMs from one datastore to another? Or is this a straightforward cut and paste job that can be done from any client PC connected to the...
See more...
Is there a recommended (or built-in) way to move powered off VMs from one datastore to another? Or is this a straightforward cut and paste job that can be done from any client PC connected to the underlying storage provider(s)?
Ever since I upgraded to 6.0, I've had an issue with one of my Windows 7 VMs where if I leave the VM alone for more than an hour or two, it'll be stuck on a black screen with an underscore at the...
See more...
Ever since I upgraded to 6.0, I've had an issue with one of my Windows 7 VMs where if I leave the VM alone for more than an hour or two, it'll be stuck on a black screen with an underscore at the very top left (I'm guessing this is supposed to be a cursor that's not blinking?) and a "This virtual machine's guest operating system has crashed" entry in the ESXi log. That seems to be all the information available, though...
Currently, my ESXi 5.5 home lab server (which has 2 physical NICs) is connected to a cheap unmanaged switch. The switch in turn has a single 1 Gbps upstream connection to my router. Everything el...
See more...
Currently, my ESXi 5.5 home lab server (which has 2 physical NICs) is connected to a cheap unmanaged switch. The switch in turn has a single 1 Gbps upstream connection to my router. Everything else on my network is connected directly to the router. So far, I've been using ESXi's default configuration - please see the attached screenshot for details. I'm decently satisfied with this, but in the spirit of learning and continuous improvement, I'm wondering if there's something that I could be doing better here - perhaps some way to make use of my second NIC, for instance?
In case anyone else has this issue, I'm happy to report that Update 2 has fixed all passthrough issues for X58/ICH10. I didn't have to do anything special - or more specifically, anything differe...
See more...
In case anyone else has this issue, I'm happy to report that Update 2 has fixed all passthrough issues for X58/ICH10. I didn't have to do anything special - or more specifically, anything different from 5.1. I just clean installed 5.5U2 from the ISO (with all SATA cables physically disconnected, of course...), (re)configured DirectPath I/O and datastores, fired up the VM, and everything worked as expected - for a change. Let's just hope future releases (5.5U3? 6.0?) don't break everything again...
Thanks for the link - I have X58/ICH10 rather than Lynx Point, so I missed that discussion but any clue is welcome As I don't have a spare 5.5 box to test with, would you mind confirming if...
See more...
Thanks for the link - I have X58/ICH10 rather than Lynx Point, so I missed that discussion but any clue is welcome As I don't have a spare 5.5 box to test with, would you mind confirming if the problem (prior to modifying the /etc/vmware/passthru.map file) is that the Lynx Point SATA controller doesn't show up in vSphere Client as a device that can be passed through, or that the Lynx Point SATA controller can be selected, but the guest can't see it?
The last time I tried (with 5.5U1) it worked if the VM was installed and booted via UEFI rather than BIOS, but unfortunately that led to a whole host of other issues and I ended up having to down...
See more...
The last time I tried (with 5.5U1) it worked if the VM was installed and booted via UEFI rather than BIOS, but unfortunately that led to a whole host of other issues and I ended up having to downgrade back to 5.1. Has a workaround been discovered in the months since? Or better yet, can anybody confirm if VMware has fixed this in 5.5U2?
Thanks for the help, everyone. Given that even in the worst case scenario I'll only need to turn off the VM and adjust some configuration settings, I guess I'll just take a leap of faith and hope...
See more...
Thanks for the help, everyone. Given that even in the worst case scenario I'll only need to turn off the VM and adjust some configuration settings, I guess I'll just take a leap of faith and hope that ESXi will do the right thing.
