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

VMware View and vsphere 5.5U3b cause composer issues

So one thing I wanted to make people aware of is that if you upgrade your host to 5.5U3b, you will break VMware View on version older than 6.2.

So why does this happen?
With the release of 5.5U3b VMware has disabled SSLv3
http://pubs.vmware.com/Release_Notes/en/vsphere/55/vsphere-esxi-55u3b-release-notes.html

Older version of View utilize the SSLv3 to communicate with both vCenter and the ESXi hosts.

You may see errors such as:

| UFA main thread 16 | FATAL | CommonLib.UfaSubsystem.UfaWorkItem - UFA error: fail in open computer operation.
| UFA main thread 16 | INFO | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA error: fail to finish init disk operation for disk: datastore: [datastore_name] VMNAME1/VMNAME1-internal.vmdk, host: FQDN, port: 902.
| UFA main thread 16 | FATAL | CommonLib.UfaSubsystem.InitializeDiskSetUfaWorkItem - Error: CompletionCallbackProxy failed to init disk with result





If you have upgraded your host , you have 2 options.

1. Upgrade to View 6.2 or 6.2.1, this meets the need to not use SSLv3 and no changes have to be made to the host, however there are some caveats to 6.2.1 ill address later.

2. Re-enable SSLv3 on all your hosts and vCenter. This has been documented , but is a painful process and exposes you to to the POODLE vulnerability.
http://kb.vmware.com/kb/2139396


Bottom line, read the release notes before upgrading, it will save you may headaches.

Comments

Popular posts from this blog

vSphere 7 - Specify a vmkernel adapter to use for NFS datastores Step By Step \ Walkthrough on a DVS

Horizon View 2-factor Authentication for Free! with Google Authenticator or others

PowerCLI Script creating Instant Clone Pools in Horizon 8 Walk through