Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

All Content in Workstation Player

older | 1 | .... | 121 | 122 | (Page 123) | 124 | 125 | .... | 252 | newer

    0 0

    I have small SSD to boot Win7 from which was great. How do I move the location of existing files of Components already downloaded...these tools have totally filled up my C-drive ...it's only the Win2k tools that I don't have room for on C. So I NEED to have them moved to D!
    These Components (tools) must be on my C-drive now as it totally filled my C. Not exactly sure where they are located yet on C.

     

    Now D have _lots_ of space.

     

    Basically I want to change the default location of the Players location of these Components (VMware Tools).

    Can I copy them to new location on D and then change something in the Registry?? If yes, where do I need to change it? one place or several places?

     

    Help much appreciated w this issue.

     

    Message was edited by: vmware4dje BTW...Im running VMware Player 7.1.0 build-2496824 on Win7 Ultimate 64-bit.


    0 0

    I was running VNC on version 5 and again on version 6, but after upgrade to version 7.1.0 the VNC capability is gone when running in Windows 8.1.  I tried to go the rounds with technical support but all they could do was to deny that any copy of VMWare Player has VNC capability and point me to a website.  I in fact did have VNC in VMWare Player for Windows, and the copy of VMWare Player 7.1.0 on my Linux OS still has VNC that is working.  I know it has the capability because I am using it.  Before anyone decides to argue with me about it whether VMWare Player has an option for VNC Connections, here is a screenshot of VMWare Player 7.1.0 running on my Ubuntu 14.04.2 LTS system.

     

    Screenshot from 2015-04-13 13:40:20.png

     

    It is not licensed and is for non-commercial use only.  It is not hacked.  It is a default installation.  I know the Windows version had it as well but it just disappeared and not even editing the VMX file works to activate it.  I finally had to break down and install a third party VNC server into the virtual machine.  Has anyone else had this experience with the VNC capability just disappearing like this? Any idea as to how to get that functionality working again? I've already upgraded the virtual machines and cannot go back to an older version of VMWare Player, as far as I know.  Or, am I wasting my time trying to figure this out because VMWare removed that functionality in the Windows version of VMWare Player?


    0 0

    Hi

     

    We have Windows 7 (64bit) host where is VMWare Player 5.0.1 build-894247 installed and registered.

     

    Quest operating system is also Windows 7 (64bit) created with VMWare Workstation  9.0.2 build-1031769. Virtual machine is encrypted and restricted. There is VNC connection enabled, set port 5902 and also password set. Network Adapter is in NAT state. These all settings has been done with Workstation.

    When starting VM in host with player we got information where was said that VNC connection is enabled and do we want to start it anyway (in first start not after that).

     

    When trying to connect with RealVNC client to address hostip:2 we get message box: "unable to connect to host: Connection refused (10061)".

     

    Where problem could be? We had this kind solution before (windows were XP in both host and quest and workstation and player older version and now doing update to newer windows) and then it worked well.


    0 0
  • 04/14/15--18:55: windows 10 and player v 6
  • Hello -- Will the beta version of windows 10 run in the latest version (v6) of Player??


    0 0

    Hi !

    I have the following configuration:

     

    Host: Windows 7 x64 Professional

    Host: Samsung 840 EVO 240GB SSD with 48GB free

     

    Guest: Windows 10 Preview

    Guest: 60GB VMDK, split into 30x 2GB vmdk's which are NOT pre-allocated

     

    Problem description:

    I'm doing Windows Update in the Win10 system, and then at some point i get a warning from VMware Player that VMDK#009 can't be accessed

     

    this is the LOG, which states that vmdk#009 has run out of space... which is very odd, considdering that i have 40GB Free in the guest OS, and 48GB free in the HOST... and that the VMDK is a self expanding volume

     

    2015-04-15T10:47:20.827+02:00| vmx| I120: MsgQuestion: msg.vmxaiomgr.retrycontabort.rudeunplug reply=2

    2015-04-15T10:47:20.827+02:00| vmx| I120: DISKLIB-LIB   : RWv failed ioId: #46815 (13) (13) .

    2015-04-15T10:47:20.827+02:00| vmx| I120: DISK: Disk i/o on scsi0:0 failed: There is not enough space on the file system for the selected operation (13)

    2015-04-15T10:47:20.827+02:00| vmx| I120: ###### dumping content of iov ######

    2015-04-15T10:47:20.827+02:00| vmx| I120: WRITE

    2015-04-15T10:47:20.827+02:00| vmx| I120: startSector = 37601304

    2015-04-15T10:47:20.827+02:00| vmx| I120: numSectors = 8

    2015-04-15T10:47:20.827+02:00| vmx| I120: numBytes = 4096

    2015-04-15T10:47:20.827+02:00| vmx| I120: numEntries = 1

    2015-04-15T10:47:20.827+02:00| vmx| I120:   entries[0] = F53A8000 / 4096

    2015-04-15T10:47:20.841+02:00| vmx| I120: VMXAIOMGR: Retry on write "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : There is not enough space on the disk.

    2015-04-15T10:47:20.841+02:00| vmx| I120: VMXAIOMGR: system : err=700002 errCode=112 freeSpace=51699863552

    2015-04-15T10:47:20.841+02:00| vmx| I120: VMXAIOMGR: "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : write s=825058708480 n=4096 ne=1, fai=0

    2015-04-15T10:47:20.841+02:00| vmx| I120: VMXAIOMGR:             v[0]=F53A9000:4096

    2015-04-15T10:47:20.844+02:00| vmx| I120: VMXAIOMGR: Retry on write "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : There is not enough space on the disk.

    2015-04-15T10:47:20.844+02:00| vmx| I120: VMXAIOMGR: system : err=700002 errCode=112 freeSpace=51699863552

    2015-04-15T10:47:20.844+02:00| vmx| I120: VMXAIOMGR: "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : write s=825058708480 n=4096 ne=1, fai=0

    2015-04-15T10:47:20.845+02:00| vmx| I120: VMXAIOMGR:             v[0]=F53A9000:4096

    2015-04-15T10:47:20.846+02:00| vmx| I120: VMXAIOMGR: Retry on write "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : There is not enough space on the disk.

    2015-04-15T10:47:20.846+02:00| vmx| I120: VMXAIOMGR: system : err=700002 errCode=112 freeSpace=51699863552

    2015-04-15T10:47:20.846+02:00| vmx| I120: VMXAIOMGR: "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : write s=825058708480 n=4096 ne=1, fai=0

    2015-04-15T10:47:20.846+02:00| vmx| I120: VMXAIOMGR:             v[0]=F53A9000:4096

    2015-04-15T10:47:20.848+02:00| vmx| I120: VMXAIOMGR: Retry on write "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : There is not enough space on the disk.

    2015-04-15T10:47:20.848+02:00| vmx| I120: VMXAIOMGR: system : err=700002 errCode=112 freeSpace=51699863552

    2015-04-15T10:47:20.848+02:00| vmx| I120: VMXAIOMGR: "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : write s=825058708480 n=4096 ne=1, fai=0

    2015-04-15T10:47:20.848+02:00| vmx| I120: VMXAIOMGR:             v[0]=F53A9000:4096

    2015-04-15T10:47:20.850+02:00| vmx| I120: VMXAIOMGR: Retry on write "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : There is not enough space on the disk.

    2015-04-15T10:47:20.850+02:00| vmx| I120: VMXAIOMGR: system : err=700002 errCode=112 freeSpace=51699863552

    2015-04-15T10:47:20.850+02:00| vmx| I120: VMXAIOMGR: "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : write s=825058708480 n=4096 ne=1, fai=0

    2015-04-15T10:47:20.850+02:00| vmx| I120: VMXAIOMGR:             v[0]=F53A9000:4096

    2015-04-15T10:47:20.851+02:00| vmx| I120: VMXAIOMGR: Retry on write "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : There is not enough space on the disk.

    2015-04-15T10:47:20.851+02:00| vmx| I120: VMXAIOMGR: system : err=700002 errCode=112 freeSpace=51699863552

    2015-04-15T10:47:20.851+02:00| vmx| I120: VMXAIOMGR: "C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10-s009.vmdk" : write s=825058708480 n=4096 ne=1, fai=0

    2015-04-15T10:47:20.851+02:00| vmx| I120: VMXAIOMGR:             v[0]=F53A9000:4096


    0 0

    Dell Precision T5500, dual Xeon E5520 @ 2.27GHz, 12 GB RAM, Ubuntu 12.04.5, VMware Player 7.1.0  A Windows 7 VM (not one I created) is bombing out with

     

    VMware Player unrecoverable error: (vcpu-0)

    Unexpected signal: 11.

     

    vmware.log ends with:

     

    2015-04-15T19:06:33.268-07:00| vcpu-0| I120: Guest: toolbox: Version: build-1031360

    2015-04-15T19:06:33.268-07:00| vcpu-0| I120: GuestRpc: Channel 0, guest application toolbox.

    2015-04-15T19:06:33.292-07:00| vcpu-0| I120: TOOLS autoupgrade protocol version 2

    2015-04-15T19:06:33.296-07:00| vcpu-0| I120: TOOLS Received tools.set.version rpc call, version = 9283.

    2015-04-15T19:06:33.296-07:00| vcpu-0| I120: ToolsSetVersionWork did nothing; new tools version (9283) matches old Tools version

    2015-04-15T19:06:33.296-07:00| vcpu-0| I120: VMware Player did not ship with the tools ISO.

    2015-04-15T19:06:33.333-07:00| vcpu-0| I120: TOOLS state change 3 returned status 1

    2015-04-15T19:06:33.333-07:00| vcpu-0| I120: Vix: [4843 mainDispatch.c:4209]: VMAutomationReportPowerStateChange: Reporting power state change (opcode=2, err=0).

    2015-04-15T19:06:34.038-07:00| vcpu-1| I120: Stream 7F1F60024810 creating

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| W110: Caught signal 11 -- tid 4843 (addr 0)

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: SIGNAL: rip 0x0 rsp 0x7f20016dbbc8 rbp 0x4

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: SIGNAL: rax 0x0 rbx 0x23ae578 rcx 0x18 rdx 0xc9b900 rsi 0x7f20016dbc70 rdi 0x7f1f68017410

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120:         r8 0x23b3468 r9 0x12eb r10 0x0 r11 0x3246 r12 0x164 r13 0x7f2007da8ec0 r14 0x2221920 r15 0x7f2007da8ec0

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7F20016DBBC8 : 0x0000000000738c6d 0x00007f2007da8f28

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7F20016DBBD8 : 0x00000000000102c8 0x00000004026b4640

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7F20016DBBE8 : 0x00000000023aa020 0x00000000023aa020

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7F20016DBBF8 : 0x00000000000765e0 0x0000000000000004

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7F20016DBC08 : 0x00000004004bcd0e 0x00007f2007da8ec0

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7F20016DBC18 : 0x00007f1f6001bad0 0x726573556468764f

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7F20016DBC28 : 0x6d654d6e69614d5f 0x0000000000000000

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: SIGNAL: stack 7F20016DBC38 : 0x26d37b21b597c600 0x0000000300000000

    2015-04-15T19:06:34-07:00[+0.010]| vcpu-0| I120: Backtrace:

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| I120: Backtrace[0] 00007f20016db660 rip=00000000004f31ee rbx=00000000004f2fc0 rbp=0000000000000000 r12=00007f20016dc690 r13=00007f20016dbc48 r14=00007f20016dbc48 r15=000000000000000b

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| I120: Backtrace[1] 00007f20016db690 rip=0000000000462ce9 rbx=000000000000000b rbp=0000000000000004 r12=00007f20016dc690 r13=00007f20016dbc48 r14=00007f20016dbc48 r15=000000000000000b

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| I120: Backtrace[2] 00007f20016db780 rip=00007f200756fcb0 rbx=00000000023ae578 rbp=0000000000000004 r12=0000000000000164 r13=00007f2007da8ec0 r14=0000000002221920 r15=00007f2007da8ec0

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| I120: Backtrace[3] 00007f20016dbbc8 rip=0000000000000000 rbx=00000000023ae578 rbp=0000000000000004 r12=0000000000000164 r13=00007f2007da8ec0 r14=0000000002221920 r15=00007f2007da8ec0

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| I120: SymBacktrace[0] 00007f20016db660 rip=00000000004f31ee in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| I120: SymBacktrace[1] 00007f20016db690 rip=0000000000462ce9 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| I120: SymBacktrace[2] 00007f20016db780 rip=00007f200756fcb0 in function (null) in object /lib/x86_64-linux-gnu/libpthread.so.0 loaded at 00007f2007560000

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| I120: SymBacktrace[3] 00007f20016dbbc8 rip=0000000000000000

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| I120: Unexpected signal: 11.

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| W110:

    2015-04-15T19:06:34-07:00[+0.011]| vcpu-0| W110+ The core dump limit is set to ZERO; no core dump should be expected

    2015-04-15T19:06:34.058-07:00| vthread-12| I120: Stream 7F1F60024810 ready

    2015-04-15T19:06:34.058-07:00| vthread-12| I120: VTHREAD initialize thread 12 "vthread-12" pid 4845

    2015-04-15T19:06:34-07:00[+0.084]| vcpu-0| W110: Core dumped.

    2015-04-15T19:06:34-07:00[+0.084]| vcpu-0| I120: Core dump pipes to process /usr/share/apport/apport %p %s %c, core file unreliable

    2015-04-15T19:06:34-07:00[+0.084]| vcpu-0| W110: A core file is available in "/vm/CP_Win7_Ex1/core"

    2015-04-15T19:06:34-07:00[+0.084]| vcpu-0| W110: Writing monitor corefile "/vm/CP_Win7_Ex1/vmmcores.gz"

    2015-04-15T19:06:34-07:00[+0.086]| vcpu-0| W110: Dumping core for vcpu-0

    2015-04-15T19:06:34-07:00[+0.086]| vcpu-0| I120: Beginning monitor coredump

    2015-04-15T19:06:34-07:00[+0.871]| vcpu-0| I120: End monitor coredump

    2015-04-15T19:06:34-07:00[+0.871]| vcpu-0| W110: Dumping core for vcpu-1

    2015-04-15T19:06:34-07:00[+0.871]| vcpu-0| I120: Beginning monitor coredump

    2015-04-15T19:06:34-07:00[+1.608]| vcpu-0| I120: End monitor coredump

    2015-04-15T19:06:34-07:00[+2.393]| vcpu-0| I120: Coredump encountered overflow 2703:2703 (609 duplicates)

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: Backtrace:

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: Backtrace[0] 00007f20016db160 rip=00000000004f31ee rbx=00000000004f2fc0 rbp=0000000000000000 r12=0000000000000001 r13=00007f20016dbc48 r14=00007f20016dbc48 r15=000000000000000b

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: Backtrace[1] 00007f20016db190 rip=00000000004ce289 rbx=00007f20016db1b0 rbp=00000000014c4260 r12=0000000000000001 r13=00007f20016dbc48 r14=00007f20016dbc48 r15=000000000000000b

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: Backtrace[2] 00007f20016db690 rip=0000000000462d38 rbx=000000000000000b rbp=00007f20016db6c0 r12=00007f20016dc690 r13=00007f20016dbc48 r14=00007f20016dbc48 r15=000000000000000b

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: Backtrace[3] 00007f20016db780 rip=00007f200756fcb0 rbx=00000000023ae578 rbp=0000000000000004 r12=0000000000000164 r13=00007f2007da8ec0 r14=0000000002221920 r15=00007f2007da8ec0

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: Backtrace[4] 00007f20016dbbc8 rip=0000000000000000 rbx=00000000023ae578 rbp=0000000000000004 r12=0000000000000164 r13=00007f2007da8ec0 r14=0000000002221920 r15=00007f2007da8ec0

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: SymBacktrace[0] 00007f20016db160 rip=00000000004f31ee in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: SymBacktrace[1] 00007f20016db190 rip=00000000004ce289 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: SymBacktrace[2] 00007f20016db690 rip=0000000000462d38 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0000000000400000

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: SymBacktrace[3] 00007f20016db780 rip=00007f200756fcb0 in function (null) in object /lib/x86_64-linux-gnu/libpthread.so.0 loaded at 00007f2007560000

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: SymBacktrace[4] 00007f20016dbbc8 rip=0000000000000000

    2015-04-15T19:06:34-07:00[+2.743]| vcpu-0| I120: Msg_Post: Error

    2015-04-15T19:06:34-07:00[+2.744]| vcpu-0| I120: [msg.log.error.unrecoverable] VMware Player unrecoverable error: (vcpu-0)

    2015-04-15T19:06:34-07:00[+2.744]| vcpu-0| I120+ Unexpected signal: 11.

    2015-04-15T19:06:34-07:00[+2.744]| vcpu-0| I120: [msg.panic.haveLog] A log file is available in "/vm/CP_Win7_Ex1/vmware.log". 

    2015-04-15T19:06:34-07:00[+2.744]| vcpu-0| I120: [msg.panic.requestSupport.withoutLog] You can request support. 

    2015-04-15T19:06:34-07:00[+2.744]| vcpu-0| I120: [msg.panic.requestSupport.vmSupport.vmx86]

    2015-04-15T19:06:34-07:00[+2.744]| vcpu-0| I120+ To collect data to submit to VMware technical support, run "vm-support".

    2015-04-15T19:06:34-07:00[+2.744]| vcpu-0| I120: [msg.panic.response] We will respond on the basis of your support entitlement.

    2015-04-15T19:06:34-07:00[+2.744]| vcpu-0| I120: ----------------------------------------


    0 0
  • 04/16/15--02:51: P2V driver issue
  • Hi,

     

    i just restored a Acronis Image into a virtual machine. After configure the machine thru the converter, it boots.

    But i get a bunch of unknown Hardware and i cant install the Driver. I tried to install VM Ware Tools without success. I also tried to extract the Drivers and install them manually, without success.

    I also could read that some other People hat the same issue. But i cant find a solution yet. The worst Thing ist, that the NICs are either not working. So i cant Access the Network with my VM.

     

    Is there a trick how to force Windows 2003 to accept the VM Drivers?


    0 0

    I have insalled VMWare Player 7.1. I click

    "Create a new virtual machine."

    The "New virtual machine wizard" starts.

    I chose "Installer disk"

    "Reading disk" spins for around 15 minutes.

    It then says "Windows XP Professional detected"

    I click "Finish"

    A black screen comes on. It says

    "Network boot from AMD...............

    Operating system not found"

    What could be wrong?


    Thanks


    0 0

    Host OS : Win 7 Pro (x64)

    Guest OS: XP Pro (x86)

     

    I had a regular (mechanical) 500 GB hard drive (2 partitions OS and DATA) with W7P (x64) and VM Player 3.x running XPP for years with no problem.

    I could access the 2nd partition through the Guest OS and modify/save files etc on it.

     

    I just got a new WD2 Black Dual Drive (120GB SSD and 1TB mechanical in one unit) so technically there are 2 partitions on the drive.

    I copied the entire Player (data) folder from the old drive to the new. I installed the same version of Player 3.x and tried to access the Guest OS - I am able to access it but unable to access network or usb drives (keep getting errors as it boots up also) etc.

    So I started from scratch on new drive - installed vmplayer 3.x (even tried every version upto v 7.1.0) and installed Guest OS (XPP) again and now I am able to access the network and usb drives etc.

    But when I add the 2nd partition in the settings and start the player I get an error that it cannot start because it cannot power up the scsi (2nd partition) drive and it shuts down.

    If I remove the 2nd partition from settings it boots up fine.

    I am able to access the 2nd partition in W7P with no problems.

    In the Guest OS I am not able to access the 2nd partition.

    I called WD Support and they said to call VMWARE support and the problem has nothing to do with the physical drive.

    I have updated all the VMware tools (as recommended) but still not able to access the 2nd partition.

     

    In W7P I had to install a "driver" software to access the 2nd partition. I tried to install the same thing in the Guest OS (XPP) it starts to install and then comes back and says it cannot see the 2nd partition.

     

    Any help in this would be greatly appreciated as I would like to keep all the documents/data on the 2nd partition and be able to access the same from both the HOST and GUEST OS's without having to create duplicates or transfer them back and forth between the two.


    0 0

    Hi All,

     

    I've got VMware Player 7.1 running on Ubuntu server 14.10, and I started to notice that the number of zombie processes in top was increasing.

     

    I dug into some logs, and I discovered the below chunk in /var/log/syslog that appears every few seconds:

    Apr 18 06:57:20 bigbox vmauthd[24945]: LOCALE en_US.UTF-8 -> NULL

    Apr 18 06:57:20 bigbox vmauthd[24945]: Msg_SetLocaleEx: HostLocale=UTF-8 UserLocale=NULL

    Apr 18 06:57:20 bigbox vmauthd[24945]: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

    Apr 18 06:57:20 bigbox vmauthd[24945]: Msg_Reset:

    Apr 18 06:57:20 bigbox vmauthd[24945]: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

    Apr 18 06:57:20 bigbox vmauthd[24945]: ----------------------------------------

    Apr 18 06:57:20 bigbox vmauthd[24945]: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

    Apr 18 06:57:20 bigbox vmauthd[24945]: Could not expand environment variable HOME.

    Apr 18 06:57:20 bigbox vmauthd[24945]: DictionaryLoad: Cannot open file "~/.vmware/config": No such file or directory.

    Apr 18 06:57:20 bigbox vmauthd[24945]: Msg_Reset:

    Apr 18 06:57:20 bigbox vmauthd[24945]: [msg.dictionary.load.openFailed] Cannot open file "~/.vmware/config": No such file or directory.

    Apr 18 06:57:20 bigbox vmauthd[24945]: ----------------------------------------

    Apr 18 06:57:20 bigbox vmauthd[24945]: PREF Optional preferences file not found at ~/.vmware/config. Using default values.

    Apr 18 06:57:20 bigbox vmauthd[24945]: Could not expand environment variable HOME.

    Apr 18 06:57:20 bigbox vmauthd[24945]: PREF Unable to check permissions for preferences file.

    Apr 18 06:57:20 bigbox vmauthd[24945]: DictionaryLoad: Cannot open file "~/.vmware/preferences": No such file or directory.

    Apr 18 06:57:20 bigbox vmauthd[24945]: Msg_Reset:

    Apr 18 06:57:20 bigbox vmauthd[24945]: [msg.dictionary.load.openFailed] Cannot open file "~/.vmware/preferences": No such file or directory.

    Apr 18 06:57:20 bigbox vmauthd[24945]: ----------------------------------------

    Apr 18 06:57:20 bigbox vmauthd[24945]: PREF Failed to load user preferences.

    Apr 18 06:57:20 bigbox vmauthd[24945]: Connect from local socket (192.168.1.25:57548).

    Apr 18 06:57:20 bigbox vmauthd[24945]: Connect from 192.168.1.25

    Apr 18 06:57:20 bigbox vmauthd[24945]: SSL Error: error:02001002:system library:fopen:No such file or directory

    Apr 18 06:57:20 bigbox vmauthd[24945]: SSL Error: error:2006D080:BIO routines:BIO_new_file:no such file

    Apr 18 06:57:20 bigbox vmauthd[24945]: SSL Error: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib

    Apr 18 06:57:20 bigbox vmauthd[24945]: SSL Error: error:02001002:system library:fopen:No such file or directory

    Apr 18 06:57:20 bigbox vmauthd[24945]: SSL Error: error:2006D080:BIO routines:BIO_new_file:no such file

    Apr 18 06:57:20 bigbox vmauthd[24945]: SSL Error: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib

    Apr 18 06:57:20 bigbox vmauthd[24945]: SSL Error: error:02001002:system library:fopen:No such file or directory

    Apr 18 06:57:20 bigbox vmauthd[24945]: SSL Error: error:20074002:BIO routines:FILE_CTRL:system lib

    Apr 18 06:57:20 bigbox vmauthd[24945]: SSL Error: error:140AD002:SSL routines:SSL_CTX_use_certificate_file:system lib

    Apr 18 06:57:20 bigbox vmauthd[24945]: Error loading server certificate

    Apr 18 06:57:20 bigbox vmauthd[24945]: recv() FAIL: 1.

    Apr 18 06:57:20 bigbox vmauthd[24945]: VMAuthdSocketRead: read failed.  Closing socket for reading.

    Apr 18 06:57:20 bigbox vmauthd[24945]: Read failed.

     

    Restarting the vmware service on the server kills the zombie processes, but they begin to accumulate again when the service is started again with the above messages continuing to accumulate in /var/log/syslog.

     

    I've tried creating /usr/lib/vmware/settings and ~/.vmware/preferences [I'm assuming in my user's home directory], but that doesn't seem to help.

     

    Any ideas on how to make these errors go away?


    0 0

    I have attempted to install WVware player 7.1 64 bit in Mageia 5 - RC.

    I do understand Mageia is not a supported host operating system, but I would like to solve this problem nonetheless, if possible. It works fine in OpenSuse 13.2

    In Mageia the installation script executed without problems.  However the post-installation kernel updater script on starting Player fails with:

    2015-04-19T13:30:50.599+10:00| vthread-4| I120: Successfully extracted the vmnet source.

    2015-04-19T13:30:50.599+10:00| vthread-4| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-WEszzM/vmnet-only auto-build HEADER_DIR=/lib/modules/3.19.4-desktop-2.mga5/build/include CC=/usr/bin/gcc IS_GCC_3=no"

    The installed version of gcc is 4.9.2.

    So, is the apparent restriction in the command line above that gcc MUST=3, or that it must be no less than 3?

    Either way, is there anything I can do? Are there other diagnostics that could help?

    Thank you.

    Vlad


    0 0

    Running CentOS 6.4 host, Windows XP guest.  Host has two network adapters, one on 10.x.x.x and the other on 192.168.x.x., both of which work fine on the host.  VMPlayer only allows connecting to 10.x.x.x.  I need it to connect to 192.168.x.x.  How do I change network adapters in VMPlayer config?  I searched everywhere (including here) and found lots and lots of info on how to do that with Workstation but none with Player, and the Workstation instructions don't apply to Player.

     

    Thanks...

     

    Eric in NH


    0 0

    VMWare Player 7.1.0 Displays VMWare Workstation 11 as current update - which is obviously wrong!

    I guess it is a try to get users to UPGRADE to a payed Version.

    But even if it is on purpose - an UPGRADE should not be displayed on a specific search for UPDATES!


    0 0

    Hi,

     

    I have a dell XPS 15 and am having issues with the touchpad when running OSX mavericks.

     

    Left and right click on the touch pad produce a CTRL click and show the menu.

     

    A two finger tap has the effect of a left click.. which is problematic.

     

    Is there a way to change this?

     

    Thanks!


    0 0

    After more than one year using a VM created with VMWare Player 6.0.1, my VM doesn't start anymore.

    The error message "The operation on file 'E:\VM\Win7\Win7.vmdk'" appears everytime I try to run it.

    The problem started when I tried to open a folder with more than 200 files. It crashed with that error message and didn't work anymore.

    Hard disk where VM is running is OK. I'm using it right now.

     

     

    Please, I need to recover those files desperately or the VM itself.

    They are very important!

    Please, help! What can I do?

     

     

    Note:

    VMWare 6.0.1

    Host: Windows 7 Ultimate x64

    Guest: Windows 7 Professional x64


    0 0

    Hi,

     

    I have P2Vd a Dell laptop, running Windows 7 and am running it on my Windows 8.1 host. The conversion seemed to work without any issues. I can log into Windows, launch Outlook, Lync etc, however, within about 5 minutes of using it, I get the error below (in the VM). The VM crashes and I have to restart Player and the VM.

    VMPlayerIssues.PNG

    If I do nothing more than log in, the VM seems to stay up. The longest, so far is ~16 hours.

     

    I have created a new VM in player and attached the VMDK, in an attempt to remove any issues / corruptions in the .vmx file. It seems to have improved the situation by allowing me to use the VM for longer, but still ~ 5 minutes makes it pretty useless.

     

    There are several posts on the same general "Exception 0xc0000005 (access violation) has occurred" error, including KB 1008485 (which I followed), but the errors in my vmware.logs are different. The most noteworthy lines of the attached vmware.log seems to be:

     

    2455 vcpu-0| I120: FILE: FileDeletionRetry: Non-retriable error encountered (C:\Users\aperson\Documents\Virtual Machines\vmhostname.intl.domain.co.uk\vmhostname.intl.domain.co.uk.vmdk~): The system cannot find the file specified (2)

    2456 vcpu-1| I120: CDROM: Emulate GET CONFIGURATION RT 2 starting feature 0

    ..

    2490 vcpu-0| I120: TOOLS call to ghi.guest.getExecInfoHash failed.

    2491 vcpu-0| I120: VMXVmdbGetExecInfoHashCB: failed: ret = VMDB failure

    2492 vcpu-0| I120: TOOLS call to unity.get.binary.info failed.

    2493 vcpu-0| I120: VMXVmdbGuestBinaryInfoCB: failed: ret = VMDB failure

    2494 vcpu-0| I120: VMXVmdbGuestBinaryInfoCB: failed: ret = VMDB failure

    2495 vthread-15| W110: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----

    2496 vthread-15| I120: VTHREAD initialize thread 15 "vthread-15" host id 8316

    2497 vthread-15| W110: ExceptionAddress 0x7ffae808e9bf eflags 0x00010206

    2498 vthread-15| W110: rwFlags 0 badAddr 0xc4

     

    And it would be correct. The file doesn't exist. It does exist without the ~ (tilde) on the end of the path name. It's contents looks like:

     

    # Disk DescriptorFile

    version=1

    encoding="windows-1252"

    CID=8c0cc8f2

    parentCID=ffffffff

    isNativeSnapshot="no"

    createType="monolithicFlat"

     

    # Extent description

    RW 137363456 FLAT "vmhostname.intl.domain.co.uk" 0

     

    # The Disk Data Base

    #DDB

     

    1. ddb.adapterType = "lsilogic"
    2. ddb.geometry.biosCylinders = "6063"
    3. ddb.geometry.biosHeads = "255"
    4. ddb.geometry.biosSectors = "63"
    5. ddb.geometry.cylinders = "8550"
    6. ddb.geometry.heads = "255"
    7. ddb.geometry.sectors = "63"
    8. ddb.longContentID = "7b12e679d8586c3aedcdd0598c0cc8f2"
    9. ddb.thinProvisioned = "1"
    10. ddb.toolsVersion = "9410"
    11. ddb.uuid = "60 00 C2 9c 28 5c 9c d2-d8 99 a5 6d df 95 3a d3"
    12. ddb.virtualHWVersion = "10"

     

    Googling for the other errors hasn't yielded any tangible results, so I guess they are insignificant.

     

    I did find a post about removing host.maxkHzEstimate.cpuidHash and host.maxkHzEstimate.value from the host. I have tried this. I can't find the post. Doesn't help than VMware seem to have downed this site!

     

    The attached log file has been rotated before starting the VM, logging in, launching Outlook, attempting to write an email and sure enough within 7 minutes, it crashed, so it doesn't have much else other than the error.

     

    VMPlayer Version: 6.0.4 build-2249910

     

    If anyone has any ideas as to what is going on and might be able to assist in providing some way to a solution, I'd be most grateful.

     

    W.


    0 0

    Hi,

     

    When I install RHEL7 in my VMplayer, RHEL7 cannot find the disk in installation.

    Does any one know how to solve this problem?

     

    VM player:6.0.3 build-1895310

    Host OS: Win7 SP1 x64


    0 0

    OS: Win 7 Pro 64bit 16GB RAM

     

    VMware Player 6.0.3 free VMs are compatible with free 7.0 VMs?

    If I want install 7 free - I must uninstall 6.0.3???? may exist both in the PC?

    In either case VMs work in 7 from 6.0.3???

     

    To install Win 10 Preview - have to use Player 7 ? even with free version can do this?

     

    Emulators in win 10 Preview like WP10/WP8.1 must run OK inside the VM if i have VT-x/SLAT & 4-Core processor i5...?


    0 0

    Hi,

     

    I have a laptop with Windows 7 64-bit & Ubuntu 64-bit installed. I mainly use the Ubuntu, but I need some software installed on the Windows system. I tried vmplayer (with the Windows partition as its virtual hard drive), the system failed to boot (blue screen).

     

    I don't want the converter, it creates a new virtual machine instead of installs necessary drivers on the original system. I tried vmscsi driver mentioned in VMware KB:     Injecting SCSI controller device drivers into Windows when it fails to boot after converting it with VMwa…
    no luck, the driver failed to install.

    ===================

    I think the question boils down to "which are the necessary drivers for a Win 7 64-bit to boot under vmplayer and how to install them".

     

    Any suggestions ?

    Thanks.


    0 0

    xUbuntu 14.04

    LINUX Kernel : 3.19.4-031904

    VMware Player 7.1.0 build-2496824


    runing vplayer show Virtual ethernet failed

    I try the method

    https://wiki.archlinux.org/index.php/VM … he_modules
    but shell return {
    Creating symlink /var/lib/dkms/vmware-modules/11/source ->
                     /usr/src/vmware-modules-11

    DKMS: add completed.

    Kernel preparation unnecessary for this kernel.  Skipping...

    Building module:
    cleaning build area....
    make KERNELRELEASE=3.19.4-031904-generic all....(bad exit status: 2)
    ERROR (dkms apport): binary package for vmware-modules: 11 not found
    Error! Bad return status for module build on kernel: 3.19.4-031904-generic (x86_64)
    Consult /var/lib/dkms/vmware-modules/11/build/make.log for more information.
    }

    this is my make.log

    Ubuntu Pastebin

    and vmware-6609.log

    Ubuntu Pastebin


older | 1 | .... | 121 | 122 | (Page 123) | 124 | 125 | .... | 252 | newer