Добрый день! Столкнулся с такой проблемой, примерно раз в день начал падать хост esxi 6.7. В логе в vmkvarning вот такие записи.

0:00:00:05.209 cpu0:2097152)WARNING: VMKAcpi: 318: \_SB_.PC00.LPC0.TMR_: skipping GSIV 0 conflict

0:00:00:05.260 cpu0:2097152)WARNING: Chipset: 396: Bus 5 (04) is already defined

2019-11-15T13:03:54.730Z cpu14:2097846)WARNING: Failed to init interrupt.

2019-11-15T13:03:54.875Z cpu14:2097846)WARNING: Failed to init interrupt.

2019-11-15T13:03:57.350Z cpu37:2097861)WARNING: ScsiPath: 8915: Adapter Invalid does not exist

2019-11-15T13:03:57.350Z cpu17:2097863)WARNING: PCI: 1209: 0000:00:14.0 is nameless

2019-11-15T13:04:02.143Z cpu26:2097926)WARNING: etherswitch: PortCfg_ModInit:910: Skipped initializing etherswitch portcfg for VSS to use cswitch and portcfg module

2019-11-15T13:04:06.041Z cpu26:2098075)WARNING: FBFT not enabled

2019-11-15T13:04:11.074Z cpu8:2097791)WARNING: ScsiDeviceIO: 10107: Mode Sense cmd reported block size 0, does not match the current logical block size 512(with physical block size 512) for device.

2019-11-15T13:04:11.074Z cpu8:2097791)WARNING: ScsiDeviceIO: 10109: The device mpx.vmhba32:C0:T0:L0 is marked format corrupt.

2019-11-15T13:04:15.558Z cpu8:2097791)WARNING: NFS: 1227: Invalid volume UUID 5d9b4bb4-89590e3c-9b54-ac1f6bd20130

2019-11-15T13:04:17.148Z cpu23:2098725)WARNING: APEI: 319: Could not initialize EINJ

2019-11-15T13:04:27.882Z cpu5:2098993)WARNING: NTPClock: 1561: system clock synchronized to upstream time servers

2019-11-15T13:04:44.460Z cpu32:2100049)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 0

2019-11-15T13:04:44.460Z cpu32:2100049)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 1

2019-11-15T13:05:14.521Z cpu25:2100282)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 0

2019-11-15T13:05:14.521Z cpu25:2100282)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 1

2019-11-15T13:05:44.492Z cpu4:2100440)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 0

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 0

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 1

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 2

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 3

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 4

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 5

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 6

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 7

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 8

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 9

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 10

2019-11-15T13:06:14.572Z cpu46:2100595)WARNING: MonLoader: 734: MonLoaderCallout_GetSharedHostPage: Invalid page offset 0 for region 8 vcpu 11

2019-11-15T13:12:16.069Z cpu14:2098993)WARNING: NTPClock: 1561: system clock synchronized to upstream time servers

Подскажите пожалуйста, где поискать проблему?

Спасибо.

Hello,

We have upgraded our vCenter appliance (VCSA) to 6.7U3 a few days ago and we noticed a gap of logs in our syslog server (kiwi) since then.

I did a bit of troubleshooting but Rsyslog (the syslog client running on VCSA) is completely new to me.

I use this command to restart Rsyslog:

systemctl restart rsyslog

Right after starting up Rsyslog, logs are being sent to our syslog server.

~10min later, no more logs are sent.

The vCenter log file in our syslog server stops getting updated.
I did a tcpdump in our vCenter and I see that the vCenter stops sending logs.
Using UDP or TCP doesn't fix the issue.

I looked for errors in various log files in the vCenter but can't find anything.

This is what /var/log/vmware/rsyslogd/rsyslogd-syslog.log looks like after restarting Rsyslog:

2019-09-11T11:53:12.812087+02:00 info rsyslogd [origin software="rsyslogd" swVersion="8.37.0" x-pid="21203" x-info="http://www.rsyslog.com"] exiting on signal 15.

