How to generate a full memory DUMP of a VM

Windows DUMP file provides information about the cause of the system crash. But generating a DUMP file on the ESXi system is a bit different. So, will look at the steps. We have divided the process into 2 main steps.

Step 01 – Create and download a VM snapshot

  • In the VMware environment, select the virtual machine that has issues.
  • Replicate the issue on the virtual machine.
  • Right-click the virtual machine and click Snapshots → Take snapshot.

  • Type the name, select the check box next to Snapshot the Virtual Machine’s memory and click OK.

  • Select the virtual machine and click Datastores and click the datastore name.
  • Select the virtual machine, select the .vmsn file (VMware Snapshot file), click Download and save the file locally.

Step 02 – Use the vmss2core tool to create a memory dump from the virtual machine snapshot

  • Download Vmss2core.
  • Select the check box next to I have read and agree to the Technical Preview License I also understand that Flings are experimental and should not be run on production systems. Select the file for your operating system from the drop-down menu (for example, if you want to run the tool on Windows, select vmss2core-sb-8456865.exe) and click Download.
  • Place the vmss2core tool and the VMware snapshot file into the same folder.
  • Run the vmss2core (vmss2core-sb-8456865.exe) in the command line with the following parameters.
  • Specify the guest operating system from which the snapshot was created.

Use quotes if the filename contains blank spaces.

vmss2core-sb-8456865.exe -W8 “virtual_machine_name.vmsn”

  • -W8 —Windows 8 and later or Windows Server 2012 and later.
  • -W —Windows 7 and older or Windows Server 2008 and older.

Finally, you may use the WinDbg tool to analyze the generated Windows DUMP file. 

Assign a static IP on Ubuntu server 20

Ubuntu 17 and later versions control the networking by a feature called “Netplan“. The configuration files are located in the /etc/netplan. Under the directory, you will find either 50-cloud-init.yaml or 00-installer-config.yaml 

Step 01: First locate the configuration file under /etc/netplan

Step 02: In my enviornment, the file is 00-installer-config.yaml. So, edit the configuration file with either nano or vim. sudo nano /etc/netplan/00-installer-config.yaml

Step 03: Update the networking configuration as appropriately. A sample configuration will look like below

network:
ethernets:
enp0s3:
dhcp4: no
addresses: [192.168.2.150/24]
gateway4: 192.168.2.1
nameservers:
addresses: [8.8.8.8, 192.168.2.1]

Step 04: Save & exit the configuration editor. And then apply the netplan configuration. sudo netplan apply

Finally, reboot the server and verify the changes by running ifconfig or ip a