VMWare Workstation 7.1.2 64 - bit Windows host failed cloning

Similar Questions

• VmWare Workstation 8 and no 64-bit support

  First of all. I'm sorry for my bad English.

  My hardware:

  ASUS Sabertooth X 58 Mainboard

  Intel Core i7 950 CPU

  12 GB of Ram

  Under a Windows 7 Ultimate (latest patches installed)

  In the Bios is VT ENABELT

  My problem is that since a little day invited VMware Server as me as my PC dosnt support 64-Bit operating system.

  Follow them Info box introduce yourself a way:

  Virtualization software is Incompatible with the long Mode on this platform, the virtual machine will not be able to run 64-bit code.

  So I have a w2k8 R2 on my server and it runns fine until the error message.

  I hope you can help me quickly while im doing certificate MCITP training and Certification tests in 4 weeks and I neet training

  Thanks a lot for your help.

  Sorry if I post in the wrong Thread.

  There are a few days ago a user had problems with 64-bit VM too well that VT has been activated. Perhaps the cause (and the resolution/workaround) are the same.

  According to Re: comments 8 and 64-bit Workstation bits in the vmware.log indicate that VT - x is turned on.

  2011 09-23 T 23: 21:35.610 + 02:00 | VMX | I120: Common: MSR 0x3a = 0x5

  Bit 0 and bit 2 are defined.

  So maybe jmattson workaround provided in the mentioned discussion can help.

  Add the following line to C:\ProgramData\VMware\VMware Workstation\config.ini:

  hv.assumeEnabled = TRUE
  

  André

• How to run VMWARE Workstation 7.1.2 securely on Windows 7?

  Hello

  I downloaded a trial version of vmware workstation 7.1.2 to check, if I could use it to keep a proven windows 2000 on a windows host environment 7.

  When I run a virtual machine, the system tells me, that the "VmWare authorization Service" does not work. When I try to start from the list of services of the Task Manager, I get the error code_6000004.

  On a forum German vmware, I found the advice to disable windows security feature 7 UAC completely. But that has not yet solved the problem I've tried with a non-administrative user account.

  Finally it works, but only in a dangerous way:

  So far, I only managed to run VMWARE 7.1.2 on Windows 7, if I disable UAC AND log in as administrator. Which would be Ok for experiment from time to time, but do not regularly the computer as is - for good reason - not recommended by windows.

  Can someone please give me some adivce on my questions:

  How can I use VMWare Workstation on a host of Windows 7 with an non-administratif account?

  Better would be, how can I use VMWare Workstation as a standard user AND you have UAC on a recommended security level?

  Is disabling the functions of central security in fact the adivce official to run VmWare on a host of Windows 7?

  I know, Windows 7 is quite new and a lot of software has not properly adapted to him so far, but in the meantime, it is still not easy to find an older host OS to be able to correctly use VMWare (on Windows 2000 as a host, it worked great and I do not want to give it up so easy)

  Kind regards

  Post edited by: nice2meetyou2

  I just removed the XML that has been added automatically

  I used Vmware Workstation 7.x for Windows 7 without problems so far. I installed the package as an administrator, of course, but then used the user to create and manage virtual machines. I have UAC in default mode and does not get a prompt either do anything.

  The option "Run as Administrator" is just to load an application with administrator credentials already loading in the token to access at the outset and you will get a prompt later, but there should be no difference here.

• Guest OS VMware Workstation with NAT cannot communicate with the host

  I often run VMware Workstation on an Ubuntu Linux box and the load of virtual machines inside.

  The default is to configure a network card for the NAT, but that NEVER works, I have never no connectivity to the physical network in my guest operating system until I have change the type of the virtual machine network adapter for bridged.

  However, when I install ESXi 4.1 as a VM bridged, he can see the physical network, but VMs decked inside it can not...  I think that if I am NAT to work he'd let me withdraw my guest as oses nested inside BONE that is a host... If this is meaningless to anyone at all network connectivity prompt.

  I could really use help figure this.  I was hitting my head for weeks and led to nothing.

  If you do not know which IP address to use in the case of NAT, I recommend you temporarily enable DHCP on the Windows 7 host and then run "ipconfig/all" to see what it looks like. To configure the IP settings manually, make a note of the settings and set the IP address of one outside the range NAT NETWORK.

  André

