conditional logic with vmware tools status
Hi Guy,
I am after a few tips here. I try to get a VMware tools State guests. I wrote the below which I think is logical, but doesn't seem to work lol. Maybe I think about this all wrong but any advice is appreciated.
$VMS = get-VM-name 'some-vm1', 'some-vm2.
foreach ($objitem to $VMS)
{
If ($objitem. PowerState - eq 'Receptor' - and $objitem. (- eq "guestToolsRunning") {Shutdown-VMGuest - VM $objitem - confirm: $false}
ElseIf ($objitem. PowerState - eq 'Receptor' - and $objitem. ExtensionData.ToolsRunningStatus - eq "guestToolsNotRunning") {stop-VM - $objitem VM - confirm: $false}
}
Thank you very much
Because I think he was part of the code is missing (I added it in red).
In fact your 2nd condition is a bad property as far as I know. I think we should $objitem. ExtensionData.Guest.ToolsRunningStatus
The script should be something like this
$VMS = Get-VM -Name "vm1","vm2" foreach ($objitem in $VMS)
{
if ($objitem.PowerState -eq "PoweredOn" -and $objitem.ExtensionData.Guest.ToolsRunningStatus -eq "guestToolsRunning"){
Shutdown-VMGuest -VM $objitem -WhatIf -Confirm:$false }
elseif ($objitem.PowerState -eq "PoweredOn" -and $objitem.ExtensionData.Guest.ToolsRunningStatus -eq "guestToolsNotRunning") {
Stop-VM -VM $objitem -WhatIf -Confirm:$false }
}
Tags: VMware
Similar Questions
-
VMware Tools status shows OK after upgrade ESX
I installed my ESX 3.5 U3 (build 123630) server to build 130756.
All virtual machines watch tool OK status, even if they are to 123630. If I connect in a virtual machine and open VMTools plateau, the upgrade button is grayed out.
If I manually start an upgrade VMTools, it upgrades 130756 tools.
How to change the current version of the tools in Virtual Center?
Some of these improvements have no change with VMware Tools. However, when you do a manual installation, they will show the new build number.
He is allowed to stay with the version of the tools that you have at the moment. Unless VC deferred that tools are outdated.
Hope that answers your question.
-Surya
-
Problem with VMWare Tools and the virtual drive
Hello
I installed the test version of "Workstation" and installed a windows 7 x 86 non-virtual DVD drive mapped, which is mounted on D:\.
Subsequently, I installed all Windowsupdates and after that I tried to install the VMWare Tools.
But every time I get the message that I should look on the 'virtual' drive on D:\.
But there is no virtual drive, it is my DVD of the hostsystem.
Is there a way to mount a virtual drive with tools or install them in another way?
Thanks in advance
Taldrit
Hello
You can directly install the VMware tool configuration by copying the setting in the machine and manually install the same.
Try VMware on another machine tool in which you will get the installation... Copies on disk and then move it to your new VM and do a manual configuration.
-
VM_STATE_INVALID_CONFIG after installation CD with vmware-tools + snapshot
I have VM_STATE_INVALID_CONFIG
VM has CD snapshot and Mount for vmware-tools
Virtual machine does not work
This article can not help me http://communities.vmware.com/message/752718?tstart=0
because the vm do not have this string in the VMX file.
Could you help me? Thank you
More information:
ls - al
Total 48587584
-rw - 1 root root 151009280 Dec 14 12:50 Syslog-000001 - delta.vmdk
-rw - 1 root root 247 14 dec 09:54 Syslog - 000001.vmdk
-rw - 1 root root 201410560 Dec 14 12:50 Syslog_1-000001 - delta.vmdk
-rw - 1 root root 251 14 dec 09:54 Syslog_1 - 000001.vmdk
-rw - 1 root root 42949672960 Dec 12 03:34 Syslog_1 - flat hard
-rw - 1 root root 401 9 Dec 18:25 Syslog_1.vmdk
-rw - r
r1 root root 37 Dec 9 18:25 Syslog - 68f713a2.hlog-rw - 1 root root 6442450944 Dec 12 03:34 Syslog - flat hard
-rw - 1 root root 8684 Dec 14 12:50 Syslog.nvram
-rw - 1 root root 20092 Dec 12 03:34 Syslog - Snapshot108.vmsn
-rw - 1 root root 398 9 Dec 18:25 Syslog.vmdk
-rw - 1 root root 586 12 dec 03:34 Syslog.vmsd
-rwxr-xr-x 1 root root 3102 Dec 14 12:50 Syslog.vmx
-rw - 1 root root 261 Dec 10 04:04 Syslog.vmxf
-rw - r
r1 root root 158208 9 Dec 18:25 0.log - vmware-rw - r
r1 root root 42727 20 December 2008 vmware - 279.log-rw - r
r1 root root 102832 20 December 2008 vmware - 280.log-rw - r
r1 root root 1033233 7 April 2009 vmware - 281.log-rw - r
r1 root root 14 May 2009 392257 vmware - 282.log-rw - r
r1 root root 1827259 26 Nov 15:23 vmware - 283.log-rw - r
r1 root root 44195 26 Nov 17:44 vmware - 284.log-rw - r
r1 root root 54573 Dec 14 12:50 vmware.logCat Syslog.vmx
#! / usr/bin/vmware
config.version = '8 '.
virtualHW.version = "4".
floppy0. Present = 'true '.
NVRAM = "Syslog.nvram."
deploymentPlatform = "windows".
virtualHW.productCompatibility = "hosted".
Tools.Upgrade.Policy = "manual".
powerType.powerOff = "default".
powerType.powerOn = "default".
powerType.suspend = "default".
powerType.reset = "default".
displayName = "Syslog".
extendedConfigFile = "Syslog.vmxf".
scsi0. Present = 'true '.
scsi0.sharedBus = 'none '.
scsi0.virtualDev = "free".
memsize = '512 '.
scsi0:0. Present = 'true '.
scsi0:0. FileName = 'Syslog - 000001.vmdk ".
scsi0:0. DeviceType = "scsi-disk" hard
SCHED.scsi0:0.shares = 'normal '.
scsi0:1.present = 'true '.
scsi0:1.filename = "Syslog_1 - 000001.vmdk".
scsi0:1.DeviceType = "scsi-disk" hard
SCHED.scsi0:1.shares = 'normal '.
ide0:0. Present = 'true '.
ide0:0.clientDevice = 'TRUE '.
ide0:0. FileName = ' / usr/lib/vmware/isoimages/linux.iso '.
ide0:0. DeviceType = "cdrom-raw"
ide0:0.startConnected = "FALSE".
floppy0.startConnected = "false".
floppy0. FileName = ' / dev/fd0.
floppy0.clientDevice = 'true '.
ethernet0. Present = 'true '.
ethernet0.networkName = 'network of the VM.
ethernet0. AddressType = 'vpx.
ethernet0.generatedAddress = "00:50:56:bf:0 b: cf.
chipset.onlineStandby = "false".
guestOSAltName = "Red Hat Enterprise Linux 5 (32-bit)"
guestOS = "rhel5.
annotation = 'server tftp, syslog, snmp, ntpd yum trap '.
UUID. BIOS = ' 50 12 33 50 e0 d8 d8 - 42 b0 65 3f 1 d dc 8A b8 65.
log.fileName = "vmware.log.
Snapshot.action = 'keep '.
SCHED. CPU.min = "200".
SCHED. CPU. Units = "mhz".
SCHED. CPU.shares = 'normal '.
sched.mem.MinSize = '30 '.
sched.mem.Max = '512 '.
SCHED.mem.shares = 'normal '.
toolScripts.afterPowerOn = 'true '.
toolScripts.afterResume = 'true '.
toolScripts.beforeSuspend = 'true '.
toolScripts.beforePowerOff = 'true '.
CPUID.1.ECX = ' R -
RRrR-0-H - RR -"
CPUID.1.ECX.AMD = 'O-
RCPUID.80000001.ECX.AMD = '-'.
RR - RR"
CPUID.80000001.EDX = "-
R""
CPUID.80000001.EDX.AMD = '-'.
"
checkpoint.vmState = «»
evcCompatibilityMode = "FALSE".
guest.commands.allowSharedSecretLogin = «»
guest.commands.sharedSecretLogin.com.vmware.vcIntegrity = «»
guestCPUID.0 = "0000000a756e65476c65746e49656e69".
guestCPUID.1 = "000006f800010800000022110febfbff".
guestCPUID.80000001 = "00000000000000000000000120000000".
hostCPUID.0 = "0000000a756e65476c65746e49656e69".
hostCPUID.1 = "000006fb000408000004e3bdbfebfbff".
hostCPUID.80000001 = "00000000000000000000000120000000".
scsi0:0. Redo = «»
scsi0:1.redo = «»
tools.remindInstall = "false".
userCPUID.0 = "0000000a756e65476c65746e49656e69".
userCPUID.1 = "000006fb000408000004e3bdbfebfbff".
userCPUID.80000001 = "00000000000000000000000120000000".
VMware.Tools.requiredVersion = "7302".
dMotion.enabled = "FALSE".
tools.syncTime = "FALSE".
UUID. Location = "56 4 d f8 d8 d9 7f b8 d1 - 2 c 24 27 10 2 39 68 16.
Migrate.hostlog = «./Syslog-68f713a2.hlog.
sched.swap.derivedName = ' / vmfs/volumes/494c8e80-a440f279-5164-001cc4c0d240/Syslog/Syslog-68f713a2.vswp '.
scsi0:0. DMotionParent = «»
scsi0:1.DMotionParent = «»
vmotion.checkpointFBSize = "4194304".
-
Cat Syslog.vmsd
snapshot.lastUID = "108".
snapshot.numSnapshots = '1 '.
Snapshot.Current = "108".
snapshot0.UID = "108".
snapshot0. FileName = ' Syslog - Snapshot108.vmsn.
snapshot0. DisplayName = "_VCB-backup_".
snapshot0. Description = "created automatically by VCB framework host VCB to Sat Dec 12 00:34:44 2009 | 0a (UTC). »
snapshot0.createTimeHigh = "293501".
snapshot0.createTimeLow = "888433336".
snapshot0.numDisks = '2 '.
snapshot0.Disk0.filename = "Syslog.vmdk".
snapshot0.Disk0.node = "scsi0:0". »
snapshot0. Disk1.filename = "Syslog_1.vmdk".
snapshot0. Disk1.node = "scsi0:1".
snapshot.needConsolidate = "FALSE".
What do you mean VM does not work?
It does not start, the operating system does not work, cannot remove the snapshot... what part does not work?
You can delete VM from the inventory. Create a NEW virtual machine, punch the config of the hard disk of the computer virtual EXISTING and create a new configuration. Then migrate to move the vmx / vmdk in the same folder, delete the complete original when configuration file.
You can be here all day trying to solve a vmx file, and it still doesn't work. Best thing to do is start over with a new configuration.
-
VMS with VMware Tools ESXi5 works for host ESX4.1?
Hello
Just upgraded a 4.1 ESX host to ESXi 5 host in a Cluster of 3 armies.
We observe that VMware tools running obsolete for the virtual machines on the host ESXi5. We would like to know if we apply the latest VMWare tools on those virtual machines, they run correctly when they are transferred to ESX 4.1 hosts?
Thank you
VMware Tools version 5.0 is compatiable on 4.x, but the virtual hardware version 8 is NOT compatible on 4.x
Se see page 3 what 's new
-
Time synchronization with host ESX to Windows start even if disabled in VMware Tools?
Hello
just got in trouble with a freshly installed Windows XP SP3 VM do not apply Active Directory group policies. After some research, I discovered that this happened only with VMware Tools installed.
With VMware Tools installed, Windows events 1030 and 1097 were generated at each start (the events say that group policy processing has been abandoned and that there is a time difference between the server and the client) and group policies have been applied.
Without VMware tools, everything was fine.
After some additional debugging I discovered that the ESXi (4.1) server was not configured with a valid NTP server and the host time was 10 minutes behind. However, as time synchronization between the guest OS and the ESX host has been disabled in VMware tools, I couldn't imagine it was really the cause of the problem. But strangely it turned out that this was indeed the case! At every Windows startup time has been at the time of the host ESX - but only for a few seconds. This can be seen in the attached photo: initially, there are guest operating system time, and then you see the jump both ESX and then jump back to the guest operating system.
Why does this happen? Hard, I could solve the problem in the first place by configuring the NTP server on the host, I would like to know why VMware tools change the time of the guest OS, even if it is disabled!
Thank you
When he put the VM must draw from somewhere and since the AI network time form more that probably not started it must draw from the host, but once the networking appears he died in the NTP source - that's why it is recommended to configure your ESXi (and ESX) to synchronize the time with NTP source.
If you find this or any other answer useful please consider awarding points marking the answer correct or useful
-
Impact of VMware tools on dvSwitch
I am currenlty working on the conversion of an environment of a bunch of standard switches to a dvSwitch.
I have tested dvSwitch and I'm ready to start the migration of virtual machines. I noticed that there are several virtual machines that do not have VMware tools installed. I'm assuming that migration Assistant virtual machines using VMware tools when the network switch.
Do I have to install/upgrade VMware tools on all machines before migrating the dvSwich most? Is it possible to not do this?
It is a 24 x 7 environment that has only 4 hours of window of maintenance once a month, if the weather is very very difficult to find. I know that install vmware tools requires a restart, because he was such a 5.0.x environment.
Thanks for the tips.
The condition of the VMware tools will not affect the migration to a VDS. The migration feature changes basically just group for the vNIC port assignment. It may be a slight loss of network connectivity when you migrate, worth perhaps as much as a single network ping, but it's normal.
Looks like you already know this, but once you get your environment set in place with the version of VMware 5.1 tools it will take not more it recharges when you upgrade tools.
-
Update VMware Tools on specific servers
Hello
I developed the following script, using various sources, I found on the internet, which I run from the virtual Center Server to update VMware tools on a number of servers:
' $insParm = "/ s v" /qn REBOOT = ReallySuppress "'
#------------------------------------------------------------------------------
# Configure the variables
#------------------------------------------------------------------------------
Host name of the server #VM
$VMServer = "06W8F5VC01".
#User account to connect to the virtual infrastructure:
$username = "root".
#Directory path to the list of targets of VM.
$updList = get-Content "C:\users\jmilano-adm\desktop\serverlist.txt".
Write-Host "Serverlist: ' $updList
write-host
#------------------------------------------------------------------------------
# Connect to the VM Server
#------------------------------------------------------------------------------
# $server = to connect-VIServer-Server $VMServer - User $username
$server = to connect-VIServer-Server $VMServer
#Search for specific VM in the production cluster:
#$folder = get-file-name "Financial Hosts' #Target financial Hosts file in the VM Infrastructure Client console
$cluster = get-Cluster-name 'MEL_Cluster_01 '.
Write-Host "cluster Var: ' $cluster
#------------------------------------------------------------------------------
# Main()
#------------------------------------------------------------------------------
foreach ($uVM to $updList)
{
$vm = get-VM-name $uVM - location $cluster
#$VM.name
write-host "
write-host "host to upgrade:" $VM.name
#$uVM.UpgradeTools_Task ($insParm)
UPDATE-TOOLS - VM $VM. Name - RunAsync - NoReboot
write-host "
write-host "host has been improved.
#Wait 30 seconds before you start another task update
Start-sleep - s 30
}I tested the script and it works very well, but what I want to do is change it so that it performs the following:
* Check this box when the line read from the ServerList.txt file is empty. If Yes, read the next line.
* Check the virtual server to verify that the VMware Tools is indeed obsolete. If so, update.
* Check if the server has no VMware tools. If it is not the case, install the latest version.
To create a log file on the server on which the script is run.
* Check if the installation was successful in fact. Add this information to the log file.
Pls know me what changes I need to run the script to reflect the foregoing. Thank you
Thinking about your questions. Here it is:
#* Checks the virtual server to verify that the VMware Tools is indeed out of date. If so, update it. foreach($vmItem in $vm) { if($vmItem.extensiondata.guest.toolsStatus -ne "toolsOK"){ #Possibilities: # - toolsOk # - toolsOld # - toolsNotRunning # - toolsNotInstalled write-host "Vmware Tools is Not ok, upgrading..."; UPDATE-TOOLS -VM $vmItem.Name -RunAsync -NoReboot }else{ write-host "Vmware Tools Ok, no need to upgrade"; } } #* Check if the server does not have VMware Tools. If it does not, install the latest version. I think the earlier script will work fine to this condition. Please tell, if not. #* Create a log file on the server which the script is being run. You can use the Measure-object cmdlet to see how long it took to run the script. #* Verifies if the installation actually succeeded. Add this information to the log file. After the Measuring, you can query again the Vmware Tools Status or create a looping to try more times till Vmware tools is readed as OK -
Registration of the VMWare Tools? No created log file
Hello
I have SuSE Linux with VMWare Tools.
I add in the /etc/vmware-tools/tools.conf
[record]
Journal = true
log.file="/var/log/VMwareTools.log".
log. Level = Debug
But the file does not create or write.
What I did wrong?
Is it a problem that the 'free' VMWareTools was insalled before?
I would like to know why the Scripts:
/ usr/sbin/pre-freezescript and/usr/sbin/postthaw-script
are not start if I run a snapshot
Thank you
You configuration in /etc/vmware-tools/tools.conf should look like this:
[record]
Journal = true
vmtoolsd. Level = debug
vmtoolsd. Handler = filevmtoolsd. Data = /var/log/vmtoolsd.log
See the following article:
Enabling debug logging for VMware Tools within a guest operating system
With these settings, I can get logging to work in a prompt of SuSe VM.
I would like to know why the Scripts:
/ usr/sbin/pre-freezescript and/usr/sbin/postthaw-script
are not start if I run a snapshot
To start the file names must be:
usr/sbin/pre-antifreeze-script
usr/sbin/post-thaw-script
These files must also be executable with 0755 permissions and owner root. Make sure that it is set to script files.
Also you can check the file vmware.log of the VM on the data store that records messages related to the VM of ESXi host point of view.
-
Upgrade VMware Tools to 11.1 in Xubuntu invited 14.04 fails
Hello
Upgrade VMware Tools from 11.0 to 11.1 in Xubuntu 14.04 fails - see the error message below.
My Xubuntu 14.04 is up-to-date. I've recently performed 'apt - get dist-upgrade'.
I can continue with the installation, but then shared folders does not work.
I don't know what the problem... Everything has worked fine up to 11.0 and I never had problems with VMware Tools upgrade. Help, please.
Annex: Error Message
Using the kernel build system.
"do: Verzeichnis" / tmp/modconfig-snuOuv/vmhgfs-only 'enter wird. "
/ usr/bin/make /lib/modules/3.13.0-46-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Verzeichnis»/usr/src/linux-headers-3.13.0-46-generic«wird enter
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/file.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-snuOuv/vmhgfs-only/link.o
In file included from usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/percpu.h:44:0,
of usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/preempt.h:5.
of include/linux/preempt.h:18.
of include/linux/spinlock.h:50.
of include/linux/mmzone.h:7.
of include/linux/gfp.h:4.
of include/linux/mm.h:8.
of include/linux/pagemap.h:7.
from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:29:
/tmp/modconfig-snuOuv/vmhgfs-only/inode.c: in function 'HgfsPermission ':
include/Linux/kernel.h:793:27: error: 'struct dentry' has no member named 'd_alias '.
const typeof (((type *) 0)-> member) * __mptr = (ptr); \
^
include/linux/List.h:687:40: Note: the expansion of the macro «container_of»
#define hlist_entry (ptr, type, member) container_of (ptr, type, member)
^
include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.
___ptr? hlist_entry (___ptr, type, member): NULL; \
^
include/linux/List.h:708:13: Note: the expansion of the macro 'hlist_entry_safe '.
for (pos = hlist_entry_safe ((head)-> first, typeof (* (pos)), member); \)
^
/tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.
hlist_for_each_entry (dentry,
^
include/Linux/kernel.h:793:48: warning: initialization of the [default] incompatible pointer type
const typeof (((type *) 0)-> member) * __mptr = (ptr); \
^
include/linux/List.h:687:40: Note: the expansion of the macro «container_of»
#define hlist_entry (ptr, type, member) container_of (ptr, type, member)
^
include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.
___ptr? hlist_entry (___ptr, type, member): NULL; \
^
include/linux/List.h:708:13: Note: the expansion of the macro 'hlist_entry_safe '.
for (pos = hlist_entry_safe ((head)-> first, typeof (* (pos)), member); \)
^
/tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.
hlist_for_each_entry (dentry,
^
In file included from include/linux/compiler-gcc.h:106:0,
of include/linux/compiler.h:54.
of include/uapi/linux/stddef.h:1.
of include/linux/stddef.h:4.
of usr/src/linux-headers-3.13.0-46-generic/include/uapi/linux/posix_types.h:4.
of include/uapi/linux/types.h:13.
of include/linux/types.h:5.
of tmp/modconfig-snuOuv/vmhgfs-only/./shared/driver-config.h:71.
from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:26:
include/Linux/compiler-gcc4.h:14:34: error: 'struct dentry' has no member named 'd_alias '.
#define __compiler_offsetof(a,b) __builtin_offsetof (a, b)
^
include/linux/STDDEF.h:17:31: Note: the expansion of the macro '__compiler_offsetof '.
#define offsetof (TYPE, MEMBER) __compiler_offsetof (TYPE, MEMBER)
^
include/Linux/kernel.h:794:29: Note: the expansion of the macro "offsetof".
(type *) ((char *) __mptr - offsetof (type, member)) ;})
^
include/linux/List.h:687:40: Note: the expansion of the macro «container_of»
#define hlist_entry (ptr, type, member) container_of (ptr, type, member)
^
include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.
___ptr? hlist_entry (___ptr, type, member): NULL; \
^
include/linux/List.h:708:13: Note: the expansion of the macro 'hlist_entry_safe '.
for (pos = hlist_entry_safe ((head)-> first, typeof (* (pos)), member); \)
^
/tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.
hlist_for_each_entry (dentry,
^
In file included from include/linux/preempt.h:10:0,
of include/linux/spinlock.h:50.
of include/linux/mmzone.h:7.
of include/linux/gfp.h:4.
of include/linux/mm.h:8.
of include/linux/pagemap.h:7.
from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:29:
include/linux/List.h:710:35: error: 'struct dentry' has no member named 'd_alias '.
POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))
^
include/linux/List.h:697:12: Note: in the definition of the macro 'hlist_entry_safe '.
({typeof (ptr) ___ptr = (ptr); \})
^
/tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.
hlist_for_each_entry (dentry,
^
include/linux/List.h:710:35: error: 'struct dentry' has no member named 'd_alias '.
POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))
^
include/linux/List.h:697:28: Note: in the definition of the macro 'hlist_entry_safe '.
({typeof (ptr) ___ptr = (ptr); \})
^
/tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.
hlist_for_each_entry (dentry,
^
In file included from usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/percpu.h:44:0,
of usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/preempt.h:5.
of include/linux/preempt.h:18.
of include/linux/spinlock.h:50.
of include/linux/mmzone.h:7.
of include/linux/gfp.h:4.
of include/linux/mm.h:8.
of include/linux/pagemap.h:7.
from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:29:
include/Linux/kernel.h:793:27: error: 'struct dentry' has no member named 'd_alias '.
const typeof (((type *) 0)-> member) * __mptr = (ptr); \
^
include/linux/List.h:687:40: Note: the expansion of the macro «container_of»
#define hlist_entry (ptr, type, member) container_of (ptr, type, member)
^
include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.
___ptr? hlist_entry (___ptr, type, member): NULL; \
^
include/linux/List.h:710:13: Note: the expansion of the macro 'hlist_entry_safe '.
POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))
^
/tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.
hlist_for_each_entry (dentry,
^
include/Linux/kernel.h:793:48: warning: initialization makes pointer from integer without a cast [default]
const typeof (((type *) 0)-> member) * __mptr = (ptr); \
^
include/linux/List.h:687:40: Note: the expansion of the macro «container_of»
#define hlist_entry (ptr, type, member) container_of (ptr, type, member)
^
include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.
___ptr? hlist_entry (___ptr, type, member): NULL; \
^
include/linux/List.h:710:13: Note: the expansion of the macro 'hlist_entry_safe '.
POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))
^
/tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.
hlist_for_each_entry (dentry,
^
In file included from include/linux/compiler-gcc.h:106:0,
of include/linux/compiler.h:54.
of include/uapi/linux/stddef.h:1.
of include/linux/stddef.h:4.
of usr/src/linux-headers-3.13.0-46-generic/include/uapi/linux/posix_types.h:4.
of include/uapi/linux/types.h:13.
of include/linux/types.h:5.
of tmp/modconfig-snuOuv/vmhgfs-only/./shared/driver-config.h:71.
from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:26:
include/Linux/compiler-gcc4.h:14:34: error: 'struct dentry' has no member named 'd_alias '.
#define __compiler_offsetof(a,b) __builtin_offsetof (a, b)
^
include/linux/STDDEF.h:17:31: Note: the expansion of the macro '__compiler_offsetof '.
#define offsetof (TYPE, MEMBER) __compiler_offsetof (TYPE, MEMBER)
^
include/Linux/kernel.h:794:29: Note: the expansion of the macro "offsetof".
(type *) ((char *) __mptr - offsetof (type, member)) ;})
^
include/linux/List.h:687:40: Note: the expansion of the macro «container_of»
#define hlist_entry (ptr, type, member) container_of (ptr, type, member)
^
include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.
___ptr? hlist_entry (___ptr, type, member): NULL; \
^
include/linux/List.h:710:13: Note: the expansion of the macro 'hlist_entry_safe '.
POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))
^
/tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.
hlist_for_each_entry (dentry,
^
make [2]: * [/ tmp/modconfig-snuOuv/vmhgfs-only/inode.o] Fehler 1
make [2]: * Auf noch nicht processes wird going going...
make [1]: * [_module_/tmp/modconfig snuOuv/vmhgfs-only] error 2
make [1]: Verzeichnis»/usr/src/linux-headers-3.13.0-46-generic«verlassen wird
make: * [vmhgfs.ko] Fehler 2
"do: Verzeichnis" / tmp/modconfig-snuOuv/vmhgfs-only "verlassen wird."
The filesystem (vmhgfs module) driver is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
regardless of this function.
If you want the shared folders feature, you can install the driver of
running vmware-config - tools.pl again after making sure that gcc, binutils, make
and your kernel sources are installed on your computer.
These packages are available on the installation of your distribution CD.
[Press the Enter key to continue]
As Barney42 pointed out, this question comes with the new kernel 3.13.0 - 46. And indeed helped me to find a workaround:
Tools can be patched manually. In vmhgfs.tar, inode.c
d_aliasshould be replaced byd_u.d_aliasput it back to the tar and then recompile tools.Here is a script that does this (tested on ubuntu 32 bit 14.04, vmware workstation on a windows host 11.1):
#!/bin/sh -x
cd /usr/lib/vmware-tools/modules/source
tar xf vmhgfs.tar
grep -q d_u.d_alias vmhgfs-only/inode.c && echo "already patched" && exit 0
sed -i -e s/d_alias/d_u.d_alias/ vmhgfs-only/inode.c
cp -p vmhgfs.tar vmhgfs.tar.orig
tar cf vmhgfs.tar vmhgfs-only
vmware-config-tools.pl -d -mNOTE: This makes incompatible tools with older versions of the kernel, i.e. 3.13.0 - 45.
However, @VMware-team, please do run again out of the box, or submit a patch for the Linux kernel. You are a large business, should be no problem.
-
Hello
I have an ESXi 5.1 U1 installation with a guest Windows 8.1 vSphere and problems with VMware Tools on this client. VMware Tools is installed, and that client vSphere summary screen says that it is running and the current, but after a certain time (do not know exactly how long, but I guess 20 minutes) VMware Tools stops running, resulting in people not being able to use remote desktop to connect to the host. As soon as I open the console to the guest in vSphere Client and click on the login screen then VMware Tools begin to run again and people can use remote desktop.
I tried to reinstall the VMware Tools, but that had no effect. Any ideas?
Thank you
Richard.
This sounds like the windows 8.1 client goes in some form of hibernation... you have all power saving / hibernation configured?
-
VMware Fusion 7 - OSx 10.9 comments iTunes hangs at each time after installing vmware tools
Hello community,
I'm having a problem with vmware tools. Yesterday, I did the upgrade of Fusion 6 to 7 Pro.
I have installed Mavericks like virtual machine. My system (iMac Late2013) has installed Mavericks.
With vmware tools iTunes crash whenever it is launched.
Without vmware tools iTunes works well... but the yield is very low (I can't use shared folders, etc.)
Before upgrading vmware fusion 7, I had fusion 6 and everything works fine (I mean iTunes with vmware tools)
I use this machine with audio application and it is important for me to use iTunes inside the virtual machine.
Is there the 'tricks' to solve this problem?
Thank you
It's finally a bug in iTunes that Apple should correct (so please click on "Send to Apple" in this window), but it is important to use to find out what triggers it.
I suspect a significant change, we did for the graphics drivers of comments (within the VMware Tools for OS X) between Fusion 6 and 7 of the merger. To test this theory, please try the following experiences in your VM Mavericks:
o experience 1
In Terminal.app, run the following command:
sudo nvram boot-args = 'vmw_gfx_caps = 0'
Then restart the client Mavericks. Does make the problem disappear? If no, continue to experiment 2
o experience 2
In Terminal.app, run the following command:
sudo rm - rf {/System,}/Library/Extensions/VMwareGfx.kext
Then restart the client Mavericks. Does make the problem disappear?
-
I have a question: -.
Suppose we have a esxi host with 2 versions one with esxi4.1 and another with esxi5.5 and vm is running on esxi5.5 with the latest vmware tools but with material 7. is it possible to migrate this virtual machine to esxi4.1 without any problems even with vmware to update tools?
From the link I provided above:
Extended support of the VMware Tools does two things:
1. it allows virtual computers running older versions of VMware Tools to operate in a supported configuration on more recent versions of ESXi.
2. it allows the VMS running newer versions of the VMware tools to run in a supported configuration on older versions of ESX/ESXi.
So, the answer is YES, you can run a virtual machine with VMware Tools of ESXi 5.5 on an ESXi 4.1 without problem.
-
No end of shooting reports supported by VMWare and VMWare tools Windos version?
Hello.
Now what I want to know exactly, that's the latest VMWare workstation with VMWare tools are supported on Windows 98 (Yes, sad, we must deploy some of these virtual machines in order to revive old software).
Is there any public document describing VMWare tools OS are supported by the version of VMWare?
Guys thank you very much in advance.
According to the HCL, Windows 98 is supported for up to WS 9.0, the Tools for this version can be the one to use.
André
-
How to launch and use the VMware tools
After installing 2008r2 as a virtual machine and install VMware Tools, I am unable to open the tools and use them. I did two days of searching, and I can't find an answer to my problem. Downstairs is an action I took, but I would appreciate any help from the community.
Purpose:
Laboratory at home training and certification.
Hardware environment: (based on "Chris Wahl" home Build Lab)
SuperMicro Motherboard MBD-X10SLH-F-O
Intel Xeon E3-1230 v3 3.30 GHz processor with 32 GB of ram
Software environment:
64-bit version of Windows 7 Professional, host operating system
VMware Workstation 10 with all updates installed with administrator privileges
VM #2: vSphere 5.1 install
VM #1: The Windows 2008R2 VM I have a problem with VMware tools.
I've deleted and rebuilt the two VM three times now, thinking it was my environment somehow. ESXi 5.1 works although I have not built anything there yet. I am able to access this part of the laboratory fine of vSphere Client.
VMware Tools:
Within the Services of VM 2008 I can see VMware Tools started service, the icon in the system tray notification area and see the files on the C: drive of the virtual computer, but there is no way to open it.
I followed several links to create a virtual laboratory, but should not be this hard to run a program. It's my first time that you try to use VMware tools, but I'm following the steps in the lab below install procedures.
In the middle of the page of "Blog Editor" part 4 "build the ultimate vSphere Lab is where it installs the VMware tool and lowest after restarting Windows Update service I'm stuck to the next step."
"Open VMware Tools, go to the Shrink ." Click on the button of the prepare to shrink . »
? How to "open the VMware Tools?
Now on the path I have searched for and deleted and reinstalled the tools, but always without success.
Here is a link where I found the following measures to be taken, but it doesn't work either. The "NOTE" at the bottom, it's something I noticed and made sure was right when I installed the last time tools.
I even found a link to where you can download the tools separately from the ISO files, and yet, it does not work. A LITTLE HELP PLEASE!
So next step that we did was
1 uninstalled VMware Tools in the virtual machine
2 restarted the VM
3. manually deleted/renamed the C:\Program VMware Tools
4. manually deleted/renamed C:\Programdata\VMware\VMware tools
5 Rebooted
6. install the VMware tools
7 RebootedThe issue is not reproducible after the same
NOTE: Make sure that the virtual computer CD player points to the correct image. I found it always go back to the windows 7 iso image on my C: drive from physical machines to where the image 2008r2 was on drive E:No need to reinstall again. You're not missing something. VMware has changed the VMware Tools tray and removed options that were available in previous versions. Take a look at for example experience front of VMware: The VMware Tools GUI is gone - now what? with some information about this change and the replacement of the command line.
André
Maybe you are looking for
-
Ink advantage 1518: first and second impression is poor third better every time
For a month, whenever I print a simple text, the first and second copies are of poor quality. Black ink is faded up or down the page. Sometimes the second copy is better, but the third copy is fine. This happens again and again. I took the cartrid
-
The last two years of data storage of email records Live disappeared. Checking records of storage on the C:\ cross Application data\Microsoft\Windows Live Mail but its all old stuff. There is a folder under Windows Live Mail backup that contains \ne
-
My dell latitude 610 d a no dvd decoder is there a way to install without disk
-
Refresh the screen when he became first on the stack
Hello I have a Refresh function on my home screen, from the home screen, a user can change the options in the options screen. However to change the options will change the content on the home screen. How can I update the home screen when a user comes
-
Media Player will not play a DVD
When I try to play a DVD in Media Player it tells me that my memory is low. It says to close other programs. I don't know what programs are to be to close and do not know why the memory would have something to do with playing a disc.