Hi...
yes, the hardware compatibility is at 12...
attached a screen shot, this occurs in a loop after a few seconds the machine is started..
attached the dxdiag and vmx and log files
in the dxdiag I have seen the system is set to 120 DPI, this is not correct, it is definitly at 100%...
but the vmtools try to set the (w7) machine also to 120 DPI, under XP and W10 they do not
Regards, Kai
Try something like this
$Failed= @()
foreach($vminGet-VM){
Try{
Move-VM-VM$vm-Datastoredatastore100-ErrorActionSilentlyContinue
}
Catch{
$failed+=$vm.Name
}
}
if($Failed){
$sMail= @{
To ='lucd@lucd.info'
From ='lucd@lucd.info'
Subject ='Failed svMotion'
SmtpServer ='mail.lucd.info'
BodyAsHtml =$true
Body = ($Failed|ConvertTo-Html|Out-String)
}
Send-MailMessage@sMail
}
This error doesn't give a lot of clues.
Check the vpxd logs to see if they contain some more information on the error
Try something like this
foreach($vminGet-VM){
$obj=[ordered]@{
Name =$vm.Name
MemoryGB =$vm.MemoryGB
GuestOS =$vm.ExtensionData.Guest.guestFullName
}
$i=1
Get-HardDisk-VM$vm|%{
$obj.Add("HD$($i)Name",$_.Name)
$obj.Add("HD$($i)Type",$_.StorageFormat)
$i++
}
New-ObjectPSObject-Property$obj
}
Hi bluefirestorm
After booting the host, I verify that the authorisation service is running.
I start the VMware GUI. When I start a VM, the UAC prompt displays.
If I shut down the VM (cleanly through the guest shutdown), but leave the VMware GUI process around, starting the VM again does not require the UAC prompt.
However, if I close the GUI process, restart it and attempt to start a VM, the UAC prompt appears again.
I wonder if there might be some clue in a VMware log file.
Any other pointers appreciated!
Cheers
Ronny
This problem is plaguing us on VDIs with nVidia 3D acceleration-- would LOVE to find out the offending process(es) or GPOs.
Appreciate any feedback from the community.
Update: It seems to hang when running local.sh.
If I deleted 100-GB files of a VM (thin-provision), I must type the command to reclaim VMFS deleted blocks on thin-provisioned LUNs on ESXi version 5.5, right?
Hello,
We have the same issue with HP DL360 G9 and the latest ESXi Custom ISO Build VMware-ESXi-6.5.0-OS-Release-5146846-HPE-650.9.6.5.27-May2017.
It occurs when a VM hardly stresses the vCPUs.
I have operated the Shift+R solution to revert to a previous build and it seams to work for me.
For us it's not a definitive solution because we can't keep our ESXi up to date in this way.
Have you got some answers from VMware about this issue?
Best Regards,
Alfredo
FYI I did find the issue, it was a dodgy power cable :-(
I though I tested them all but this is a rare event in my experience where sometimes it works other times doesn't. Probably a loose connection.
Replaced and now everything works fine.
So nothing to do with ESXi :-)
Hi,
If you are not comfortable with command line, use svmotion if the vmdk sizes are not huge.
Ciao a tutti sono un nuovo utente e sto studiando vmware. Quali sono i vantaggi nell'usare Thick Provision Eager Zeroed Thick Provision Lazy Zeroed e Thin Provision?
Perchè usare una modalità piuttosto di un'altra?
Quando è consigliabile usarle?
Dove posso trovare queste risposte in rete?
Trovo solo scritto cosa sono ma non dicono quando e perchè usare una piuttosto dell'altra
Spero in una risposta
Ciao!
Right, item1 is located in the workflow List path in guest, which is used by the workflow Check for directory in guest, which is used by your workflow.
The problem is that List path in guest (and other guest operations workflows) do not have their output exception binding set, so when some guest operation throws an error, you cannot just catch and not print the error message
The easiest way to fix it would be to modify these workflows and bind the output exception to some attribute. However, these workflows are sealed (as all out-of-the-box workflows) so you cannot edit them easily. One option would be to duplicate them and use the duplicated copies. Another option would be to write your custom workflows/scripting code to deal with the guest operations, using the existing workflows as a template (the code is not complex).
Got a reply from CAFE plug-in team that they are aware of this issue, there is an PR open and it is being worked on.
On what occasions do you use one rather than the other?
Hello,
i want to ask the community what steps to do in order to move a windows host vm to MacOs.
The prerequisites are:
Windows 10VM on Windows 10 host. The VM is splitted into multiple files.
On MacOS i guess i need to install Fusion (?).
What should i do in order to move the VM to MacOS ? Just copy the folder over network ?
Should i clone it in 1 file or not ?
Are there any stumble blocks, except to say "I moved it" when migrating on MacOS ?
Thank you for your thoughts.
Yes, vRO 7.3 should work with vSphere 6.0 as authentication provider. I just checked it in my lab, and was able to configure vSphere 6.0 GA as authentication provider without issues.
You can ignore API mismatch warnings.
Please attach the logs as files (screenshot is not complete). Also, please provide more info, like the vSphere build number, what was the authentication set to before you tried to change it to vsphere, screenshots with the steps you did to configure it, etc.
Yes, you need to install Fusion on the macOS host.
You have to add a .vmwarevm extension to the Windows folder of your Windows 10 VM on Windows 10. And just simply copy over to the Mac that entire folder. I used external disk instead of network copy but the difference is probably just the speed.
As for answering "I moved it" or "I copied it", from my experience, the difference between the two was one re-prompted for the Windows 7 key (my Windows 10 VM was an upgrade from a Windows 7 laptop converted to VM) and I just had to re-enter the original Windows 7 key to reactivate the Windows 10 licence. I think it was the "I copied it" that prompted for the key.
For more details you can look at this
Using VMware Workstation virtual machines in VMware Fusion (1002320) | VMware KB
Anybody there ?
I used to face this similar problem, albeit inconsistently, when I was using a Windows 8.1 host. Back then, I just didn't bother to find out what was wrong as it was not consistent.
You could try to look at the vmware logs at
%TEMP%\VMware\vmware-%USERNAME%
Maybe start with the vmware-ui-nnnn.log where nnnn is a process ID number.