As a follow up, I heard back from VMWare. All they could tell me was:
"There should be a small resync providing that all the hosts are up before the VMs and that when you shut the environment down, it was healthy. We should expect a small resync but not a full rebuild."
So, once again, this forum was more useful than paid support. :-/ Thanks again Bob and GreatWhiteTec!
My bad. Thank you for pointing that out.
Hehe, the ESXi part is a bit different, but it has quite a few things that are similar or the same.
Yes, the bundle name is the term used for filename part that is before the .vmwarevm file extension.
So if you have a virtual machine folder that is called "MacOS 10.11.vmwarevm" then the whole folder with contents is referred to as a bundle.
However as the .vmwarevm file extension is hidden by default, with the bundle name is most often meant "MacOS 10.11".
If you want to rename the folder name, do the following:
In Fusion Library, from the context menu select "Delete", it will ask you if you want to "Move to trash, Cancel or Keep file"
With "file" they mean bundle and if you select "Keep file" you're fine.
By removing the VM from the library you don't end up with a non function VM in the list that has a confusing name.
Then you can rename the folder, rename the .vmx and from "File -> Open" you can select the renamed vmx in the renamed folder.
--
Wil
Ulli,
Joy, sounds like fun. Unfortunately I do not have the time for reproducing the problem at the moment.
640x480 is pretty unusable, even back then.
If I had the time and I was not able to get it to work like you tried, then it might be an idea to try a nested workstation 8?
See if it works there, although of course nesting adds its own intricacies.
--
Wil
To be fair, I wouldn't understand the level of vSAN that I do without working providing those support services you speak of (alongside a lot of talented people!). But also consider that maybe you gave more detail here than your SR and/or had more back and forth to be specific about your concerns (and more than one vSANer to help).
If contacting support (VMware or otherwise) and the answers to your questions are not specific enough then just ask (and ask the right things), but really at the admin-level of vSAN the answer you got is correct.
Bob
Exact same issue.
Hi Bob
Thanks for the reply!
Currently I am using 100GB of RAM out of the 128GB available (taking HA into account) so I think I am ok here.
Can you expand on what you mean by "no controllers"? The Supermicro servers I have can take up to 6 SATA drives, one M2 drive and there is a PCIe slot for another drive. I think you can have a maximum of 7 drives in total in these machines. Why would I need a controller at all? Can't I just plug the capacity drives into the hot swapable bays and plug the cache tier PCIe drive into the PCIe slot? Why do I need a controller?
Regarding the Witness, yes, I have a switch so the two nodes and Witness appliance can communicate with each other.
I have a standalone ESXi 6.5 host with a generic installation.
The generic installation uses self-signed certificates, which give the typical "there is a problem with this certificate..." error message.
so for laughs and giggles, I want to replace the self-signed cert with an Active Directory Certificate Services cert.
(which is setup with offline root and online intermediate).
the host is not joined to active directory nor is managed by vcenter.
the basic steps to create a cert request, submit to ADCS, download cert, and install into ESXi is not too complicated.
however, the cert does not include the full certificate chain (root + intermediate + host), so I still get the "there is a problem with this certificate"
only now the error is "the certificate cannot be verified up to a trusted certificate authority".
generally, you solve this error message by either
1 - adding the certificate chain for the certificate authority into the host cert store, or
2 - ensure the intermediate CA is accessible to the host
existing documentation has lots of references to VMCA, but that is not installed on ESXi (I checked the file system just to be sure).
so, are there any ssh based instructions for adding the root cert and intermediate cert into the host certificate store?
virtualDD,
No roles for a Standalone ESXi host. Understand.
Will you attach the kickstart script?
I am using Windows 10 Professional.
On my Windows 10 Professional PC, I created a local account and placed the local account in the Administrators group.
I made the password the same as the ESXi local account with the same name.
The firewall has been re-enabled.
I logged into the Windows 10 PC as the local account.
I opened a cmd prompt using the "Run As Administrator" and I issued the command
vicfg-user.pl --server x.x.x.x -l "ABCD" -p "changeme"
I do longer received the Permission Denied message.
I now receive :
Use of uninitialized value in string eq XYZ ...line 869.
Use of uninitialized value in string eq XYZ....line 873.
Use of uninitialized value in string eq XYZ....line 878.
Use of uninitialized value in string eq XYZ....line 882.
Use of uninitialized value in string eq XYZ....line 892.
Any help with the attached script would be appreciated.
Ok. I'll look into upgrading with out backing up the ESXi host.
T.J.
I assume that it will work in WS 12 using virtual hardware #5 - and then finetuning /etc/X11/XF86config.
Next time when I have some time to kill I install it inside WS 7 (still working on a very old laptop here) and then try to use that XF86config in the WS 12 VM.
I think I'm getting it. To successfully rename the Virtual Machine (i.e., the "bundle), I'd need to rename what precedes .vmwarevm, then show the package contents, find the single .vmx file amid the bunch of .vmdk and other files, and change the .vmx file to the same name as the .vmwarevm file.
Moreover, when File>Open looks into the Virtual Machine folder, I gather it doesn't scan the names in that folder but rather looks at the name assigned to the .vmx file inside each of the bundles. Interestingly, the icon for that .vmx file is the icon of the bundle in the VM folder while all the other icons are different. Inside the .vmx file there seems to be a cross reference to the other files which compose the VM and those file names thus don't need to be updated. And in exploring that, I found that the name which appears in the VM Library list does not have to match the name of the .vmwarevm file which that VM on the list will open.
Nothing is ever simple...
Check out below link which clearly explain how to pull firmware info for Qlogic HBA
ESXi: How to find HBA/NIC driver/Firmware version | Virtual Allan
If you found this or any other answer helpful, please consider the use of the Helpful to award points.
Best Regards,
Deepak Koshal
CNE|CLA|CWMA|VCP4|VCP5|CCAH
The name you see in the library and the one you can change is stored in the .vmx file under displayName.
eg.
displayName = "macOS 10.12"
But as you can set that directly from within Fusion it is best edited using Fusion itself instead of directly mucking with settings in the vmx file.
Note that you don't _have_ to rename the vmx file to match your bundle(folder) name, but for consistency it might help.
--
Wil
Yup, there it is on line 46 of that particular .vmx file in the VM in question.
What would I lose in consistency if the .vmx file name doesn't match the .vmwarevm name of the bundle?
First, the key item is that vCenter doesn't care about Horizon View and isn't even aware of it. View is just making API calls to vCenter to run tasks, the focus is not on vCenter but Horizon View. The roadblock people typically hit when upgrading the vCenter with Horizon View is the hostname. If you are upgrading and keeping the hostname, you can pull this off with little pain.
Worse case, you may have to remove and re-add the vCenter server in View Admin. Congrats you avoided the worst which is dealing with a new vCenter hostname and updating all your pools to point to it.
ProTip - PowerCLI for View is excellent if you needed to mass update the pools.
For those interested in pierrelxlabplugin... I have recompiled it for vRops 6.6... but please note I have not tested it in my lab.... as I have my own custom one.... but in theory it should work as I recompiled it with the new libs from 6.6 and JRE 1.8 which I used for my own version.
If you plan to use it .... make sure to test it in a lab environment before deploying it so something more important, if the Analytics fails to start just remove the JAR and restart vRops.... (or just snapshot maybe?)
Please post your result in here for others to know.... if it fails to work I can have a further look at it in my lab when I get time...
I hope you don't mind me posting it pierrelxlab, I tried to contact you over your blog but it doesn't appear to have worked.... If your not happy with me posting it PM me and I will delete this post.
Cheers
vMan
OK.... so I'm an idiot... I posted the one compiled with 1.7... and named it v66
Here is the correct one, I just tested it and vRops Analytics starts... I did not trigger any alerts as I don't use his version of the custom integration...
Let me know how you go with this version.
Cheers
vMan
This is more on my issue:
Using vmhgfs with drvfs on 16179 · Issue #1959 · Microsoft/BashOnWindows · GitHub
Just consistency for you, for the VM itself it doesn't matter.
--
Wil
That's Sierra, not High Sierra
