Re: List total number of vCPU per ESX host to avoid CPU over allocation when deploying VM
Re: booting on a physical drive (installation made with Workstation 15.5.6)
thanks for reply
it seems to me that i did that some years ago with mbr disk, but perhaps i made a mistake in my memory
so is there a solution to simply modify the disk to make it run on a netbook ?
Re: booting on a physical drive (installation made with Workstation 15.5.6)
Re: Error with Mac OS Big Sur
I get this error when the kernel extension isn't loaded.
Once it's loaded, I get the "physical memory" error as described above and in that thread.
Check if your kernel extension is loaded with "kextstat"
xbytez@donglebookpro ~ % kextstat | grep vmware
115 0 0xffffff7f9f049000 0x4000 0x4000 com.vmware.kext.vmioplug.19.5.0 (19.5.0) 93055748-9D70-3575-B2E3-DDF295C269B4 <61 6 5 3 1>
xbytez@donglebookpro ~ %
Dell Esxi 7.0 upgrade files no longer available
In the past, when Dell provided their version of an update to Esxi, you could download it in the form of a zip file. You then applied it in this manner (from the esxi command line):
esxcli software profile update -d /VMware-VMvisor-Installer-7.0.0-15843807.x86_64-DellEMC_Customized-A00.zip -p DEL-ESXi-700_15843807-A00
When you go to the Dell website and attempt to download the latest version (Version 7.0, A02), the files are no longer there and, instead you are met with this message:
"Dell EMC has migrated the latest revision of the Dell customized ESXi images with customized drivers to VMware's website. This change aligns with industry-standard practices and brings the Dell EMC-customized image to the same location as our competitors. For customers who manage heterogeneous fleets, this simplifies the procurement of SW images as they will all be housed in one location. Please go to your my.vmware.com license portal or click the link below to be redirected now. Older revisions of these images can be downloaded from www.dell.com/support in case there is a requirement
ISO Image Link: https://my.vmware.com/en/web/vmware/downloads/details?downloadGroup=OEM-ESXI70GA-DELLEMC&productId=974"
One you go to the link provided, you no longer have any file available except the ISO file. I know of no way to upgrade from the command line via the ISO file.
Any ideas?
SEG KCD Certificate Issues
Hi All,
I'm hoping someone has run into this before as I've been overthinking and driving myself crazy trying to figure it out.
I'm working on setting up SEGv2 on UAG KCD.
We are continuing to run into this error:
Unable to get Peer Certificate Chain, won't be able to determine UPN. Error: peer not authenticated
I've been told that the Client Chain that needs to be uploaded is the full chain for your CA, which I have done several times. My understanding is that the device presents your user certificate to the SEG, and the SEG compares that to the truststore.
I know that those certificates live in the truststore.jks but beyond that and confirming the certs are present in there I have had zero luck.
Has anyone run into this and solved it?
Re: booting on a physical drive (installation made with Workstation 15.5.6)
thanks for the documentation
i would just like to say that it's not a vmdk file, the installation and the partitions seems to be like on a physical machine
i have just made an experiment, i booted with supergrub and i manage to boot on this key
so perhaps it's possible to boot with just by modifying something in the efi partition ?
Re: Error with Mac OS Big Sur
Does not work, will not work. Wait for the update to the tech preview coming sometime in July.
Re: VMware Fusion HOSTING of NEWER version of Mac OS the NATIVELY installed?
Your process is right. As for the version issues, I know there was a defect with the installer that didn't properly do a version check, so that's probably part of the problem.
Re: booting on a physical drive (installation made with Workstation 15.5.6)
It seems to me that all information provided by VMware regarding V2P is rather outdated (6+ years old). In addition, the legalese in the Note of this VMware Knowledge Base article is quite frightening. Could some Moderator please enlighten us whether V2P is some sort of a taboo issue (and perhaps a non-desirable topic to raise in this Community) and whether performing V2P is actually legal or not and under which circumstances?
Re: booting on a physical drive (installation made with Workstation 15.5.6)
I only recommended reading those posts. I have not added actions to do.
I don't think there is anything else to add.
ARomeo
Re: booting on a physical drive (installation made with Workstation 15.5.6)
It’s not for moderators to say one way or another. We “police” what we know is illegal, such as running MacOS on a Windows PC with a hacked copy of Workstation, but I personally see no reason for us to get involved in this topic - perhaps another moderator will think differently though.
Re: Нет пункта migrate и clone
Moderator: Thread moved to the Russian forum area.
Re: VCSA 6.7U2 VAMI Update Fails With "Check the URL and try again"
I updated our test ENV vcenter from 6.5 to 7.0
I ran into this error with the proxy setting
Disabling the proxy and manually putting the proxy settings via SSH into /etc/wgetrc allowed me to update to the latest vcenter 7.0 build
thanks
Re: Dell Esxi 7.0 upgrade files no longer available
Hi,
below what you can do:
Downloading Dell EMC customized ESXi image from VMware site
To download the ESXi image, do the following
- Go to my.vmware.com and log in with your account credentials.
- Select
- Select the image version from the Select Version list.
- Click Custom ISOs.
- Expand the OEM Customized Installer CDs option and then click Go to Downloads to download the image.
VMware vSphere ESXi 7.x on Dell EMC PowerEdge Systems Image Customization Information
ARomeo
Re: booting on a physical drive (installation made with Workstation 15.5.6)
sorry, i didn't know it was illegal
it was just a question to make an experiment
it's true that nowodays, virtualization is probably sufficent in most of case
so it's not a problem at all
thanks for your answers
Ошибка в консолидации и Veeam
Добрый день. Имеется два сервера - файловый сервер и бекап сервер с Veeam . Бекап сервер производил снепшоты файлового сервера, в один из дней часть снепшотов были "в грязную" удалены с диска бекап сервера, что естественно было ошибкой. Через некоторый промежуток времени файловый сервер запросил консолидацию в vmware, но консолидация происходила с ошибкой. После отключения бекап сервера консолидация прошла успешно (отключение бекап сервера видимо тоже было ошибкой), но после этого бекап сервер перестал запускаться с ошибкой:
Failed to start the virtual machine.
Cannot open the disk '/vmfs/volumes/файловый сервер.vmdk' or one of the snapshot disks it depends on.
Failed to lock the file
Module Disk power on failed.
Если отключить файлоый сервер, то бекап сервер начинает запускаться, то есть одноврменно сервера не запускаются.
Как выйти из этой ситуации с минимальными потерями? В случае удаления бекап сервера и настройки его заново это может привести к ошибкам в работе файлового сервера?
Буду рад любой помощи, спасибо!
Re: Dell Esxi 7.0 upgrade files no longer available
He ask for an upgrade ZIP rather than an ISO and he took notice that the ISO is now also available on vmware.com. Notice: 2 days ago the ISO was also on dell.com as always.
Regards,
Joerg
VMWare not compatible with Windows 10 2004 upgrade
Hi all,
Running W10 Pro x64. Today I started with the 2004 update. During the update I got the message that VMWare had to be uninstalled as it is not compatible with Windows 10. I thought this was nonsense as it has allways been working well and still does. I purchased it and I use it, so uninstalling was no option. I wasn't able to continue the update process without uninstalling VMWare, so I quitted the update.
So the 2004 update is no option for me.
I hope I can skip this one and receive other updates. Let's wait and see.
I'm using the VMWare Pro 12 version.
Updating this to 15.5 is no option as it will cost me $ 150,-, and the current version 12 works fine.
Any of you had the same problem?
Fokke Nauta
All VMs Are a Blank Screen after Workstation Pro Update
Workstation Pro Version: 15.5.6 build-16341506 on Windows 10 2004
ESXi Version: 7.0.0 (Build 16324942)
After applying the most recent Worksation update, all my VMs show nothing but a black screen in Workstation Pro. It doesn't matter if they are local or remote VMs, or whether they are Windows, Linux. I can't even see the console on a headless Linux server VM.
I have an another device with Workstation Pro 15.5.2 build-15785246 running on a Linux laptop and everything is functioning normally.
Is there a way to uninstall a Workstation Pro update?