I removed the 5.5 host and now all the datastores say "inaccessible".
So from that I assume that their earlier, normal-looking appearance was just because they were accessible on the 5.5 host, but for whatever reason, vCenter showed them as accessible on the other host too, even though they weren't.
Well, I was able to right-click each inaccessible datastore on the 6.7 host and do "Mount..." and successfully mount each one. But then when I tried to add the 5.5 host I again got the error, "[host] has a datastore that conflicts with an existing datastore in the datacenter". And unfortunately, this version of vCenter doesn't tell you which datastore it's referring to.
I feel like I'm in a Catch-22 scenario!
By running macOS on non-Apple hardware (and by hacking VMware Workstation, which you knowingly did) you are violating the EULAs of both Apple and VMware. As a result, we cannot and will not help you here.
This may be relevant: if I do this on the 6.7 host in PowerCLI...
$vmHost = Get-VMHost [host] | Get-Datastore
$vmHost.extensiondata.summary.multiplehostaccess
...I get "False" for all the datastores.
If I do the same thing on the 5.5 host I get "True" for all datastores except the boot vol. The same is true for other 6.7 hosts attached to the same SAN.
If that's the root of the issue then I'm not sure how to resolve it. I've never had to worry about setting anything for multiple access for a FC datastore - the SAN has no options for that. It's always simply worked that way by default.
I do it all the time, works great. Just make sure you suspend or shut down the VM, and completely quit fusion before ejecting with Finder (and definitely eject with finder rather than pulling the plug...had a bad experience with a cat, a cord, and a VM once).
It may save you a few bucks, but a USB-C 3.1 drive also works great...it's not as fast as thunderbolt, but I haven't found it noticeably different in real-world use. The new Samsung T-series is 2x as fast as the T3's (which is what I use).
Oh I am a moderator , but being a moderator does not mean knowing better than Ulli.
BTW, that thread was two years old, things might have changed since then.
Still don't think it is a good idea to run both VMware Workstation as well as VirtualBox on the same host at the same time.
VMware most likely does not test that scenario much. But I do know that they will try to fix issues if there are some that are fixable.
Running VMware Workstation and Hyper-V simultaneously however... stay tuned.. (somewhere this week even).
--
Wil
We are about to roll out the Self Service Portal. Before we do, it needs to be behind PingID. Has anyone set this up successfully?
Author : mimartin
Topic Name : Host Failure Types
Publication Name : vSphere Availability
Product/Version : VMware vSphere/7.0
Question :
If a vm is powered off prior to an ESXi host HA event, wull a powered off VM restart on another esxi host if HA kicks in ?
ok i got you thanks alot so i have to take VCP 2019 or 2020 then the new design that's it right
Hi Gurus,
First of all, thank you so much for providing with wonderful and precise solutions to almost any individual problems that one can come across. With that being said, I am having a small hiccup when ot comes to patching vCenter 7.0. My current version of vCenter is as follows
Version - 7.0.0.10100
Build - 15952498
I am planning to patch it to the following -
Version - 7.0.0.10300
Build -16189094
I have vCenter setup in HA mode. The procedure that I am following is as per the Vmware Documentation over Here
I have downloaded the correct .iso for the same. But as soon as I try to stage the iso, I encounter an error. Just to be sure, I have now downloaded the iso twice to eliminate the doubt of a corrupt download. The error that I get is as follows:
Command> software-packages stage --iso
[2020-05-27T19:21:43.148] : ISO mounted successfully
[2020-05-27T19:21:44.148] : Not running on a VMC Gateway appliance.
[2020-05-27T19:21:44.148] : Not running on a VMC Gateway appliance.
[2020-05-27T19:21:44.148] : Target VCSA version = 7.0.0.10300
[2020-05-27T19:21:44.148] : Not running on a VMC Gateway appliance.
[2020-05-27T19:21:44.148] : No manifest whitelist present, it is not leaf service upgrade.
[2020-05-27T19:21:44.148] : Not running on a VMC Gateway appliance.
[2020-05-27T19:21:44.148] : Not running on a VMC Gateway appliance.
[2020-05-27T19:21:44.148] : Not running on a VMC Gateway appliance.
[2020-05-27T19:21:44.148] : Not running on a VMC Gateway appliance.
[2020-05-27T19:21:44.148] : Checking if HLM is enabled
[2020-05-27T19:21:44.148] : Product configuration file does not exists.
[2020-05-27T19:21:44.148] : Filtering components as not all are allowed to run. Whitelist []
Blacklist []
[2020-05-27T19:21:45.148] : Not running on a VMC Gateway appliance.
[2020-05-27T19:21:45.148] : Not running on a VMC Gateway appliance.
[2020-05-27T19:21:45.148] : About to perform WCP checks
[2020-05-27T19:21:45.148] : Performing WCP checks
[2020-05-27T19:21:45.148] : Adding WCP path to Python path
[2020-05-27T19:21:45.148] : Found Kubernetes versions {'1.17', '1.16', '1.15'} in /storage/core/software-packages/scripts/patches/payload/components-script/wcp/wcp_versions.yaml
[2020-05-27T19:21:45.148] : Found Kubernetes versions {'1.16', '1.15'} in /etc/vmware/wcp/wcp_versions.yaml
Error Code : 1021
[2020-05-27T19:21:45.148] : Exception raised while running wcp prechecks.
Traceback (most recent call last):
File "/storage/core/software-packages/scripts/update_wcp_utils.py", line 51, in doWcpPrechecks
result = precheck.doPrecheck(skipPrechecksIds)
File "/storage/core/software-packages/scripts/patches/payload/components-script/wcp/precheck.py", line 113, in doPrecheck
stub_cfg = utils.create_vapi_stub_config()
File "/storage/core/software-packages/scripts/patches/payload/components-script/wcp/utils.py", line 214, in create_vapi_stub_config
token_data = token_handler[0]()
File "/storage/core/software-packages/scripts/patches/payload/components-script/wcp/utils.py", line 171, in get_hok_token
sts_auth = get_sts_authenticator()
File "/storage/core/software-packages/scripts/patches/payload/components-script/wcp/utils.py", line 158, in get_sts_authenticator
ls_url = VmafdClient().get_ls_location()
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 83, in get_ls_location
return self.client.GetLSLocation()
RuntimeError: unidentifiable C++ exception
Process Process-1:1:
Traceback (most recent call last):
File "/usr/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
self.run()
File "/usr/lib/python3.7/multiprocessing/process.py", line 99, in run
self._target(*self._args, **self._kwargs)
File "/storage/core/software-packages/scripts/update_wcp_utils.py", line 56, in doWcpPrechecks
json_result = JsonSerializer().serialize([result, ex])
File "/usr/lib/applmgmt/base/py/vmware/update/json_utils.py", line 222, in serialize
cnt = json.dumps(o, default=ObjectJsonConverter(True).encode, indent=4)
File "/usr/lib/python3.7/json/__init__.py", line 238, in dumps
**kw).encode(obj)
File "/usr/lib/python3.7/json/encoder.py", line 201, in encode
chunks = list(chunks)
File "/usr/lib/python3.7/json/encoder.py", line 429, in _iterencode
yield from _iterencode_list(o, _current_indent_level)
File "/usr/lib/python3.7/json/encoder.py", line 325, in _iterencode_list
yield from chunks
File "/usr/lib/python3.7/json/encoder.py", line 438, in _iterencode
o = _default(o)
File "/usr/lib/applmgmt/base/py/vmware/update/json_utils.py", line 176, in encode
result = json.JSONEncoder().default(o)
File "/usr/lib/python3.7/json/encoder.py", line 179, in default
raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type RuntimeError is not JSON serializable
[2020-05-27T19:21:45.148] : ISO unmounted successfully
[2020-05-27T19:21:45.148] : Staging process failed.
Do you folks have any idea regarding the same? Could it be that the source iso was released with a problem?
Appreciate any inputs.
Thanks & Regards,
Siddhesh
I'd recommend opening a support case with VMware.
Hi Daphissov,
Thank you for the immediate response. I am afraid I can't open a support case since I am using the vCenter in Evaluation Mode as of now. We were planning to explore vCenter 7 a bit before we made a decision to purchase it.
Regards,
Siddhesh
Buenas noches,
Estoy intentado convertir un equipo físico con Windows y llevarlo al hypervisor ESXi. He utilizado la herramienta VCenter Converter y también mediante Veeam pero obtengo el mismo resultado. La máquina enciende pero aparece pantalla azul con el mensaje:
Gracias de antemano.
Adding to the solution. Although utilising a CIFS mount addressed the file name too long problem it introduced a new issue under linux. Under Windows 10 it seems when copy with timestamp preservation (e.g. cp -p) is used a "Errno::EACCES: Permission denied" error is encounter. Sounds like its a known issue with Window 10 and CIFS and the relevant linux drivers don't have a work around.
I hit this when using puppet and puppet-librarian build operations.
i am using script below to delete snapshots older than 5 days by excluding "donotdelete" snapshots, my question is how i will add more names to exclude or read from a file to exclude the snapshot names.
if its from a file its easy as i can ask users to update the txt file if the want to exclude some snapshots.
$vcenter = "hostname"
$creds = Get-VICredentialStoreItem -file "C:\Vmware script\pass.cred"
#Connect to the vCenter server defined above. Ignore certificate errors
connect-viserver $vcenter -User $creds.User -Password $creds.Password -WarningAction 0
Clear-Host
Get-VM | Get-Snapshot |Where {$_.Created -lt (Get-Date).AddDays(-5) -and $_.Name -notmatch "donotdelete" } | Remove-Snapshot -Confirm:$false
Although I had to go a little different way, I was able to resolve this.
Here's what I did
Hope this helps.
Thanks & Regards,
Siddhesh
Both of your Macs seem to be attempting to run VMware Tools on your host, and it is a part of VMware Tools which is causing the failure. If you are intentionally installing VMware Tools onto your host, please be aware that it is only needed inside your virtual machine(s) and has no useful purpose on your host, so you should uninstall it.
(If you are not intentionally installing VMware Tools on your host, we need to figure out how it came to be present and running on your host...)
Thanks,
--
Darius
Hi Mach1_70
> Take a snapshot of connection servers and take a backup of ADAM database:
C:\Program Files\VMware\VMware View\Server\tools\bin\vdmexport.exe > vdmbackup.ldf
> Connect to View ADAM database as per VMware Knowledge Base
> Expand the tree items in the left pane and locate the entry OU=Global,OU=Properties,DC=vdi,DC=vmware,DC=int.
In the right pane, double-click the entry CN=Common.
Double-click the attribute pae-AllowKerberosRealmAuth.
In the attribute editor dialog box, set the pae-AllowKerberosRealmAuth attribute to 0 to disable Kerberos realm authentication
Click OK to save changes to the attribute value.
Click OK or Apply to save changes to the entry.
> Check now if issue is resolved.
You are looking at the right documentation Quick-Start Tutorial for VMware App Volumes | VMware
Once you have assigned the appstack to the RDSH computer OU (RDSH only support computer-based assignment for appstacks: VMware Knowledge Base ), you can create a new application pool in horizon view and select the remote applications from the AppStack assigned to the RDSH server.
Добрый день,
Подскажите, у меня вопрос следующего характера, планируем отказоустойчивую структуру на базе VMware
Имеем два сервера - 2 хоста
Имеем два QNAP NAS TVS-1672XU-RP - 2 NAS
Планируем использовать один сервер как основной, второй как запасной, как отказоустойчивую технологию планируем использовать HA, но тогда возникает вопрос, что все виртуальные машины будут храниться на одном NAS и в случаи его отказа все рухнет. Какими средствами можно сделать, чтобы два хранилища к примеру синхронизировались между собой и в случаи отказа NAS происходило переключение на резервную машину ? Подскажите направление, как лучше построить отказоустойчивый кластер имея несколько NAS.
В голове пока идея только такая, но по мне как то кривовато
Между NAS делать Rsync.
Host 1 <> NAS 1 <=> NAS 2 <> Host 2