Hi,
Normally that error only happens on install, so you getting it at a "random" time, makes me wonder if you are bumping into something else.
Like running out of character device major numbers.
For more details see the following threads:
Fusion 5 - Could not open /dev/vmmon: No such file or directory.
"Could not open /dev/vmmon" on macOS 10.12
hope this helps,
--
Wil
Hello,
Having an issue with the latest version of VMRC where you connect into a VM and it works for about 2 seconds before then disconnecting and saying "Waiting for connection".
I can close the connection and open it back up, and it will do the same thing, work properly for about 2 seconds then disconnect.
Is this a known issue, and if so, is there a workaround for it?
Thank you
Yes, my Management Console "DEM configuration share" looked like that. I removed the \general and copied the files from the temp\general folder. Now I see a different message in the log file.
2020-10-20 16:37:15.904 [DEBUG] Conditions: Evaluating condition set 'Microsoft Office 2016.xml'
2020-10-20 16:37:15.904 [DEBUG] Conditions: Check for path 'C:\Program Files (x86)\Microsoft Office\Office16' = false
Office 2016 is not installed in that directory. It is actually installed in 'C:\Program Files (x86)\Microsoft Office\root\Office16'. So based on this thread, Office 365 not working with UEM 9.3 , I changed the path in the Condition set. Unfortunately I am still not getting any archive folder for Office 2016. I will post a log shortly.
I agree that it is easy to install. They got that part covered quite well.
Less convinced of the maintain part, especially on dist upgrades, they regularly mess up things there and it can become quite messy.
To be fair they even state that you should do a fresh install on a version upgrade, but I don''t always have the time for that.
--
Wil
Having played around with it some more I have been able to make it work, but no idea how. It's entirely inconsistent. Some times on reboot I can, sometimes I cannot. Pausing and resuming seems to be okay though, so if I pause while the screen is correct then when I resume it will still work.
No real clue what's going on.
Hi,
I was having issues with 6.5 and rather than reinstalling, I stupidly upgraded to 7.0, which doesn't see much of the server's hardware, including the drive it's installed on as a datastore, even though under 6.5 it did. My fault, I know. I have now downloaded 6.5 and reinstalled it over 7.0 and it sees the hardware and datastore... but for some reason, I can't even see the 7.0 license, which I'm sure doesn't work for 6.5 anyway,.. but if doing the upgrade changed the license key to 7... how do I downgrade it to 6.5? And if I don't need to downgrade it, but use my previous 6.5 license... how do I even get that back since when I click on anything that should point to my licenses the site just gives me an error and says that page isn't available.
Thoughts?
Thanks!
-Mark
Is it possible to change the password/pincode complexity required by the HUB app? By default you are not allowed to have repeating numbers, which although secure, may not be workable in all circumstances.
Thank you!
Hi sorry,
They are set to auto upgrade.. but they won't since the app is running almost all the time.
Understood. Thank you!
After upgrading to ovftool v4.4, ovftool started breaking on a specific ExtraConfig parameter. It seems to be working correctly with all other ExtraConfigs, but adding a specific entry is causing it to break.
With a standard set of ExtraConfig parameters specified in envoy-proxy-bae.ovf. Conversion to OVA goes through perfectly.
<vmw:ExtraConfig ovf:required="true" vmw:key="guest.command.enabled" vmw:value="false"/>
```
ubuntu@cdm-node:~$ ovftool --allowAllExtraConfig envoy-proxy-base.ovf test.ova
Opening OVF source: envoy-proxy-base.ovf
The manifest validates
Opening OVA target: test.ova
Writing OVA package: test.ova
Transfer Completed
Warning:
- Wrong file size specified in OVF descriptor for 'envoy-proxy-base-1.vmdk' (specified: -1, actual 910012416).
Completed successfully
```
However, when we add the following entry to the list of ExtraConfigs, ovftool fails.
<vmw:ExtraConfig ovf:required="true" vmw:key="sched.mem.pin" vmw:value="true"/>
```
ubuntu@cdm-node:~$ ovftool --allowExtraConfig envoy-proxy-base.ovf test.ova
Opening OVF source: envoy-proxy-base.ovf
The manifest validates
Error: OVF Package is not supported by target:
- Line -1: Unsupported value 'sched.mem.pin' for attribute 'key' on element 'ExtraConfig'.
Completed with errors
```
Why is this specific ExtraConfig breaking ovftool? Is there something different about the naming that is causing the issue? Why do we only see this issue when this specific ExtraConfig is added to the ovf?
After upgrading to ovftool v4.4, ovftool started breaking on a specific ExtraConfig parameter. It seems to be working correctly with all other ExtraConfigs, but adding a specific entry is causing it to break.
With a standard set of ExtraConfig parameters specified in envoy-proxy-bae.ovf. Conversion to OVA goes through perfectly.
<vmw:ExtraConfig ovf:required="true" vmw:key="guest.command.enabled" vmw:value="false"/>
```
ubuntu@cdm-node:~$ ovftool --allowAllExtraConfig envoy-proxy-base.ovf test.ova
Opening OVF source: envoy-proxy-base.ovf
The manifest validates
Opening OVA target: test.ova
Writing OVA package: test.ova
Transfer Completed
Warning:
- Wrong file size specified in OVF descriptor for 'envoy-proxy-base-1.vmdk' (specified: -1, actual 910012416).
Completed successfully
```
However, when we add the following entry to the list of ExtraConfigs, ovftool fails.
<vmw:ExtraConfig ovf:required="true" vmw:key="sched.mem.pin" vmw:value="true"/>
```
ubuntu@cdm-node:~$ ovftool --allowExtraConfig envoy-proxy-base.ovf test.ova
Opening OVF source: envoy-proxy-base.ovf
The manifest validates
Error: OVF Package is not supported by target:
- Line -1: Unsupported value 'sched.mem.pin' for attribute 'key' on element 'ExtraConfig'.
Completed with errors
```
Why is this specific ExtraConfig breaking ovftool? Is there something different about the naming that is causing the issue? Why do we only see this issue when this specific ExtraConfig is added to the ovf?
Experiencing the same issue. Using logitech bluetooth wireless mouse. Works good before but after update mouse pointer is not visible on screen already updated to IOS 14.1
Hi chrischay,
Please try disabling the network on SRM appliance VM. Initiate a ping to see if you get a reply from another device/VM in the environment.
Share screenshot/log snippet where it reported duplicate IP address
Hi Jake,
You won't be able to revert to previous version of ESXi 6.5 due to partition changes to boot devices in ESXi 7.0 version.
Refer this KB article for more details: VMware Knowledge Base.
However, you can try to reinstall the ESXi 6.5 version and select option "Install ESXi, preserve VMFS datastore" during reinstallation process. However you might need to do all configurations manually.
If you have different ESXi 6.5 host along with VC you can make use of host profile and apply the configuration using host profile after setting up management network to connect the reinstalled ESXi host to vCenter Server.
Regards
Tami
how to increase SDDC limit for org to 6 SDDCs and 80 hosts in AWS
VDINinja311 I don't see that key on my laptop, or vdi vm or connection server. do I have to add USB key and then that dword? And on which device? I see USB Unavailable in my client. I cannot get my android phone to show up in the instant clone VM. I have installed the adb usb drivers.
Jangari 様
ご返信ありがとうございます。
おっしゃる通り、現在のigbnドライバはESXi v6.7u3 インストール時に含まれているデフォルトのドライバになります。
コメントいただいた内容を参考に、互換性ガイドを確認し、ESXi v6.7u3で現状最新の下記ドライバをインストールして確認してみます。
・igbn version 1.5.1.0
I've run into a problem as follows:
The ESXI 6.7 UI is not allowing me to login from any pc or any browser. I've tried 4 different browsers to no avail. I am using the correct credentials but the whenever I try to login it throws the following "error", "Please refresh your browser" that pops up right underneath the VMware ESXi logo. This is the first time its done this. I am wondering if it has something to do with the certificate but I'm not really sure. It does have a error on certificate but again not sure if that will cause this.
Thank You for your help.
I was able to finally get it to succeed by giving it 8vcpu and 16gb ram. (it only had 2vcpu and 12 before)
It has however still not told me its done in the 5480 UI. It gives me the error: "Update installation is in progress" when trying to login in.
Logs show this:
2020-10-21T01:39:46.206 [62589]INFO:vmware.appliance.vapi.auth:Authorization request for service_id: com.vmware.cis.session, operation_id: create
2020-10-21T01:39:46.214 [62589]DEBUG:vmware.appliance.update.update_state:In State._get using state file /etc/applmgmt/appliance/software_update_state.conf
2020-10-21T01:39:46.215 [62589]INFO:vmware.appliance.update.update_state:Found operation in progress /storage/core/software-update/stage_install_operation
2020-10-21T01:39:46.216 [62589]DEBUG:vmware.appliance.update.update_state:Updating Task progress with B2B Framework progress.
2020-10-21T01:39:46.218 [62589]DEBUG:vmware.vherd.transport.vapi:State 'INSTALL_IN_PROGRESS'
2020-10-21T01:39:46.218 [62589]DEBUG:vmware.vherd.transport.vapi:Only ['INSTALL_IN_PROGRESS'] block []
2020-10-21T01:39:46.231 [62589]INFO:vmware.appliance.vapi.auth:Reset pam tally for root
2020-10-21T01:39:46.232 [62589]DEBUG:vmware.appliance.vapi.auth:stdout: b'Login Failures Latest failure From\nroot 0 \n'
2020-10-21T01:39:46.244 [62589]INFO:vmware.appliance.vapi.auth:Authorization request for service_id: com.vmware.appliance.local_accounts, operation_id: get
2020-10-21T01:39:46.244 [62589]DEBUG:vmware.vherd.base.authorization_local:Verify privileges user (root) privilege ['ViewConfiguration']
2020-10-21T01:39:46.245 [62589]DEBUG:root:Validated user privileges in localstore or SSO
2020-10-21T01:39:46.246 [62589]DEBUG:vmware.appliance.update.update_state:In State._get using state file /etc/applmgmt/appliance/software_update_state.conf
2020-10-21T01:39:46.246 [62589]INFO:vmware.appliance.update.update_state:Found operation in progress /storage/core/software-update/stage_install_operation
2020-10-21T01:39:46.247 [62589]DEBUG:vmware.appliance.update.update_state:Updating Task progress with B2B Framework progress.
2020-10-21T01:39:46.248 [62589]DEBUG:vmware.vherd.transport.vapi:State 'INSTALL_IN_PROGRESS'
2020-10-21T01:39:46.248 [62589]DEBUG:vmware.vherd.transport.vapi:Only [] block []
and the file /etc/applmgmt/appliance/software_update_state.conf says :
{
"state": "INSTALL_IN_PROGRESS",
"version": "7.0.1.00000",
"latest_query_time": "2020-10-20T00:08:43Z",
"operation_id": "/storage/core/software-update/stage_install_operation"
}
I am assuming changing this state value to something else will allow log in again.
Any ideas what "state" should be when install is finished?
Rebooting it does not seem to reset this value.
dion