Posts

How to get llama 2 up and running , in a VM, with no GPU, and limited memory on Ubuntu

Image
OK I decided to write this up after unsuccessfully being able to find all the required info I needed in one place. In this setup we will be using Ubuntu Server 22.04.2 LTS as the OS. I have this running on a home lab ESXi server 8, on a HP Compaq Pro 6300 SFF CPU = Intel Core i7-3770 Installed Memory 16 GB I have some 10K SAS drives installed for the VM's If you have not already, navigate to  Get Ubuntu Server | Download | Ubuntu and download the 22.04.2 LTS ISO Next Lets create our VM that we are going to run this in. *Note Im using ESXi however you can probably do this in Workstation, Fusion, VirtualBox etc The main things to note on the VM creation. Set Ubuntu 64 bit as the guest OS Set your CPU relevant to the physicals CPU, I will be starting with 4 VCPU Set your Memory to as much as you can tolerate, I will be using 12 Disk Space - we are creating a 100G swap file, and the rest of the file can take up some room , so more is better if you can afford it Dont forget to add the U

vCenter Services Dependency tree

 The other day I needed a list of dependency's for the vCenter services. Found out you can do this with service-control --list-dependencies <service name> Version 7.0.3U3h So I started with service-control --status --all, created a list. I started to do this one by one, but of course its more fun to script it so I put all of them and ran a FOR LOOP on it for SERV in $(cat ./serv.txt); do echo $SERV "--" && service-control --list-dependencies $SERV; done >> ServiceDepend.txt applmgmt -- statsmonitor lookupsvc -- rhttpproxy vmware-vpostgres lwsmd -- observability -- observability-vapi -- lookupsvc vpxd-svcs pschealth -- vpxd vlcm -- lookupsvc vmware-vpostgres vpxd vmafdd -- lwsmd vmcad -- vmafdd vmdird vmdird -- vmafdd vmonapi -- lookupsvc sts vmware-analytics -- envoy lookupsvc vmafdd vpxd vmware-certificateauthority -- lookupsvc sts vpxd-svcs vmware-certificatemanagement -- lookupsvc sts vpxd-svcs vmware-cis-license -- envoy lookupsvc sts vmware-conten

Upgrading to vSphere 8 on unsupported hardware

 So im still running unsupported hardware, but perhaps this workaround will let me hold on to my lab hardware just a couple more years longer. Enable SSH into the ESXi host This is what i did that so far is working vi /bootbank/boot.cfg **add in allowLegacyCPU=true to kernelopt vi /altbootbank/boot.cfg **add in allowLegacyCPU=true to kernelopt esxcli software vib remove -n synology-nfs-vaai-plugin ** this vib comes up in the pre-check so it had to be removed reboot cat /bootbank/boot.cfg cat /altbootbank/boot.cfg **Make sure the allowLegacyCPU=true is still there esxcli software profile update -p ESXi-8.0.0-20513097-standard -d /vmfs/volumes/340ffc1d-98386c9a/VMware/vSphere/8.x/VMware-ESXi-8.0-20513097-depot.zip --no-hardware-warning cat /bootbank/boot.cfg cat /altbootbank/boot.cfg **Make sure the allowLegacyCPU=true is still there reboot cat /bootbank/boot.cfg cat /altbootbank/boot.cfg **Make sure the allowLegacyCPU=true is still there reboot **reboot one more time just to be sure

VMSA-2022-0024 CVE-2022-31676 How to update your VMware tools 12.1 and beyond

Image
 With VMSA-2022-0024 just coming out, figured Id do a quick post on how to update your VMware tools. First open up lifecycle Manager, and click Action 'Sync Updates': If you VCSA does not have internet access or the depo is not updated , you can manually import updates (as I had to). Create (or edit ) a new Base Line- Select Patch Select  VMware as the Vendor Any , Any, Any Release date  After 8/1/2022 Click Matched and make sure they are selected Click Next, Next Finish Attach base line to your ESXi host, and check compliance Remediate as soon as possible (no reboot required). Once All ESXi host are updated, you can then right click the VM and upgrade VMware tools. Optionally if you have them set to auto update tools on reboot then simply shutdown and power back on.

