Nested ESXi install in Proxmox: Step-by-Step
Learn how to use Proxmox VE for nested ESXi virtualization in your home lab with this step-by-step guide. Learn ESXi clustering and other configurations with nested virtualization.
Month: December 2023
vSphere data loss bug returns – CBT issues in…
vSphere data loss bug returns – CBT issues in…
The Issue | I keep saying, there are no new ideas in technology, just re-hashes of old ones. That is also true for VMware and their data loss issues. The vSphere-based change block tracking (CBT) bug […]
VMware Holodeck in a #HomeLab
VMware Holodeck in a #HomeLab
So since all the announcement’s at VMware Explore 2023 in Vegas I thought it was time to get my lab back in order along with all the latest updates. I noticed during some of the sessions that a project called Holodeck was mentioned and soon found this was a great expansion of an automated full […]
Simplified Guide: How to Convert VM Snapshots into Memory Dumps Using vmss2core
Introduction
In the complex world of virtualization, developers often face the challenge of debugging guest operating systems and applications. A practical solution lies in converting virtual machine snapshots to memory dumps. This blog post delves into how you can efficiently use the vmss2core tool to transform a VM checkpoint, be it a snapshot or suspend file, into a core dump file, compatible with standard debuggers.
Step-by-Step Guide
Break down the process into clear, step-by-step instructions. Use bullet points or numbered lists for easier readability. Example:
Step 1: Create and download a virtual machine Snapshots .vmsn and .vmem
- Select the Problematic Virtual Machine
- In your VMware environment, identify and select the virtual machine experiencing issues.
- Replicate the Issue
- Attempt to replicate the problem within the virtual machine to ensure the snapshot captures the relevant state.
- Take a Snapshot
- Right-click on the virtual machine.
- Navigate to Snapshots → Take snapshot
- Enter a name for the snapshot.
- Ensure “Snapshot the Virtual Machine’s memory” is checked
- Click ‘CREATE’ to proceed.
- Access VM Settings
- Right-click on the virtual machine again.
- Select ‘Edit Settings’
- Navigate to Datastores
- Choose the virtual machine and click on ‘Datastores’.
- Click on the datastore name
- Download the Snapshot
- Locate the .vmsn ans .vmem files (VMware Snapshot file).
- Select the file, click ‘Download’, and save it locally.
Step 2: Locate Your vmss2core Installation
- For Windows (32bit): Navigate to
C:\Program Files\VMware\VMware Workstation\ - For Windows (64bit): Go to
C:\Program Files(x86)\VMware\VMware Workstation\ - For Linux: Access
/usr/bin/ - For Mac OS: Find it in
/Library/Application Support/VMware Fusion/
Note: If vmss2core isn’t in these directories, download it from New Flings Link (use at your own risk).
Step 3: Run the vmss2core Tool
vmss2core.exe -N VM-Snapshot1.vmsn VM-Snapshot1.vmem vmss2core version 20800274 Copyright (C) 1998-2022 VMware, Inc. All rights reserved.
Started core writing.
Writing note section header.
Writing 1 memory section headers.
Writing notes.
... 100 MBs written.
... 200 MBs written.
... 300 MBs written.
... 400 MBs written.
... 500 MBs written.
... 600 MBs written.
... 700 MBs written.
... 800 MBs written.
... 900 MBs written.
... 1000 MBs written.
... 1100 MBs written.
... 1200 MBs written.
... 1300 MBs written.
... 1400 MBs written.
... 1500 MBs written.
... 1600 MBs written.
... 1700 MBs written.
... 1800 MBs written.
... 1900 MBs written.
... 2000 MBs written.
Finished writing core.- For general use:
vmss2core.exe -W [VM_name].vmsn [VM_name].vmem - For Windows 8/8.1, Server 2012, 2016, 2019:
vmss2core.exe -W8 [VM_name].vmsn [VM_name].vmem - For Linux:
./vmss2core-Linux64 -N [VM_name].vmsn[VM_name].vmemNote: Replace [VM_name] with your virtual machine’s name. The flag -W, -W8, or -N corresponds to the guest OS.
#vmss2core.exe
vmss2core version 20800274 Copyright (C) 1998-2022 VMware, Inc. All rights reserved. A tool to convert VMware checkpoint state files into formats that third party debugger tools understand. It can handle both suspend (.vmss) and snapshot (.vmsn) checkpoint state files (hereafter referred to as a 'vmss file') as well as both monolithic and non-monolithic (separate .vmem file) encapsulation of checkpoint state data. Usage: GENERAL: vmss2core [[options] | [-l linuxoffsets options]] \ <vmss file> [<vmem file>] The "-l" option specifies offsets (a stringset) within the Linux kernel data structures, which is used by -P and -N modes. It is ignored with other modes. Please use "getlinuxoffsets" to automatically generate the correct stringset value for your kernel, see README.txt for additional information. Without options one vmss.core<N> per vCPU with linear view of memory is generated. Other types of core files and output can be produced with these options: -q Quiet(er) operation. -M Create core file with physical memory view (vmss.core). -l str Offset stringset expressed as 0xHEXNUM,0xHEXNUM,... . -N Red Hat crash core file for arbitrary Linux version described by the "-l" option (vmss.core). -N4 Red Hat crash core file for Linux 2.4 (vmss.core). -N6 Red Hat crash core file for Linux 2.6 (vmss.core). -O <x> Use <x> as the offset of the entrypoint. -U <i> Create linear core file for vCPU <i> only. -P Print list of processes in Linux VM. -P<pid> Create core file for Linux process <pid> (core.<pid>). -S Create core for 64-bit Solaris (vmcore.0, unix.0). Optionally specify the version: -S112 -S64SYM112 for 11.2. -S32 Create core for 32-bit Solaris (vmcore.0, unix.0). -S64SYM Create text symbols for 64-bit Solaris (solaris.text). -S32SYM Create text symbols for 32-bit Solaris (solaris.text). -W Create WinDbg file (memory.dmp) with commonly used build numbers ("2195" for Win32, "6000" for Win64). -W<num> Create WinDbg file (memory.dmp), with <num> as the build number (for example: "-W2600"). -WK Create a Windows kernel memory only dump file (memory.dmp). -WDDB<num> or -W8DDB<num> Create WinDbg file (memory.dmp), with <num> as the debugger data block address in hex (for example: "-W12ac34de"). -WSCAN Scan all of memory for Windows debugger data blocks (instead of just low 256 MB). -W8 Generate a memory dump file from a suspended Windows 8 VM. -X32 <mach_kernel> Create core for 32-bit Mac OS. -X64 <mach_kernel> Create core for 64-bit Mac OS. -F Create core for an EFI firmware exception. -F<adr> Create core for an EFI firmware exception with system context at the given guest virtual address. Links:
How to Rebuild a VMX File from vmware.log on an ESXi 8 Host via SSH
Introduction
Rebuilding a VMX file from vmware.log in VMware ESXi can be crucial for restoring a virtual machine’s configuration. This guide will walk you through the process using SSH according KB 1023880, but with update for ESXi 8.0. It was necessary add #!/bin/ash because of error “Operation not permitted”.
Step 1: SSH into Your ESXi Host
First, ensure SSH is enabled on your ESXi host. Then, use an SSH client to connect to the host.
Step 2: Navigate to the Virtual Machine’s Directory
Change to the directory where your VM resides. This is usually under /vmfs/volumes/.
cd /vmfs/volumes/name-volume/name-vmStep 3: Create and Prepare the Script File
Create a new file named vmxrebuild.sh and make it executable:
touch vmxrebuild.sh && chmod +x vmxrebuild.shStep 4: Edit the Script File for ESXi 8
Edit the vmxrebuild.sh file using the vi editor:
- Run
vi vmxrebuild.sh. - Press
ito enter insert mode. - Copy and paste the following script (adjust for your ESXi host version).
- Press
ESC, then type:wq!to save and exit.
Script Content for ESXi 8.0:
#!/bin/ash
VMXFILENAME=$(sed -n 's/^.*Config file: .*\/\(.\+\)$/\1/p' vmware.log)
echo -e "#\041/usr/bin/vmware" > ${VMXFILENAME}
echo '.encoding = "UTF-8"' >> ${VMXFILENAME}
sed -n '/DICT --- CONFIGURATION/,/DICT ---/ s/^.*DICT \+\(.\+\) = \(.\+\)$/\1 = \2/p' vmware.log >> ${VMXFILENAMEStep 5: Run the Script
Execute the script to rebuild the VMX file:
./vmxrebuild.shConclusion
This process extracts the necessary configuration details from the vmware.log file and recreates the VMX file, which is vital for VM configuration. Always back up your VM files before performing such operations.
Optimizing NSX Performance Based on Workload…
Optimizing NSX Performance Based on Workload…
Optimizing NSX Performance Based on Workload Overview Performance tuning, in general, requires a holistic view of the application traffic profiles, features leveraged and the criteria for performance from the application perspective. In this blog, we will take a look at some of the factors to […]
Enhancing the Raspberry Pi 5 with PCIe Gen 3.0 Speeds
The Raspberry Pi 5, a remarkable addition to the Raspberry Pi series, boasts an advanced configuration with five active PCI Express lanes. These lanes are ingeniously distributed with four dedicated to the innovative RP1 chip, which supports a variety of I/O functionalities such as USB, Ethernet, MIPI Camera and Display, and GPIO. Additionally, there’s a fifth lane that interfaces with a novel external PCIe connector.
In its default setup, the Raspberry Pi 5 operates all PCIe lanes at Gen 2.0 speeds, offering a throughput of approximately 5 GT/sec per lane. This standard setting is fixed for the internal lanes connected to the RP1 chip. However, for users seeking enhanced performance, there’s an exciting tweak available for the external PCIe connector. By simply adding a couple of lines to the /boot/config.txt file and rebooting your device, you can elevate the external connector to Gen 3.0 speeds. This upgrade boosts the data transfer rate to 8 GT/sec, nearly doubling the default speed.
To achieve this, insert the following commands in your /boot/config.txt file:
dtparam=pciex1
dtparam=pciex1_gen=3After these adjustments and a system reboot, your Raspberry Pi 5 will operate the external PCIe lane at the faster Gen 3.0 speed, unlocking new potential for your projects and applications.
Links:
UniFi Network Server with Docker
UniFi Network Server with Docker
LinuxServer.io makes some great Docker images. I’ve been using their UniFi Controller image for a very long time. Sadly it is being deprecated in January 2024. Fortunately, they have a new replacement image named UniFi Network Application. There’s a bit more to the setup as the database portion [..]
12 Days of Home Labs
12 Days of Home Labs
Welcome to the “12 days of Home Labs”! Over the course of the next twelve days, we will be sharing with you some fascinating home lab projects, ideas, and tips that will take your lab to the next level. Whether you are just starting or already an experienced home-labber, we have something for […]
🎁 #12DaysOfHomelabs Holiday Series – Podcast…
🎁 #12DaysOfHomelabs Holiday Series – Podcast…
During this week’s #VMware #vCommunity Podcast #674, host @ericnipro & @vFrankyB will preview our ever-popular #12DaysOfHomelabs holiday series, kicking off THIS Thurs, Dec. 21! Tune in Weds, tomorrow, at noon Pacific