Interestingly just tried the following:
- provision node via "vagrant up"
- suspended node
- Started up node again and see vmnet route entries re-added to host node
- I am able to connect to instane again over SSH
So issue appears to be vmnet routes to NAT subnet being dropped during first startup.
[Edit]
NAT routes are dropped after a time period on these failing machines. Lost connection again after above sequence because local routing was lost again.
Totally agree its a workaround, I am in the situation where VMWare and Hyper-V cannot coexist.
If and only if you are on 15.5.5 of Vmware workstation pro and your host is on Windows 10 version 2004, you need to go into the vm settings try under the hardware >> processors setting the virtualization (Intel or AMD) and the virtualization counters if your guest is any version of Windows.
In addition under the options tab >> advanced, make sure UEFI and secure boot are both checked for Windows 10 guests. For windows 7 guest make sure the BIOS instead of UEFI is selected. Prior versions may also need that BIOS setting also enabled.
I have not yet tried either "Credential guard" or "Device guard" active on the host OS. Please be aware to this point, I have seen nothing about this. I have given you the settings that work in my situation where the Host OS is Windows 10 version 2004 and the guests are Windows 10 version 1909 and Windows 7 service pack 1.
I hope this helps.
I forgot to note that I do have hyper-v installed on the host!
LUCD,
I got it I fixed the RED Green
Now the reset rules have an email address
Only thing is Reset Rule 2 and reset rule 3 do not have send email option enabled
I see the email address
See attached
UPDATE:
I copied the ISOs over ethernet instead of wifi and verified the sha1 checksums and file sizes are identical but ESXi still won't boot from them. I have Win10 & Server 2016 ISOs and neither will boot. Both boot from USB if I burn the ISO with Rufus. I suppose I can just use USB drives to set up my VMs but it's less convenient.
Any other ideas? Thanks!
Yea, I saw that and added a comment as well. But I don't think we have a solution yet. I am thinking of raising an SR.
Against which checksums did you validate the transferred ISOs? What you had on your local machine, or those published by Microsoft?
I'm comparing them to the checksum values on my local machine. They are not official ISOs from MS so I'm not able to compare them that way but they are bootable and install if burned to USB.
Use curl command for vcsa . Check VMware Knowledge Base
They are not official ISOs from MS
So they're like homebrew Windows ISOs you built? If so, don't know what to tell you other than you've done something wonky with the boot sector that causes them to be malformed somehow as an ISO file. Don't know what to tell you other than it's an ISO problem. It's not an ESXi problem as the only time I've ever seen or heard of ISOs not booting is when it's the file itself. You can verify by getting a vanilla ISO from MS of some Windows variety, uploading it, and booting off it.
Hi,
I'm in a vCF 3.9 environment and am trying to delete my tier 0 router. This I am unable to delete because its connected to a tier 1 router. This in turn is connected to a test segment I used some time ago for testing. There are no VMs connected to this segment.
When attempting to delete the logical switch I receive the following error:-
Segment Test-Servers has 1 VMs or VIFS attached. Disconnect all VMs and VIFs before deleting a segment.
As I stated there are no VMs attached to this segment however in Segment ports a segment port is listed..
1680b35e-dc45-29e5-63af-e443b56bdd01/test-vm.vmx@6332b6-67-3164-49c2-8b22.-bd5fddb9c4c
This VM does not exist! It was deleted a long time ago.
I have attempted shutting down all the ESXi hosts, vCenter, NSX-T, edges etc. Started them back up, same issue.
I am therefore left with a completely unusable SDDC. As I cannot delete anything northbound of this non-existent VM?
Any ideas anyone?
You will need to do a force detach via the API. See instructions here.
Fixed...
Find the logical ID of the Switch with the NSX Search button, it will be listed with a GUID.Copy this to the clipboard, do another NSX search based on the GUID. You will find the entry for your port, click on this and you will then be able to delete it.
Credit to malasfar who posted a thread previously that led me to finding this!
I also got the same issue. I was able to get the VM working by disabling Virtualize Intel VT-x/EPT or AMD-V-RI and Virtualize CPU performance counters under VM Settings -> Processors -> Virtualization Engine. This is still a big upset for me because I was using VMs inside VMs sometimes. But since I want to try WSL2, I'm going to live with it for now.
No issues with disabling RDP for vCenter service users
Hi，
Thank you for posting your query in community.
Per WS user guide https://docs.vmware.com/en/VMware-Workstation-Pro/15.0/workstation-pro-15-user-guide.pdf
Running Workstation on a Hyper-V Enabled Host is available in 15.5.5 version of Workstation Pro.
System Requirements
Nested VMs/PMCs/RTM and HLE/PKUare not supported so far.
Could you please try to change the Hyper-V status as follow:
How to change Hyper-V status
dgreadiness_v3.6 is a tool that Microsoft published to enabled/disable Device Guard/Credential Guard
-- https://www.microsoft.com/en-us/download/details.aspx?id=53337
Set-ExecutionPolicy Unrestricted if needed
If Execution-Policy is not already set to allow running script, then you should manually set it as below and then use the readiness script:
To Enable DG/CG. If you have a custom SIPolicy.p7b then use the -Path parameter else the hardcoded default policy is used
Usage: DG_Readiness.ps1 -Enable OR DG_Readiness.ps1 -Enable -Path <full path to the SIPolicy.p7b>
To Disable DG/CG. For more usage, you can refer to the readme.txt from the download bundle file.
How to verify your host is ready to run with/without Hyper-V?
Check Hyper-V & VBS Status & Device Guard status
By windows cmd line msinfo32.exe
Thanks,
I ran into this issue as a Mac Admin who deploys the profile. Our whitelist is correctly whitelisting the VMWare Fusion kext. However, I would get this same error. Only when I exempted myself from the whitelist, and then re-launched VMWare Fusion did the prompt for the blocked kext show up, and I was able to allow it. Very strange.
Also there is an another to disable/enable Hyper-V Re: VMware Workstation does not support nested virtualization on this host. Thanks ppan7 for the solution.
Thanks.
Hi redraider806
You can capture the personal certificates using DEM if you are using it along with mandatory profile in your environment.In case you are running DEM, you need the GPO setting in the UEM GPO to capture the personal certificates :
"Certificate support for mandatory profiles"
In addition to enabling this setting, you also need to create a Flex config file with the “Personal Certificates” Windows Common Setting.
Create a Flex Configuration File by Using Windows Common Settings
Can you please configure a VM to boot from the .iso, power it on, wait for it to fail booting, power it off, and then grab the vmware.log from inside the VM's directory on the datastore, and post it as an attachment here? (Just look for the Attach link in the lower-right corner when composing your reply.)
--
Darius