Re: Workstation 14 on Windows 10 - All VMs have a red X.
Re: Windows Me não enxerga a rede
Oi Diego,
Uma mistura de Hobby, saudosismo e desafio técnico.
Meu hobby é brincar com sistemas operacionais antigo e botar para rodar milhares de dólares em softwares que hoje estão de graça, só para ver como é.
Saudosismo porque o Windos Me foi o primeiro OS que eu comprei, a muito tempo atrás, e queria ver ele funcinando a todo vapor novmente.
Desafio técnico porque fazer o Me dava pau até quando vinha já instalado na máquina. Mas não deu bug nenhum...
Obrigado pela dica. Respondeu, Vou atrás do VMWare 9.0 então.
Abraços,
Lorenzo.
Re: Assistance with scrip to bulk set Perennially Reservations using Get-ESXCLi
Hi Luc,
I also tried to set perennial-reserved=true flag to the rdm disk that belongs to virtual machine on all hosts in that cluster. When i tried to use your script, i got the error below. I think it is related with the get-esxcli usage. It does not return the elements of command. I really appreciated if you help me. Thanks
PS C:\Users\> $esxcli = Get-EsxCli -VMHost $esx -V2
PS C:\Users\> $esxcli
===================
EsxCli: 10.x.x.x
No elements here
Error:
You cannot call a method on a null-valued expression.
+ $esxcli.storage.core.device.setconfig($false,$rdm.ScsiCanonicalNa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull
Regards
Hamza
Re: Assistance with scrip to bulk set Perennially Reservations using Get-ESXCLi
When you use the V2 switch, the way to call the methods and pass the arguments is different.
Have a read through PowerCLI 6.3 R1: Get-ESXCLI Why the V2?
Re: Assistance with scrip to bulk set Perennially Reservations using Get-ESXCLi
Hi Luc,
Actually the same without V2 parameter, i also tried with this and same result. What do you suggest about Get-EsxCli command? I think this is the problem why script gives this error. The value returns none elements. On blogs i saw the elements should appear when you check the $esxcli. I can not find the reason of that.
$vmName = "myvm"
$vm = Get-VM -Name $vmName
$rdm = Get-HardDisk -DiskType rawPhysical -Vm $vm
$vmhosts = Get-Cluster -VM $vm | Get-VMHost
foreach($esx in $vmhosts){
$esxcli = Get-EsxCli -VMHost $esx
Get-HardDisk -DiskType rawPhysical -Vm $vm | %{
$esxcli.storage.core.device.list($rdm.ScsiCanonicalName) |
Select @{N="Time";E={"{0:g}" -f (Get-Date).TimeOfDay}},Device,IsPerenniallyReserved
$esxcli.storage.core.device.setconfig($false,$rdm.ScsiCanonicalName,$true)
$esxcli.storage.core.device.list($rdm.ScsiCanonicalName) |
Select @{N="Time";E={"{0:g}" -f (Get-Date).TimeOfDay}},Device,IsPerenniallyReserved
}
}
Re: 3d App crashes VMWare Fusion Windows app but Parallels works fine
attached.
i looked through it and didn't see any references to the graphics drivers, but then i could have overlooked it.
Dave
Re: Assistance with scrip to bulk set Perennially Reservations using Get-ESXCLi
Are you saying $esxcli is empty after the Get-EsxCli cmdlet?
Can Workspace ONE enroll third party smart watch ?
Hi All,
I have a one partner in Taiwan that the name of partner is Askey.
They develop the smart watch by themself who would like to know their smart watch can enroll to Workspace ONE or not ?
If you have any reference information like this project, please share with me, thanks.
Re: Assistance with scrip to bulk set Perennially Reservations using Get-ESXCLi
Yes it is empty. My hosts are 6.5.0.
PS C:\Users\t> $esxcli = Get-EsxCli -VMHost $esx
PS C:\Users\t> $esxcli
===================
EsxCli: 10.x.x.x
PS C:\Users\tasksch.000> $PSVersionTable
Name Value
---- -----
PSVersion 5.1.14409.1005
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14409.1005
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Re: Fail to logging via web client vcenter 6.5
you don’t confused. administrator@vsphere.local is default account in vCenter this will alway Loging if password not expired or something strange issue. So you can focus on the issue what you are facing. Please check as I said earlier... Also, the local user which created have access in vCenter that also check...
Vmware Workstation and Device/Credential Guard are not compatible.
I have now read just about all the threads on this and have exhausted all solutions. Is this still a problem with others.
Windows 10 PRO 1903 OS Build 18363.720
VMware® Workstation 15 Pro 15.5.2 build-15785246
Re: Windows 10 crashed with bugcheck at vmx86.sys
Its so annoying..loosing data cause of this
Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`55000000 PsLoadedModuleList = 0xfffff802`55448150
Debug session time: Sat Apr 11 15:12:43.332 2020 (UTC + 2:00)
System Uptime: 2 days 4:52:55.718
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`551c2380 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`5a075b10=0000000000000101
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffa48079820180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on CHAOS10
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 7
Key : Analysis.Memory.CommitPeak.Mb
Value: 66
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 101
BUGCHECK_P1: 10
BUGCHECK_P2: 0
BUGCHECK_P3: ffffa48079820180
BUGCHECK_P4: 1
FAULTING_PROCESSOR: 1
PROCESS_NAME: vmware-vmx.exe
FAULTING_THREAD: ffffb588a7940080
STACK_TEXT:
ffff9f84`164bc4a8 fffff802`5b148308 : ffffa480`79820180 fffff802`55121385 ffffb588`98a68220 00000000`00000000 : vmx86+0x100a
ffff9f84`164bc4b0 fffff802`5b14abd3 : ffffb588`a8050160 00000000`00000000 ffffa480`7bd28000 00000000`0000006b : vmx86+0x8308
ffff9f84`164bc5f0 fffff802`5b141f4e : ffff9f84`164bc978 00000000`00000000 ffff9f84`164bc978 ffffb588`86e02000 : vmx86+0xabd3
ffff9f84`164bc6c0 fffff802`5b14298e : 00000000`00000000 fffff802`553543a9 ffffb588`abe58cc0 fffff802`551132e4 : vmx86+0x1f4e
ffff9f84`164bc8a0 fffff802`556b24eb : 00000000`000003e4 00000000`00000001 00000000`00000000 ffffb588`ab9b07a0 : vmx86+0x298e
ffff9f84`164bc900 fffff802`556b1db6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x71b
ffff9f84`164bca20 fffff802`551d3c18 : 00000000`00000000 ffff9f84`00000001 00000000`000003e4 ffff9f84`164bcb80 : nt!NtDeviceIoControlFile+0x56
ffff9f84`164bca90 00007ffc`d5bdc1a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000c0`c61ffcd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`d5bdc1a4
STACK_COMMAND: .thread 0xffffb588a7940080 ; kb
SYMBOL_NAME: vmx86+100a
MODULE_NAME: vmx86
IMAGE_NAME: vmx86.sys
BUCKET_ID_FUNC_OFFSET: 100a
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_vmx86!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e206f958-3924-e3cb-af92-ab296be9b5e9}
Followup: MachineOwner
Re: Assistance with scrip to bulk set Perennially Reservations using Get-ESXCLi
The $esxcli variable is not empty, it seems to show your ESXi node (EsxCli: 10.x.x.x).
But normally it should also show the elements
======================
EsxCli: esx12.local.lab
Elements:
---------
device
esxcli
fcoe
graphics
hardware
iscsi
network
nvme
rdma
sched
software
storage
system
vm
vsan
Are you connected to a vCenter?
Which PowerCLI version are you using?
Do other PowerCLI cmdlets on that ESXi node work? The New-VM cmdlet for example?
Blue Screen caused by vmx86.sys VM Workstation 15.5.2
It started begin of this year that I got a bluescreen cause of vmware workstation vmx86.sys
i m not sure, if it was the moment, where i upgraded to 15.5
but it is now 2 or 3 times per week, since i upgraded to 15.5.2
surely all 40gb ram and also the processor have had done checks under highload, without any fault
google found this error several times over the last years, but never a solution
i lost now 2 times my database running inside, one time even ubuntun was damaged
maybe now someone can fix it please...
Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`55000000 PsLoadedModuleList = 0xfffff802`55448150
Debug session time: Sat Apr 11 15:12:43.332 2020 (UTC + 2:00)
System Uptime: 2 days 4:52:55.718
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`551c2380 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`5a075b10=0000000000000101
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffa48079820180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on CHAOS10
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 7
Key : Analysis.Memory.CommitPeak.Mb
Value: 66
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 101
BUGCHECK_P1: 10
BUGCHECK_P2: 0
BUGCHECK_P3: ffffa48079820180
BUGCHECK_P4: 1
FAULTING_PROCESSOR: 1
PROCESS_NAME: vmware-vmx.exe
FAULTING_THREAD: ffffb588a7940080
STACK_TEXT:
ffff9f84`164bc4a8 fffff802`5b148308 : ffffa480`79820180 fffff802`55121385 ffffb588`98a68220 00000000`00000000 : vmx86+0x100a
ffff9f84`164bc4b0 fffff802`5b14abd3 : ffffb588`a8050160 00000000`00000000 ffffa480`7bd28000 00000000`0000006b : vmx86+0x8308
ffff9f84`164bc5f0 fffff802`5b141f4e : ffff9f84`164bc978 00000000`00000000 ffff9f84`164bc978 ffffb588`86e02000 : vmx86+0xabd3
ffff9f84`164bc6c0 fffff802`5b14298e : 00000000`00000000 fffff802`553543a9 ffffb588`abe58cc0 fffff802`551132e4 : vmx86+0x1f4e
ffff9f84`164bc8a0 fffff802`556b24eb : 00000000`000003e4 00000000`00000001 00000000`00000000 ffffb588`ab9b07a0 : vmx86+0x298e
ffff9f84`164bc900 fffff802`556b1db6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x71b
ffff9f84`164bca20 fffff802`551d3c18 : 00000000`00000000 ffff9f84`00000001 00000000`000003e4 ffff9f84`164bcb80 : nt!NtDeviceIoControlFile+0x56
ffff9f84`164bca90 00007ffc`d5bdc1a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000c0`c61ffcd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`d5bdc1a4
STACK_COMMAND: .thread 0xffffb588a7940080 ; kb
SYMBOL_NAME: vmx86+100a
MODULE_NAME: vmx86
IMAGE_NAME: vmx86.sys
BUCKET_ID_FUNC_OFFSET: 100a
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_vmx86!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e206f958-3924-e3cb-af92-ab296be9b5e9}
Followup: MachineOwner
Re: Find unused vmnic
Re: Fail to logging via web client vcenter 6.5
Ensure the password foruser@vsphere.local contains only ASCII characters. Here is kb for similar issue.
VMware Knowledge Base
Re: Find unused vmnic
Looks like you might have switches with no pNICs connected.
Add a test for that.
$esx=Get-VMHost MyEsx
$esx.ExtensionData.Config.Network.Pnic|%{
$nicTab.Add($_.Key,$_.Device)
}
# Regular switches
$esx.ExtensionData.Config.Network.Vswitch|%{
$_.Pnic|%{
if($_){
$nicTab.Remove($_)
}
}
}
# dvSwitches
$esx.ExtensionData.Config.Network.ProxySwitch|%{
$_.Pnic|%{
if($_){
$nicTab.Remove($_)
}
}
}
# What is left ?
$nicTab.GetEnumerator()
Re: Assistance with scrip to bulk set Perennially Reservations using Get-ESXCLi
I am connected to Vcenter, other cmdlets are working (Get-Cluster, Get-VMhost, New-VM..etc). Get-EsxCli is the same for all hosts, i also tried on other hosts. It does not bring the elements as you show. I tried with PowerCLI version 6.3, 6.5 and finally i upgraded to 12.0 latest version. But it is the same. I also search on Google but nothing found.
Is another way possible to set perennial-reserved flag to true, another cmdlet maybe?
PowerCLI Version
----------------
VMware PowerCLI 12.0.0 build 15947286
PS C:\Users\t> New-VM
cmdlet New-VM at command pipeline position 1
Supply values for the following parameters:
Name:
Re: Assistance with scrip to bulk set Perennially Reservations using Get-ESXCLi
You can always do an SSH session to the ESXi node and run the esxcli command on there.
Re: Assistance with scrip to bulk set Perennially Reservations using Get-ESXCLi
Actually this is the method i am using now but for big clusters it is really hard to do it one-by-one. I mean another cmdlet in powercli to set the flag.