Directly on the ESXi host: esxcfg-info | grep -w “Serial Number” Remotely with PowerCLI: $myCredentialsObject = Get-Credential Connect-VIServer -Server <ServerName> -Credential $myCredentialsObject Get-VMHost | Select @{N=’VMHost’;E={$_.Name}}, @{N=’Serial’;E={($_.ExtensionData.Hardware.SystemInfo.OtherIdentifyingInfo | where {$_.IdentifierType.Key -eq “ServiceTag”}).IdentifierValue}}
Qemu is a generic and open source machine emulator and virtualizer. This article will show you how to check and test if an ISO or USB Drive is bootable using Qemu in the Linux operating system. In my opinion this is a cool way to confirm whether or not image files (ISO) and USB drives/devices should be expected to be bootable during boot of a normal x86/x64 desktop/laptop/server. With a Bootable drive, you can not only install distro applications, you can also use the disk to test the desktop experience of Ubuntu without needing to meddle with your computer’s configuration
If you have messed up the routing table on a remote Windows Server, this network adapter recovery method may help you or inspire one even better. Since my particular issue happened over 5 years ago I’m honestly having a hard time remembering the exact scenario, but obviously there was a communication problem due to accidental static route deletion. The remote computer still needs to have layer 3 connectivity with your own client machine which might entail putting yourself in the same broadcast domain if that is do-able. psexec.exe \\ServerName -s powershell Enable-PSRemoting -Force Invoke-Command -ComputerName ServerName -ScriptBlock {route add -p
Enable Inter-VM Transparent Page Sharing (v5.x – 6.7) If you’re using VMWare ESXi in a non-production environment, such as a home lab, consider changing the advanced host setting Mem. ShareForceSalting to “0” in order to encourage likeliness of the hypervisor to increase the inter-VM page sharing pool. After doing so, the PSHARE on my host increased from about 3GB to 4.5GB with 3767MB savings (esxtop then press m). PMEM /MB: 32672 total: 1636 vmk,28639 other, 2397 free VMKMEM/MB: 32510 managed: 939 minfree, 15602 rsvd, 16907 ursvd, clear state PSHARE/MB: 4541 shared, 788 common: 3753 saving SWAP /MB: 0 curr, 0
If your VMWare vSphere 6.x environment command output of esxtop looks like a bunch of garbled gibberish (it’s actually CSV format), then you need to change the terminal declaration to xterm but don’t ask me why it’s configured like this in the first place. The fix for this problem is: TERM=xterm esxtop Remember that Linux is case-sensitive and therefore this needs to be entered as TERM=xterm and not term=xterm This is what you and everyone else should see: [root@esxi67:/] TERM=xterm esxtop 3:18:40am up 3:09, 647 worlds, 10 VMs, 12 vCPUs; CPU load average: 0.08, 0.10, 0.14 PCPU USED(%):