Hot answers tagged

7

WARNING about your setup I would advise you caution using this system in this setup, if you have only one physical adapter and then only one uplink to the universe from the system. I would suggest going and purchasing an extra adapter for the system, and add that to your system - this way you can still have a backup physical connection. The ...


3

Were the snapshots taken while the machine was powered on? If so the VM snapshot state requires the CPU features match the original state. Otherwise the feature set of the CPU would wildly change in the middle of powered-on operation, that's a huge no-no. If it's powered off, yeah that makes no sense, it shouldn't matter. NOT SUPPORTED BY VMWARE, TRY AT ...


3

Create a new VM within your ESXi environment that runs nginx and use the proxy module to direct your traffic: server { listen 80; server_name hostname1 hostname2 hostname3 ... hostnameN; if ($http_host = hostname1) { proxy_pass http://192.168.0.1; } if ($http_host = hostname2) { proxy_pass http://192.168.0.2; } ...


2

At 100% CPU on the VM, the hypervisor is going to have a devil of a time writing those snapshots in. You can see all the snapshots by going to the datastore and looking for all snapshots: cd /vmfs/volumes/ then run ls -alR | grep -I *.*delta | less This will display all snapshots in each VM. You could go into the specific VM's directory to see just ...


2

CPU Core power management is a function that can be owned by the system/BIOS on its own but usually it's a collaborative effort with the OS, in an Intel world this is done via Speedstep extensions, AMD have similar mechanisms. VMs each have a 'CPU mask' that the hypervisor exposes to each VM to tell it what CPU capabilities it can call on, some of these are ...


2

I have a Cisco UCS-C240 server that runs ESXi 5.5 U2 to run 2 VMs, an standalone host, no vcenter (so almost the same problem). I opened a ticket in VMware and after a webex the solution was: 1-Log via SSH to the host. 2-Run the following commands: ~ # localcli hardware ipmi sel clear ~ # /etc/init.d/sfcbd-watchdog restart 3-Click the Reset Sensors ...


1

Despite the network config that led to the situation, this remains a legit question: what's the best way to get an ESXi host to see its iSCSI storage again without a reboot? Note: I wasn't able to actually get this to work because my entire network stack was FUBAR and I needed to reboot ESXi to get it back anyhow. I'm posting this as an answer because what ...


1

I had this same issue and could not figure out how to change the password for monitoring through the web-interface. However, I tracked down the user/password file on the nagiosxi server and changed it there and all is good. To find where the password file is located to change, go to one of the Service reporting the error, go to the configuration tab and ...


1

I found the problem and a solution. The packet loss was caused by identical MAC-addresses on different switch ports. The virtual interface VMK0 Blade 7 had the same MAC as the hardware interface of Blade 11. So what I've done is this: I gave the VMK0 interface a new MAC address. For that I go over the iDRAC interface of the Blade Enclosure and loging ...


1

Your snapshots won't be useful here. The original snapshots came from a system with a completely different architecture, so the error you're receiving is very clear in its message. AMD and Intel are not compatible in vmotion or EVC terms.



Only top voted, non community-wiki answers of a minimum length are eligible