VMware Workstation 9.0 – Initial Tests.. and a Fix for Kernel 3.5.2..
Just completed some basic tests with the new VMware Workstation 9.0 on my ‘test’ system (x86_64, Fedora 17)…
Initial results..
Compiles and runs OK on kernel 3.4.9.
Compiles OK, but causes general protection fault (with tombstone..) on kernel 3.5.2. (scroll down for the fix..)
…………………….
/dev/vmnet: port on hub 8 successfully opened /dev/vmnet: open called by PID 1055 (vmnet-dhcpd) /dev/vmnet: port on hub 8 successfully opened general protection fault: 0000 [#1] SMP CPU 1 Modules linked in: tpm_infineon vmnet(O) fuse vsock(O) vmci(O) vmmon(O) btusb snd_hda_codec_analog uvcvideo bluetooth videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media snd_hda_intel snd_hda_codec arc4 iwlwifi snd_hwdep snd_pcm snd_page_alloc mac80211 cfg80211 hp_accel snd_timer snd rfkill soundcore joydev serio_raw fan lpc_ich lis3lv02d sky2 pcspkr mfd_core input_polldev microcode thermal container processor nfsd exportfs nfs_acl lockd uinput sunrpc ipv6 radeon i2c_algo_bit drm_kms_helper ttm drm i2c_core [last unloaded: scsi_wait_scan] Pid: 1379, comm: vmware-hostd Tainted: G IO 3.5.2 #1 Hewlett-Packard HP Compaq 6830s/30E9 RIP: 0010:[<ffffffffa02aff99>] [<ffffffffa02aff99>] HostIF_SafeRDMSR+0x6/0x1d [vmmon] RSP: 0018:ffff880136eedbb0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000001 RCX: 000000000000048c RDX: 0000000000000000 RSI: ffff880139ba1490 RDI: 000000000000048c RBP: 0000000000000000 R08: ffff880139ba1480 R09: 0000000000013790 R10: 0000000005e98b70 R11: 0000000000000246 R12: ffff880139ba1480
…………. etc etc ………..
So – I will stay with VMware W/S 8.0.4(patched) – which runs fine on 3.5.2, for the time being. Hopefully a patch for 9.0 will be available soon.
I will examine the 8.0 patch set to see if there is anything that can be applied to the 9.0 code..
Update: No need… A patch is already available.. Tested with VMware W/S 9.0 on kernel 3.5.2 on my ‘crash and burn’ system, and it works fine. Just need to test with ‘live’ data, now..
More details – and the fix, here:
This was of great help to me thanks a ton :)
Glad it helped.. VMware have consistently been behind the curve when it comes to support of the very-latest Linux kernel, as they are focussed on the ‘business’ market for Linux, which typically has an older-but-stable kernel. Fortunately, someone in the community always comes up with a patch..