• Linux - compilation of the modules in the kernel (bundle of VMware Workstation 9.0.2) against core 3.10 fails

  Hey,.

  I try to get VMware Workstation running on an Ubuntu 13,10 pre 9.0.2 bundle, but the kernel modules won't get compiled with the kernel 3.10.0 - 6.

  Here is the log of the build scripts:

  Using 2.6.x kernel build system.

  do: go in Verzeichnis "/ tmp/modconfig-DQkPL0/vmnet-only.

  / usr/bin/make /lib/modules/3.10.0-6-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Betrete Verzeichnis ' / usr/src/linux-headers-3.10.0-6-generic'

  CC [M] /tmp/modconfig-DQkPL0/vmnet-only/driver.o

  CC [M] /tmp/modconfig-DQkPL0/vmnet-only/hub.o

  CC [M] /tmp/modconfig-DQkPL0/vmnet-only/userif.o

  CC [M] /tmp/modconfig-DQkPL0/vmnet-only/netif.o

  In file included from tmp/modconfig-DQkPL0/vmnet-only/vnet.h:28:0,

  of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

  from /tmp/modconfig-DQkPL0/vmnet-only/netif.c:42:

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompilePtr ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2558:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

  MAKE_ATOMIC_TYPE (Ptr, 64, void const *, void *, uintptr_t)

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompileInt ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2562:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

  MAKE_ATOMIC_TYPE (Int, 32, int, int, int)

  ^

  In file included from tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:31:0,

  of tmp/modconfig-DQkPL0/vmnet-only/vnet.h:29.

  of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

  from /tmp/modconfig-DQkPL0/vmnet-only/netif.c:42:

  /tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h: in function 'MonitorActionSet_AtomicInclude ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:91:4: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

  ASSERT_ON_COMPILE ((ACTION_WORD_SIZE & (ACTION_WORD_SIZE-1)) == 0);

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/Netif.c: in function 'VNetNetIf_Create ':

  /tmp/modconfig-DQkPL0/vmnet-only/Netif.c:191:33: error: dereferencing pointer to incomplete type

  netIf-> port.jack.procEntry-> read_proc = VNetNetIfProcRead;

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/Netif.c:192:33: error: dereferencing pointer to incomplete type

  netIf-> port.jack.procEntry-> data is netIf;.

  ^

  make [2]: * [/ tmp/modconfig-DQkPL0/vmnet-only/netif.o] Fehler 1

  make [2]: * Warte auf noch nicht processes going...

  In file included from tmp/modconfig-DQkPL0/vmnet-only/vnet.h:28:0,

  of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

  from /tmp/modconfig-DQkPL0/vmnet-only/hub.c:43:

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompilePtr ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2558:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

  MAKE_ATOMIC_TYPE (Ptr, 64, void const *, void *, uintptr_t)

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompileInt ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2562:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

  MAKE_ATOMIC_TYPE (Int, 32, int, int, int)

  ^

  In file included from tmp/modconfig-DQkPL0/vmnet-only/vnet.h:28:0,

  of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

  from /tmp/modconfig-DQkPL0/vmnet-only/driver.c:51:

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompilePtr ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2558:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

  MAKE_ATOMIC_TYPE (Ptr, 64, void const *, void *, uintptr_t)

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompileInt ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2562:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

  MAKE_ATOMIC_TYPE (Int, 32, int, int, int)

  ^

  In file included from tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:31:0,

  of tmp/modconfig-DQkPL0/vmnet-only/vnet.h:29.

  of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

  from /tmp/modconfig-DQkPL0/vmnet-only/hub.c:43:

  /tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h: in function 'MonitorActionSet_AtomicInclude ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:91:4: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

  ASSERT_ON_COMPILE ((ACTION_WORD_SIZE & (ACTION_WORD_SIZE-1)) == 0);

  ^

  In file included from tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:31:0,

  of tmp/modconfig-DQkPL0/vmnet-only/vnet.h:29.

  of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

  from /tmp/modconfig-DQkPL0/vmnet-only/driver.c:51:

  /tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h: in function 'MonitorActionSet_AtomicInclude ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:91:4: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

  ASSERT_ON_COMPILE ((ACTION_WORD_SIZE & (ACTION_WORD_SIZE-1)) == 0);

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/hub.c: in function 'VNetHubFindHubByID ':

  /tmp/modconfig-DQkPL0/vmnet-only/hub.c:132:49: warning: 'sizeof' into 'memcmp' appeal argument is the expression even as the first source. Did you provide an explicit length? [- Wsizeof - pointer-memaccess]

  memcmp (idNum, currHub-> id.pvnID, sizeof idNum))) {}

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/hub.c: in function 'VNetHubAlloc ':

  /tmp/modconfig-DQkPL0/vmnet-only/hub.c:315:36: warning: the argument of 'sizeof' into 'memcpy' appeal is the same type of pointer ' uint8 *' as the destination. EXPECTED "uint8" or explicit length [- Wsizeof - pointer-memaccess]

  memcpy (hub-> id.pvnID, id, id sizeof);

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/hub.c:366:28: error: dereferencing pointer to incomplete type

  Jack-> procEntry-> read_proc = VNetHubProcRead;

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/hub.c:367:28: error: dereferencing pointer to incomplete type

  -->--> Data procEntry Jack is jack.;

  ^

  In file included from tmp/modconfig-DQkPL0/vmnet-only/vnet.h:28:0,

  of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

  from /tmp/modconfig-DQkPL0/vmnet-only/userif.c:46:

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompilePtr ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2558:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

  MAKE_ATOMIC_TYPE (Ptr, 64, void const *, void *, uintptr_t)

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h: in function 'AtomicAssertOnCompileInt ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2397:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused];             \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_atomic.h:2562:1: Note: the expansion of the macro 'MAKE_ATOMIC_TYPE '.

  MAKE_ATOMIC_TYPE (Int, 32, int, int, int)

  ^

  In file included from tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:31:0,

  of tmp/modconfig-DQkPL0/vmnet-only/vnet.h:29.

  of tmp/modconfig-DQkPL0/vmnet-only/vnetInt.h:24.

  from /tmp/modconfig-DQkPL0/vmnet-only/userif.c:46:

  /tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h: in function 'MonitorActionSet_AtomicInclude ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/monitorAction_exported.h:91:4: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

  ASSERT_ON_COMPILE ((ACTION_WORD_SIZE & (ACTION_WORD_SIZE-1)) == 0);

  ^

  make [2]: * [/ tmp/modconfig-DQkPL0/vmnet-only/hub.o] Fehler 1

  /tmp/modconfig-DQkPL0/vmnet-only/userif.c: in function 'VNetUserIfIoctl ':

  /tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/userif.c:810:7: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

  ASSERT_ON_COMPILE(VNET_NOTIFY_VERSION == 5);

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/vm_assert.h:320:20: WARNING: typedef "AssertOnCompileFailed" locally defined but not used [- Wunused - local-typedefs]

  typedef char AssertOnCompileFailed [AssertOnCompileMisused]; \

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/userif.c:811:7: Note: the expansion of the macro 'ASSERT_ON_COMPILE '.

  ASSERT_ON_COMPILE(ACTION_EXPORTED_VERSION == 2);

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/userif.c: in function 'VNetUserIf_Create ':

  /tmp/modconfig-DQkPL0/vmnet-only/userif.c:1049:34: error: dereferencing pointer to incomplete type

  userIf-> port.jack.procEntry-> read_proc = VNetUserIfProcRead;

  ^

  /tmp/modconfig-DQkPL0/vmnet-only/userif.c:1050:34: error: dereferencing pointer to incomplete type

  userIf-> port.jack.procEntry-> data = userIf.

  ^

  make [2]: * [/ tmp/modconfig-DQkPL0/vmnet-only/userif.o] Fehler 1

  make [1]: * [_module_/tmp/modconfig-DQkPL0/vmnet-only] error 2

  make [1]: Verlasse Verzeichnis ' / usr/src/linux-headers-3.10.0-6-generic'

  make: * [vmnet.ko] Fehler 2

  make: Verlasse Verzeichnis "/ tmp/modconfig-DQkPL0/vmnet-only.

  Vmnet failed.  Cannot run the command build.

  Using 2.6.x kernel build system.

  do: go in Verzeichnis "/ tmp/modconfig-DQkPL0/vmblock-only.

  / usr/bin/make /lib/modules/3.10.0-6-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Betrete Verzeichnis ' / usr/src/linux-headers-3.10.0-6-generic'

  CC [M] /tmp/modconfig-DQkPL0/vmblock-only/linux/block.o

  CC [M] /tmp/modconfig-DQkPL0/vmblock-only/linux/control.o

  CC [M] /tmp/modconfig-DQkPL0/vmblock-only/linux/dentry.o

  CC [M] /tmp/modconfig-DQkPL0/vmblock-only/linux/file.o

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/dentry.c:38:4: warning: initialization of the [default] incompatible pointer type

  .d_revalidate = DentryOpRevalidate,

  ^

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/dentry.c:38:4: WARNING: (near initialization for 'LinkDentryOps.d_revalidate') [default]

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/dentry.c: in function 'DentryOpRevalidate ':

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/dentry.c:104:7: warning: argument passing 2 of 'actualDentry-> d_op-> d_revalidate' makes whole pointer without a [default] casting

  return actualDentry - > d_op-> d_revalidate (actualDentry, nd);

  ^

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/dentry.c:104:7: Note: expected 'unsigned int' but argument is of type ' struct nameidata *'

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c: in function 'SetupProcDevice ':

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c:211:4: error: implicit declaration of function 'create_proc_entry' [-Werror-implicit-function-declaration =]

  controlProcEntry = create_proc_entry (VMBLOCK_CONTROL_DEVNAME,

  ^

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c:211:21: warning: assignment makes pointer from integer without a cast [default]

  controlProcEntry = create_proc_entry (VMBLOCK_CONTROL_DEVNAME,

  ^

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c:221:20: error: dereferencing pointer to incomplete type

  controlProcEntry-> proc_fops = & ControlFileOps;

  ^

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c: in function 'ExecuteBlockOp ':

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c:285:9: warning: [default] incompatible pointer type assignment

  name = getname (buf);

  ^

  /tmp/modconfig-DQkPL0/vmblock-only/Linux/control.c:296:4: warning: passing argument 1 of the [default] incompatible pointer type "putname"

  putname (Name);

  ^

  In file included from include/linux/proc_fs.h:8:0,

  from /tmp/modconfig-DQkPL0/vmblock-only/linux/control.c:28:

  include/Linux/FS.h:2055:13: Note: expected ' struct filename *' but argument is of type ' char *'

  extern void putname (struct filename * name);

  ^

  Cc1: some warnings are treated as errors

  make [2]: * [/ tmp/modconfig-DQkPL0/vmblock-only/linux/control.o] Fehler 1

  make [2]: * Warte auf noch nicht processes going...

  make [1]: * [_module_/tmp/modconfig DQkPL0/vmblock-only] error 2

  make [1]: Verlasse Verzeichnis ' / usr/src/linux-headers-3.10.0-6-generic'

  make: * [vmblock.ko] Fehler 2

  make: Verlasse Verzeichnis "/ tmp/modconfig-DQkPL0/vmblock-only.

  Vmblock failed.  Cannot run the command build.

  I hope that the core 3.10 will be supported with the next version of bundle.

  Greetings

  Thilo

  There is a patch for VMWare WS 9.0.2 to play nice with 3.10 kernel here:

  https://wiki.archlinux.org/index.php/VMware#3.10_kernels

  Or you can wait for VMWare WS 10.0 out...

• VMware Workstation 7. Machine.The virtual Windows XP file specified is not a virtual disk

  Hi all, thank you in advance for your help and sorry for my English.

  I was normally using Workstation on a Win7 system, emulating a Windows XP system. Now I try to turn on the machine and the following message appears:

  "The specified file is not a virtual disk.

  I reviewed the logs, the file .vmx and I can't find the error. I think that VMware can recognize the virtual drive as a SCSI unit.

  The files in the directory of virtual disk:

  VMware.log

  VMware - 0.log

  VMware - 1.log

  VMware - 2.log

  Windows XP Professional.nvram

  Windows XP Professional.vmdk (10 GB file)

  Windows XP Professional.vmsd

  Windows XP Professional.vmx

  Windows XP Professional.vmxf

  Tie newspapers, the .vmx file and a screenshot of the machine.

  Thanks again for your help

  As I have not examined the content of the hard I cannot give you a definitive answer but I'll tell you that, with the obvious corruption, shown in the first two sectors of the disk recovery at this stage, it is necessary advanced if it is not very advanced and can also be extremely laborious to get you in very advanced techniques.  The problem is that I don't have time to explain, and or to teach someone how to do what else can be right now because it was not learned and understood all night and just can not be easily passed along.

  Suffice to say if you did not good backups along the way, while it may have been a hard lesson learned I bet that in the future do you good backups from that point forward to easily recover when something bad happens new!

• VMware Workstation 7 - comments cannot connect to the host computer

  My problem is compounded by the fact that I've upgraded to VMware 7 and added several virtual Win7 64 virtual machines at the same time so I don't know what (or who) is causing the problem.

  I have 2 host computers running Windows XP 64 and VMware 7.  Firewall is turned off on all real and virtual computers and antivirus software disabled to facilitate debugging.

  I can 'see' host an extra to my network of machines, but I can't connect any virtual machine (Win XP 64 or Windows 7 64) to the drives or folders in a. host Virtual Machines of all the flavors to host B (as can host B himself) can connect to drives and folders in host A or B computers.

  I'm really confused, because it is a new problem in a network that worked without problem for a long time.

  Thank you

  k

  kriemer wrote:

  Scissor

  I was using AVG Anti-virus v8.5.  I uninstalled since then to try to resolve the problem.

  AVG should be ok.  Other AV problems even if 'disabled '.

  I'll try to disable settings NIC "unloading" next Monday (it's my wifes computer and I'm sure you can guess the rest).

  Not to be pedantic, but you mention that it would be temporary disabling.  What happens if this does not resolve the problem, what I won't give in now the settings?

  Give you up to a tiny fraction of one percent of time processor, because your host CPU would be checksums compensable package instead of the card NETWORK adapter.  Any difference would be unnoticable on a modern desktop computer.

  If a new NETWORK adapter driver becomes available, you can always try which allows once again to see if the new driver fixes it.  Even if a newer version of the workstation out.

• Portege R700 with Windows 7 64-bit: Windows Explorer fails to update

  It happens regularly after using my laptop for a while (1 hour more?) that Windows Explorer is no longer refreshes one of its windows. EG., delete a file and it is always displayed and disappears only after pressing the refresh (F5) button.

  Anyone who has had this experience, knows the problem, may suggest a solution (with the exception of maintenance by pressing F5 and possibly restart in frustration, which helps during some time)?

  It's very strange. I tested it on my Win7 64 bit-Satellite P500. I ve open two windows explore with in the same place, so I got the same content in both entities. When I delete a file or folder in the left window the right showed immediately that certain document has disappeared.

  I m really surprised that describes the problem may occur.
  Are you using the original OS that you got with your laptop?

• VMware Workstation 6.5.3 IntelCore2Quad Q8200 + XPx64 host cannot create x 64 guests

  I checked the BIOS: VT enabled. I checked the operating system: XP pro x 64 sp2 (5.2.3790). I checked VMware: version 6.5.3 - 185404, license to use OK.  I use a processor Intel Core2Quad Q8200 with 4 GB of Ram.

  Whenever I try to create a virtual machine based on a x 64 OS iso file, I get the message "64-bit operating systems are not supported by this host and will not work."

  Any idea?

  VT - x is needed to support 64-bit client on systems Intel (see 1901 KB).   The Q8200 does not support VT - x (see http://processorfinder.intel.com/details.aspx?sSpec=SLB5M).

• VMWare Workstation stops in the middle of the night without user interaction

  Hello

  We conduct the following problem:

  We have a Windows Server 2008 hosting two Windows XP virtual machines using VMWare Workstation 7.0.1. Every few days/weeks, we find the host that is running but VMWare Workstation closed without error message either. I checked the log of the virtual machine and here is the interesting part. What can trigger such behavior?

  03:17:02.995 12 August: vmx | VMXVmdbCbVmVmxExecState: Change of State Exec asked the State suspended without reset, hard.

  03:17:02.997 12 August: vmx | CPT current = 0, asking 1

  03:17:02.997 12 August: vcpu-0 | Fact Sync monModules (1).

  03:17:02.997 12 August: vcpu-0 | CPT: monitor build mode 1

  03:17:03.737 12 August: vmx | CPT current = 1, asking 2

  03:17:03.737 12 August: vcpu-0 | CPT: generate 2 monitor mode

  03:17:03.737 12 August: vmx | CPT current = 2, asking 3

  03:17:03.765 12 August: vcpu-0 | Fact monModules (3) CPT.

  03:17:03.765 12 August: vcpu-0 | CPT: build mode monitor 3

  03:17:03.767 12 August: vmx | Progress - 1% (msg.checkpoint.saveStatus)

  03:17:03.767 12 August: vmx | Controlled in VMware Workstation 7.0.1 build 227600, Windows host

  03:17:03.785 12 August: vmx | BusMemSample: initPercent 3 75 hit 42106 checkpoint

  03:17:03.787 12 August: vmx | MM: Renamed E:\Virtual Machines\VM-DEVGW10G\564d914f-6520-6161-6d40-f23fec40dc4c.vmem.\VM-DEVGW10G.vmem

  03:17:03.787 12 August: vmx | 0% (none)

  03:17:03.787 12 August: vmx | Progress 1% (none)

  03:17:03.790 12 August: vmx | Progress of 2% (none)

  03:17:03.790 12 August: vmx | Progress of 3% (none)

  03:17:03.790 12 August: vmx | Increased by 4% (none)

  03:17:03.792 12 August: vmx | Progress of 5% (none)

  03:17:03.792 12 August: vmx | Increased by 6% (none)

  03:17:03.792 12 August: vmx | Advance of 7% (none)

  03:17:03.792 12 August: vmx | Progress of 8% (none)

  03:17:03.795 12 August: vmx | Progress of 9% (none)

  03:17:03.795 12 August: vmx | Progress of 10% (no)

  03:17:03.795 12 August: vmx | Increased by 11% (none)

  03:17:03.797 12 August: vmx | Progress of 12% (none)

  03:17:03.797 12 August: vmx | Progress of 13% (none)

  03:17:03.797 12 August: vmx | Progress of 14% (none)

  03:17:03.800 12 August: vmx | Progress of 15% (none)

  03:17:03.800 12 August: vmx | Progress of 16% (none)

  03:17:03.800 12 August: vmx | Progress of 17% (none)

  03:17:03.802 12 August: vmx | Progress of 18% (none)

  03:17:03.802 12 August: vmx | Progress of 19% (none)

  03:17:03.802 12 August: vmx | Advance of 20% (none)

  03:17:03.805 12 August: vmx | Progress of 21% (none)

  03:17:03.805 12 August: vmx | Progress of 22% (none)

  03:17:03.805 12 August: vmx | Progress of 23% (none)

  03:17:03.807 12 August: vmx | 24% (none)

  03:17:03.807 12 August: vmx | Progress of 25% (none)

  03:17:03.807 12 August: vmx | Increased by 26% (none)

  03:17:03.810 12 August: vmx | Progress of 27% (none)

  03:17:03.810 12 August: vmx | Progress of 28% (none)

  03:17:03.810 12 August: vmx | Advance of 29% (none)

  03:17:03.812 12 August: vmx | Advance of 30% (none)

  03:17:03.812 12 August: vmx | Rise by 31% (none)

  03:17:03.815 12 August: vmx | 32% (none)

  03:17:03.815 12 August: vmx | Progress of 33% (none)

  03:17:03.817 12 August: vmx | Advance of 34% (none)

  03:17:03.817 12 August: vmx | 35% (none)

  03:17:03.820 12 August: vmx | Increased by 36% (none)

  03:17:03.820 12 August: vmx | Progress of 37% (none)

  03:17:03.822 12 August: vmx | 38% (none)

  03:17:03.822 12 August: vmx | Progress of 39% (none)

  03:17:03.825 12 August: vmx | Progress of 40% (none)

  03:17:03.825 12 August: vmx | 41% (none)

  03:17:03.825 12 August: vmx | 42% (none)

  03:17:03.827 12 August: vmx | 43% (none)

  03:17:03.827 12 August: vmx | 44% (none)

  03:17:03.827 12 August: vmx | Progress of 45% (none)

  03:17:03.830 12 August: vmx | 46% (none)

  03:17:03.830 12 August: vmx | 47% (none)

  03:17:03.832 12 August: vmx | 48% (none)

  03:17:03.832 12 August: vmx | 49% (none)

  03:17:03.832 12 August: vmx | Advance of 50% (none)

  03:17:03.835 12 August: vmx | 51% (none)

  03:17:03.835 12 August: vmx | Progress of 52% (none)

  03:17:03.837 12 August: vmx | Progress of 53% (none)

  03:17:03.837 12 August: vmx | 54% (none)

  03:17:03.837 12 August: vmx | Progress of 55% (none)

  03:17:03.840 12 August: vmx | 56% (none)

  03:17:03.840 12 August: vmx | Progress of 57% (none)

  03:17:03.842 12 August: vmx | Progress of 58% (none)

  03:17:03.842 12 August: vmx | 59% (none)

  03:17:03.842 12 August: vmx | Advance of 60% (none)

  03:17:03.845 12 August: vmx | 61% (none)

  03:17:03.845 12 August: vmx | Progress of 62% (none)

  03:17:03.847 12 August: vmx | 63% (none)

  03:17:03.847 12 August: vmx | 64% (none)

  03:17:03.850 12 August: vmx | 65% (no)

  03:17:03.850 12 August: vmx | Progress of 66% (none)

  03:17:03.850 12 August: vmx | 67% (none)

  03:17:03.852 12 August: vmx | 68% (none)

  03:17:03.852 12 August: vmx | 69% (none)

  03:17:03.855 12 August: vmx | Progress of 70% (none)

  03:17:03.855 12 August: vmx | 71% (none)

  03:17:03.857 12 August: vmx | 72% (none)

  03:17:03.857 12 August: vmx | 73% (none)

  03:17:03.857 12 August: vmx | 74% (none)

  03:17:03.860 12 August: vmx | Progress of 75% (none)

  03:17:03.860 12 August: vmx | 76% (none)

  03:17:03.862 12 August: vmx | 77% (none)

  03:17:03.862 12 August: vmx | 78% (none)

  03:17:03.862 12 August: vmx | 79% (none)

  03:17:03.865 12 August: vmx | 80% (none)

  03:17:03.865 12 August: vmx | 81% (none)

  03:17:03.865 12 August: vmx | 82% (none)

  03:17:03.867 12 August: vmx | 83% (none)

  03:17:03.867 12 August: vmx | Progress of 84% (none)

  03:17:03.867 12 August: vmx | 85% (none)

  03:17:03.870 12 August: vmx | 86% (none)

  03:17:03.870 12 August: vmx | 87% (none)

  03:17:03.870 12 August: vmx | 88% (none)

  03:17:04.085 12 August: vmx | GuestRpc: Reset of channel 0 (toolbox)

  03:17:04.085 12 August: vmx | GuestMsg: Channel 0, can't unpost because the previous post is already completed

  03:17:04.085 12 August: vmx | GuestRpc: Channel 0 reset.

  03:17:04.085 12 August: vmx | GuestRpc: Reset the 3(toolbox-dnd) channels

  03:17:04.085 12 August: vmx | GuestMsg: Channel 3, cannot unpost because the previous post is already completed

  03:17:04.085 12 August: vmx | GuestRpc: Channel reset 3.

  03:17:04.132 12 August: vmx | Progress at 89% (none)

  03:17:04.152 12 August: vmx | 90% (none)

  03:17:04.172 12 August: vmx | 91% (none)

  03:17:04.190 12 August: vmx | 92% (none)

  03:17:04.212 12 August: vmx | 93% (none)

  03:17:04.235 12 August: vmx | 94% (none)

  03:17:04.257 12 August: vmx | 95% (none)

  03:17:04.280 12 August: vmx | 96% (none)

  03:17:04.300 12 August: vmx | Progress of 97% (none)

  03:17:04.317 12 August: vmx | 98% (none)

  03:17:04.335 12 August: vmx | Progress of 99% (none)

  03:17:04.365 12 August: vmx | 100% (no)

  03:17:04.452 12 August: vmx | Progress of 101% (none)

  03:17:04.490 12 August: vmx | VIX: : VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1875, success = 1

  03:17:04.490 12 August: vmx | VIX: : VMAutomation: ignoring ReportPowerOpFinished because the VMX stops.

  03:17:04.737 12 August: vmx | Stopping VCPU threads...

  03:17:06.490 12 August: mks | End MKSRole pseudocalls, the State was 1

  03:17:06.490 12 August: mks | MKSHostOps_Exit3D: 1: 0

  03:17:06.490 12 August: mks | Fate of MKS Async thread

  03:17:06.490 12 August: vmx | VIX: [2684 mainDispatch.c:915]: VMAutomation_PowerOff: power off the power.

  03:17:06.602 12 August: vmx | Application of TOOLS received in VMX to set the 'enableDnD' option - & gt; '0'

  03:17:06.602 12 August: vmx | Application of TOOLS received in VMX to set the option "copypaste" - & gt; '0'

  03:17:06.602 12 August: vmx | Application of TOOLS received in VMX to set the option "copypaste" - & gt; '0'

  I know that this is perhaps a very obvious thing to check, but sometimes, they are the most neglected

  The server reboots after updates windows for example? or is there no idea in the windows event log to moor with vmware logs?

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Windows 7 64-bit and VMWare Workstation

  Someone had problems with VMWare Workstation 6.5 on Windows 7 64-bit? My computer hangs when creating the virtual machine guests. I have VirtualBox running very stable with Windows 7. I was wondering if anyone has had problems? I think try VMWare Workstation 7.

  Yes, my Dell PC meets all the requirements. I enabled VT, 2-2CoreDuo 3.06 Ghz CPU, 8 GB of RAM, 1 TB SATA, Windows 7 64-bit.

  Your comments are welcome!

  Thank you

  EC

  Windows 7 as a host is not supported up to what VMware Workstation 7. You can run Windows 7 as a GUEST/VM under WS 6.5.3, but not as the host. You can use the guide to compatibility/guest conductor OS here: http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software to see for yourself...

  VMware VCP4

  Review the allocation of points for "useful" or "right" answers.

• How to install 64-bit vmware workstation 9 on a win 7 64-bit operating system

  I am trying to load the 64-bit version of the workstation 9 on a 64-bit windows system 7.

  I down loaded the bundle (VMware-workstation-full-version 9.0.0 - 812388.exe) that has the 64-bit and 32-bit.  When I run the Setup, it puts

  C:\Programs(x86 folder) that I am under the impression is for 32-bit applications.

  I have two questions

  (1) how to determine which version of workstation (64 or 32) I loaded?

  (2) if it is 32, how a force installing 64-bit?

  VMware Workstation is the two 32-bit 64 bit.  On 64-bit host, it uses a 64-bit vmware-vmx with it process the lats and the Virtual Machine itself, but the front-end GUI is 32-bit.

• 64-bit in ESXi running in Vmware Workstation machines

  Hi all

  I have a Lenovo Thinkpad W510 with an i7 processor.

  I have Windows 7 Enterprise 64-bit as OS for my vmware Workstation 7.1.3 (64-bit), I install ESXi 4.1 as a virtual machine in my machine and now start importing the VM since my ESX datacenter (you want to use what I already create in data centre infrastruture in my laptop)

  I was very surprised, inside my ESXi 4.1 it says when I try to start a Windows Server 2008 R2 or trying to create an image of the installation CD to:

  msg.cpuid.noLongmodeQuestionFmt: this Machine vistual is configured for 64-bit systems Nailer quest. However, exploitation of 64-bit is not possible. This host does not support VT for more information, see http://vmware.com/info?id=152. Continue support 64 - bit wihout?

  Any thing I can change or change to make it work?

  Thank you

  Paulo

  You can't execute nested invited 64bits.  Autoprogramming comments any64bit hardware assisted virtualization must be enabled (VT-x/AMD-v). When you run ESX (i) as a guest, it is not possible to passdown technology.

  In conclusion, you can run 32-bit clients nested

• What version of Windows host running better on VMWare Workstation 32 or 64?

  Hello

  IM planning to install VMWare Workstation and I want to hear what you guys have to say on what host Windows works better under VMWare Workstation platform.

  Will install Windows on Macbook Pro C2D 4 GB operating system.

  KR,

  Cristiano Botelho

  on a 4 Gb machine 32-bit and 64-bit systems probably all detect 3.x GB RAM just so you can use a good 32-bit or a 64-bit system.

  My first choice staff would be 2003 32-bit, but you will be here other recommendations as well.

  This question usually results in contradictory answers... you have been warned

  whatever you do - do NOT use any taste of Vista

  ___________________________________

  VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

• installation of vmware workstation 6.5 on windows 10 error

  After you install vmware workstation 6.5 on windows 10 it gets error and restart. Is vmware workstation 6.5 support windows 10? FAILED TO INSTALL. vmware workstation 6.5 on windows 8, 8.1 and 10 support. ALL SUPPORT. I still don't understand...

  VMware Workstation 6.x do not support Windows 10 and will never support Windows 10.

  VMware Workstation 6.x reached "end of support" four years, October 1, 2011: Matrix.pdf product lifecycle

  We produce updates for release until its date of "end of support".  A product may not work properly with host OSes, processors or comments OSes that are not compatible with the product, especially the things that have been published after the date of "end of support".  We put a huge amount of effort to ensure that new hardware and operating systems works with each new major release of VMware Workstation, but we cannot go back and update any previous version of product to add support for all hardware and operating systems more recent.  If we tried to do this, VMware Workstation cost much more that it is today, simply because of the amount of work required to maintain!

  You need to upgrade your installation of VMware Workstation to something more recent, or downgrade your host operating system to a version compatible with VMware Workstation 6.5.

  I hope this helps!

  --

  Darius