I have two users that can in the vm user role (sample) who can power off any VMs but cannot power on any. When they power on the VM, they receive the error below.
"
The "Power on virtual machine" operation failed for the entity with the following error message.
Virtual machine cannot be found.
"
However, when the users tried to power on the VM using the vSphere client on Windows, it works just fine. Could this be a bug???
Thanks,
Alex
I am just starting to play around with Horizon to help on a VDI pilot. I am not a desktop expert, I will be helping with the storage, and vcenter, etc.
So while playing in a home lab I am curious how I can solve this, because I know its doable, and I am sure the desktop people do.
On my instant clone snapshot, the Windows 10 image is joined to my test AD domain. When I login through any Horizon Client with the credentials that I used to join the machine before I snapshot it, the Windows 10 instant clone pulls up quick and nice. If I enter any other AD credentials, it goes through the Welcome setup basically. Which I am sure this is because of a new user. But how is this solved I am curious? Again this is just a home lab with me trying to get familiar with the other side of the house.
Over the past year, my VM box will crash at random times, sometimes months apart. I was on 5.5 and now am running 6.0. The NUC is a 5i7 with 32GB RAM and the datastore is on a Synology NAS.
When this crashes, for some reason I am unable to ping anything on my network. As soon as the NUC is restarted, everything is fine. It's strange, but I am more interested in tracking down why ESXi is crashing in the first place.
The PSOD tells me Machine Check Exception: Fatal MCE on PCPU3 in world 1388527:vmm0:Visual_
System has encountered a hardware error......
I have a VM named "Visual Studio 2012 - 32 bit" and I am only guessing that error is referring to that VM.
I've been playing with this for a while, but green when it comes to troubleshooting it. Any help appreciated. Thanks.
The issue is quite obvious and already pretty clear from the title. Using the previous Windows 10 version "Anniversary Update" (1607) VMware Fusion would detect the Boot Camp partition without an issue. After clean installing the new Windows 10 with the Creators Update, it would not get detected by Fusion and only report that no Boot Camp partition was found. Reinstalling Windows 10 1703 did not change anything, only a reinstall using the older 1607 version would fix the issue.
VMware Fusion therefore probably just needs an update to be able to detect the new W10 Creators Update.
Hi,
we have a VSAN cluster built with 4 ESXi hosts. For some reason one of those hosts become unresponsive - 2nd time within three weeks. This means: ESXi host lost his connectivity to vCenter Server. I can't ping the ESXi host. If I connect to the management network, it looks ok but I can't do anything. No response to F12 or F2. I have to cycle power or perform a hard reset to reboot the server. Then it will boot again, initialize the VSAN disk and is back in the cluster.
I checked all server logs but nothing here why it lost his connectivity. What VMware logs can I check? Who can help? I would like to know what happened and how to avoid this.
Thanks for your answers in advance!
Blocking this *may* have issues, not *will* have and i have not had any negative effort in networking by blocking this by Firewall on Host..
However, why is this unique to OS X and not to Windows ?
Hello
I have managed to finally resolve the OpenStack images working with VIO. It appears that VIO did not convert the OpenStack cloud images properly. I have to use qemu-img to first convert the image.
Anyway, now moving on to Metadata.
I have VIO installed as per the guide and with NSX. However the Cirros image I receive metadata failures.
It may be a firewall issue but need some guidance on what needs to be looked at as all the NSX firewall rules are as standard. Does ICMP need to be open or any other ports for metadata ?
I have tried the curl request to http://169.254.169.254 using port 8775 but that does not receive any response.
After 20 failures we can login
Not sure why there are detached ports.. Is it safe to remove these ?
how to set a VM OSX to have a different IP address from its host also macOS 10.12.5.
Have tried bridging but that didn't work. Shared networking does not allow me to see the VM from another non-virtual Mac.
using VM's for testing including the upcoming macOS High Sierra.
Any help would be appreciated.
We are having some very odd networking problems and working with the network team we are running out of ideas.
The problem:
VMs on standard vSwitches are experiencing problems talking to other systems on the same vLAN resulting in dropped packets and RPC errors even when on the same VM Host.
Here is a quick and dirty how the network is laid out: http://imgur.com/a/iJIFJ
ESXi NICs are hooked up to Nexus1 and Nexus2. When VMs attempt to communicate the path will often go to the wrong physical address, fail to communicate, and then update ARP tables and go to the other NIC.
The vSwitches are configured to load balancing with "Route based on IP hash" and because we are using standard vSwitches we do NOT have LACP enabled.
We have noticed this problem only exists on the Dell cluster which is hooked directly into the nexus environment. The UCS cluster which is plugged into FIs does not share the problem. I suspect this is because the UCS FIs share ARP tables and it never makes it back to the Nexus 5ks.
My suspicion is that there is a problem between the 2 Nexus 5k switches and they are not sharing ARP tables properly, but the network team is insisting that the problem lies with either the ESXi or Windows OS layer within the VMs. I'm not versed enough in low level network operations to argue this, but I'm at a loss for how to troubleshoot this further and get a definitive answer.
Some solutions we've tried:
1. Setting up a dvSwitch on a test box and enabling LACP. This saw no change.
2. Dropping 1 NIC on the vSwitch and force paths to go up Nexus1. This caused the problem to stop, but is unacceptable as a solutions as it removes our path redundancy.
Some things network team wants us to try but we haven't done yet:
1. Manually changing the VMs' "reachable time" on the NICs to a lower value.
2. Changing out the VMXNET3 interfaces for E1000
3. Enabling LACP on the Standard vSwitches (This isn't supported)
4. Upgrading to ESXi 6 (we're note ready for this migration yet)
We're really pulling our hair out over this one...has anyone ever encountered these problems before?
Hello,
i had a workstation 11.1.4 and a guest system windows 10 64bit. After an update of the windows 10 to windows 10 1703, i get this message.
After uninstall the vmwaretools it works but with the reduced functionality. If i install the tools, i get the black screen with this message again.
I tried all combinations of the display options but nothing helps.
Has someone an idea to fix this issue?
How do you change the boot order on a VM using the 6.5 web client ?
If I want to deploy the FT function on a VM, that was formed by Thick Provision Eager Zeroed, right?
Team,
Is there a simple, recommended solution folks typically use to automate upgrades of the client in ESXi 6.5?
Thanks,
Brad
I wanna know, is there anyway to take vcp6.5 dcv exam without sitting official training. Is ccna > vcp nv > vcp dcv path still valid help me please.
Hi All,
I am planning to upgrade my VC6.0 to 6.5, when I am trying to run vcsa-ui-installer\win32\installer.exe file getting JAVA script error.
Need your help to resolve this issue.
OS version : Windows 2012 R2 standard edition.
Error message screen shot attached.
I'm suffering from the condition where I updated my VM from Windows 8.1 to Windows 10 and am now getting a blank screen upon boot up. I know from other articles that this is because the VMWare tools installed (specifically the video driver) is incompatible with Windows 10. To solve this, I have to go into safe mode to remove the video driver and install the latest VMWare tools.
The problem I am having is that I can't get the VM booted into safe mode! I have the Windows 10 installation ISO mounted to the drive, I've slowed down the bios so I can access the boot menu, and now easily access the boot menu...but when I choose CD-Rom, it continues to load into windows 10 main and present me with a blank screen.
Does anyone have any tips how to get Windows 10 into safe mode when it is in a VM? I've tried other .isos too...I even created an ISO from my USB recovery drive without luck.
Any assistance would be greatly appreciated!
-Spurk
Hi,
I am using one app stack called appstack-1.0 (size: 8GB) which is taking 5 min. to log-in,
Later, I updated the appstack-1.0 to appstack-2.0 by adding new app's in it (size: 12 GB), now it took only 3 min. to log-in, I don't have any answer to the client, why it is behaving like it?
Thank you,
Vkmr.
Hi,
I am trying to persist my time settings on non-persistent VDI, how can we persist time?
Thank you,
Vkmr.
Hi Team,
I have an issue with vmnet0, whereby vmnet0 is not showing up in "ifconfig -a". This is my environment:
Host: Ubuntu 14.04
VMware Workstation version 11.1.2
This started happening about 2 weeks ago: when starting a VM that uses the bridged interface, it comes up with the error message "The network bridge on device /dev/vmnet0 is temporarily down because the bridged Ethernet interface is down."
When looking at "vmware-netcfg", all settings are as they have always been. Specifically with respect to the bridged connection: it is bridged to "Automatic" and the "Automatic Settings..." have a tick for each interface on my system. The line item for vmnet0 shows:
Name: vmnet0
Type: bridged
External Connection: auto-bridging
Host Connection: ---
DHCP ---
Subnet IP Address: ---
I have also tried to force the bridging onto a specific interface, by changing the automatic settings to a specific interface. This does not resolve the issue.
I decided to upgrade VMware Workstation to version 12.5.6, hoping the issue would get resolved that way. This did not make a difference.
I then decided to wipe out my hard drive and install Ubuntu 16.04.2. After the installation, I installed VMware Workstation 12.5.6. Doing all this, also did not resolve the issue.
I found that the vmnet-bridge process is running:
$ ps aux | grep vmnet-bridge
root 21321 0.0 0.0 7004 196 ? Ss 13:25 0:00 /usr/bin/vmnet-bridge -s 12 -d /var/run/vmnet-bridge-0.pid -n 0
However, while researching this issue, I found that sometimes you have to manually run:
/usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet0.pid /dev/vmnet0 vmnet0
After running this, I can see the vmnet0 interface listed in the output of "ifconfig -a", however I cannot seem to use it.
BTW, I got the above from this link: networking - Bridged virtual interface is not available or visible to ifconfig - Server Fault
Some other info: /dev/vmnet0 exists.
Not sure what to do anymore at this stage. Any help is greatly appreciated.
Marc.
Recently update MacBook Pro OS to newest version and now VMWare crashed. Getting a message that says "Internal Error". Weird thing is that it will not work on my MacBook pro but I did copy the VM to a USB flash drive and plugged it into my iMac with VMWare Fusion 7.1.3 and I was able to run it. I am having trouble figuring out what is going on with the macbook pro. I downloaded the diagnostics on it and I will attach that. Please help and thanks.