2019-09-11T11:54:42.617065+02:00 warning rsyslogd environment variable TZ is not set, auto correcting this to TZ=/etc/localtime [v8.37.0 try http://www.rsyslog.com/e/2442 ]

2019-09-11T11:54:42.617568+02:00 info rsyslogd imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.37.0]

2019-09-11T11:54:42.618409+02:00 info rsyslogd [origin software="rsyslogd" swVersion="8.37.0" x-pid="22235" x-info="http://www.rsyslog.com"] start

Rsyslog is still running based on this command

systemctl status rsyslog.service

● rsyslog.service - System Logging Service

   Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)

   Active: active (running) since Wed 2019-09-11 11:54:42 CEST; 39min ago

     Docs: man:rsyslogd(8)

           http://www.rsyslog.com/doc/

Main PID: 22235 (rsyslogd)

    Tasks: 12

   Memory: 5.7M

      CPU: 191ms

   CGroup: /system.slice/rsyslog.service

           └─22235 /usr/sbin/rsyslogd -n

Sep 11 11:54:42 vcenter.domain.local systemd[1]: rsyslog.service: Main process exited, code=killed, status=9/KILL

Sep 11 11:54:42 vcenter.domain.local systemd[1]: Stopped System Logging Service.

Sep 11 11:54:42 vcenter.domain.local systemd[1]: rsyslog.service: Unit entered failed state.

Sep 11 11:54:42 vcenter.domain.local systemd[1]: rsyslog.service: Failed with result 'signal'.

Sep 11 11:54:42 vcenter.domain.local systemd[1]: Starting System Logging Service...

Sep 11 11:54:42 vcenter.domain.local systemd[1]: Started System Logging Service.

Sep 11 11:54:42 vcenter.domain.local rsyslogd[22235]: environment variable TZ is not set, auto correcting this to TZ=/etc/localtime  [v8.37.0 try http://www.rsyslog.com/e/2442 ]

Sep 11 11:54:42 vcenter.domain.local rsyslogd[22235]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.37.0]

Sep 11 11:54:42 vcenter.domain.local rsyslogd[22235]: [origin software="rsyslogd" swVersion="8.37.0" x-pid="22235" x-info="http://www.rsyslog.com"] start

(real hostname has been replaced by vcenter.domain.local)

I created a ticket at VMware support, but the agent wasn't able to find any errors as well and she suggested to take a backup of our vCenter and reinstall with a restore to get a fresh install of Photon OS since Rsyslog is integrated in Photon OS. I'm not going to do that now, maybe as a last troubleshooting step.

In the meantime, do you guys have an idea? Wrong Rsyslog config?

Thx for your help.

I am looking in GPO the setting to prevent local disk access.

All the ADMX settings was installed (view 4.6)

Thanks

Werner

Morning Everyone,

Recently I've encountered a problem on one of my VMs not starting due to missing descriptor files. I've looked at how to make a descriptor file but I am only a maintainer of a network I don't really work with command lines much on a ESX server and I am not to confident when it comes to this. I am here asking if it is possible that someone more experienced could help out with making a descriptor file.

Hi,

Having build a new lab server with:

Gigabyte C246M-WU4 Motherboard

128GB Corsair RAM

Intel Xeon E-2176G CPU

Samsung 970 PRO NVMe SSD

Fresh install of ESXI 6.7.0 Update 3 (free version)

I often experience that the host completely freezes with the black/white screen also frozen. No VM's are running, no ping/login to host. Num Lock doesn't work. F2 doesn't work. Everything has freezed.

I know that only the chipset + CPU are on the compatbility list, but I figured that if ESXI could run off an old HP laptop, then why not this machine.

Any suggestions to, how to find the root cause of the freezes? I'd really hate having to change to virtualbox

Hello, i have problem when i install windows 7 x32 using installation from USB flash drive creating second hard drive, when install complete sucessfully and i go on desktop. after that i connect that USB drive what i use windows installation. i get that error and machine shutdown when i remove second hard drive from settings i cant boot windows please help

