Although version 7.0 comes with a couple of changes, enhancements, and new features (especially in vCenter Server), I still think that version 6.7 is still excellent for learning purposes. Depending on your hardware, you may even be able to install ESXi 7.0 as a virtual machine on the ESXi 6.7 host. Setting up a virtual environment on ESXi, or VMware Workstation is actually what a lot of people do to run home labs.
André
Hi,
You also need to change the size of the disk via Disk Utility in the guest OS.
See this post for more details:
--
Wil
hi, the host is windows 10
the tools were installed automatically.
see attached from Manage log.
thanks,
That may very well be it. Try using the actual Apple power adapter that came with it, and see if that solves the problem.
You'll definitely need to upgrade to Fusion 11.5 to get it to run on Catalina.
Time machine is not a reliable method to backup/move virtual machines, so if you're using the migration wizard, do it direct, machine to machine, or clone to an external drive with Carbon Copy Cloner, and then migrate from it.
Here's the steps
1) Shut down (not suspend) the VM on the old machine
2) Delete/commit any snapshots on the old machine
3) Do the migration
4) Uninstall Fusion 8 (drag it to the trash, if it even migrated) on the new machine
5) install Fusion 11.5.x
6) Run Fusion, follow the security prompts carefully
7) Start the virtual machine - it'll prompt you to upgrade the virtual hardware, do so
8) If the VMWare tools upgrade process doesn't start automatically, do it manually from the menu
Then I'd exclude the virtual machine folder from time machine, and make other backup arrangements. Wil (a top poster here) has a great tool to do that if you want something automated. Otherwise, using finder when the VM is shut down, to drag a copy to an external drive periodically is the manual option.
Horizon Client 5.4.3 for Windows 7.
Finally I found that the reason is privilege of windows account.
When I change to Administrator account the installation goes well.
Thank you.
Hi hacknetik1 ,
Have you ever set packet loss to the VM? This could be checked via VM settings -> Network Adapter -> Advances Options.
Hi, can you please collect vmware tools support as it says in capture and upload the log
We have published a blog explaining steps for VDI capacity planning with view planner:
VDI Capacity Planning with View Planner - VMware VROOM! Performance Blog
We have published a new blog explaining view planner reports:
Understanding the View Planner Report - VMware VROOM! Performance Blog
Hello Dave,
If you run the next command what does it shows you: software-packages list --staged --verbose
Also you can run the whole patch from the VAMI. Simply follow the next procedure which is really short: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.upgrade.doc/GUID-FF533442-66F0-4797-976D-1DA99102DD0A.html
Please upgrade to WS latest branch. I can not reproduce this issue with WS 15.5.6 and Win10 2004 HOS/GOS.
Thanks
This seems to be one of those timeless problems that keeps coming back across versions.
In my homelab errors popped up out of nowhere: Lost access to volume 5f48d732-cdc8d5db-14d9-0cc47ac9b978 (local-ssd) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.
I did some checks with smartctl and it looked like of my ssd's was turning bad (some pending sectors) so I replaced the SSD with a new EVO 860 but to my surprise the errors kept on coming. I tried disabling the VMFS reclaim option which didn't help.
Was using this version of ESXi 6.7:
esxcli software vib list | grep ahci with build-16316930
sata-ahci 3.0-26vmw.670.0.0.8169922 VMW VMwareCertified 2019-06-08
vmw-ahci 1.2.8-1vmw.670.3.73.14320388 VMW VMwareCertified 2019-12-22
grepping the vmkernel log gave me hope reading through the 2020-08 6.7 patch release notes because I was seeing these errors:
| vmkernel.log |
|---|
[root@labhost:/vmfs/volumes/5a4894b1-dd26f0cc-1182-0cc47ac9b978/patches] cat /var/log/vmkernel.log | grep vmw_ahci 2020-09-02T06:20:13.255Z cpu6:2097972)vmw_ahci[0000001f]: scsiTaskMgmtCommand:VMK Task: VIRT_RESET initiator=0x430458b8b940 2020-09-02T06:20:13.255Z cpu6:2097972)vmw_ahci[0000001f]: ahciAbortIO:(curr) HWQD: 0 BusyL: 0 2020-09-02T07:08:27.784Z cpu17:2107862)vmw_ahci[00000011]: HBAIntrHandler:new interrupts coming, PxIS = 0x8, no repeat 2020-09-02T12:50:26.982Z cpu17:2158172)vmw_ahci[0000001f]: scsiTaskMgmtCommand:VMK Task: ABORT sn=0x7475a5 initiator=0x430458b8b940 2020-09-02T12:50:26.982Z cpu17:2158172)vmw_ahci[0000001f]: ahciAbortIO:(curr) HWQD: 27 BusyL: 27 2020-09-02T12:50:27.980Z cpu6:2097972)vmw_ahci[0000001f]: scsiTaskMgmtCommand:VMK Task: VIRT_RESET initiator=0x430858ee9340 2020-09-02T12:50:27.980Z cpu6:2097972)vmw_ahci[0000001f]: ahciAbortIO:(curr) HWQD: 27 BusyL: 27 2020-09-02T12:50:31.981Z cpu8:2158172)vmw_ahci[0000001f]: LogExceptionSignal:Port 0, Signal: --|--|--|AB|--|--|--|--|--|--|--|-- (0x0008) Curr: --|--|--|--|--|--|--|--|--|--|PR|-- (0x0400) 2020-09-02T12:50:33.115Z cpu0:2097689)vmw_ahci[0000001f]: ExecInternalCommandPolled:FAIL!!: Internal command b0, 00 2020-09-02T12:50:33.115Z cpu0:2097689)vmw_ahci[0000001f]: LogExceptionProcess:Port 0, Process: --|--|--|AB|--|--|--|--|--|--|--|-- (0x0008) Curr: --|--|--|AB|--|--|--|--|--|--|--|-- (0x0008) 2020-09-02T12:50:33.115Z cpu0:2097689)vmw_ahci[0000001f]: ExceptionHandlerWorld:AHCI_SIGNAL_ABORT_REQUEST signal. 2020-09-02T12:50:33.115Z cpu0:2097689)vmw_ahci[0000001f]: ProcessAbortRequest:Aborting command tag 4 from the Busy list 2020-09-02T12:50:33.115Z cpu0:2097689)vmw_ahci[0000001f]: ProcessAbortRequest:aborted command I:0x430458b8b940 SN:0x7475a5 tag:4 2020-09-02T12:50:33.115Z cpu0:2097689)vmw_ahci[0000001f]: ExceptionHandlerWorld:Abort scan took 6 (us) to complete, 0 commands aborted. 2020-09-02T12:50:33.116Z cpu9:2097972)vmw_ahci[0000001f]: LogExceptionSignal:Port 0, Signal: --|--|--|AB|--|--|--|--|--|--|--|-- (0x0008) Curr: --|--|--|--|--|--|--|--|--|--|--|-- (0x0000) 2020-09-02T12:50:33.116Z cpu0:2097689)vmw_ahci[0000001f]: LogExceptionProcess:Port 0, Process: --|--|--|AB|--|--|--|--|--|--|--|-- (0x0008) Curr: --|--|--|AB|--|--|--|--|--|--|--|-- (0x0008) 2020-09-02T12:50:33.116Z cpu0:2097689)vmw_ahci[0000001f]: ExceptionHandlerWorld:AHCI_SIGNAL_ABORT_REQUEST signal. 2020-09-02T12:50:33.116Z cpu0:2097689)vmw_ahci[0000001f]: ProcessAbortRequest:aborted command I:0x430858ee9340 SN:0xc8718ac8 tag:5 2020-09-02T12:50:33.116Z cpu0:2097689)vmw_ahci[0000001f]: ProcessAbortRequest:aborted command I:0x430858ee9340 SN:0xc871bed0 tag:6 2020-09-02T12:50:33.116Z cpu0:2097689)vmw_ahci[0000001f]: ProcessAbortRequest:aborted command I:0x430858ee9340 SN:0xc8717d90 tag:25 2020-09-02T12:50:33.116Z cpu0:2097689)vmw_ahci[0000001f]: ExceptionHandlerWorld:Abort scan took 10 (us) to complete, 3 commands aborted. 2020-09-02T12:50:33.117Z cpu0:2097689)vmw_ahci[0000001f]: _IssueComReset:Issuing comreset... 2020-09-02T12:50:33.125Z cpu0:2097689)vmw_ahci[0000001f]: IssueCommand:tag: 20 already active during issue, reissue_flag:1 2020-09-02T12:50:33.125Z cpu0:2097689)vmw_ahci[0000001f]: IssueCommand:tag: 21 already active during issue, reissue_flag:1 2020-09-02T12:50:33.125Z cpu0:2097689)vmw_ahci[0000001f]: IssueCommand:tag: 22 already active during issue, reissue_flag:1 2020-09-02T12:50:33.125Z cpu0:2097689)vmw_ahci[0000001f]: IssueCommand:tag: 23 already active during issue, reissue_flag:1 2020-09-02T12:50:33.125Z cpu0:2097689)vmw_ahci[0000001f]: IssueCommand:tag: 24 already active during issue, reissue_flag:1 2020-09-02T12:50:33.125Z cpu0:2097689)vmw_ahci[0000001f]: IssueCommand:tag: 26 already active during issue, reissue_flag:1 2020-09-02T12:50:33.125Z cpu0:2097689)vmw_ahci[0000001f]: IssueCommand:tag: 27 already active during issue, reissue_flag:1 2020-09-02T12:50:33.125Z cpu0:2097689)vmw_ahci[0000001f]: ProcessActiveCommands:Commands completed: 0, re-issued: 7 2020-09-02T12:50:33.126Z cpu11:2097972)vmw_ahci[0000001f]: scsiTaskMgmtCommand:VMK Task: VIRT_RESET initiator=0x430858ebc800 2020-09-02T12:50:33.126Z cpu11:2097972)vmw_ahci[0000001f]: ahciAbortIO:(curr) HWQD: 0 BusyL: 0 2020-09-02T12:50:33.128Z cpu11:2097972)vmw_ahci[0000001f]: scsiTaskMgmtCommand:VMK Task: VIRT_RESET initiator=0x430858eba200 2020-09-02T12:50:33.128Z cpu11:2097972)vmw_ahci[0000001f]: ahciAbortIO:(curr) HWQD: 0 BusyL: 0 2020-09-02T12:50:33.130Z cpu11:2097972)vmw_ahci[0000001f]: scsiTaskMgmtCommand:VMK Task: VIRT_RESET initiator=0x430458b8b940 2020-09-02T12:50:33.130Z cpu11:2097972)vmw_ahci[0000001f]: ahciAbortIO:(curr) HWQD: 0 BusyL: 0 2020-09-02T12:50:33.132Z cpu9:2097972)vmw_ahci[0000001f]: scsiTaskMgmtCommand:VMK Task: VIRT_RESET initiator=0x430858ebc4c0 2020-09-02T12:50:33.132Z cpu9:2097972)vmw_ahci[0000001f]: ahciAbortIO:(curr) HWQD: 0 BusyL: 0 2020-09-02T12:50:33.134Z cpu9:2097972)vmw_ahci[0000001f]: scsiTaskMgmtCommand:VMK Task: VIRT_RESET initiator=0x430858edbdc0 2020-09-02T12:50:33.134Z cpu9:2097972)vmw_ahci[0000001f]: ahciAbortIO:(curr) HWQD: 0 BusyL: 0 2020-09-02T12:50:33.136Z cpu9:2097972)vmw_ahci[0000001f]: scsiTaskMgmtCommand:VMK Task: VIRT_RESET initiator=0x430458b8b940 2020-09-02T12:50:33.136Z cpu9:2097972)vmw_ahci[0000001f]: ahciAbortIO:(curr) HWQD: 0 BusyL: 0 2020-09-02T14:07:30.319Z cpu15:2108092)vmw_ahci[0000001f]: AHCI_EdgeIntrHandler:new interrupts coming, IS= 0x1, no repeat 2020-09-02T14:07:51.959Z cpu13:2097204)vmw_ahci[0000001f]: AHCI_EdgeIntrHandler:new interrupts coming, IS= 0x1, no repeat 2020-09-02T14:08:16.168Z cpu0:2107827)vmw_ahci[0000001f]: AHCI_EdgeIntrHandler:new interrupts coming, IS= 0x1, no repeat 2020-09-02T14:16:53.668Z cpu16:2097207)vmw_ahci[0000001f]: AHCI_EdgeIntrHandler:new interrupts coming, IS= 0x1, no repeat 2020-09-02T14:17:00.628Z cpu2:2097193)vmw_ahci[0000001f]: AHCI_EdgeIntrHandler:new interrupts coming, IS= 0x1, no repeat 2020-09-02T14:17:07.235Z cpu15:2097206)vmw_ahci[0000001f]: AHCI_EdgeIntrHandler:new interrupts coming, IS= 0x1, no repeat 2020-09-02T15:50:44.368Z cpu16:2097689)vmw_ahci[0000001f]: ExecInternalCommandPolled:FAIL!!: Internal command ec, 00 2020-09-02T23:21:35.836Z cpu0:2172046)vmw_ahci[00000011]: AHCI_EdgeIntrHandler:new interrupts coming, IS= 0x2, no repeat 2020-09-03T12:51:09.420Z cpu8:2097689)vmw_ahci[0000001f]: ExecInternalCommandPolled:FAIL!!: Internal command ec, 00 2020-09-03T14:32:24.865Z cpu7:2158172)vmw_ahci[00000011]: scsiTaskMgmtCommand:VMK Task: ABORT sn=0x652b initiator=0x430458b81bc0 2020-09-03T14:32:24.865Z cpu7:2158172)vmw_ahci[00000011]: ahciAbortIO:(curr) HWQD: 4 BusyL: 0 |
Since then I updated the host which updated the vmw_ahci driver to this version:
esxcli software vib list | grep ahci with build-16316930
esxcli software vib list | grep ahci with build-16713306
sata-ahci 3.0-26vmw.670.0.0.8169922 VMW VMwareCertified 2019-06-08
vmw-ahci 2.0.5-1vmw.670.3.116.16713306 VMW VMwareCertified 2020-09-03
The errrors have not come back since then ( *knocks on wood)
Not a lot information on this error on the net about this potentially could point to a vmware driver error so sharing my experience here
Moderator: Thread moved to the Workstation Player area.
Hello folks,
I am dealing with the "deletion in progress"status in multiple objects such as Segments and Tier-0. I went over every single place on the NSX-T Global Interface and to each local region but i cannot find any relationship with these objects and it is saying that they are already deleted but they are still in the UI.
I went over the API Reference guide to look for maybe some orphaned existing relationships between the objects but i could not find anything. I went over:
If i try to get the information from the objects using the header "include_mark_for_delete_objects" on the API Calls i can see that the objects are still there and when i try to delete them with force options or using X-Allow-Overwrite=true (For policy objects) it just says that the object does not exists.
Any ideas?
Добрый день, имеется ESXi_test, который стоит на "боевом" ESXi (вложенная виртуализация. Не спрашивайте зачем и почему, так нужно, это личная тестовая среда). Поставил виртуальную машину, ОС Windows 10 на ESXi_test, сетевой адаптер в моем случае один единственный, что на "боевом" ESXi, что на тестовом - дефолтный VM network. По логике работы, сеть должна работать в режиме бриджа. Моя виртуалка получила IP адрес по DHCP, но с виртуалки сеть не доступна. Не пингуется ни основной шлюз, ни другие тачки. Так же, с других тачек не пингуется данная виртуалка. Подскажите пожалуйста, может в таких случаях есть какие то ньюансы?
Thanks for letting me know. I think I may build a host running 6.7 to see if that helps.
Thanks!
Scott
Добрый день, столкнулся с такой проблемой, Виртуальная машина не забэкапилась, еще и затерла старые бекапы.
2020-09-06 23:48:21 -- info: Initiate backup for SmartGen_DatakomRus
2020-09-06 23:48:21 -- info: Creating Snapshot "ghettoVCB-snapshot-2020-09-06" for SmartGen_DatakomRus
2020-09-06 23:50:57 -- info: ERROR: error in backing up of "/vmfs/volumes/datastore1/VMBitrix5.1.8-x86_64/VMBitrix5.1.8-x86_64.vmdk" for SmartGen_DatakomRus
2020-09-06 23:51:05 -- info: Removing snapshot from SmartGen_DatakomRus ...
2020-09-06 23:51:05 -- info: Backup Duration: 2.73 Minutes
2020-09-06 23:51:05 -- info: ERROR: Unable to backup SmartGen_DatakomRus due to error in VMDK backup!
Остановил машину, залез сделать бекап вручную простым копированием "cp" и так же не дало сделать. Ошибка:
cp read error input/output error
Другие машины бекапятся и работают без проблем. Эта машина работает, но скопировать я ее не могу, подскажите как быть?
Version:
5.5.0 Update 3 (Build 3568722)
Hi LuCD
I am trying to pull the same report for storage path as like Network device. Can you please help to provide your inputs to correct the lines.
esxcli.storage.core.path.list [ESXi host Name Adapter Device LUN ID LUN State Target Runtime Name]
Get-VMHost -PipelineVariable esx |
ForEach-Object -Process {
$esxcli = Get-EsxCli -VMHost $esx -V2
$esxcli.storage.core.path.list.Invoke() |
ForEach-Object -Process {
$storage = $_
$Storage.adapter | where{$_ -ne $null} | %{
$path = $_
$StorAdapt = Get-VMHostHba -VMHost $esxcli.VMHost -Name $path
$storList = $esxcli.storage.core.path.list.Invoke() | where{$_.Name -eq $path}
$esxcli.storage.core.path.get.Invoke(@{storname="$_"}) |
Select @{N='VMHost';E={$esx.Name}},
@{N='Adapter';E={$storList.Adapter}},
@{N='Device';E={$storList.Device}},
@{N='LUN ID';E={$storList.LUN}},
@{N='Target';E={$storList.Target}},
@{N='LUN State';E={$storList.State}},
@{N='Plugin';E={$storList.Plugin}},
@{N='Runtime Name';E={$storList.RuntimeName}}
}
}
} | Format-Table -Autosize
Hi LucD,
Thanks for the reply.
Tried the above script and got this output (:
