Monthly Archive: May 2017

VMware Tools Client - Main Window 4

VMware Tools Client – Interact with a VM without Network Connectivity

VMware Tools Client VMware Tools Client is a beta tools to interact with VMs without network connectivity. May know, there is some vSphere API that developers can write some codes and developing their tools for vSphere environments. VMware Tools Client written by Pierre Lainé is a useful tool to managing virtual machines via vSphere Guest API and VMware Tools. The tool developed by Java, so JRE or JDK should installed on manage machine. As Java is cross-platform run-time, so VMware Tools Client will run on any machine, Windows, Linux, Unix and Mac. VMware Tools Client allows administrators to: Upload and download files between management client machine and virtual machine. Run scripts to reconfigure operating system, troubleshooting and other tasks. Troubleshooting network by ping some addresses from within the virtual machine. VMware Tools Client be able to connect to vCenter and load vCenter inventory, so administrators can select and manage any virtual machine. PowerCLI also provides commands such as Invoke-VMScript to run script or batch via VMware Tools on virtual machines but VMware Tools Client is more featured. It’s beta version yet but available on this link for public download: Download Link Screenshots:

kernel: WARNING: at fs/sysfs/dir.c:536 sysfs_add_one+0xbb/0xe0 – Oracle Enterprise Linux 0

kernel: WARNING: at fs/sysfs/dir.c:536 sysfs_add_one+0xbb/0xe0 – Oracle Enterprise Linux

Most of modern servers hardware are using UEFI instead of legacy BIOS and modern OS has dedicated partition to stores boot and EFI values. Some times, the partition gets full or OS generate the below log: kernel: WARNING: at fs/sysfs/dir.c:536 sysfs_add_one+0xbb/0xe0 Kernel includes a CONFIG_EFI_VARS_PSTORE feature, and a feature that dumps kernel message log (= the “dmesg” command output) into UEFI variables for persistent storage if the system is crashing (or even if the system is working normally, depending on the options chosen). The cause of the warning is duplicate dump file in EFI partition and OS is trying to write values on same file. There is a simple solution, remove old dump file! I hope this article help you to find out root cause of the warning and resolve that. Here is the complete log on our virtual machine: kernel: WARNING: at lib/kobject.c:196 kobject_add_internal+0x205/0x260() kernel: Hardware name: VMware7,1 kernel: kobject_add_internal failed for dump-type2-0-0-1493749396-cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0 with -EEXIST, don’t try to register things with the same name in the same directory. kernel: Modules linked in: vmw_vsock_vmci_transport vsock oracleasm autofs4 ipv6 vfat fat uinput vmw_balloon coretemp crc32c_intel ghash_clmulni_intel microcode pcspkr sg ixgbe hwmon dca vmw_vmci i2c_piix4 shpchp ext4 jbd2 mbcache dm_round_robin scsi_dh_emc sd_mod...