Configure windows (and MAC) to point to a specific DNS server for Specific domain

 I have probably searched off an on for this solution for about 10 years at this point, and always found some other way to work around the issue. Well today I was searching for some other DNS settings and found this: https://docs.microsoft.com/en-us/powershell/module/dnsclient/add-dnsclientnrptrule?view=windowsserver2022-ps And it actually works! So here is my example: Add-DnsClientNrptRule -Namespace ".universe.lab" -NameServers "10.10.1.1" Ran this as an admin I want any thing going to 'universe.lab' (dont forget to pre-pend the "." ) to go to 10.10.1.1 And then you can check what you have configured PS C:\WINDOWS\system32> get-DnsClientNrptRule Name                             : {2942DF55-16A3-4EED-B71B-7274B18F4FED} Version                          : 2 Namespace                        : {.universe.lab} IPsecCARestriction               : DirectAccessDnsServers           : DirectAccessEnabled              : False DirectAccessProxyType         

VCSA Partition size by Storage Selection Size

Image
 Ran into an issue upgrading a VCSA where it ran out of storage in the /storage/seat partition. Figured it would be easy enough to select a larger options during deployment, however I wanted to know what my options were as I didn't want to go over kill on the partition. Interestingly I was only able to find info on a Tiny deployment, no one seams to have any additional info on the additional deployment sizes. So I just deployed the appliance over and over again and here are the results: XL Storage Size Large Storage Size Default So lets create a matrix: Mounted Default Large Extra Large /storage/core 25GB 25GB 25GB /storage/log 9.8GB 9.8GB 9.8GB /storage/db 9.8GB 9.8GB 9.8GB /storage/dblog 15GB 15GB 15GB /storage/seat 9.8GB 541GB 1.4TB /storage/netdump 985MB 985MB 985MB /storage/autodeploy 9.8GB 9.8GB 9.8GB /storage/imagebuilder 9.8GB 9.8GB 9.8GB /s

Upgrade VMware tools to the latest version , automatically

Image
Wanted to put out a quick post about updating VMware tools to the latest version, in this case 12.0.5 on all VMs in an environment. For vSphere 7.x this is really easy. First download the " VMware Tools Offline VIB Bundle" . https://customerconnect.vmware.com/en/downloads/details?downloadGroup=VMTOOLS1205&productId=1259&rPId=88838 Upload this to your vSphere Lifecycle Manager by clicking on three bars on the left, then in the Lifecycle Manager page, click Actions > Import Updates Select the file and it will upload This should add it to the Non-Critical Patches (Predefined) baseline. If not you can create a new baseline and just add in the tools package Attach the redefined or custom baseline to your ESXi host and remediate the host , the tools update did not require a reboot. Once all the hosts are updated, you can set your VMs to automatically upgrade on next power on \ reboot https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/G

vSphere 7.0 U3c released

Image
 vSphere U3c finally released. TL;DR https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3c-release-notes.html Here is my lab process: ESXi Host I am not using vLCM as these hosts are unsupported. Well maybe not to night , Ill check again in a little while. Dates appear to be a bit off: Wow... alot of updates Here we go....... Well... That was un event full No option to update vCenter... guess ill check tomorrow. Hmm nothing this morning...  Nothing found in the logs 2022-01-28T13:07:47 PM UTC [2136]DEBUG:vmware.appliance.update.update_functions:runCommandAndCheckResult failed: '--2022-01-28 13:07:47--  https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899- be0a-6daade4005a3/7.0.3.00200.latest/manifest/manifest-latest.xml\nResolving vapp-updates.vmware.com ... 69.192.208.24\nConnecting to vapp-updates.vmware.com|69.192.208.24|:443... connected.\nHTTP request sent, a waiting response... \n  HTTP/1.1 404 Not Found\ n  Accept-Ranges: bytes\n