Hi there,

I have got my own license for ESXi from the eval centre and as far as I am aware that license does not expire, however nowhere do I see a mention for commercial use. What are the terms of commercial use associated with these licenses?

Thanks,

Alexander Horner

I've got a ESXi 6.7 virtual machine running Redhat Workstation 7.6.

Horizon view agent installs without issue and regsiters with the connection server.

RHEL VM has been integrated with AD using SSSD.   Domain users can log in via SSH without issue.

I can establish a session from the connection server but all I get is a black screen.   Black screen sits for about 30 seconds and then terminates.

I've tried this with HZ 7.9 and 7.10. 

Also re-installed vmware tools multiple times (with re-installing the agent after the tools are installed)

Also tried with a Nvidia GPU attached (passthrough using quadro driver) and without a GPU attached.   I get the same behavior.  

firewalld/iptables is disabled.

Thanks in advance

Hi,

I got the following error when I tried to call retreiveInternalContent().

I used smartConnect to get the serverinstance.

Could someone know the reason? Thank you!

Traceback (most recent call last):

  File "perfNamespace.py", line 696, in main

    guestOperationDict.get(args.guestoperation.lower(), unknownOperation)(leftovers, args)

  File "perfNamespace.py", line 189, in listNamespaces

    svcInstIntCont = svcInst.RetrieveInternalContent()

AttributeError: 'vim.ServiceInstance' object has no attribute 'RetrieveInternalContent'

Running Win 10 home version 1803. Microsoft has decided I need to upgrade to 1903 for my own good which has already downloaded just waiting for the next reboot. 1903 is not compatible with WS pro version 10. My problem is if I install ws pro 15 and reboot windows 1903 will install at the same time. That will leave me with 2 new upgrades at the same time and if I have any problems I may not know which new upgrade is the problem. I propose to do the following:

1. Power off my two virtual machines, vista and xp.

2. Back both of them up.

3. deinstall ws pro 10.

4. reboot letting windows 1903 install.

5. make sure every thing works normally.

6. install ws pro 15

7. reboot and make sure everything still works ok.

Anyone see any problems with this?

Anyone have a better idea?

Thanks for your help

Dennis

Greetings,

I've noticed that datastores seem to not like to have their host controller changed. I tried to move one of my drives from the raid controller to my onboard storage controller but VMware lost the link to the datastore and would only let me wipe and reprovision the drive via the UI.

My current raid controller has a drive capacity limit of 2TB and I'm suspect of whether it's beginning to fail or not as I've had an issue with occasional high latency via it.

I plan on dropping in a PCI-E Sata or SAS controller card and moving anything currently on the raid controller onto that.

I would like to migrate the data stores over, is there a simple method for re linking them without having to wipe and rebuild?

Running VSphere 6.7u3 (Free License)

Hi

