This is exactly the issue. Thanks for pointing that out. I never even thought to look into whether or not there was another macOS / darwin iso floating around. So VMware needs to either get rid of that iso or work on their detection logic! After mounting the correct darwin.iso it installed perfectly.
Unfortunately Unity display is still not working.
hi brother：
what‘s it ？ I couldn't see ！
I have Workstation Pro 12.5.4 and Fusion 8.5.5 and each have one guest VM that is Windows 10 x64 Professional (both upgraded to W10 from W7 laptops that were converted to VMs).
Oddly enough, if the "Accelerate Graphics" is not checked in the display properties of the VMs, dxdiag reports a higher DX feature level support for the guest VMs.
I am not aware of any free and readily available software to test and verify the DX feature level properties other than dxdiag.
Driver Version: 8.15.1.50
(with Accelerate Graphics checked on both Workstation Pro and Fusion VMs)
DDI Version: 10
Feature Levels: 10_0,9_3,9_2,9_1
(with Accelerate Graphics unchecked on Workstation Pro VM)
DDI Version: 11.2
Feature Levels: 11_1,11_0,10_1,10_0,9_3,9_2,9_1
(with Accelerate Graphics unchecked on Fusion 8.5.5 VM)
DDI Version: 12
Feature Levels: 11_1,11_0,10_1,10_0,9_3,9_2,9_1
So two things you may want to do/check:
(1) you may want to make sure that "Accelerate Graphics" is checked in the Display properties of the VM.
(2) you may also want to check the actual feature level required for the software that you want to run as dxdiag reports 10_0 but there is a 10_1 feature level
Not sure if VMware reads these or if there's a better forum for these complaints, but I've been seeing poor performance in my Windows 10 VM as well which I think started with the upgrade to Fusion 8. I've been using Fusion for a long time (since version 2 or 3) and have bought every version along the way. I've stuck with VMware partly because I don't like some of Parallels' upgrade practices but between problems like this, the issues with sleeping the Mac with a VM running, and the laying off of the UI team it's getting harder to justify sticking on the Fusion path.
I've been using Parallels on a work machine for the past few months -- not a fair comparison exactly because that's a brand new install of Win10 but its performance is pretty much indistinguishable from native. Like I said, getting harder to keep using Fusion...
Hi All,
What all the things must be noted before updating patch to esxi server ,and what are the backup need to be done .
Thanks,
Hi,
I forgot to mention the VMs will be shutdown and migrate as we have no choice; we have to take the downtime hit. There are only 20 VMs averaging 150GB disk space. Some Hosts are in a cluster while other are in stand alone ESXi.
So the plan is to not live SVM but to migrate them to the NAS and as you stated below.
So to be sure cold migrate is supported correct?
May also look into Veeam for doing this as well.
Thanks
Jeff
Yeah its a typo, not in the actual script.
foreach ($line in $csv)
{
#################################################################################
# Set Variables
#################################################################################
$vmhost_user = "user"
$vmhost_pass = "pass "
$newhost = $line.Host
$host_IP = $line.IP
$san0 = $line.SAN0
$san1 = $line.SAN1
$subnet = $line.Subnet
$gateway = $line.Gateway
$mgmt = $line.ManagementIP
$ntp = $line.NTP
$dns1 = $line.DNS1
$dns2 = $line.DNS2
#################################################################################
# Connect to Hosts
#################################################################################
Write-Host "Connecting to $newhost ESXi Host!" -ForegroundColor Green
Connect-VIServer $newhost -User $vmhost_user -Password $vmhost_pass
#################################################################################
# Get VMKernel PortGroup and Assign IP and Subnet4
#################################################################################
Write-Host "Find the VMKernel PortGroup on Host $newhost and Assign New IP and Subnet to it!" -ForegroundColor Green
$vmkernel0 = Get-VMHostNetworkAdapter $newhost | where { $_.PortGroupName -eq "SAN 0" }
Set-VMHostNetworkAdapter -VirtualNIC $vmkernel0 -IP "$san0" -SubnetMask "$subnet" -confirm:$False
##Dont Test With This One##
#$vmkernel1 = Get-VMHostNetworkAdapter | where { $_.PortGroupName -eq "SAN 1" }
#Set-VMHostNetworkAdapter -VirtualNIC $vmkernel0 -IP "$san0" -SubnetMask "$subnet" -confirm:$False
#################################################################################
# Assign NTP Server Information and Configure NTP Settings
#################################################################################
Write-Host "Configuring NTP and Enabling Auto-Start!" -ForegroundColor Green
Get-VMHost $newhost | Add-VMHostNtpServer -NtpServer $ntp
Get-VmHostService -VMHost $newhost | Where-Object {$_.key -eq "ntpd"} | Start-VMHostService
Get-VmHostService -VMHost $newhost | Where-Object {$_.key -eq "ntpd"} | Set-VMHostService -policy "automatic"
################################################################################
# Disconnect Each Host After Configuration
#################################################################################
Disconnect-VIServer $newhost
Hello Jeff,
If you can attach the NAS to both sites (5.1 environment hosts and the 6.5 vSAN cluster) having a shared vCenter is not necessary.
And yes, cold-migrating these VMs to NAS/other datastore and then to vSAN is supported.
I also thought of mentioning that (but was unsure of what you had available), if you have Veeam or something else that can do full-backup and restore, you could pull from the existing cluster and have vSAN datastore as target (but again, this is likely going to be using the same shared-storage as doing it manually).
Bob
-o- If you found this comment useful or answer please select as 'Answer' and/or click the 'Helpful' button, please ask follow-up questions if you have any -o-
No dice Luc.
I have the impression you are connected to multiple vSphere servers at once.
Can you display the contents of $global:defaultviservers in the script to check?
Update: you could perhaps also add the -Verbose switch on the Connect-ViServer and Disconnect-ViServer to see what is happening there.
And perhaps show the output of the script
Yeah thats my impression as well, which is why I included the Disconnect-VIServer command.
Ill run the verbose options through and see what it says.
Running guest Windows Server 2012 R2 with Exchange 2016 in an ESXi 6.0 host. The issue I'm experiencing is a long time it takes for the server to start responding after each reboot. The guest will reboot, come up, allow me to log in and interact with it. However, it will takes several minutes (~10) past that before the server starts responding to external clients, even an RDP login. The built-in soft firewall is disabled on the domain network since I have a hardware firewall at the gateway.
When I log into the console right after a reboot but before the server is responsive on the network, any network-relate features such as the "Network and Sharing Center" or "Windows Firewall" don't come up. Blank windows just sit there for a few minutes in a "loading" phase and then they come up simultaneously to the server becoming responsive on the network.
I have another 2012 Server on the SAME esxi host and that one works fine! It's just this one with Exchange on it.
Guest: 2 x QuadCore Intel Xeons 2.266GHz / 32 GB RAM / 500 GB Storage
$global:defaultviservers shows two vCenters connected.
Do I need to force a Disconnect-VIServer?
force, no.. just use Disconnect-VIServer $newhost -confirm:$false as Luc shared earlier.
I just got into the same situation;
Folder: "vmdkdump" & File: ""xxxxx-xxxxx-xxxxxx-xxxxx.dumpfile" stuck in one of 16 LUNs I was deleting.
I tried all my tricks but nothing worked out, so this is what I did if anyone needs to get rid of this file in order to remove datastore from a host.
NOTE:
Make sure you delete the ".dumpfile" & "vmkdump" before removing the datastore.
Enable SSH on all the host to find out which one got the "Active value of true and Configured value of true" It is an "active core dump file"
So how to find out?
1. Run the following command from all the host until one of them display "Active value of true and Configured value of true"
EXAMPLE:
[root@K-YOUR HOST:~] esxcli system coredump file list
Path Active Configured Size
------------------------------------------------------------------------------------------- ------ ---------- ---------
/vmfs/volumes/xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx/vmkdump/xxxxx-xxxxx-xxxxxx-xxxxx.dumpfile true true 2542796800
So how to remove it?
2. Run the follwing 2 commands from the host that displays "Active value of true and Configured value of true"
esxcli system coredump file set -u
esxcli system coredump file remove -f /vmfs/volumes/xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx/vmkdump/xxxxx-xxxxx-xxxxxx-xxxxx.dumpfile
3. Finally delete the folder: "vmkdump" from the datastore & Unmount/Detache the datastore. DONE!
For more info follow this link: Removing the ESXi coredump to file (2090057)
Raul.
VMware VDI Administrator
"Just Join" the VCSA to the domain implies creating a dependence of the VCSA on the domain! No domain may equal no VCSA!
I much prefer using LADP or LDAPs as that allows AD authentication without creating a dependence!.
Hey All,
I am upgrading my Horizon View environment from 7.0.3 to the new 7.1 and am having issues getting to the view admin after the upgrade. I am leaning towards the Certs i created causing this uses but the View Blast GW is started and i know that pauses if it doesn't like the cert or if its not exportable.
Basically after upgrade my CS is 7.1 , but when i go to the page to grab the client or hit it through HTML 5 or go to the / admin site it cant be reached. All my services are started and i thought i may have been an issue w/ me not being patience for the page to display but its been a while and its not working. My cert is using the Friendly name of VDM and is a Web Server Cert issued by an internal Domain CA.
Any ideas?
Thanks all
To me this seems like a bug until unless someone is having some suggestion for me. Planning to report this internally to VMware Account Team and filling a VMware SR
Hey all, I was just trying to update my ESXi hosts and I've hit a snag -- I neglected a closing " at the end of the update command. The command never ran and now I can't exit the shell. I accessed this host using a program called mRemoteNG that I use for all of my remote server access and I use the SSH v2 protocol for accessing my VMware devices.
I've tried quit, exit, Quit, Exit, CTRL-C, CTRL-Z, ESC and repeatedly pounding on my keyboard. I Googled this and found nothing so I'm guessing it's a simple key combination for people who have been using VMware longer than I have. SO, how do I exit the shell?
Thanks,
Joe B
There's probably a stale entry in your VM configuration (vmx) file.
Please open the vmx file and see if it contains the following entry:
usb.autoConnect.device0 = "path:0/1/5"
or
usb_xhci.autoConnect.device0 = "path:0/1/5"
If so, remove it.
Thanks,
Lance
