We have 3 departments in a Business Group and have created 3 entitlements for the same and assigned the Catalogs accordingly. Now the requirement is, users of their own department would be able to see their deployments? How this can be accomplished?
We are using vRA/vRO 7.6
I've been seeing people using Paravirtual adapters in there desktops, and I'm working how many people have used it without issue
Well vmware support finally came up with a solution.
Within this registry key:
HKLM\Software\VMware, Inc.\ViewComposer\ga
I had to create this DWord entry
GPUpdateEnabledOnIT Set to 0
After that i was able to create a new snapshost and deploy it without issue. I've been able to deploy snapshots from multiple 1903 VM's so hopefully this issue is resolved.
Thats good new, any idea why that fixed the issue? I can't see any information online about that key and was wondering why it was needed.
Hello everyone,
I'm new here so I hope this is the correct place for this question... We've recently installed an ESXi Server, and connected to a SAN for our students to learn how to create their own cloud infrastructure. I'm looking for the right permission set for them - they need to be able to explore (read-only) the interface, and create and run their own VM's. I'd rather them not see anyone else's VM (or at least not be able to modify them).
We're using ESXi v6.7.0 update 3.
I've been playing with a bunch of different permission configurations, but can't quite seem to find the right config. I've come close a couple times, but not 100%. Any help would be appreciated!
Thank you,
Scott
New releases always contain all older patches, so in this case the patch for the mentioned issue is already included in the current installation image.
André
Has anyone else encountered this after patching hosts from the HTML-5 client, where the hosts are automatically removed from maintenance mode.
Apparently this is a known issue and is documented in the below KB
https://kb.vmware.com/s/article/66845
https://kb.vmware.com/s/article/66845
Using the Flex client for host patching and upgrades might be the workaround until this is fixed.
Cheers, Onil
I want to add an additional note on my setup. Hopefully I'll help other people too.
From the steps documented above I suggest a minor modification to point 5)
The modification being: do not set up your NVIDIA as primary and only display! Stick the the Intel or built in whatever you have and assign no screen to the NVIDIA. As long as Windows recognises the NVIDIA this will be used on an application basis. Obvious but likewise important: you must be on the console to do so, of course RDP will not allow you to set up display settings.
Windows 10 1909 (but even earlier version, same concept) - Settings/System/Display/Graphic Settings
Select "Classic App" and browse the applications you want to benefit from the NVIDIA.
In my case I use Handbrake for video encoding.
Since I did the above about two months ago I did not get a single VM freeze any more.
HTH
The script got executed and in the the destination VM the test1 directory got created but the script failed the below 500 error code.
Can anyone please help, why we are getting the Response status code does not indicate success: 500 (Internal Server Error) even after the directory creation.
Either in the vmware log are vmware tool log, could not see any error detail message. PowerCLI 11.5.0 is being instal
Invoke-VMScript -ScriptText "mkdir c:\test1\" -VM 'TestMachine' -GuestUser 'Test' -GuestPassword 'Test@123' -Verbose
VERBOSE: Performing the operation "Invoke-VMScript" on target "TestMachine".
VERBOSE: 11/19/2019 3:32:25 PM Invoke-VMScript Finished execution
Invoke-VMScript : 11/19/2019 3:32:32 PM Invoke-VMScript Response status code does not indicate success: 500 (Internal Server Error).
At line:1 char:1
+ Invoke-VMScript -ScriptText "mkdir c:\test1\" -VM 'TestMach ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Invoke-VMScript], ViError
+ FullyQualifiedErrorId : Client20_VmGuestServiceImpl_DownloadFileFromGuest_DownloadError,VMware.VimAutomation.ViCore.Cmdlets.Commands.InvokeVmScript
Hello,
I managed to execute "start" and "stop" vmrun commands if i use Terminal, but I use the same commands in Applescript I get the error "Cannot open VM: /Users/pascal/Documents/Virtal Machine/Win 10 x64 iMac 2017.vmwarevm/Win 10 x64.vmx, Cannot read the virtual machine configuration file."
remark: the proper name of the folder is "Virtal Machine", with the spelling mistake :-(
Commands I use with Terminal: and both work!
vmrun stop /Users/pascal/Documents/Virtal\ Machine/Win\ 10\ x64\ iMac\ 2017.vmwarevm/Win\ 10\ x64.vmx soft
vmrun start /Users/pascal/Documents/Virtal\ Machine/Win\ 10\ x64\ iMac\ 2017.vmwarevm/Win\ 10\ x64.vmx
The syntax I use in Applescript:
property usr : "myuser"
property pswd : "mypsw"
do shell script "sudo /Applications/'VMware Fusion.app'/Contents/Library/vmrun start '/Users/pascal/Documents/Virtal Machine/Win 10 x64 iMac 2017.vmwarevm/Win 10 x64.vmx'" user name usr password pswd with administrator privileges
do shell script "sudo '/Applications/VMware Fusion.app/Contents/Library/vmrun' stop '/Users/pascal/Documents/Virtal Machine/Win 10 x64 iMac 2017.vmwarevm/Win 10 x64.vmx' soft" user nameusrpasswordpswd with administrator privileges
Can you tell me what i do wrong in applescript?
Manhy thanks
mac book air Catalina
Fusion 11.5.1
Hi,
I am trying to do a compute and svMotion of a multi TB VM (FTT1) from one vSAN cluster to another over 1Gbit uplink.
After several hours (around 10 hours and was more than 50%) it fails with Event: Migration to host xx.xx.xx.xx failed with error Connection closed by remote host, possibly due to timeout (195887167)
Source vSAN is 6.2U2 and destination vSAN is 6.7U2
vmkping -I does not show any ping loss from source to destination vmk when I test RTT min=0173 avg=0.460 max=1.218
Both cluster/hosts connected to the same switch
VM is not busy but still powered on, does it help if I try again with the VM powerd off?
I selected "Schedule vMotion with high priority (recommended) - not sure if instead I select "Schedule regular vMotion" would help?
I am thinking this might be saturation the uplink during the migration and timing out, could that be the case and would it not lower the transfer speed if so?
Any specific logs I should check or any other methods I can try to migrate?
I tested a migration (compute and svMotion) of a very small VM from the same cluster (same source host) to the same destination host in other cluster and migration worked fine, so think it must be failing because of its size.
On source host vmkernel I see events related to:
S: failed to read stream keepalive: Connection reset by peer
S: Migration considered a failure by the VMX. It is most likely a timeout...
Destroying Device for world xxxxxxxx
Destroying Device for world xxxxxxxx
disabled port xxxxxxxxxxxx
XVMotion: 2479 Timout out while waiting for disk 2's queue count to drop below the minimum limit of 32768 blocks. This could indicate network or storage problems...
Thanks
I have a Windows 7 guest that was happily running in Player 15.5 under Windows 8.1 build 9600, but ever since I fixed my dual-monitor configuration in Windows 8 so that the 2nd monitor works and the resolution behaves correctly on the 1st monitor, the Windows 7 guest has crashed with a Blue Screen of Death (the crash screen says Windows 7 was loading the ndis.sys driver at the time of the crash).
Does anyone have any suggestions? Maybe I simply need to reinstall Player to take into account the new monitor drivers?
Here's how to check in powershell
(Get-VM myVM).extensiondata.config.flags.VbsEnabled
And how to set
$vm = Get-VM myVM $spec = New-Object VMware.Vim.VirtualMachineConfigSpec $flags = New-Object VMware.Vim.VirtualMachineFlagInfo $flags.VbsEnabled = $true $spec.flags = $flags $vm.ExtensionData.ReconfigVM($spec)
Update - We have 2 connection servers and both allow the user to log in but only one is sending a command to power the VM on from a powered-off state. If the VM is already on then you can connect using either connection server. What in the connection server sends a command to vsphere to power the VM on?
I've attached vmkernel.log from out R730 host
I see an entry every 10 seconds:
lsi_mr3: megasas_hotplug_work:495: lsi_mr3: Event : Enclosure PD 00(c 00/p0) is unstable
That would be our external enclosure. I will look into disconnecting it to see if that changes anything. First I have to figure out somewhere else to send backups as that is where they are currently stored.
I have not looked in the vmkernel.log before this upgrade so can't say for sure if these messages appeared before. I assume they did because I did notice ever since installing this enclosure that the iDRAC reports:
Communication with Enclosure 0 on Connector 0 of RAID Controller in Slot 7 is intermittent.
about every 10 minutes or so. It is still reporting this, nothing has changed. The disks have always worked though, without issues. This is an old Dell MD1200 connected through a Perc H30 adapter which is older hardware not supported anymore on newer Dell servers, but it works... and didn't seem to cause any issues with esxi 6.7
Even if that is an issue, it doesn't explain why we see some symptoms on our T630 which has no unsupported hardware. I've attached it's vmkernel.log as T630-vmkerne.log
Hello andvm,
You should consider moving this to general vSphere sub-forum as while there is a vSAN at either end of the vMotion, this is likely failing for generic reasons (unless of course either cluster on either end is having some issues - do of course check this).
"vmkping -I does not show any ping loss from source to destination vmk when I test"
Unless you were pinging this for the 10 hours that this was running, this is not exactly a valid test, e.g. that you see no connectivity issue now does not mean one did not occur.
Using high priority or regular shouldn't matter unless you are vMotioning other VMs at the same time:
Migrate a Virtual Machine to a New Compute Resource
If they are going over 1Gb uplinks and Management network (what it will go over if cold) also has 1Gb uplinks then doing this cold may be beneficial as the data will be static.
Is the VM comprised of multiple vmdks or one relatively large one? If multiple, then you could consider moving it using the advanced vMotion options of 1 to few disks at a time (which by the law of odds has less chance of timing out).
"I tested a migration (compute and svMotion) of a very small VM from the same cluster (same source host) to the same destination host in other cluster and migration worked fine, so think it must be failing because of its size."
Yes it surely is, if you have X chance of something timing out per hour (for whatever reason) and you multiply that by multiple orders of magnitude then the odds of this occurring are multiple orders of magnitude higher.
Bob
No. Sorry.
This download fixed my problem with the windows 10 upgrade. Thanks
What vSphere are you running? The vCenter and the ESXi node on which the VM is running?
Is port 902 to the ESXi node on which the VM is running open?
The vmware.log file in the VM's folder should show you the execution sequence.
It would be useful to see if all steps are executed or not.