I was sent some VMs which I have imported into my environment (they just sent a full copy of the servers folder from there datastore), they seem to be working fine but I noticed they were showing as non-compliant for the storage policy, I have tried to reapply the policy but it just comes back with an error straight away (I don't have access to check as I had to leave for the day but will post the exact message when I can get signed on later) the error pretty much says the action cannot be completed and the reason as no reason. Has anyone seen this before and have any idea what I can do so or picks up the policy? The VMs were build off-site on someone else's environment on the same version as us (6.5). I have checked and out storage policy is working fine with every other VM, I have changed a test server to the policy the imported VMs need to go on and it worked fine. I looked at the monitor and policy details and the servers show the VM Home folder as picking up default datastore policy and complaint and the disk shows as non-compliant? Sorry as the post is a big vague but I'm hoping someone might have an idea, I wil post the exact error when I get chance

Thanks

Hi

I can't get Workstation to work on my work computer.

I get the error message when I try to load (any) OS in Workstation, "This host supports AMD-V, but AMD-V is disabled"

I've already done/tried the following:

-virtualization eanbled in BIOS

- hyper-v removed under "turn windows features on or off".

I'm in touch with company IT support and they suspect that this may be linked to Virtualization Based Security on Credential Guard GPO.

What exactly should they look for?

I'm running Windows 10 Enterprise, version 1803, and currently latest Workstation Pro Edition, 15.5.1

here is how I do not drop anything I test on another motherboard all is well I llance the virtual machine windows 7/10 can inporte I install the driver NVDIA I restart the machine and the most error may be a black screen . why thank you for and for your help ???

Has anyone successfully deployed 1803 linked clones in their environment. I have been having some serious login time issues and performance with 1803. Stuck on "Please wait for the user profile service." My expected logon time supposed to be 22-24 seconds using UEM when preparing the image but now in the middle of deployment I am getting 2 minutes logon time. I also have some RDS farms, Windows 2016, using the same UEM policies and they are login users in 15-20 seconds.

Hi there!

I recently got access to VMwareTestDrive and been setting up the sandbox Identity Manger and Work-space one UEM etc. I have followed many guides on how to set it all up. I have got all three components calling with each other. Air-watch work-space UEM and Identity Manger. I have connected them with my AD domain and can sync successfully.

But my problem is when I select my domain in the login prompts and try to login using a domain account is fails with incorrect username or password. I can confirm a have verified I am using the correct passwords and have created a few test accounts and all act in the same way. If I use the System Domain which is default works just fine. I am not sure if I am missing a step or if I am thinking in the wrong direction.

If any information is needed please let me know what you need.

I am new to cloud connecting so the more information you can give me I greatly appreciate it!

Thanks

-Jon

In VirtualBox, I have been able to set a USB filter that captures the USB WiFi adapter. This means that the host is prevented from going online when the guest is running; only the guest has Internet access. Is there a similar tool or technique in VMware Player 15?

I set up a Mac OS X 10.11 virtual machine so I can run 32-bit apps like Adobe CS) (since Catalina 10.15 won't support 32-bit), but the VMware Tools don't seem to be working.

The display won't resize from the default 1024x768 and none of the shared folders appear.

Is this a known problem?

Hello,

I would like help getting my two Windows 7 guest OS VMs to ping the Windows 7 host. 

Background:

• Host is Windows 7 64 bit.
  
• Guests are both Windows 7 32 bit, recently converted from VPC. 
  
• I have both guests functioning normally other than this issue. 
  
• both guests are configured to use bridged network
  
• bridge network (vmnet0) is configured to use a single wireless adapter, not automatic
  

What I have tried:

• firewalls on both guest and host are turned off
  
• verified host and guests are assigned expected IPs and are on same subnet
  
• pinging from guest to guest works both ways
  
• pinging from host to both guests works
  
• guests can ping router
  
• guests can reach the internet, browse google, etc.
  
• VPN on guests are off
  
• guests can ping other PCs on network
  
• other PCs on network can ping host
  
• other PCs on network can ping guests
  
• verified vmnetbridge service is running
  
• verified adapter related registry keys
  
• I briefly had success when I was playing with enabling Internet Connection Sharing on my host's wireless adapter settings.  I could not understand how that should help, and while I was experimenting, turning it off and on, it stopped working for me. 
  
• rebooted VMs
  
• tested using both IP and name, resolving name with hosts file
  

Here is my vmx file for one guest, they are both similar:

.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "7"
memsize = "1424"
MemAllowAutoScaleDown = "FALSE"
displayName = "W7 Sonicwall VPN"
guestOS = "windows7"
floppy0.present = "TRUE"
floppy0.autodetect = "TRUE"
floppy0.filename = "auto detect"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.connectionType = "bridged"
ethernet0.startConnected = "TRUE"
ide0:0.present = "TRUE"
ide0:0.fileName = "W7 Sonicwall VPN.vmdk"
ide1:0.present = "TRUE"
ide1:0.autodetect = "TRUE"
ide1:0.filename = "auto detect"
ide1:0.deviceType = "cdrom-raw"
vmci0.present = "TRUE"
pciBridge0.present = "TRUE"
tools.upgrade.policy = "useGlobal"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
extendedConfigFile = "W7 Sonicwall VPN.vmxf"
virtualHW.productCompatibility = "hosted"
ide1:0.startConnected = "TRUE"
tools.syncTime = "FALSE"
uuid.location = "56 4d 1e e7 3a ae c7 10-eb ae 21 97 b0 4c 06 3d"
uuid.bios = "56 4d b5 b7 8a 15 7e 47-e4 4f a9 cf c2 ba 4a d6"
replay.supported = "FALSE"
unity.wasCapable = "TRUE"
replay.filename = ""
ide0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
ethernet0.pciSlotNumber = "32"
vmci0.pciSlotNumber = "33"
vmotion.checkpointFBSize = "24576000"
vmci0.id = "-1027978538"
floppy0.startConnected = "FALSE"
ethernet0.vnet = "VMnet0"
checkpoint.vmState = ""
cleanShutdown = "FALSE"
debugStub.winOffsets.version = "7"
scsi0.virtualDev = "lsisas1068"
scsi0.pciSlotNumber = "160"
sound.pciSlotNumber = "34"
scsi0.present = "TRUE"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
debugStub.winOffsets.value = "0xb8,0xb4,0x18,0x188,0x16c,15,408,0x268,0x260,0x230,0x218,0x88,0x28,0x18,0x20,0x24,1,0x280,0x0,0xc,0x14,0x200000,0x1a8,0xc,0xc,0x18,0x12c,0x1ec"
scsi0.sasWWID = "50 05 05 67 8a 15 7e 40"
ethernet0.addressType = "static"
ethernet0.address = "00:50:56:00:4a:01"

And here is the ipconfig /all for my guest:

C:\Program Files\Microsoft Visual Studio 10.0\VC>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : VMW7SONICVPN
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-50-56-00-4A-01
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d00e:125e:4e:afa0%17(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.123(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, July 18, 2011 3:14:19 PM
   Lease Expires . . . . . . . . . . : Friday, September 16, 2011 3:14:19 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 469765161
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-09-D0-2F-00-03-FF-1E-AA-4C

   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{830B6778-EB77-443C-9BDC-08B62E813411}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:30f6:3f82:3f57:ff84(Preferred)
   Link-local IPv6 Address . . . . . : fe80::30f6:3f82:3f57:ff84%12(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Program Files\Microsoft Visual Studio 10.0\VC>

Your time and advice is greatly appreciated.  I have spent much time researching and testing but I am stuck.  I am a newbie to vmware.

Thanks,

Glenn

Hi all,

I am in the process of building an NSX-V home lab (based on ESXi 6.7U3 + vCenter 6.7U3a + NSX 6.4.6). Everything is running on a single bare metal server (Intel i7, 32GB RAM) with EVE-NG as the underlying hypervisor (as per: https://www.eve-ng.net/index.php/documentation/howtos/ - see VMware ESXi/vCenter/NSX links for details).

Everything works fine regarding the nested ESXi hosts, vCenter, and initial NSX manager deployment. I have VMs running fine on the nested ESXi hosts with Distributed vSwitches etc.

But I hit problems when deploying the NSX controller VMs. It basically just sits at “Deploying” and eventually the controller VM gets deleted.

I think I have enough resources allocated to the nested ESXi host where the NSX controller is getting deployed to (4 vCPU, 8 GB RAM). I briefly see the Photon OS boot screen on the console of the controller VM but then it changes to black with no response on the keyboard.

Any hints on why a controller VM would fail to boot? Screenshots attached.

Thanks,

Bob

Stays on "Deploying":

Controller VM gets deployed but fails to fully boot. After the Photon  screen all I see is black with no response on the keyboard. VM gets deleted after ~10 minutes: