VMware: Unterschied zwischen den Versionen

Version vom 5. November 2015, 10:14 Uhr

ESXi / vSphere

Configuring a persistent scratch location using the vSphere Client

You can configure persistent scratch space for ESXi using the vSphere Client:

1. Connect to vCenter Server or the ESXi host using the vSphere Client.
2. Select the ESXi host in the inventory.
3. Click the Configuration tab.
4. Click Storage.
5. Right-click a datastore and select Browse.
6. Create a uniquely-named directory for this ESX host (for example, .locker-ESXHostname)
7. Close the Datastore Browser.
8. Click Advanced Settings under Software.
9. Select the ScratchConfig section.
10. Change the ScratchConfig.ConfiguredScratchLocation configuration option, specifying the full path to the directory.
11. Click OK.

Put the ESXi host in maintenance mode and reboot for the configuration change to take effect.

   For example:
   /vmfs/volumes/DatastoreName(uid)/.locker-ESXHostname

Mount CDROM (ESXi)

1. esxcfg-mpath –l

Disk clonen

VMDK zu RDM

1. Load the iso9660 module with this command: vmkload_mod iso9660
2. Mount the CDROM using the device determined earlier with

   esxcfg-mpath -l:/sbin/vsish -e set /vmkModules/iso9660/mount mpx.vmhba32:C0:T0:L0

The CDROM will be mounted under /vmfs/volumes/ [CDROM Label] /

Treiberpaket installieren ESXi4.1

• SSH aktiviern.
• Treiberpaket mit WinScp Lokal zur Verfügung stellen.

   esxupdate -b ....vib update

Dumpfile vom Datastore verschieben

• Aktuelle Konfiguration ansehen.

    esxcli --server="Servername" system coredump file list
    Path                                                                                                     Active  Configured       Size
    -------------------------------------------------------------------------------------------------------  ------  ----------  ---------
    /vmfs/volumes/4f02cf6a-5f688578-9659-001aa0c05815/vmkdump/4C4C4544-0031-4310-804D-B9C04F543032.dumpfile   false       false  556793856
    /vmfs/volumes/4f02cf6a-5f688578-9659-001aa0c05815/vmkdump/4C4C4544-005A-4210-804D-CAC04F543032.dumpfile   false       false  556793856
    /vmfs/volumes/4f02d0d4-cf5fa1e5-8740-001aa0c05815/vmkdump/4C4C4544-0054-3310-8054-CAC04F42354A.dumpfile   false       false  552599552
    /vmfs/volumes/4f0d3c58-d333831b-2300-b8ac6f83a070/vmkdump/4C4C4544-004C-5310-804A-B9C04F39354A.dumpfile    true        true  552599552
    /vmfs/volumes/4f0d3c58-d333831b-2300-b8ac6f83a070/vmkdump/4C4C4544-005A-4210-804D-CAC04F543032.dumpfile   false       false  556793856
    /vmfs/volumes/52e12e61-ee80218c-830e-00237dde6e74/vmkdump/4C4C4544-0031-4310-804D-CAC04F543032.dumpfile   false       false  556793856
    /vmfs/volumes/52e12eb7-28781c0c-928a-00237dde6e74/vmkdump/4C4C4544-004C-5310-804A-B8C04F39354A.dumpfile   false       false  552599552
    /vmfs/volumes/53a00284-78ae425f-79be-0026b986caf4/vmkdump/4C4C4544-0030-4310-804D-C8C04F543032.dumpfile   false       false  556793856
    esxcli --server="Servername" system coredump file get
    Active: /vmfs/volumes/4f0d3c58-d333831b-2300-b8ac6f83a070/vmkdump/4C4C4544-004C-5310-804A-B9C04F39354A.dumpfile
    Configured: /vmfs/volumes/4f0d3c58-d333831b-2300-b8ac6f83a070/vmkdump/4C4C4544-004C-5310-804A-B9C04F39354A.dumpfile

• Neues Dumpfile erstellen. (Datastorename)

    esxcli --server="Servername" system coredump file add -d "Datastorename"

• Dumpfilekonfiguraton löschen.

    esxcli --server="Servernsme" system coredump file set -u

• Dumpfilekonfiguration erstellen.

    esxcli --server="Servername" system coredump file set -p /vmfs/volumes/4f02cf6a-5f688578-9659-001aa0c05815/vmkdump/4C4C4544-004C-5310-804A-B9C04F39354A.dumpfile

VMwareplayer

Ubuntu Vmware Player recompilieren

Nach dem Einspielen von Sicherheitsupdates (Kernel) auf dem Hostbetriebsystem stehen keine Netzwerkverbindungen beim VMwareplayer zur Verfügung. Dazu mus das Kernelmodul neu eingebunden werden.

    vmware-modconfig --console --install-all