Problems in Arch as guest in VMware Player

I'm running a fully updated Arch installation without a graphical interface in VMware Player 5, with Windows 7 as host. I've installed open-vm-tools from the repository, created the /etc/arch-release file and appended the daemon open-vm-tools to rc.conf as mentioned in the wiki. But every time I open the virtual machine I'm greeted with the warning:
The VMware Tools resume script did not run successfully in this virtual machine.
If you have configured a custom resume script in this virtual machine, make sure that it contains no errors.
You can also submit a support request to report this issue.
I don't even know where the resume script is and I'm pretty sure I haven't customized it. But as the machine boots correctly, I tried continuing and sharing a folder with the host.
I've set to share my Windows desktop in VMware player, set as "Always enabled" and with name "desktop". I tried mounting this folder adding the following line in /etc/fstab:
.host:/desktop /home/boppreh/desktop vmhgfs defaults 0 0
and the following commands
mount -t vmhgfs .host:/desktop ~/desktop
and
mount -t -v -o rw .host:/desktop ~/desktop
Those two commands print the message "Could not add entry to mtab, continuing".
All of them result in the same weird behavior: whenever I try to access the ~/desktop directory, I get kicked out back to Arch's login screen. I tried piping the output of those commands to a file, so I could see the error, but it never writes anything. It happens when I cd to the directory, or a simple ls.
So what's going on here? Is there any problem with the default resume script? Maybe open-vm-tools requires some kind of graphical access but didn't bother to tell? Did I do something wrong or forgot any step?

Solved the problem with the "resume script did not run successfully" warning by using the systemd specific configuration: https://wiki.archlinux.org/index.php/In … systemd%29
The shared folders still kick me out, though, even after following the Shared Folders instructions in the wiki for systemd. When running the mount command the folder is added correctly to /etc/mtab, even though the "Could not add entry to mtab, continuing" warning persists. I just tried cd-ing in the mounted directory as root, and it seems to work. Running commands as "sudo" doesn't help, I have to su first and then navigate to the directory to see its contents. Changing the permission of the folder didn't help either.
I'm thinking of just serving the files in a webserver. This is way too much work and by the number of strange problems it looks like I'm not supposed to be doing this.
Edit: exploring the shared folder as root works, but coping the files hangs the entire machine. Yeah, I'm going with the webserer alternative for now. If anyone has experienced this problems before, please share your ideas.
Last edited by BoppreH (2012-11-15 18:16:30)

