2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder0.present = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder0.enabled = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder0.readAccess = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder0.hostPath = C:\Dokumente und Einstellungen\kb\Eigene Dateien
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder0.guestName = EigeneDateien
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder0.expiration = session
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder1.present = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder1.enabled = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder1.readAccess = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder1.writeAccess = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder1.hostPath = C:\Programme\Siemens
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder1.guestName = Siemens
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder1.expiration = session
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder2.present = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder2.enabled = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder2.readAccess = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder2.writeAccess = FALSE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder2.hostPath = E:\
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder2.guestName = Sys
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder2.expiration = session
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder3.present = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder3.enabled = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder3.readAccess = TRUE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder3.writeAccess = FALSE
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder3.hostPath = G:\
2013-04-30T20:09:09.521+01:00| vmx| I120: DICT sharedFolder3.guestName = Lic
2013-04-30T20:09:09.522+01:00| vmx| I120: DICT sharedFolder3.expiration = session
2013-04-30T20:09:09.522+01:00| vmx| I120: DICT sharedFolder.maxNum = 4
Damit kann Linux nichts anfangen und normalerweise überspringt VMware ihm unbekannte/unsinnige Einträge. Letzteres klappt aber nicht immer.
2013-04-30T20:09:09.379+01:00| vmx| I120: hostCPUID vendor: GenuineIntel
2013-04-30T20:09:09.379+01:00| vmx| I120: hostCPUID family: 0x6 model: 0xf stepping: 0xd
2013-04-30T20:09:09.379+01:00| vmx| I120: hostCPUID codename: Conroe/Woodcrest/Merom (Core)
2013-04-30T20:09:09.379+01:00| vmx| I120: hostCPUID name: Intel(R) Core(TM)2 Duo CPU T5450 @ 1.66GHz
Keine guten Voraussetzungen für die Virtualisierung. Mobil-CPUs haben meist mehr Einschränkungen als deren Desktop-Pendants.
2013-04-30T20:09:09.542+01:00| vmx| I120: MsgHint: msg.monitor.BTnoLM2
2013-04-30T20:09:09.542+01:00| vmx| I120+ Binary translation is incompatible with long mode on this platform. Disabling long mode. Without long mode support, the virtual machine will not be able to run 64-bit code. For more details see
http://vmware.com/info?id=152.
2013-04-30T20:09:09.542+01:00| vmx| I120+ ---------------------------------------
2013-04-30T20:09:11.190+01:00| vmx| I120: HV Settings: virtual exec = 'software'; virtual mmu = 'software'
Das war bei der CPU nicht anders zu erwarten gewesen.
2013-04-30T20:09:11.495+01:00| mks| I120: Disabling 3D on this host due to presence of Mesa DRI driver. Set mks.gl.allowBlacklistedDrivers = TRUE to override.
2013-04-30T20:09:11.498+01:00| mks| I120: Disabling 3D on this host due to presence of Mesa DRI driver. Set mks.gl.allowBlacklistedDrivers = TRUE to override.
2013-04-30T20:09:11.499+01:00| mks| W110: GL-Backend: Failed to start GLBackend's screen compositor, GLBackend will stop working!
2013-04-30T20:09:11.499+01:00| mks| W110: MKS-RenderMux: Backend GLBackend<8F23A08> failed to start. Disabling.
2013-04-30T20:09:11.499+01:00| mks| I120: MKS-SLC: failed to start svga3d vmiop to render 3d.
...
2013-04-30T20:09:11.703+01:00| vmx| I120: Msg_Post: Warning
2013-04-30T20:09:11.703+01:00| vmx| I120: [msg.glX.noHardwareAccel] Hardware graphics acceleration is not available. As a result, this virtual machine may experience very low graphics performance. Follow the instructions provided by your graphics card vendor or Linux distribution in order to update your computer's OpenGL drivers.
2013-04-30T20:09:11.703+01:00| vmx| I120: ----------------------------------------
2013-04-30T20:09:11.836+01:00| vmx| I120: Msg_Post: Warning
2013-04-30T20:09:11.837+01:00| vmx| I120: [msg.mks.no3D] No 3D support is available from the host. The 3D features of the virtual machine will be disabled.
2013-04-30T20:09:11.837+01:00| vmx| I120: ----------------------------------------
Welche Grafik hat dein NB?
Die Übernahme bestehender VMs auf einen anderen Host stellt im Normalfall kein Problem dar. Problematisch wird es, wenn sich die CPU-Features oder Dateisystemkonventionen grundlegend unterscheiden. Bei letzterem muß man halt manuell eingreifen. Wenn man geschickt ist, erstellt man einfach zwei VMX-Dateien für Linux und Windows als Host-OS und kann die VM dann problemlos zwischen beiden Welten austauschen.