Hey guys,
Does anybody have any idea why this is happening:
I had Fedora 25 installed on my machine, on that I had VMware Player installed working just fine, this weekend I upgraded my PC to Fedora 26 and VMware Player stopped working, I tried uninstalling it and re-installing it with no luck, it won't show anything, no errors, no messages, nothing, not even running it as root will give anything.
Any ideas what can cause that?
Thanks in advance.
I have tried to use a second mouse & keyboard for the VM unfortunately I wasnt able to. once I changed the settings in my VM to show all usb connections it doesnt do that and on top of the VM there only the basic connections to the VM. Can someone please help me to figure it out? Thanks in advance!
I've created a RAW image of my disk (has 2 partitions, including one bootable Windows7).
How can I use this RAW image and boot it in VMware Workstation Player?
Context Menu Map or Mount a Virtual Disk to a Drive on the Host System
Error reading volume information
Map button is gray, not available.
I'm running a Win10 VM via Workstation Player on a second desktop (Win10 host) and I'd like to use the context menu key/AppsKey to swap from the VM to the main desktop.
I've made an AHK script that should remap this to the AppsKey, but the Ctrl+Alt to release cursor doesn't work, neither when run from within the VM nor from the host OS.
Is there a way to do this?
Hi all,
I have noticed that with my VMs running in VM Player, when I launch them, they go to full screen mode straight off the bat, which is what I want, and this works great when I am out and about, because they launch with the correct resolution to run full screen (just using my laptop monitor). When I am docked and have 2 additional screens that run a slightly different resolution to my laptop (screens are 1920 x 1200 and laptop is 1920 x 1080), if I use Win + Shift + Left Cur to move the VM to my left most screen (1920 x 1200) off my laptop screen (1920 x 1080), with the VM in full screen mode, VM Player does not trigger to recalculate the resolution that the VM should be running in.
Its not a massive issue, but an annoying one as it means I have to exit full screen mode and then re-enter it, which is a PITA.
Is this a known bug? Is there a way to work around it by hitting a shortcut keycombo to trigger a refresh of the GFX res that VMWare uses?
Thanks
Hi folks,
I'm having some problems in running the VM i copied from my School machine, problems as below:
1) First problem:
"Binary translation is incompatible with long mode on this platform. Long mode will be disabled in this virtual environment and applications requiring long mode will not function properly as a result. See http://vmware.com/info?id=152 for more details."
2) Second problem:
" VMware Player unrecoverable error: (vcpu-0)
vcpu-0:VERIFY vmcore/vmm/main/cpuid.c:386 bugNr=1036521
A log file is available in "C:\Users\USER\Desktop\***\REMWorkstationVM\vmware.log".
You can request support.
To collect data to submit to VMware technical support, run "vm-support".
We will respond on the basis of your support entitlement."
My machine is running in below spec:
Processor: Intel i5-7200U @2.50Ghz
System Type: 64 bit Operating System, x64-based processor
I have attached vmware.log, feel free to let me know if other details are required. Thank guys!
I asked a question in the Japanese vmware community, but since there seems to be nobody with similar case,
I will also post it to the English version.
I do not have much English is good at.
Because it is translating by google translation, it may be incomplete English, but please understand.
This sentence is very long. I'm sorry.
I am using a virtual machine (vmware player 12.5.7) with "MSI A88X-G43".
Immediately after starting the virtual machine, after several hours, etc. irregularly
"BSOD CLOCK_WATCHDOG_TIMEOUT (101)" occurs in the host OS.
When "vmware player" is executed with "MSI A88X-G43", in the same way
Is there anyone with an error "BSOD CLOCK_WATCHDOG_TIMEOUT (101)"?
Please tell me if there is a BSOD error occurring.
The CPU is AMD A10-7850K.
AMD CPU uses "vmware player" but BSOD CLOCK_WATCHDOG_TIMEOUT (101)
Is there anyone who doesn't happen?
Could you tell me the CPU, BIOS version information, and motherboard name of the machine that does not occur?
By the way, even with VMware 12.5.7 or earlier, the same BSOD is occurring, it is not a problem of VMware 12.5.7.
With various trial and error, with the virtual machine running,
If you do the following operation, you know that it always occurs in the environment where this failure occurs.
Press [Setting (T)] on "Startup and Recovery" in the [Control Panel] - [System and Security]
- [System] - [Advanced System Settings] - [Detail Setting] Tag.
(I think that the English version is somewhat different, because it is the display wording of the Japanese version)
At first, I thought of hardware and driver problems, and removed all connected devices such as USB and expansion cards.
And even with minimal configuration with CPU, memory, hard disk, power supply, mouse, keyboard
When running vmware player BSOD occurred.
I diagnosed memory and hard disk with the following tools.
Memory windows OS included tool, memtest86
HDD WD Data Lifeguard Diagnostic for Windows
By doing this, I confirmed that it is not abnormal in the hardware.
So I installed Windows 10 offline and clean install.
When running vmware player on this host OS, "BSOD CLOCK_WATCHDOG_TIMEOUT" similarly occurred.
In addition, we prepared another motherboard A88X-G43 of the same model number.
I have created another machine that has a separate power source, another CPU, another memory,
another mouse, another keyboard, another hard disk, and no identical parts at all. (See the end for details)
I cleanly installed Windows 10 offline on this machine.
If you run "vmware player" on this machine, the host OS similarly raises "BSOD CLOCK_WATCHDOG_TIMEOUT".
I tried using the guest OS which cleanly installed Windows 10, but similarly BSOD occurs.
Therefore, it is neither an individual defect of hard nor an OS problem.
Here I thought that there might be a problem with the BIOS.
Until then, I used the latest 3.C (3.12).
If this version is downgraded to 3.9, BSOD no longer occurs.
There are two A88X-G43 as above.
For both machines "BSOD CLOCK_WATCHDOG_TIMEOUT" will occur if "BIOS" is 3.10 or more.
If "BIOS" is 3.9, it does not occur at all.
Therefore, it is obvious that it is BUG of BIOS.
AMD provides microcode such as CPU, memory controller and HT bus controller in the form of AGESA code.
When examining the AMD AGESA version in the BIOS, it seems that it changed significantly between 3.9 and 3.10 (3.A).
The results of examining the BIOS and AGESA version with HWINFO 64 are as follows.
■BIOS where BSOD occurs
(1)BIOS Version: V3.12(3.C)
BIOS Date: 08/10/2016
AMD AGESA Version: CarrizoFM2r2PI V1.2.0.4X
(2)BIOS Version: V3.11(3.B)
BIOS Date: 04/08/2016
AMD AGESA Version: CarrizoFM2r2PI V1.2.0.3X
(3)BIOS Version: V3.10(3.A)
BIOS Date: 01/14/2016
AMD AGESA Version: CarrizoFM2r2PI V1.2.0.2X
■BIOS that BSOD does not occur
(1)BIOS Version: V3.9
AMD AGESA Version: GodavariPI V1.0.0.0
BIOS Date: 04/20/2015
This "BSOD" seems to occur when updating "BIOS" to V3.10 (2016/01/14) or later and using "vmware player" and using virtual instruction set of AMD CPU.
We analyzed complete memory dump at BSOD with windbg.
The CPU has four processors, but the 0, 1 and 2 processors were waiting for the completion of the 3rd processor.
Conversely, the third processor waited for the completion of 0, 1 and 2 processors, and it seemed to be deadlocked.
In this third processor, the program being executed was vmware.
It seemed like a problem of exclusive processing of memory and resources peculiar to multiprocessor.
When running vmware in this single processor state, BSOD no longer occurs.
However, it is slow with a single core, it can not be used at all times.
I thought to downgrade the BIOS to V3.9, which does not cause BSOD problems.
However, with this V3.9, connecting the Asmedia 1061 SATA Hostcortroler to the PCI-e causes another BSOD to occur frequently and the OS can not be started.
Therefore, it is necessary to use problematic V3.10 or later.
I am troubled because I can not avoid the BSOD problem by downgrading to V3.9.
The problematic BIOS, V3.10 seems to be released for compatibility with the new CPU Carrizo.
Unfortunately, it seems that the following fatal troubles are mixed from this version.
With old CPU (Trinity / Kaveri) BSOD occurs when virtual function is used.
For this motherboard, the carrizo core CPUs are "Athlon X4 845" and "Athlon X 4 835".
This product has no GPU and the clock is lower than the previous generations.
If there is no merit and the AGESA code is the cause, it is an annoying story.
However, the Microcode of the CPU in the AGESA code is as follows and there is no change.
AGESA code seems to be microcode other than CPU as a problem.
#1"AMD A10-7850K", the BIOS version 3.9 - 3.12 was all the same as "6003106".
#2"AMD A4-5300", BIOS version 3.9 - 3.10 was the same as "6001119".
However, as mentioned above, although the version of the AGESA code has certainly changed,
it is a situation where it can not be concluded that this is the cause.
Because recent UEFI BIOS is considerably huge, complicated, compressed and stored in 8 MB.
Besides the AGESA code, it is made up of more than 200 modules.
It contains various programs (initialization code and firmware driver) as below.
1)chipet
2) Storage controller
3) LAN controller
4) Clock generator
5) Power supply IC type etc.,
In addition, many modules such as MSI company and BIOS maker AMI company are built in.
I took the difference between the modules of BIOS 3.9 and 3.10.
Looking at it seems that not only the AGESA code but also many modules have been changed. (See attached file)
The yellow module shows that there is a difference.
However, there are many things that only change a few bytes of the BIOS version.
Therefore, I think there are fewer modules that have been modified or changed.
Some of these modules have been greatly changed.
I think this module is likely to have bugs.
Like me, if I run vmware on AMD platform, is there anyone with "BSOD CLOCK_WATCHDOG_TIMEOUT (101)"
occurring in the host OS?
Likewise, if there are people with BSOD errors, please let me know.
AMD CPU uses "vmware player" but BSOD CLOCK_WATCHDOG_TIMEOUT (101)
Is there anyone who doesn't happen?
Could you tell me the CPU, BIOS version information, and motherboard name of the machine that does not occur?
The specifications of the A88X-G43 are as follows.
[Current Computer]
Computer Brand Name: MSI MS-7793
UEFI Boot: Present
[Motherboard]
Motherboard Model: MSI A88X-G43 (MS-7793)
Motherboard Chipset: AMD A88X (Bolton-D4)
Motherboard Slots: 1xPCI, 5xPCI Express x1, 1xPCI Express x2, 2xPCI Express x4, 1xPCI Express x16
PCI Express Version Supported: v3.0
USB Version Supported: v3.0
[BIOS]
BIOS Manufacturer: American Megatrends
BIOS Date: 08/10/2016
BIOS Version: V3.12
AMD AGESA Version: CarrizoFM2r2PI V1.2.0.4X
UEFI BIOS: Capable
Super-IO/LPC Chip: Fintek F71879A/F71889A
BIOS ----------------------------------------------------------------------
BIOS Vendor: American Megatrends Inc.
BIOS Version: V3.12
BIOS Release Date: 08/10/2016
BIOS Start Segment: F000
BIOS Size: 8192 KBytes
System BIOS Version: 4.6
ISA Support: Not Present
MCA Support: Not Present
EISA Support: Not Present
PCI Support: Present
PC Card (PCMCIA) Support: Not Present
Plug-and-Play Support: Not Present
APM Support: Not Present
Flash BIOS: Present
BIOS Shadow: Present
VL-VESA Support: Not Present
ESCD Support: Not Present
Boot from CD: Present
Selectable Boot: Present
BIOS ROM Socketed: Present
Boot from PC Card: Not Present
EDD Support: Present
NEC PC-98 Support: Not Present
ACPI Support: Present
USB Legacy Support: Present
AGP Support: Not Present
I2O Boot Support: Not Present
LS-120 Boot Support: Not Present
ATAPI ZIP Drive Boot Support: Not Present
IEE1394 Boot Support: Not Present
Smart Battery Support: Not Present
BIOS Boot Specification Support: Present
Function key-initiated Network Service Boot Support: Not Present
Targeted Content Distribution Support: Present
UEFI Specification Support: Present
The specifications of the CPU are as follows.
# 1st machine
CPU information
[General Information]
Processor Name: AMD A10-7850K
CPU ID: 00630F01
Extended CPU ID: 00630F01
CPU Brand Name: AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G
CPU Stepping: KV-A1
CPU Code Name: Steamroller/Kaveri
Microcode Update Revision: 6003106
# 2st machine
CPU information
[General Information]
Processor Name: AMD A4-5300
CPU ID: 00610F01
Extended CPU ID: 00610F01
CPU Brand Name: AMD A4-5300 APU with Radeon(tm) HD Graphics
CPU Stepping: TN1-A1 (Trinity)
CPU Code Name: Piledriver/Trinity
Microcode Update Revision: 6001119
Thank you for reading very long sentences.
Howdy,
I'm trying to create a new machine but point it to an existing VMDK. I found this link: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2010196 But it only applies up to v10. Can anybody tell me how I do this? My only option as I see it is create a new one with an empty vdmk and then copy the vmdk I want on top of the empty one.
Thanks
I recently had a kernel update. I was prompted to install the update which I did but the update does not install. I have the following errors:
Virtual machine monitor failed
Virtual ethernet failed
I did some research and I was told to deactivate secure boot on my BIOS but my BIOS does not have the secure boot option. I do not know what to do. Please can you help me?
Hey,
I am using VMware Player 12 and just hat two VMs running like I always do. The files of the VMs are stored on an USB HDD, so that I can easily transport my VMs.
Just now, the USB plug on my PC acted up and the HDD was disconnected from the PC for a few seconds. Both VMs reported that as an error, but when I reconnected the HDD I initially was able to use the VMs again. They reported the error that they were unable to write to NVRAM, but I was able to close some windows after confirming the error.
Sadly, this only lasted a few seconds, and both VMs froze entirely. Sending Ctr-Alt-Del via VMware menu did nothing, and trying to shut the guests down, even using the "Power Off" option didn't do anything either.
Left with no other choices, I killed the VMware Player tasks via the host's task manager. Trying to start them up again was first denied because they were in use by another user, but knowing this issue I went into the folders and renamed the lck folders.
When I try to start the VMs now, I get the following error:
---------------------------
VMware Workstation 12 Player
---------------------------
Error while powering on: VMware Player cannot connect to the virtual machine. Make sure you have rights to run the program, access all directories the program uses, and access all directories for temporary files.
The VMX process exited prematurely.
---------------------------
OK
---------------------------
I haven't done anything else so far to the VMs, and I can still play other VMs that weren't running when the HDD disconnected just fine.
Is there any chance to recover these two VMs?
Hi,
Been using VMWare Player for years with no problems.
I am using the most up to date VMWare Player version 12.5.7 build-5813279.
I have a Linux Mint 18.2 KDE 64Bit host
with a Windows 10 Pro 64Bit guest.
I have bad audio on the Win 10 guest.
I've tried everything available on the Internet to fix this issue
but it is still there.
(it's on 3 different desktops, so we can illuminate a hardware issue)
How do I fix bad audio on Win 10 guest?
(the Win 10 guest is Genuine and virus free)
If this is a known issue, when will Player be updated to fix this?
If you need additional information then just ask, thanks!
Jesse
Hi, I'm new to VM. I've allocated 500MB hard disk - and want to reduce this now to 50 instead - can someone please help me work out how to do this? I'm happy to uninstall and reinstall everything if that is easy enough to do?
I'm using VM Workstation 12 Player.
Fail to copy files from CD-ROM.Legacy Emulation Is enabled and tried after disabling it too tried with both enabled and disabled.tried on all three nodes.The Iso Image Is 100% Fine.I booted a DVD from it and its running in Live mode please Help.I also get Error in Mounting Where As I have Nothing to Mount Because I am using .iso image.And the bad part is that My DVD was Cracked yesterday By My CD/DVD-ROM.Please Help.Images Below will Fully Describe You Whats Happening.
Hi!
I just installed VMWare Player 12 (12.5.7 build-5813279) and tried to install Windows Server 2016 Essentials. However, the configuration of Windows Server is stall at 17% - and it doesn't move further (screen shot attached). I tried it on two different computers - same thing. It's impossible to work with Windows Server until initial configuration is finished. From this I conclude this is something with VMWare.
Hi all,
My VMWare workstation 12 Player stopped working to access anything but itself.
My VMWare is using 192.168.203.89/28, my host ( Windows 10 ) is using 192.168.203.86/28 and my gateway is using 192.168.203.81/28.
On my VMWare , I can ping myself 192.168.203.89. But I can't ping 192.168.203.86 or 192.168.203.81. Of course, I can't Ping 4.2.2.2 .
On my VMWare, I installed Ubuntu, and Fortinet FortiManager products. All not working.
This happened all of sudden. I tried to use "Bridge mode", "NAT mode" , even "Host Only" mode for VMWare network settings, still same.
I also tried to repair / reinstall / upgrade to latest VMWare workstation 12 Player version 12.5.7, still same issue.
This issue also happened to my laptop ( Windows 10 ) and my desktop ( Windows 8.1 ).
Please can anyone help me on this issue? I can't use my VMWare at all now.
Regards,
Jerry
Chrome does not render the tab controls in any of its windows. The Chrome window's title bar where those buttons should be is just all white. Only the 3 window buttons are visible.
Though when I right click somewhere on the title bar it shows the proper menus as if the tab is there but I just don't see it.
In an incognito tab it looks like this:
It's most likely a problem with how chrome renders its GUI and how VMware player accelerates rendering on GPU because when I go to the VM settings and uncheck "Accelerate 3D graphics" chrome renders normally again.
I didn't have this problem initially when creating this VM, it just appeared someday.
Gues OS:
Win10 x64, 4G RAM, 4 Cores
Host OS:
Win10 x64, 16G RAM, i7 6700K (4c/8t), GTX 1070 8G (driver 384.94)
Ultimately, I really don't want to reinstall my guest because of this annoying bug. Can something else be done?
Over the last 10 days or so, for some reason every time I attempt to shutdown or restart Windows (Windows guest - Arch is the host), VMWare immediately freezes and the process cannot be killed to the point I need to do a hard reboot because I can't even shutdown my system cleanly (although my system is totally responsive in every other way before I shutdown with the exception of VMWare) and I get the following showing up when I run dmesg:
[ 1954.873606] BUG: unable to handle kernel paging request at ffffffffc057f14e
[ 1954.873651] IP: report_bug+0x94/0x120
[ 1954.873666] PGD 23ba0c067
[ 1954.873666] P4D 23ba0c067
[ 1954.873677] PUD 23ba0e067
[ 1954.873688] PMD 32ed01067
[ 1954.873700] PTE 800000032edf7161
[ 1954.873730] Oops: 0003 [#1] PREEMPT SMP
[ 1954.873744] Modules linked in: dm_mod dax ctr ccm cmac rfcomm vmnet(O) ppdev parport_pc parport fuse vmw_vsock_vmci_transport vsock vmw_vmci vmmon(O) arc4 bnep bbswitch(O) intel_rapl dell_wmi x86_pkg_temp_thermal intel_powerclamp sparse_keymap iTCO_wdt coretemp iTCO_vendor_support kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc dell_laptop dell_smbios dcdbas aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf btusb psmouse btrtl btbcm i915 pcspkr btintel bluetooth i2c_i801 iwlmvm snd_hda_codec_hdmi mac80211 ecdh_generic snd_hda_codec_realtek snd_hda_codec_generic input_leds evdev led_class joydev mousedev mac_hid iwlwifi snd_hda_intel atl1c lpc_ich cfg80211 drm_kms_helper snd_hda_codec uvcvideo videobuf2_vmalloc drm snd_hda_core
[ 1954.873979] videobuf2_memops snd_hwdep rfkill videobuf2_v4l2 snd_pcm videobuf2_core intel_gtt syscopyarea videodev snd_timer mei_me sysfillrect snd sysimgblt fb_sys_fops media mei soundcore i2c_algo_bit shpchp thermal wmi battery dell_smo8800 video tpm_tis button tpm_tis_core ac tpm sch_fq_codel ip_tables x_tables ext4 crc16 jbd2 fscrypto mbcache sd_mod hid_generic usbhid hid serio_raw atkbd libps2 xhci_pci xhci_hcd ahci libahci libata scsi_mod ehci_pci ehci_hcd usbcore usb_common i8042 serio
[ 1954.874130] CPU: 3 PID: 5334 Comm: vmx-vcpu-0 Tainted: G O4.12.6-1-ARCH #1
[ 1954.874156] Hardware name: Dell Inc. Dell System XPS 15Z/0MFNCV, BIOS A12 09/07/2012
[ 1954.874184] task: ffff89daea7a8e40 task.stack: ffffa34688da4000
[ 1954.874204] RIP: 0010:report_bug+0x94/0x120
[ 1954.874219] RSP: 0018:ffffa34688da7b10 EFLAGS: 00010202
[ 1954.874237] RAX: 0000000000000907 RBX: ffffa34688da7c78 RCX: ffffffffc057f144
[ 1954.874260] RDX: 0000000000000001 RSI: 0000000000000ed2 RDI: 0000000000000001
[ 1954.874283] RBP: ffffa34688da7b30 R08: ffffa34688da8000 R09: 000000000000034e
[ 1954.874306] R10: ffffffffa6a06a80 R11: ffff89daea7a8e00 R12: ffffffffc0532e34
[ 1954.874329] R13: ffffffffc0577366 R14: 0000000000000004 R15: ffffa34688da7c78
[ 1954.874353] FS: 00007fb1dd387700(0000) GS:ffff89daffac0000(0000) knlGS:0000000000000000
[ 1954.874379] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1954.874398] CR2: ffffffffc057f14e CR3: 000000032aea2000 CR4: 00000000000406e0
[ 1954.874421] Call Trace:
[ 1954.874439] ? ext4_set_page_dirty+0x44/0x60 [ext4]
[ 1954.874459] fixup_bug+0x2e/0x50
[ 1954.874474] do_trap+0x119/0x150
[ 1954.874487] do_error_trap+0x89/0x110
[ 1954.874504] ? ext4_set_page_dirty+0x44/0x60 [ext4]
[ 1954.874522] ? __enqueue_entity+0x6c/0x70
[ 1954.874537] ? enqueue_entity+0x109/0x740
[ 1954.874553] do_invalid_op+0x20/0x30
[ 1954.874567] invalid_op+0x1e/0x30
[ 1954.874582] RIP: 0010:ext4_set_page_dirty+0x44/0x60 [ext4]
[ 1954.874600] RSP: 0018:ffffa34688da7d28 EFLAGS: 00010246
[ 1954.874618] RAX: 017fff0000001068 RBX: ffffdee80b6ad200 RCX: 0000000000000000
[ 1954.874642] RDX: 0000000000000000 RSI: 0000000000000041 RDI: ffffdee80b6ad200
[ 1954.874665] RBP: ffffa34688da7d28 R08: ffff89daef2ce240 R09: 0000000180400037
[ 1954.874688] R10: ffffa34688da7d48 R11: ffff89daea7a8e00 R12: 0000000000000041
[ 1954.874711] R13: 0000000000000001 R14: ffff89dace1dc860 R15: 0000000000000000
[ 1954.874745] set_page_dirty+0x5b/0xb0
[ 1954.874767] qp_release_pages+0x64/0x80 [vmw_vmci]
[ 1954.874792] qp_host_unregister_user_memory.isra.20+0x27/0x80 [vmw_vmci]
[ 1954.874825] vmci_qp_broker_detach+0x245/0x3f0 [vmw_vmci]
[ 1954.874854] vmci_host_unlocked_ioctl+0x18e/0xa30 [vmw_vmci]
[ 1954.874887] do_vfs_ioctl+0xa5/0x600
[ 1954.874908] ? __fget+0x6e/0x90
[ 1954.874927] SyS_ioctl+0x79/0x90
[ 1954.874947] entry_SYSCALL_64_fastpath+0x1a/0xa5
[ 1954.874970] RIP: 0033:0x7fb34cf8f8b7
[ 1954.874990] RSP: 002b:00007fb1dd37eb28 EFLAGS: 00003246 ORIG_RAX: 0000000000000010
[ 1954.875029] RAX: ffffffffffffffda RBX: 00007fb1dd386580 RCX: 00007fb34cf8f8b7
[ 1954.875066] RDX: 00007fb1dd37eb40 RSI: 00000000000007aa RDI: 0000000000000065
[ 1954.875106] RBP: 0000000000000006 R08: 0000000000000002 R09: 00007fb1dd37ecd0
[ 1954.875147] R10: 00007fb1dd386bfe R11: 0000000000003246 R12: 00007fb34b8be010
[ 1954.875191] R13: 00000000747ff0ec R14: ffffffffffffffff R15: 0000000000000006
[ 1954.875236] Code: 74 59 0f b7 41 0a 4c 63 69 04 0f b7 71 08 89 c7 49 01 cd 83 e7 01 a8 02 74 15 66 85 ff 74 10 a8 04 ba 01 00 00 00 75 26 83 c8 04 <66> 89 41 0a 66 85 ff 74 49 0f b6 49 0b 4c 89 e2 45 31 c9 49 89
[ 1954.875365] RIP: report_bug+0x94/0x120 RSP: ffffa34688da7b10
[ 1954.876980] CR2: ffffffffc057f14e
[ 1954.886476] ---[ end trace cdf1cc11c1557bdd ]---
I've now tried kernels 4.12.{3,5,6,8}, with VMWare 12.5.6 as well as 12.5.7. The issue also persists with existing and clean installs of Windows 10.
I can't think of anything else that's changed, and everything has worked fine for a very long time up to this point.
Any ideas as to what might be going on?
I'm running lubuntu in a win10 guest machine under vmware workstation 12.5.7 build-5813279. Folder sharing is enabled, the host folder is named and created but ...
- vmware tools can't find the shared folder
- nor can it find a vmware perl script needed to find the shared folder
So evidently vmware tools is broken. But "Update VMware Tools" from the WorkStation Player menu does not deposit a tools installer file on the lubuntu desktop, so there's no installer file to unpack and install.
How do I solve this?
Hi; I am running Windows 7, 64 Bit OS. I am experiencing the following error message: "Error while powering on: The operation was canceled by the user" when I attempt to power up my VMWare Player from a "Suspended" state. It works fine until then.
Thanks
