Dayworker's Posts

Here is your VMX: checkpoint.vmState = "" cleanShutdown = "FALSE" config.version = "8" displayName = "Windows Server 2012" ehci.pciSlotNumber = "34" ehci.present = "TRUE" etherne... See more...
Here is your VMX: checkpoint.vmState = "" cleanShutdown = "FALSE" config.version = "8" displayName = "Windows Server 2012" ehci.pciSlotNumber = "34" ehci.present = "TRUE" ethernet0.addressType = "generated" ethernet0.connectionType = "nat" ethernet0.generatedAddress = "00:0c:29:77:2f:1d" ethernet0.generatedAddressOffset = "0" ethernet0.pciSlotNumber = "192" ethernet0.present = "TRUE" ethernet0.virtualDev = "e1000e" ethernet0.wakeOnPcktRcv = "FALSE" extendedConfigFile = "Windows Server 2012.vmxf" floppy0.present = "FALSE" guestOS = "windows8srv-64" gui.exitOnCLIHLT = "FALSE" gui.lastPoweredViewMode = "fullscreen" hpet0.present = "TRUE" mem.hotadd = "TRUE" memsize = "3072" migrate.hostlog = ".\Windows Server 2012-0ceee322.hlog" monitor.phys_bits_used = "42" numvcpus = "4" nvram = "Windows Server 2012.nvram" pciBridge0.pciSlotNumber = "17" pciBridge0.present = "TRUE" pciBridge4.functions = "8" pciBridge4.pciSlotNumber = "21" pciBridge4.present = "TRUE" pciBridge4.virtualDev = "pcieRootPort" pciBridge5.functions = "8" pciBridge5.pciSlotNumber = "22" pciBridge5.present = "TRUE" pciBridge5.virtualDev = "pcieRootPort" pciBridge6.functions = "8" pciBridge6.pciSlotNumber = "23" pciBridge6.present = "TRUE" pciBridge6.virtualDev = "pcieRootPort" pciBridge7.functions = "8" pciBridge7.pciSlotNumber = "24" pciBridge7.present = "TRUE" pciBridge7.virtualDev = "pcieRootPort" powerType.powerOff = "soft" powerType.powerOn = "soft" powerType.reset = "soft" powerType.suspend = "soft" sata0.pciSlotNumber = "36" sata0.present = "TRUE" sata0:1.deviceType = "cdrom-image" sata0:1.fileName = "C:\Users\LAVIN\Documents\Final Year Project\Downloads\SfB-E-9319.0-enUS.ISO" sata0:1.present = "TRUE" sata0:1.startConnected = "TRUE" scsi0.pciSlotNumber = "160" scsi0.present = "TRUE" scsi0.sasWWID = "50 05 05 6c 4b 11 d1 e0" scsi0.virtualDev = "lsisas1068" scsi0:0.fileName = "Windows Server 2012.vmdk" scsi0:0.present = "TRUE" scsi0:0.redo = "" serial0.fileType = "thinprint" serial0.present = "TRUE" softPowerOff = "TRUE" sound.autodetect = "TRUE" sound.fileName = "-1" sound.pciSlotNumber = "33" sound.present = "TRUE" sound.virtualDev = "hdaudio" svga.guestBackedPrimaryAware = "TRUE" tools.remindInstall = "TRUE" tools.syncTime = "FALSE" toolsInstallManager.lastInstallError = "0" toolsInstallManager.updateCounter = "2" usb.pciSlotNumber = "32" usb.present = "TRUE" usb_xhci.pciSlotNumber = "224" usb_xhci.present = "TRUE" usb_xhci:4.deviceType = "hid" usb_xhci:4.parent = "-1" usb_xhci:4.port = "4" usb_xhci:4.present = "TRUE" usb_xhci:6.deviceType = "hub" usb_xhci:6.parent = "-1" usb_xhci:6.port = "6" usb_xhci:6.present = "TRUE" usb_xhci:6.speed = "2" usb_xhci:7.deviceType = "hub" usb_xhci:7.parent = "-1" usb_xhci:7.port = "7" usb_xhci:7.present = "TRUE" usb_xhci:7.speed = "4" uuid.bios = "56 4d 29 2c 4b 11 d1 ee-04 c2 ed b6 ec 77 2f 1d" uuid.location = "56 4d a7 5b ae bb 88 29-ec 2a b9 c3 09 a7 6f e1" vcpu.hotadd = "TRUE" vhv.enable = "TRUE" virtualHW.productCompatibility = "hosted" virtualHW.version = "12" vm.genid = "7852997396133807699" vm.genidX = "-678439561331704097" vmci0.id = "-327733475" vmci0.pciSlotNumber = "35" vmci0.present = "TRUE" vmotion.checkpointFBSize = "4194304" vmotion.checkpointSVGAPrimarySize = "33554432"
The problem seems to be the "Time Warner Cable through a Netgear AC1750 WiFi Cable Modem". Mostly if not cable providers prevent the usage of multiple devices and/or own DNS settings. I believe t... See more...
The problem seems to be the "Time Warner Cable through a Netgear AC1750 WiFi Cable Modem". Mostly if not cable providers prevent the usage of multiple devices and/or own DNS settings. I believe the DNS settings are hard-coded in the router firmware. I suggest to use a second router behind the Netgear to solve this barrier. This router gets an IP from the Netgear via DHCP and opens its own net for LAN/WLAN. In this net can you do what you want.
I suggest to upgrade to the latest player version and try again.
What did you use to recreate your VMX file? A VMX file does not contain any format strings. You need a pure ASCII editor like Notepad++ and nothing like M$-Word.
IMO the vSphere-Client is useless in this case because we are talking about VMware-Workstation. But all your Shared VMs are listed in the file "vmInventory.xml"... The file "vmAutoStart.xml" c... See more...
IMO the vSphere-Client is useless in this case because we are talking about VMware-Workstation. But all your Shared VMs are listed in the file "vmInventory.xml"... The file "vmAutoStart.xml" contains all settings for the start order. In "vmAutoStart.xml" the entry <moid>1</moid> is the same like <objID>1</objID> in "vmInventory.xml". The AutoStartOrder for all shared VMs is viewable in "vmAutoStart.xml" via the entries "<e id="0">" and so on. Each <e id>-entry means a further VM will be started by the VMware-Workstation and the <e id>-number is changeable. I don't know what happened, if you add a further VM after manually changing the "vmAutoStart.xml". Either the existing order will be kept or the Workstation changes this order.
Your syntax is not correct. Open a CMD or terminal windows and execute "vmrun". At the bottom you will find some examples. Accoding to theses examples you have to run: vmrun -T ws start "c:\St... See more...
Your syntax is not correct. Open a CMD or terminal windows and execute "vmrun". At the bottom you will find some examples. Accoding to theses examples you have to run: vmrun -T ws start "c:\Stuff\VMs\Windows 7 x64.vmx" runprograminguest "c:\Program Files\yourProgram.exe"
Second run. Please add the following entries: MemTrimRate = "0" sched.mem.pshare.enable = "FALSE" prefvmx.useRecommendedLockedMemSize = "TRUE" Where did you save your Thick/Preallo... See more...
Second run. Please add the following entries: MemTrimRate = "0" sched.mem.pshare.enable = "FALSE" prefvmx.useRecommendedLockedMemSize = "TRUE" Where did you save your Thick/Preallocated VMDK? Different drive (partitions does not count) from the host OS?
First enable the setting: "Fit all virtual machine memory into reserved host RAM" in the VMware-Workstation host-settings and then add the following VMX entry: Linux host: mainmem.backing = ... See more...
First enable the setting: "Fit all virtual machine memory into reserved host RAM" in the VMware-Workstation host-settings and then add the following VMX entry: Linux host: mainmem.backing = "swap" or Windows host: mainmem.useNamedFile = "false" For further tuning read the KB-entry Troubleshooting hosted disk I/O performance problems (1008885).
Fehler mit "IRQL_NOT_LESS_OR_EQUAL" und deinem Fall mit der BSOD-Nummer "0x0000000A"deuten auf einen schwerwiegenden Fehler hin. Meist ist dann ein System-Treiber beschädigt. Da du jedoch 3 versc... See more...
Fehler mit "IRQL_NOT_LESS_OR_EQUAL" und deinem Fall mit der BSOD-Nummer "0x0000000A"deuten auf einen schwerwiegenden Fehler hin. Meist ist dann ein System-Treiber beschädigt. Da du jedoch 3 verschiedene ISOs genutzt hast, würde ich erstmal von keinem defekten ISO ausgehen. Je nach Grösse des ISOs und des zum Download genutzten Browsers könnte das aber dennoch der Fall sein. Microsofts IE war in älteren Versionen bekannt für dieses Problem. Solche Fehler liessen und lassen sich aber sehr einfach über die md5/sha1-Checksummen herausfinden, die Microsoft zu seinen ISOs veröffentlicht. Wenn die Checksummen übereinstimmen, kommen auf dem Host auch noch die Security-Suite sprich Virenscanner, Internet-Suite etc und fehlerhafter Arbeitsspeicher in Betracht. Die dann vielfach gemachten Memtest86-Durchläufe sind in meinen Augen absoluter Murks, da sich heutzutage die vielen CPU-Caches nicht mehr abschalten lassen. Wenn also Memtest86 gefühlte 1000x das Datum 00 oder auch FF in den RAM schrieben will, um es hernach wieder auszulesen, hat es aufgrund heutiger Cache-Grössen eigentlich nur den Cache selbst beschrieben. Daher lautet die Empfehlung nicht nur für RAM-Tests einfach Prime95 und den darin eingebauten Streß-Test zu verwenden. Bei Primzahlen gibt es nur ja oder nein und jedwede Abweichung ist ein Fehler. Da die Primzahlen sehr groß werden, passen diese auch nicht mehr in die Caches und damit wird der Arbeitsspeicher zuverlässig getestet. RAM-Fehler zeigen sich dann meist bereits nach wenigen Sekunden. Falls Prime95 auch nach 24 Stunden ohne Fehler läuft, sollte, wie bereits gesagt, noch der Virenscanner überprüft werden. Avira beispielsweise war, und ist es wahrscheinlich auch heute noch, dafür so bekannt, daß VMware dessen Eingriffe sogar im "vmware.log" protokolliert. Die Lösung ist hier recht einfach, da Avira eine Ausnahmeliste sowohl für Prozesse als auch Ordner und Dateien verwaltet. Wenn man sowohl den VMware-Programmeordner als auch Haupt-Ordner mit den VMs aufnimmt, ignoriert Avira diese komplett und funkt nicht mehr beim Zugriff darauf dazwischen. Weshalb dies so entscheidend ist, dürfte dir klarer werden, wenn du dir die Arbeitsweise jedes Virenscanners verdeutlichst. Jeder installierte Virenscanner schiebt nämlich nach dem Dateisystem-Treiber noch seinen eigenen Filter-Treiber dazwischen und verhindert dadurch ggf den Zugriff komplett. Da die meisten Scanner sowohl beim Lesen als auch Schreiben aktiv werden, sperren diese dann kurzzeitig sämtlichen Zugriff auf eine Datei und für eine VM sieht es dann so aus, als ob der Datenträger komplett ausgefallen ist.
I think this is a known problem and exists since many years. Therefore I suggest you to disable the "Auto-Bridging/Connect" and connect all host NICs manually with a given vmnetX. The first NIC m... See more...
I think this is a known problem and exists since many years. Therefore I suggest you to disable the "Auto-Bridging/Connect" and connect all host NICs manually with a given vmnetX. The first NIC must ever be connected with the vmnet0 (Bridged). All further host NICs have to be manually connected to an unused vmnicX (vmnet2-7 and vmnet9-10 are free by default). Example: vmnet0 = 1st host NIC vmnet2 = 2nd host NIC vmnet3 = 3rd host NIC Later in every VM config. Add a NIC, change it to custom (available modes are Bridged, Host-only, NAT and Custom) and use the scroll-down menu on the right side to switch to the desired vmnetX. After switching to for example vmnet2, the VM will work in ip-range of the second host NIC. The ip-range is changeable only in the host network configuration. If you configure an IP outside the ip-range of the connected vmnetX, your VM will have no network access. If you configure a VM with Bridged, the VM will communicate to the outside through all with Bridged assigned vmnetX. Therefore should you use ever the custom NIC interface, if you have more than one NIC in host and want to use the Bridged interface.
A raid. Do you created images of all raid member disks? If not then you have created an image of the raid but this contains only the volume build by the raid adapter itself.
How much vRAM was configured to this VM? VMware writes a vmem-file on the host disk. The file size is equal to the configured vRAM-size of this VM.
The VMware Workstation built-in tool does not really defrag your guests. It tries to save your sparse or thin vDISK en bloc. If your guests are saved on a SSD, this would be double useless. First... See more...
The VMware Workstation built-in tool does not really defrag your guests. It tries to save your sparse or thin vDISK en bloc. If your guests are saved on a SSD, this would be double useless. Firstly, every SSD uses "wear leveling" and secondly each write access lowers the SSD lifetime. Why did you use snapshots? They are no backup and decrease the performance of a vDISK.
Here are some thoughts: Lower the amount of cores/cpu's to single- or max dualcore-VM Config not more than 1-2GB of vRAM per VM use preallocated vDISK do not use snapshots or only for backup... See more...
Here are some thoughts: Lower the amount of cores/cpu's to single- or max dualcore-VM Config not more than 1-2GB of vRAM per VM use preallocated vDISK do not use snapshots or only for backup
For 32bit VMs it should not be needed but it does not harm. The virtualization option has to be set via Workstation GUI in the "Virtual Machine Settings" or you can change your VMX file. monitor.... See more...
For 32bit VMs it should not be needed but it does not harm. The virtualization option has to be set via Workstation GUI in the "Virtual Machine Settings" or you can change your VMX file. monitor.virtual_exec = "hardware" will result in a log message of: HV Settings: virtual exec = 'hardware' This should result in a lower CPU usage for your host and a faster execution for your guest/VM. If this does not help, please deactivate 3D support for this VM. Either via Workstation-GUI or change the setting in the VMX file to: mks.enable3d = "false"
2014-07-22T09:42:21.588+01:00| vmui| I120: cui::OnLocalHostAbort: Not connected to Workstation Server. Opening VM K:\Virtual Machines\VWEBDEV02ADA.lta.org.uk\VWEBDEV02ADA.lta.org.uk.vmx as a st... See more...
2014-07-22T09:42:21.588+01:00| vmui| I120: cui::OnLocalHostAbort: Not connected to Workstation Server. Opening VM K:\Virtual Machines\VWEBDEV02ADA.lta.org.uk\VWEBDEV02ADA.lta.org.uk.vmx as a standard VM. 2014-07-22T09:42:21.588+01:00| vmui| I120: VMMgr::OpenVM (cfgPath=K:\Virtual Machines\VWEBDEV02ADA.lta.org.uk\VWEBDEV02ADA.lta.org.uk.vmx) 2014-07-22T09:42:21.600+01:00| vthread-5| I120: VTHREAD initialize thread 5 "vthread-5" host id 3392 2014-07-22T09:42:24.203+01:00| vthread-5| I120: FILE: FileLockWaitForPossession timeout on 'K:\Virtual Machines\VWEBDEV02ADA.lta.org.uk\VWEBDEV02ADA.lta.org.uk.vmx.lck\M45140.lck' due to a local process '5616-130504912711266479(vmware.exe)' 2014-07-22T09:42:24.204+01:00| vthread-5| I120: VMHS_ManageVM failed: ret = The virtual machine appears to be in use 2014-07-22T09:42:24.204+01:00| vthread-5| I120: Cmd /host2/#_client/util/vm/cmd/##7a/op/manageVM/ failed: The virtual machine appears to be in use 2014-07-22T09:42:24.205+01:00| vmui| I120: DlgUI: This virtual machine appears to be in use. 2014-07-22T09:42:24.205+01:00| vmui| I120+ If this virtual machine is not in use, press the "Take Ownership" button to obtain ownership of it. Otherwise, press the "Cancel" button to avoid damaging it. 2014-07-22T09:42:24.205+01:00| vmui| I120+ Configuration file: K:\Virtual Machines\VWEBDEV02ADA.lta.org.uk\VWEBDEV02ADA.lta.org.uk.vmx. 2014-07-22T09:42:31.653+01:00| vmui| I120: DlgUI: Could not open virtual machine: K:\Virtual Machines\VWEBDEV02ADA.lta.org.uk\VWEBDEV02ADA.lta.org.uk.vmx 2014-07-22T09:42:31.653+01:00| vmui| I120+ 2014-07-22T09:42:31.653+01:00| vmui| I120+ Taking ownership of this virtual machine failed. 2014-07-22T09:42:31.653+01:00| vmui| I120+ The virtual machine is in use by an application on your host computer. 2014-07-22T09:42:31.653+01:00| vmui| I120+ Configuration file: K:\Virtual Machines\VWEBDEV02ADA.lta.org.uk\VWEBDEV02ADA.lta.org.uk.vmx. 2014-07-22T09:42:31.714+01:00| vmui| I120: VMMgr: Failed to open pending VM: Taking ownership of this virtual machine failed. 2014-07-22T09:42:31.714+01:00| vmui| I120+ The virtual machine is in use by an application on your host computer. 2014-07-22T09:42:31.714+01:00| vmui| I120+ Configuration file: K:\Virtual Machines\VWEBDEV02ADA.lta.org.uk\VWEBDEV02ADA.lta.org.uk.vmx. What is your local drive K? NAS or external USB drive? According to this snippet, "The virtual machine appears to be in use". If you are sure that she is not, then delete all LCK-files and -folders and try to restart the VM.
You have forgotten to add the PCI address area and the vGPU ram (depends also on screen resolution and color depth) for each VM. If I calculate with 128MB (PCI adress and vGPU together) for each ... See more...
You have forgotten to add the PCI address area and the vGPU ram (depends also on screen resolution and color depth) for each VM. If I calculate with 128MB (PCI adress and vGPU together) for each VM, I get 640MB per VM or 23,680MB for all 37 VMs... Do not nail me on this 128MB. Real values are viewable in the Workstation manual.
Why did you changed the assignment from VMnet0 and VMnet1? The VMnet2-VMnet7 and VMnet9-VMnet10 (VMnet10 or higher is depended of the used Workstation version) are free for change. VMnet0... See more...
Why did you changed the assignment from VMnet0 and VMnet1? The VMnet2-VMnet7 and VMnet9-VMnet10 (VMnet10 or higher is depended of the used Workstation version) are free for change. VMnet0 is known as Bridged and VMnet1 as Host-only. A change of both assignments is possible. But without some background knowledge ends this mostly in a communication error.
The answer for "bypass the limit" and "utilize 100% of your cpu" is NO. Maybe VMware changes it sometime in the future.
Please append the log from "C:\Users\dan-smith\AppData\Local\Temp\vmware-daniel.alvares\vmware-ui-2996.log"