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...
Post a Comment
-

Thanks to Arron Parker for his writeup on the changes

Profile Changes in Windows Vista/Longhorn Server

by Aaron Parker on Friday, August 25, 2006

in Windows

Windows Vista and Longhorn Server introduce a number of new user profile paths and environment variables that differ from earlier versions of Windows and these changes may have an impact on scripts such as logon scripts and application install scripts. Most scripts should work correctly – VBScript scripts that use system functions to find folder paths should work as expected, however batch scripts that use environment variables or hard codes scripts will require modifications. Here’s a short run down of the changes.

The following table lists the old profile path and the corresponding new path under Windows Vista/Longhorn Server:

Old Path New Path
\Documents and Settings \Users
\Documents and Settings\Default User or
%LOGONSERVER%\NETLOGON\Default User		 \Users\Default or
%LOGONSERVER%\NETLOGON\Default User.v2
\Documents and Settings\\My Documents \Users\\Documents
\Documents and Settings\\My Documents\My Pictures \Users\\Pictures
\Documents and Settings\\My Documents\My Music \Users\\Music
\Documents and Settings\\Favorites \Users\\Favorites
N/A \Users\\Contacts
N/A \Users\\Downloads
N/A \Users\\SavedGames
\Documents and Settings\\Application Data \Users\\AppData\Roaming
\Documents and Settings\\Local Settings\Application Data \Users\\AppData\Local
\Documents and Settings\\Start Menu \Users\\AppData\Roaming\Microsoft\Windows\Start Menu
\Documents and Settings\All Users \Users\Public
\Documents and Settings\All Users\Start Menu \ProgramData\Microsoft\Windows\Start Menu
\Documents and Settings\All Users\Desktop \Users\Public\Desktop

Folders to take note of here are the folders in the All Users path. Many older applications that use out of date methods to resolve system folders, will resolve paths under \ProgramData when looking for common locations. For example the common desktop may be resolved as \ProgramData\Desktop, however this is actually a junction point for \Users\Public\Desktop. A DIR /A:H listing in \ProgramData folder reveals the following junction points:

Path Points To
\ProgramData\Application Data \ProgramData
\ProgramData\Desktop \Users\Public\Desktop
\ProgramData\Documents \Users\Public\Documents
\ProgramData\Favorites \Users\Public\Favorites
\ProgramData\Start Menu \ProgramData\Microsoft\Windows\Start Menu
\ProgramData\Templates \ProgramData\Microsoft\Windows\Templates

These junction points should offer backward compatibility for older applications, however I have found that some of my installation scripts are not cleaning up shortcuts from the public desktop as expected.

There are also differences in environment variables between the new version of Windows and the older versions. Windows Server 2003 and below define the following variables relating to profiles:

ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\aaron\Application Data
HOMEPATH=\Documents and Settings\aaron
TEMP=C:\DOCUME~1\aaron\LOCALS~1\Temp
TMP=C:\DOCUME~1\aaron\LOCALS~1\Temp
USERPROFILE=C:\Documents and Settings\aaron

Windows Vista and Longhorn Server define the same variables while adding a couple more.

ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\aaronp\AppData\Roaming
HOMEPATH=\Users\aaronp
LOCALAPPDATA=C:\Users\aaronp\AppData\Local
ProgramData=C:\ProgramData
PUBLIC=C:\Users\Public
TEMP=C:\Users\aaronp\AppData\Local\Temp
TMP=C:\Users\aaronp\AppData\Local\Temp
USERPROFILE=C:\Users\aaronp

In practice, I’ve found that scripts that reference locations such as %ALLUSERSPROFILE%\Desktop, are not performing actions as intended and will have to be updated to use %PUBLIC% instead. Certainly something that requires more investigation.

Comments

Post a Comment

Popular posts from this blog

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

-
Image
 Recently I needed to setup a NFS server but needed it to specifically be on a specific vmkernel adapter. I found this KB https://kb.vmware.com/s/article/50112854 however there were some things missing so I decided to write this walkthrough incase it helps any one else. First thing , remove all NFS mounted datastores if you haven't already. I ran through this on 7.0.2 however is probably the same for other versions. Step 1: This is going to be on a DVS, so we want to go ahead and create a port group to silo off our NFS traffic. To make life easy, we will just call it NFS Static binding and elastic port allocation were the defaults so I let these there. If you are VLAN'ing your traffic modify this info here, and complete the wizard. Next put your host into Maintenance Mode We are going to add a New TCP/IP stack to the host. First check that you have not already created one in the UI by opening a browser to the ESXi host, navigate to networking > TCP/IP Stacks SSH into your E...
Read more

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

-
Image
So after quite a bit of work on my proof of concept google authenticator server, a colleague pointed out that LinOPT has already created this, along a whole slew of other options. So after spending a couple of nights reading and testing I figured id post a simple walk-through to get this up and running in your environment. As mentioned in the title this is a Free solution , however if you are wanting to scale this in a large organization you would most likely want to explore their support contracts , this is a good fall back when things just don't work and this also help the developers keep this type of software free for the rest of us. To start off we want to create 2 objects in Active Director. The first is just a standard user account LinOTP will use to connect to your domain. You can put these any where in your domain as we will access them directly later. In my case i create one called 'LinOTP Svc' and put it in the default Users OU. Next create a Global or ...
Read more

VMware View 2-factor authentication with Google Authenticator - Part Four

-
Image
Adding View to the Mix. Now that we have (almost) everything setup on the Linux server side, we just need to finish the view configuration and the client portion. Open up the View administrator, navigate to View Configuration > servers. Select the Connection Servers tab Select your Server and click the Edit button. in the "Edit Connection Server Settings" pop up window, change 2-Factor authentication to RADIUS Check enforce 2-factor and windows user name matching On Select Authenticator Select New. Update the fields with your information. We are now down with the View Configuration. download and install the google authenticator app for your device: https://support.google.com/accounts/answer/1066447?hl=en Now we sill set up the user to authenticate. Open up a putty session to your ubuntu server. type su someADusername you should now be logged in as that users run gauth, this will generate the QR code to scann from the install app on your ...
Read more