Similar Messages

  • Windows 7 DPI scaling causes problems in VMware Player

    Hi there,
    I'm running Windows 7 x86 Professional and VMware Player 3.0.0. Windows 7 is set to 150% larger fonts (DPI scaling).
    If I start VMware Player with this DPI setting the guest VM is scaled aswell. If I set Windows 7 NOT to use DPI scaling only for VMware Player about 25% of the guest's screen is unreachable (lower-right). (See this screenshot: http://pix.sonhult.se/vmware.jpg)
    The guest is running Ubuntu 9.10 x86.
    Have anyone else been experimenting with DPI scaling and VMware Player? Any ideas?
    Thanks in advance!

    I know this is a thread necro but it's kinda hilarious and sad. I just searched the forums for "player dpi" and here I stumble upon my own post on the subject over five years ago.
    This time I'm running VMware Player version 11.1.0.58002 on a Windows 7 SP1 host where I've got the DPI set to 125%. I ran a Visual Studio tool called Spy++ while one of my VMs is compacting and it shows this information for that window:
    Window (id) "VMware Player" (Dialog)
    --- Window (id) "Compacting virtual disk..." Static
    --- Window (id) "" msctls_progress32
    --- Window (id) "Cancel" Button
    At 125% DPI I've never seen the Cancel button.
    Besides continuing to be indifferent to people who don't have perfect eyesight, this problem is going to occur more frequently when 4K displays become more popular with businesses. People will need to use much higher DPI to be able to read the fonts at those super-high resolutions.

  • Vmware Player in Arch Linux and RFKILL

    Hi,
    I am a newbie to Arch Linux, I have installed Vmware player in Arch but it doesn't seem to be running. I have followed the guide in the Arch Wiki. This is the output of the related commands.
    [root@swallowed Desktop]# uname -r
    2.6.35-ARCH
    [root@swallowed Desktop]# vmware-installer -l
    No protocol specified
    No protocol specified
    Product Name Product Version
    ====================== ====================
    vmware-player 3.1.2.301548
    [root@swallowed Desktop]# /etc/rc.d/vmware
    vmware vmware.d/
    [root@swallowed Desktop]# /etc/rc.d/vmware start
    Starting VMware services:
    VMware USB Arbitrator done
    Virtual machine monitor failed
    Virtual machine communication interface failed
    VM communication interface socket family failed
    Blocking file system failed
    Virtual ethernet failed
    [root@swallowed Desktop]# vmplayer
    No protocol specified
    xprop: unable to open display ':0.0'
    GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)
    No protocol specified
    xprop: unable to open display ':0.0'
    GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)
    No protocol specified
    (vmware-modconfig:5602): Gtk-WARNING **: cannot open display: :0.0
    [root@swallowed Desktop]#
    Does anyone know how to resolve this problem?
    Besides, I installed Arch on Dell Studio XPS 1640 and I don't seem tobe able to remove the hard block on my Wifi card. I installed all the driver already. This is the output of commands.
    [root@swallowed Desktop]# rfkill list
    0: dell-wifi: Wireless LAN
    Soft blocked: yes
    Hard blocked: yes
    1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: yes
    [root@swallowed Desktop]# rfkill unblock 0
    [root@swallowed Desktop]# rfkill list
    0: dell-wifi: Wireless LAN
    Soft blocked: yes
    Hard blocked: yes
    1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: yes
    [root@swallowed Desktop]#
    I even try to include this inside modprobe but it doesn't work.
    [root@swallowed Desktop]# cat /etc/modprobe.d/modprobe.conf
    # /etc/modprobe.d/modprobe.conf (for v2.6 kernels)
    options ath_pci rfkill=0
    options snd-pcsp index=2
    options iwlcore led_mode=1
    Thank you so much!

    vmware products need patching for kernel 2.6.35 - you didn't mention if you did that or not, but if you didn't, that would explain why vmware is not starting.

  • Problem installing Free BSD 64-bit with VMware Player on Thinkpad W510

    I installed VM Ware Player on the latest Thinkpad W510 with a 2.66ghz Intel processor. I am getting an error message indicating that the CPU doesn't support long mode. I was advised by the freenode #freeBSD channel that long mode is x86_64/amd64/emt64. This same channel also suggested that I tell vmware it was a 64bit guest. But I don't know how to do this. How do I do this? VMware Player didn't offer me any user options during the install. Is this something I should setup in the bios of the Thinkpad? Or something else? Is there more than one version of the VMware pLayer?

    Look on BIOS if VT is enabled.
    Best regards.
    IPnaSh
    First Spanish Community Guru - Colaborador ad honorem

  • I'm having problems loading web pages on a vmware workstation 6.05 guest OS using Firefox 3.5.9. I can ping external websites fine from the guest. No proxy. Any ideas?

    I'm having problems loading web pages on a vmware workstation 6.05 guest OS using Firefox 3.5.9. Also tried the latest 3.6 version. I can ping external websites fine from the guest. No proxy. Any ideas?
    == This happened ==
    Every time Firefox opened
    == I installed a guest OS

    I'm using the same swear words as you. There are several threads about this problem - no answers.
    I have a LaserJet 8100N and 8150DN, get the 79.01FE error on the 8150 from print outs from Safari, Firefox, and Preview, for only some sites/documents. CNN.com has become my test site, seems I can crash the printer 90% of the time with their home page at any given time in the day.
    A summary of what I have tried:
    - Upgraded the firmware to the latest for both the JetDirect card and the printer.
    - Swapped the JetDirect cards between the 8100 and 8150.
    - Swapped ram on the 8150 board.
    - Disconnected external trays, bins, and removed extra RAM and hard drives from the 8150.
    - Tried setting the JetDirect link and matching switch port link to 100FD, 10HD, 10FD, 100HD, as suggested by a poster.
    - Tried having client's print to the printer through a XServer Print Server.
    - Can consistently create the error from multiple systems running 10.3.9, 10.4.5, and 10.4.6 (didn't have an install base of 10.4 before 10.4.5).
    Someone in the 'know' (which means they're likely not), said 10.4.7 will likely fix this. Being Apple has not even addressed that the problem exists (that I could find), I doubt the magic fix is a release away.
    Apple's software is triggering something that Windows systems appears not to be, so one could say it's an Apple problem; but ulimately it's HP's software/hardware that is at fault in that it is allowing their system to crash from input alone.
    G4/G5 XServes    

  • [Solved] VMWare Player 4.0.0 and kernel 3.1.4-1-ARCH

    Hi,
    i followed the instructions here https://wiki.archlinux.org/index.php/VM … n.2FPlayer
    while running the modconfig command i get this error.
    Stopping VMware services:
    VMware Authentication Daemon done
    VM communication interface socket family done
    Virtual machine communication interface done
    Virtual machine monitor done
    Blocking file system done
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
    make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
    LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
    LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko
    make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
    make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
    make[1]: »postbuild« ist bereits aktualisiert.
    make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
    cp -f vmmon.ko ./../vmmon.o
    make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
    No protocol specified
    No protocol specified
    Built vmmon module
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
    make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
    CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
    In file included from /tmp/vmware-root/modules/vmnet-only/bridge.c:51:0:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
    include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
    include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
    include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
    include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
    include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
    include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
    include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
    include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
    include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
    include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
    cc1: Einige Warnungen werden als Fehler behandelt
    make[2]: *** [/tmp/vmware-root/modules/vmnet-only/bridge.o] Fehler 1
    make[2]: *** Warte auf noch nicht beendete Prozesse...
    In file included from /tmp/vmware-root/modules/vmnet-only/netif.c:43:0:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
    include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
    include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
    include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
    include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
    include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
    include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
    include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
    include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
    include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
    include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
    /tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfSetup«:
    /tmp/vmware-root/modules/vmnet-only/netif.c:149:7: Fehler: »struct net_device« hat kein Element namens »init«
    /tmp/vmware-root/modules/vmnet-only/netif.c:150:7: Fehler: »struct net_device« hat kein Element namens »open«
    /tmp/vmware-root/modules/vmnet-only/netif.c:151:7: Fehler: »struct net_device« hat kein Element namens »hard_start_xmit«
    /tmp/vmware-root/modules/vmnet-only/netif.c:152:7: Fehler: »struct net_device« hat kein Element namens »stop«
    /tmp/vmware-root/modules/vmnet-only/netif.c:153:7: Fehler: »struct net_device« hat kein Element namens »get_stats«
    /tmp/vmware-root/modules/vmnet-only/netif.c:154:7: Fehler: »struct net_device« hat kein Element namens »set_mac_address«
    /tmp/vmware-root/modules/vmnet-only/netif.c:155:7: Fehler: »struct net_device« hat kein Element namens »set_multicast_list«
    /tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfNetDeviceToNetIf«:
    /tmp/vmware-root/modules/vmnet-only/netif.c:196:14: Fehler: »struct net_device« hat kein Element namens »priv«
    /tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIf_Create«:
    /tmp/vmware-root/modules/vmnet-only/netif.c:311:4: Fehler: Implizite Deklaration der Funktion »compat_alloc_netdev« [-Werror=implicit-function-declaration]
    /tmp/vmware-root/modules/vmnet-only/netif.c:311:8: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung [standardmäßig aktiviert]
    /tmp/vmware-root/modules/vmnet-only/netif.c:316:7: Fehler: »struct net_device« hat kein Element namens »priv«
    /tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfReceive«:
    /tmp/vmware-root/modules/vmnet-only/netif.c:397:4: Warnung: Übergabe des Arguments 1 von »netif_running« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
    /tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifOpen«:
    /tmp/vmware-root/modules/vmnet-only/netif.c:477:4: Warnung: Übergabe des Arguments 1 von »netif_start_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
    /tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifClose«:
    /tmp/vmware-root/modules/vmnet-only/netif.c:525:4: Warnung: Übergabe des Arguments 1 von »netif_stop_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
    /tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »netif_running«:
    /tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:236:1: Warnung: Kontrollfluss erreicht Ende von Nicht-void-Funktion [-Wreturn-type]
    cc1: Einige Warnungen werden als Fehler behandelt
    make[2]: *** [/tmp/vmware-root/modules/vmnet-only/netif.o] Fehler 1
    make[1]: *** [_module_/tmp/vmware-root/modules/vmnet-only] Fehler 2
    make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
    make: *** [vmnet.ko] Fehler 2
    make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
    Unable to install vmnet
    Maybe someone has an idea whats going wrong ?
    stubb
    Last edited by stubb (2011-12-01 23:45:44)

    rm /usr/lib/vmware/modules/source/.patched
    fixed it

  • Issues with Arch 2009.02 in VMware Workstation [SOLVED]

    I installed Arch Linux 2009.02 i686 as a guest in VMware Workstation 6.5.1, my host is Vista x64. The installation of Arch itself and Xorg wasn't a problem although from this point I've had several issues.
    I was unable to 'startx' or 'xinit' without getting crashes, however adding hal to the daemons fixed that problem - some wiki entries state to add dbus, but dbus is already started. A lot of content on the wiki is outdated, telling users to use hwd; I did install hwd separately (from sourceforge) although it gave me hundreds? of errors related to PCI and eventually failure to parse some x configuration binary in /usr/bin.
    Multimedia Issues
    I then installed xfce4 and gstreamer-plugins. All video and audio play back too quickly, i.e. it seems to play the streams as fast as they can decode. This also happens with flash content such as youtube after I'd installed the appropriate programs. Thinking this may be a timing issue, I editted the vmware config file on my Windows host although it did not help; the timing in the VM seemed to be correct anyway.
    Display Issues
    When I run 'startxfce4' from a terminal, Xfce will start as 800x600 - if I go to change this resolution all options show 0Hz as the refresh rate and many options my monitor cannot display are shown even though I have VMware set to allow a maximum size of 1680x1050. I was unable to generate a 'good' xorg.conf file using 'X -configure' and as mentioned earlier, hwd would not work for me. I installed xf86-video-vmware and xf86-video-vesa as well as both open-vm-tools and normal vmware-tools (not at the same time or together) but can't seem to sort this issue. vmware-tools was able to generate a valid xorg.conf file but it only included a handful of 4:3 resolutions and some of these still showed 0hz. For some strange reason 'startx' and 'xinit' now do not work having failed to find /dev/fb0.
    VMware Tools
    When I did try to install vmware-tools, it had many difficulties trying to build the modules - mostly regarding to not recognising __FREEBSD__, I cannot remember the complete error. I also tried to build open-vm-tools but that gave an error about not being able to find libproc even though I had procps installed. Stopping open-vm-tools on shutdown also always fails and occurs twice.
    I'm going to try reinstalling now that I know a little more about what I did to get things working but if anyone could give me a hand it'd be much appreciated.
    Last edited by andyxl987 (2009-08-04 00:17:29)

    After a lot of experimentation I've got a satisfactory installation although a few minor problems remain:
    Adjustments required to correctly run Alsa+Xorg in Arch Linux 2009.02 using VMware Workstation
    The current kernel does not play nicely with alsa, downgrade to kernel26-2.6.29.4-1:
    wget http://www.schlunix.org/archlinux/core/ … pkg.tar.gz
    pacman -U kernel26-2.6.29.4-1-i686.pkg.tar.gz
    Install/Upgrade dbus:
    pacman -Sy dbus
    Add hal (if it's not installed then make sure to do so) to your daemons located in /etc/rc.conf, e.g.
    DAEMONS=(syslog-ng network netfs crond hal)
    The current open-vm-tools-modules is not compatible with the older kernel, instead use open-vm-tools-modules-2009.04.23-1:
    wget http://www.schlunix.org/archlinux/commu … pkg.tar.gz
    pacman -U open-vm-tools-modules-2009.04.23-1
    The installation will prompt you with an error that /etc/modprobe.conf could not be found (as does the current version), add the following to /etc/modprobe.d/modprobe.conf:
    install pcnet32 /sbin/modprobe -q --ignore-install vmxnet; /sbin/modprobe -q --ignore-install pcnet 32 ; /bin/true;
    You can now install open-vm-tools:
    pacman -S open-vm-tools
    To autoload open-vm-tools on start up you need to add it to your daemons located in /etc/rc.conf, e.g.
    DAEMONS=(syslog-ng network netfs crond hal open-vm-tools)
    Add vmware-user to your /etc/X11/xinit/xinitrc file if you desire (for seamless mouse and display switching), e.g. my xinitrc with xfce4 ends with:
    vmware-user &
    exec startxfce4
    Install the following components: xf86-video-vmware xf86-video-vesa xf86-input-vmmouse xf86-input-mouse:
    (You will not be able to start x if you have installed xf86-video-fbdev and do not have a valid xorg.conf file, this is addressed later)
    pacman -S xf86-video-vmware xf86-video-vesa xf86-input-vmmouse xf86-input-mouse
    Lastly we need to edit/create the /etc/X11/xorg.conf file to use our vmware drivers, this will enable automatic resolution switching and seamless mouse functionality:
    (All of the following is necessary otherwise X will ignore our vmware drivers)
    Section "ServerFlags"
        Option "AllowEmptyInput" "false"
    EndSection
    Section "InputDevice"
        Identifier  "VMware Mouse"
        Driver      "vmmouse"
        Option "Protocol"         "ps/2"
        Option "Device"           "/dev/input/mice"
        Option "ZAxisMapping"     "4 5"
        Option "Emulate3Buttons"  "true"
    EndSection
    Section "Device"
        Identifier  "VMware SVGA"
        Driver      "vmware"
    EndSection
    Section "ServerLayout"
        Identifier  "VMware Config"
        InputDevice "VMware Mouse" "CorePointer"
    EndSection
    Issues
    * open-vm-tools fails to stop during a shutdown or /etc/rc.d/open-vm-tools stop/restart
    * most screen resolutions show 0Hz (although everything works correctly) and adding VertRefresh to xorg.conf produces a major error
    * playback of flash video produces a sound artefact when starting - although I think this may be to do with the decoder rather than system
    I've marked this as solved although I welcome any suggestions regarding these minor issues. The open-vm-tools one I can probably sort out but it's too late now to look into tonight
    Last edited by andyxl987 (2009-08-04 00:21:03)

  • How to install Oracle Enterprised Linux on VMware PLayer 4

    Hi Everyone,
    My name is John and I've a small issue which I would like to share with you and hopefully, you are able to assist.
    My laptop is installed with a Window 7 Home Edition operating system and I've installed VMware-player-4.0.2. After reboot, I've also downloaded the file - V29609-01 which is the ISO file of Oracle Enterprise Linux 6.2.
    After that, I've tried to create a Virtual Machine - Oracle Enterprise Linux using the VMware Player by specifying the path and file name of the V29609-01.iso file on my local c:\ drive. I've tried it several times, but every time it just returns the message - 'pxe-e53 no boot filename received' and it just hangs there without proceeding further. Please let me know what I've done wrong and the correct steps and procedures to solve this problem as this is my first time installing a Linux operating system. Thank you for your assistance.
    Regards,
    John

    Hi,
    Can you clarify and explain what is your exact meaning of 'Are you sure you've added the ISO to the VM to boot from?'? Because the following is what I did:
    1.) Click the Create A New Virtual Machine.
    2.) Select the 'Install disc image file (iso):' option and enter the full path of the V29609-01.iso (Oracle Enterprise Linux 6.2) file that I've downloaded from https://edelivery.oracle.com/. But underneath it, that is a message saying - 'Could not detect which operating systems is in this dsic image. You will need to specify which operating system will be installed.'
    3.) Click 'Next'.
    4.) I chose "Linux' under the Guest operating system and chose 'Oracle Enterprise Linux' under the Version drop down.
    5.) Click 'Next'.
    6.) I left the Virtual machine name as 'Oracle Enterprise Linux' and click 'Next'.
    7.) I set the Maximum disk size to 300 GB and have the 'Split virtual disk into multiple files' option selected and click 'Next'.
    8.) I have the 'Power on this virtual machine after creation' checked and click 'Finish'.
    9.) A black screen displayed inside the VMware Player saying:
    'CLIENT MAC ADDR: 00 0C 289 ......
    PXE-E53: No Boot filename received
    PXE-M0F: Exiting Intel PXE ROM.
    Operating System not found
    10.) And the process just hangs there.
    Regards,
    John

  • VMware Player and mouse not behaving correctly with the vmmouse driver

    I'm running Arch on VMware Player and having problems with the mouse behavior.
    - Arch is updated, 32 -bit
    - VMware Player 6.0.1
    - Host is Windows 8.1 64-bit
    - XFCE 4.10
    If I install xf86-input-vmmouse, the following happens:
    - If cursor touches the edge of the screen when scrolling a window with the scroll bar, scrolling stops. If I continue pressing the mouse button and moving the mouse (and not touching any edges), the scrolling starts working again after two seconds.
    - When opening any new window, hovering and clicking will register only after two seconds. This is very noticeable when opening the application menu and trying to launch any app - first click never works.
    Uninstalling the vmmouse driver fixes the above problems. The mouse "feeling" gets very bad though, it seems jumpy and the acceleration is crazy and can't be tweaked to be satisfactory with the mouse settings. With vmmouse the mouse feels otherwise just fine.
    Installing or uninstalling Open-VM-Tools doesn't do anything.
    I tried this, but it had no effect: https://wiki.archlinux.org/index.php/In … s_expected
    Happens both in fullscreen and windowed, scrolling behavior happens every time, hover/click lag is not so predictable (seems to happen 50 % of the time).
    Might there be any easy fix for this?

    Hi Sung, Thanks for your reply.
    Leonardo:
    If I understand your msg correctly, I'm wondering if
    the data model as you described is complete.
    You state that you have MaintenanceType, Maintenance,
    and MaintenanceOrder, but don't you need
    MaintenanceOrderLine?MaintenanceOrderLine is what I'm calling Maintenance. A Maintenace record is used just to link a MaintenanceOrder to a MaintenanceType
    >
    Otherwise, you say that you removed all Maintenance's
    in step 2). How did you form a list of all
    Maintenance's in step 4)? How do you form this
    list?
    was raised due to unique constraint violationAt step 3) I'm using a view object, MaintenanceTypeView, to create a list of checkboxes, one for each MaintenanceType.
    At step 4), for each MaintenanceType selected in the form, I'm creating a new Maintenance using:
    //All codes of maintenance types, that already have a
    //respective maintenance record in the db, have already
    //been remove from the maintenancesToInsert list at this
    //point
    for (Iterator iter = maintenancesToInsert.iterator(); iter.hasNext();) {
    MaintenanceViewRow maintenanceRow = (MaintenanceViewRow) maintenanceView.createRow();
    maintenanceRow.setMaintenanceTypeCode(Integer.valueOf((String)iter.next()));
    maintenanceView.insertRow(maintenanceRow);
    >
    Sung

  • [Solved]Vmware Player - Blocking File System not fails to load

    All the mods load fine, except Vmblock.
    this is what i get when i run vmplayer.
    make: *** /tmp/modconfig-NtGU4D/vmblock-only: No such file or directory. Stop.
    Starting VMware Services:
    Virtual machine monitor....
    (finishes loading without problems)
    i suspect this has to do with the fact that i couldn't patch it following the wiki's guide (vmnet patched fine).
    I have the latest vmware player and the current arch linux kernel  (3.10.7-1)
    The patch doesn't seem to find the file it's meant to patch.
    I'd also like to know if i can safely ignore this.
    Edit: I suspect i just made a failure during the installation, i reinstalled it and it loaded this time... i think.
    Last edited by rabcor (2013-08-23 09:10:09)

    andy_v wrote:Make sure you create a 'compiz.desktop' file under /usr/share/applications.
    And that fixed it! Don't know how I overlooked that.  Thanks!

  • [SOLVED] VMWare Player won't install

    Hello,
    I have a problem installing VMWare player on arch. (disclaimer: I have RTFM *and* searched and googled hehe)
    I'm trying to install  VMware-Player-2.5.1-126130.x86_64.bundle on the following machine:
    Linux 2.6.29-ARCH #1 SMP PREEMPT x86_64 AMD Phenom(tm) 9850 Quad-Core Processor AuthenticAMD GNU/Linux
    I was following the guide here: http://wiki.archlinux.org/index.php/Installing_VMware
    and somewhat here: http://forums.fedoraforum.org/showthread.php?p=1126993
    My problem is though when i run /usr/bin/vmplayer it complains that
    Unable to build kernel module
    See log file /tmp/vmware-root/setup-12218.log for details
    and wont do anything else. I've basicly followed the guide I listed above in its steps so I'm a little lost now.
    Any advice would be greatly appriciated as its for a university assigment im rapidly running out of time on heheh.
    Regards,
    Mike.
    Last edited by DrMikeDuke (2009-04-05 16:50:59)

    Thanks for your help so far, awesome!
    I got it to work but a little differently since it still wouldnt patch for me
    Anyhow Il post my solution here since i know I always hate visiting a
    SOLVED thread only to find noone said HOW
    So I move my file from binary to binary old
    (mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old)
    then i go to my source directory
    (cd /usr/lib/vmware/modules/source)
    i untar everything in sight (:P)
    [root@TOMATO source]# ls
    vmblock-only vmci.tar vmnet-only vmppuser.tar
    vmblock.tar vmmon-only vmnet.tar vmware-workstation-2.6.29-v2.patch
    vmci-only vmmon.tar vmppuser-only vsock.tar
    then I used the scripts from here http://communities.vmware.com//thread/203231
    Finally I run step 6). vmware-modconfig --console --install-all
    And done!:D

  • [Solved] Can not build modules for VMware Player after kernel updates

    I have a problem generating the modules for VMware Player after kernel updates. I am using  VMware Player version 5.02 (without patches) and the softlink according to the Wiki.
    When I start the installation of the modules from the GUI, the program just closes. Running vmware-modconfig in the CLI generates the following log file:
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: Log for VMware Workstation pid=7478 version=9.0.2 build=build-1031769 option=Release
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: The process is 64-bit.
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: Host is Linux 3.8.10-1-ARCH 2012.11.29
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: Msg_Reset:
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden.
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: ----------------------------------------
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: Msg_Reset:
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": Datei oder Verzeichnis nicht gefunden.
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: ----------------------------------------
    2013-04-29T09:49:27.891+01:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
    2013-04-29T09:49:27.891+01:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-7478.log
    2013-04-29T09:49:27.892+01:00| vthread-3| W110: Icon name must be set.
    Interestingly, after deinstallation and reinstallation the VMWare Player works fine.
    Any hint, what's going wrong?
    Last edited by Thomas_Do (2013-08-07 07:25:51)

    Today, (Kernel  3.10.5-1, VMware Player version 5.02 with kernel patches) the modules could successful be generated from the CLI:
    vmware-modconfig --console --install-all
    Solved (somehow).

  • My keyboard acts up after launching VMware Player

    As the title says, after i launch VMware Player, my keyboard works fine inside of VMware Player, but outside of it it acts up sometimes i can't type anything and sometimes it wont type letters for every button i hit, depending on what i'm trying to type in the keyboard will only pick up certain letters (it does pick up the keypresses).
    My WM is Enlightenment 17 and the computer i'm on is a Lenovo Thinkpad laptop. Current arch kernel (3.10) and current VMware Player version too.
    If i change to another terminal (such as Ctrl+Alt+F2) the keyboard will work fine within that.
    If i turn off VMware Player, the keyboard will still act up.
    Edit:
    I installed openbox for the purpose of running VMware Player from it in a seperate instance of X. It turns out the problem is not present there, so it's only happening in E17.
    Last edited by rabcor (2013-08-23 10:18:58)

    Try checking the setting option for the keyboard setting and see if there is a option for turbo or quick keys because that what sounds like id happing.

  • VMWare Player Freezes on User Switching

    Hello,
      I'm running an AMD-64 X2 based system with 6GB RAM.  Host OS is Windows 7 Ultimate 64-bit.  Using VMware Player 3.0.1.
    Guest OS is Windows 7 Enterprise 64-bit.  Was originally built on an Intel based system, and complained when I switched it to an AMD system, but the image seems to run fine while it's active.
      The problem I'm having is when I leave VMware Player running and somebody performs a Switch User from Windows to switch to another user profile on the same host machine.  The player seems to run OK in the background, but then when I switch back to the original user and attempt to resume working with the virtual machine, the Player seems to be locked up with only a black screen where the guest OS should be visible.
      The only resolution is to use Player to force Power Off the guest OS.  I can then usually wait a bit, start Player, and re-boot the guest OS.
      The issue seems to be related to Windows User Switching on the Host OS while running the guest OS.
      Any thoughts or ideas?
    Thanks,
    Tom

    TallTomD > Any updates out there?  Anybody else experiencing similar issues?
    Count me in!
    Was using an old version and refused to update for a long time because it was working fine!
    Finally, I gave in to security paranoia and updated to the latest version and: BOOM!
    My VM locks-up upon user swithing!
    OS: MS-Vista.
    CPU: AMD-X3
    RAM: 4GB
    Any help on this?

  • BUG - client-side iPad keyboard in MRD 8.1.5 is mis-mapped for remote VMware Player console on Windows 8.1 Pro

    Client system: iPad 4 running iOS 8.1.1
    Client language/locale: US English
    Client app: MRD 8.1.5
    Server system: 64-bit Windows 8.1 Pro
    Server language/locale: US English
    Problem: client-side keyboard in MRD 8.1.5 does not work properly within VMware Player 6 console only
    When interacting with VMs through the VMware Player 6 console app on the remote Windows 8.1 host, the client-side iPad keyboard for MRD 8.1.5 is not properly mapped. Letter keys and the top-row number keys send function keys or non-standard key scan codes
    that aren't used by traditional PC keyboards. The spacebar sends the D key, and some keys send nothing at all. Many other keys work properly, including the client-side numeric keypad, and uppercase letters sent by using the Shift key (but not the iPad up-arrow
    shift key). The only way to send the proper keystrokes to VMware Player from MRD 8.1.5 is to not use the client-side iPad keyboard and instead switch to the on-screen keyboard provided by the remote Windows server.
    This problem only occurs within the VMware Player console app, and only with RDP connections that use the MRD 8.1.5 client on iOS. I do not encounter the problem with other iOS RD clients such as iFreeRDP by Thinstuff or Pocket Cloud Remote Desktop by Wyse.
    Steps to reproduce:
    Connect to Windows 8.1 Pro system from the MRD 8.1.5 client for iOS 8.1.1
    Using the client-side iPad keyboard within MRD 8.1.5, bring up the Run dialog by typing Windows-R
    Launch Notepad by typing notepad.exe in the Run dialog and pressing Enter on the client-side iPad keyboard
    Type some sample text in Notepad until you're confident that the client-side iPad keyboard is functioning properly
    Launch VMware Player 6 and start up a VM (mine was Windows Server 2008)
    Open the sign-on prompt in the VM by sending Ctrl-Alt-Ins from the client-side keyboard or by pressing the Ctrl-Alt-Del icon in VMware Player
    Touch or click in the password field in the VM to ensure it has keyboard focus
    Using the client-side keyboard, try to type letters or numbers in the password field, and notice that dots generally do not appear for most keypresses
    Switch to the server-side on-screen keyboard and delete the contents of the password field if it is not already empty
    Use the server-side on-screen keyboard to sign on to the VM
    Inside the VM, open Notepad or some other text editor
    Enter text into the editor from both the client-side and server-side keyboards to verify that only the server-side keyboard is functioning properly within the VM
    This issue is the only problem I'm having with MRD for iOS, and I hope it is resolved soon.
    Thanks,
    Fred

    Client system: iPad 4 running iOS 8.1.1
    Client language/locale: US English
    Client app: MRD 8.1.5
    Server system: 64-bit Windows 8.1 Pro
    Server language/locale: US English
    Problem: client-side keyboard in MRD 8.1.5 does not work properly within VMware Player 6 console only
    When interacting with VMs through the VMware Player 6 console app on the remote Windows 8.1 host, the client-side iPad keyboard for MRD 8.1.5 is not properly mapped. Letter keys and the top-row number keys send function keys or non-standard key scan codes
    that aren't used by traditional PC keyboards. The spacebar sends the D key, and some keys send nothing at all. Many other keys work properly, including the client-side numeric keypad, and uppercase letters sent by using the Shift key (but not the iPad up-arrow
    shift key). The only way to send the proper keystrokes to VMware Player from MRD 8.1.5 is to not use the client-side iPad keyboard and instead switch to the on-screen keyboard provided by the remote Windows server.
    This problem only occurs within the VMware Player console app, and only with RDP connections that use the MRD 8.1.5 client on iOS. I do not encounter the problem with other iOS RD clients such as iFreeRDP by Thinstuff or Pocket Cloud Remote Desktop by Wyse.
    Steps to reproduce:
    Connect to Windows 8.1 Pro system from the MRD 8.1.5 client for iOS 8.1.1
    Using the client-side iPad keyboard within MRD 8.1.5, bring up the Run dialog by typing Windows-R
    Launch Notepad by typing notepad.exe in the Run dialog and pressing Enter on the client-side iPad keyboard
    Type some sample text in Notepad until you're confident that the client-side iPad keyboard is functioning properly
    Launch VMware Player 6 and start up a VM (mine was Windows Server 2008)
    Open the sign-on prompt in the VM by sending Ctrl-Alt-Ins from the client-side keyboard or by pressing the Ctrl-Alt-Del icon in VMware Player
    Touch or click in the password field in the VM to ensure it has keyboard focus
    Using the client-side keyboard, try to type letters or numbers in the password field, and notice that dots generally do not appear for most keypresses
    Switch to the server-side on-screen keyboard and delete the contents of the password field if it is not already empty
    Use the server-side on-screen keyboard to sign on to the VM
    Inside the VM, open Notepad or some other text editor
    Enter text into the editor from both the client-side and server-side keyboards to verify that only the server-side keyboard is functioning properly within the VM
    This issue is the only problem I'm having with MRD for iOS, and I hope it is resolved soon.
    Thanks,
    Fred
    I'm experiencing exactly the same problem. Is there a solution yet?

Maybe you are looking for

  • Custom Category in Template Chooser

    When I open the template chooser I'd like to be able to have category folders for my templates. I have quite a few for work and it would be nice if they could be sorted by category as opposed to the name of the template. The iWork manuals suggest tha

  • Sending http data via GPRS Nokia 6600

    Hello! We are trying to make a multiplayer game over GPRS. The midlet-server application works fine when we were using the emulator. however, when we test it on the real phone, Nokia 6600, it seems that the data being sent by the MIDlet is not receiv

  • Add release strategy in the PO document type

    Dear all, I create one PO Return but there is no release strategy in ME28, what should I do to add the release strategy for that PO doc type. Thanks Pauline

  • Hour scale missing from iCal on daily display.

    Did anyone else notice that the time scale for the day is no longer displayed down the left side of the daily display. Didn't it used to show?

  • Can't enable root access in Lion 10.7.2

    Hi all, I have read this Apple article on enabling root in Lion. It doesn't work for me. I did a fresh install of Lion 10.7.2 to a formatted drive from a USB thumbdrive. I ran Software Update until there were no more updates. When I open the "Directo