Similar Questions

• ESXi 5.0 boot partition size

  What is the size of storage recommended for installing ESXi 5.0?

  I recommend you do at least 6 GB (I usually use 10GB). Depends on how the systems of storage performer GBs (1 GB = 1,000 * 1,000 KB or 1,024 * 1,024 kb) 5 GB may not be enough.

  André

  EDIT: fixed the calculation for 1 GB

• Solaris VM is not running on ESX4.0 after the conversion of VMware workstation 6.5

  I have created Solaris VM on VMware workstation 6.5, but now I want to run it on ESX 4.0. After the conversion of Solaris VM from VMware workstation in format by converter 4.0.This VMware ESX VM restarts again and again on the boot of power.

  VMware workstation is running on Intel (R) Xeon (R) CPU E5420 and ESX 4 running on the Unisys ES3220L system

  Help, please...

  How was the original virtual controller?

  If it's IDE, you will need to also change SCSI to IDE on ESX 4.0.

  André

• CentOS 6: / boot partition to small with Easy Install

  Hello

  I installed CentOS 6 64-bit in a version of VMware Workstation 7.14 - 385536 on Windows 7 Enterprise 64-bit. If you are using Easy Install it came with a partition/boot to ~ 48MB where are only 8.3 MB of free space. Therefore, an update of the kernel fails with the error: '[...] 19 MB required. "This happends with the default size of the drive of 20 GB and when I changed it to 40 GB.

  If I do not use Easy Install the partition/Boot has the size of 500 MB (size disc 20 and 40 GB), which would be more than enough. Another difference is the use of lvm (logical volume management) when I use the manual installation and the lack of it with Easy Install.

  Is it possible to change the partition scheme when you use Easy Install?

  Kind regards

  Andreas

  Easy install creates a custom Kickstart configuration file the autoinst.iso file created in the folder of in that the Virtual Machine is created and you must change the following setting in the KS. CFG file.

  part /boot --size 50
  

  Should extract the KS. The autoinst.iso file, change the setting and the injection of the edited KS, CFG folder. CFG file in file autoinst.iso before you begin the installation.  Or you are needs that this process can be script.

• VMware Workstation 10.0.1 and Windows 7 VM crash on CentOS 6.5 host

  Just upgraded to 6.5 CentOS 64-bit (2.6.32 - 431.el6.x86_64). After the updates and reboot I launched VMware Workstation 10.0.1 as I normally and began my OpenVPN (Wheezy Debian) VM with all the problems. I then started my Windows 7 64-bit VM and the entire army what OS hangs and I have to reboot using the reset button.

  I was able to reproduce twice in a row. The Windows 7 VM seems to start fine and then when I type my credentials in and it starts to load the office which is when everything goes south and the host completely freezes.

  The Windows 7 VM has nothing too complicated installed in it. Some Epson software to start uTorrent and printer in network at startup. Steam does as well, but it is not auto-login or do anything really.

  I just did some testing of synthetic load and covered all 8 cores (much more than the usual load) up to 24 GB, 32 GB of RAM and 50% of CPU on the host computer and things remained stable. I thought that a second question could be RAM related because after a soft on boot the Windows 7 VM running I am to about 7 GB of RAM used on the host computer and from the WIndows 7 VM would put me over 8 GB, which resembled a number of nice where things might go wrong If it is RAM related.

  Log files:

  kdump(1): https://Paste.Fizi.ca/?f5c7c3e6945f8ce4#hPoN0VUJbPKA07hbDPWuE1D0e9FC7Ss8RNvF5Qv7yy0=

  vmware - 0.log: https://Paste.Fizi.ca/?05d42cd929bb5237#Zgbtlm7R+bZEHEOs5uSyA6Xin6FOOflWYWvNnHnxksM=

  Any ideas?

  Looks like I need to learn how to use the forum search tool.

  It is a dupe of VMware Workstation - 10.0.1 fails after the software update from RedHat-6.

• VMware tools install fails - Centos 6.2 on VMware Workstation 8

  Some setting in context.

  ArcSight make an OVF vmware assessment based on Centos 6.2. I am able to install VMware tools on the ESXi 5.1 platform supported but NOT on VMware Workstation version 8.0.6 build 1035888 which is apparently not supported but works fine on my laptop.

  
  

  The big problem here is that the time on the host computer is massively adrift without VMware tools and make more from the point of the eval worthless SIEM.

  
  

  I'm sure it's a problem of script, but is not certain. When configuring VMware tools that occurs the following

  
  

  START INSTALLATION TEXT

  [root@logger bin]./vmware-config-tools.pl # ]

  Initializing...

  Ensuring services for VMware Tools are arrested.

  [EXPERIMENTAL] The synchronization of VMware filesystem (vmsync) driver is a new feature which

  creates backups of virtual machines. Please refer to the VMware Knowledge Base

  For more details on this ability. You want to enable this feature?

  [None]

  Before you can compile modules, you must have the following installed...

  do

  CCG

  headers of the kernel running kernel

  Looking for a CCG...

  The path "" is not a valid path to the GCC binary.

  You want to change it? [Yes]

  What is the location of the program CCG on your machine? CCG

  The path "/ usr/bin/gcc" is not a valid path to the GCC binary.

  You want to change it? [Yes]

  TEXT OF INSTALLATION END

  I played with the script Perl, but similar problems continue with the location of the kernel headers having precisely defined the variable PATH CCG.

  A few pieces of information of the host.

  [root@logger bin] # uname - m.

  2.6.32 - 220.EL6.x86_64 x86_64

  [root@logger bin] # gcc - v

  Using plug integrated.

  Target: x86_64-redhat-linux

  Configured with:... / configure - prefix = / usr - mandir = / usr/share/man - infodir = / usr/share/info-with-bugurl = http://Bugzilla.redhat.com/Bugzilla --enable-bootstrap--enable-shared--enable-threads = posix--enable-vérification = libération--with-système-zlib--enable-__cxa_atexit--disable-libunwind-exceptions--enable-gnu-unique-objet--enable-langues = c, c ++, objc, obj-c + +, java, fortran, ada--enable-java-awt = gtk--disable-dssi--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre--enable-libgcj-multifile--enable-java-maintainer-mode--with-ecj-jar=/usr/share/java/eclipse-ecj.jar--disable-libjava-multilib--avec-ppl--avec-cloog--avec-tune = generic--avec arch_32 = i686--build = x86_64-redhat-linux

  Thread model: posix

  GCC version 4.4.6 20110731 (Red Hat 4.4.6 - 3) (CCG)

  [root@logger bin] # / usr/bin/make - v

  GNU Make 3.81

  Copyright (C) 2006 Free Software Foundation, Inc.

  This is free software; See the source for copying conditions.

  There is NO WARRANTY; not even a MARKET value or fitness for a

  PARTICULAR PURPOSE.

  This program built for x86_64-unknown-linux-gnu

  [root@logger bin] # / usr/bin/make - v

  GNU Make 3.81

  Copyright (C) 2006 Free Software Foundation, Inc.

  This is free software; See the source for copying conditions.

  There is NO WARRANTY; not even a MARKET value or fitness for a

  PARTICULAR PURPOSE.

  This program built for x86_64-unknown-linux-gnu

  [root@logger bin] #

  
  

  Thank you in advance. Kevin
  

  I solved this problem by upgrading VM Workstation v10 v8.

  All installed now.

  As a newbie here, is there a way I can move this post a status resolved?

• VMware Workstation 12.1.1 Pro is unable to install the network grows on CentOS 6.8 host

  Just upgraded my 6.7 CentOS Server (where the VMware Workstation 12.1.1 worked fine) to 6.8.

  After a reboot, VMware has done, it is usual thing where she wanted to reinstall its readers. He doesn't have to install the network component. Here are my logs:

  2016-05-28T18:21:09.477-07:00| vthread-4| I125: Log for VMware Workstation pid=27658 version=12.1.1 build=build-3770994 option=Release
  2016-05-28T18:21:09.477-07:00| vthread-4| I125: The process is 64-bit.
  2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8
  2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host is Linux 2.6.32-642.el6.x86_64 CentOS release 6.8 (Final)
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/home/sa_schewee/.vmware/config": No such file or directory.
  2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /home/sa_schewee/.vmware/config. Using default values.
  2016-05-28T18:21:09.501-07:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-27658.log
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Obtaining info using the running kernel.
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Created new pathsHash.
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.511-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.518-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.518-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.587-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
  2016-05-28T18:21:09.587-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Read 12201 symbol versions
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmmon module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmnet module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmblock module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmci module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vsock module.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Setting vsock to depend on vmci.
  2016-05-28T18:21:09.597-07:00| vthread-4| I125: Invoking modinfo on "vmmon".
  2016-05-28T18:21:09.600-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.600-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
  2016-05-28T18:21:09.601-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
  2016-05-28T18:21:09.601-07:00| vthread-4| I125: Invoking modinfo on "vmblock".
  2016-05-28T18:21:09.603-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.603-07:00| vthread-4| I125: Invoking modinfo on "vmci".
  2016-05-28T18:21:09.605-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.605-07:00| vthread-4| I125: Invoking modinfo on "vsock".
  2016-05-28T18:21:09.607-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
  2016-05-28T18:21:09.618-07:00| vthread-4| I125: to be installed: vmnet status: 0
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Obtaining info using the running kernel.
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.624-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.632-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.632-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.701-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
  2016-05-28T18:21:09.702-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Read 12201 symbol versions
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/2.6.32-642.el6.x86_64/build/include
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Update kernel header path to /lib/modules/2.6.32-642.el6.x86_64/build/include
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.711-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.719-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.719-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.720-07:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"
  2016-05-28T18:21:09.724-07:00| vthread-4| I125: Got gcc version "4.4.7".
  2016-05-28T18:21:09.724-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.724-07:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".
  2016-05-28T18:21:09.727-07:00| vthread-4| I125: Got gcc version "4.4.7".
  2016-05-28T18:21:09.727-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: No matching PBM set was found for kernel "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.729-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.737-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.737-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.738-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.746-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.746-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.746-07:00| vthread-4| I125: Using temp dir "/tmp".
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Obtaining info using the running kernel.
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
  2016-05-28T18:21:09.747-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
  2016-05-28T18:21:09.755-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
  2016-05-28T18:21:09.755-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
  2016-05-28T18:21:09.825-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
  2016-05-28T18:21:09.825-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
  2016-05-28T18:21:09.834-07:00| vthread-4| I125: Read 12201 symbol versions
  2016-05-28T18:21:09.834-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
  2016-05-28T18:21:09.836-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
  2016-05-28T18:21:10.081-07:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/2.6.32-642.el6.x86_64/misc/vmnet.ko".
  2016-05-28T18:21:10.081-07:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
  2016-05-28T18:21:10.087-07:00| vthread-4| I125: Successfully extracted the vmnet source.
  2016-05-28T18:21:10.087-07:00| vthread-4| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-tH7bci/vmnet-only auto-build HEADER_DIR=/lib/modules/2.6.32-642.el6.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
  2016-05-28T18:21:11.063-07:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.
  
  
  

  Hi, I faced the same problem, and now I have corrected this issue.

  He was vmnet.ko, at least for me.

  Here's how to solve,

  You can find the latest vmnet.ko of /lib/modules/~previous_kernel_version~/misc/vmnet.ko

  Copy vmnet.ko into your current/lib/modules/your_current_version/misc folder.

  And then run vmware, if you fail at the first, please run again.

  If so, you can run vmwre!

  I hope this will help you.

  Good day.

• Core upgraded to 4.0 on Centos 7 VMWare Workstation 11 won't build the virtual network device

  As shown in the topic, I have manually compiled kernel 4.0 for my installation of CentOS 7. After the installation of the kernel (in rpm mode, followed the instructions here: How to compile a Kernel - The Way CentOS ) installed all 3 rpm, kernel, kernel-headers and kernel-devel and then tried to start my installation of workstation with it leads to having to re - build the components (as usual)

  It does not, when it came to the compilation of the network management module. See attached log file that it generated.

  I also tried to uninstall, downloaded VMware-Workstation-Full - 11.1.0 - 2496824.x86_64.bundle and re-installed with the same result.

  Any help would be appreciated!

  aaand..., I fixed my only problem!

  Credit:

  https://wiki.archlinux.org/index.php/VMware

  just applied the 3.19 patch and He-voila!

• Problem with VMWare Workstation combo, .vhd virtual drives and physical disks in the sector of size 4K?

  All,

  I suspect something wrong with some of my virtual machines.  I have been using these virtual machines for a while, and I see some weird behaviour recently.

  I see a lot of corruption in the virtual hard disk (.vhd based).  CHKDSK automatically gets performed many large files such as Oracle datafiles get damaged etc...  It all seems quite random and inconsistent, but I am using .vhd virtual machines in VMWare Workstation for years without problem.  This problem is new, and hard drives are basically unstable.

  I * think * (and I'm totally off base) that is perhaps the issue with my new external hard drives.  These discs have a 4 KB sector size, without e512.  Thanks to this architecture of hard drive, don't mount not the tools of Microsoft or manupulate .vhd files on these disks.  The questions seem to go away if I switch to vmdk or switch to the physical hard disk size-one-sector 512kb.  Because errors are not compliant, that I don't really have a way to document/prove that is the case, but it seems to be.

  I use version 9.0.0 on Windows 7 Workstation, and the guest is Windows Server 2008R2.

  My question is:

  (1) what meaning?

  (2) how I prove/document, since it is a contradiction?

  (3) is this a known problem?

  (Btw, switching HDD's vmdk is not an option in our case due to an obscure legal agreement with Microsoft.  I have to distribute my VMs in vhd format, even if they are designed to run on VMWare...)

  -> Adam

  These discs have a 4 KB sector size, without e512.

  (I've highlighted "without e512" in "BOLD" to key in my answer to the host operating system.)

  -L'OS is Windows 7 Enterprise

  According to the political support for the 4 K sector hard drives in Windows, Windows 7 does not support the native 4 K (logical 4 k sector size) but it does not support Advanced Format or 512th (size of logical sector physical and 512 bytes of 4 K) and that is can be the question.

• VMware Workstation BIOS 9 - cannot change the boot sequence

  I have a Windows 2003 server that has almost zero space on the C drive, so I'm trying to start a utility disk so I can I repartition.

  HOWEVER... F12 not letting me NOT select a different boot device. If I go into the BIOS and go to the start menu, I see the hard disk and not the CD is at the top of the list and there is no way to change the boot order. Up, down and '+' and '-' keys don't do. The machine is a version that compatible with 6-7, but I shouldn't have to level 9 (I think, anyway).

  The boots of the virtual machine so fast but after that everything a 100 attempts I can't else primary hard drive to boot first.

  TIA

  Kevin

  With VMware Workstation (or at least tab of the virtual machine) closed, add

  bios.bootDelay = "5000".

  to the virtual machine's .vmx file. This will add a 5 second delay for the startup process that will allow you to hit the "ESC" key to the start menu and to attach an ISO or CD image to the virtual machine. Make sure that the virtual CD-ROM presents itself as 'Connected' before proceeding with the selection of the boot device.

  André

• VMware Workstation is unable to open one of the virtual disks required by this virtual machine because it is larger than the maximum file size supported by the host file system.

  I'm transitioning from Windows XP (64-bit) on a new computer with Windows 7 installed.  I undertook to VMWare Workstation 6 7.0.1 in the process.  The problem is with a very large RAID 5 volume on the new system.  It's a score of 5.45 TB (TPG and NTFS).

  When I try to start a virtual machine on this volume, I get the message "VMware Workstation cannot open one of the virtual disks required by this virtual machine because it is larger than the maximum size of the files supported by the host file system.".  This is obviously not true.  If I copy the virtual machine to another drive on the system, it starts without a problem.

  Anyone have any ideas on how to work around this problem?

  try to add this line in the vmx file:

  diskLib.sparseMaxFileSizeCheck = "false".

  Maybe it helps.

  VMDK-type do you use?

  monolithicSparse? -C' is the only part type more?

  ___________________________________

  VMX-settings- Workstation FAQ -[MOA-liveCD | http://sanbarrow.com/moa241.html]- VM-infirmary

• Unable to Boot PXE under VMWare Workstation

  Note: This is a LABORATORY environment!

  I have 2 servers

  SRV1 - DHCP, ADDS

  SRV2 - WDS

  Both are installed in VMWare Workstation 12 and is assigned to a Segment named "Server LAN" local network.

  I have 2 Workstation

  WKS1 - no BONES and Belonged to a local Network Segment named "LAN Workstation"

  WKS2 - with OS (Win8) and Belonged to a local Network Segment named "LAN Workstation"

  1 Virtual router connected both the Segment of LAN 'Server LAN' and 'LAN workstation.

  Virtual router is configufed for transfer/DHCP relay.

  I can say that the DHCP relay works because WKS2 can get an ip address from the SRV1 when starting Windows 8. However, WKS1 and WKS2 in PXE startup I get this message.
  

  Any ideas?

  I solved the problem, it turns out that option 66 and 67 was not configured in my DHCP for the scope that has been maintaining the "LAN workstation.

  I have configured the DHCP in SRV1

  Option 66 for point on my WDS server.

  

  and Option 67 to point to the 64-bit version of wdsnbsp.com in the wds server.

  

• VMWare Workstation 6.5 Auto boot OS invited at startup?

  I'm under XP 64 bit on my host OS.

  I have 3 * nix OS in my VMWare Workstation 6.5 install, and I would love it if they could start automatically when the server restarts. Is this possible? Google is coming short.

  > Google is coming short.

  ? -you will find several instructions on how to run a virtual machine as a service provider in google.

  What all simply create a batch that looks like this

  Start vmplayer.exe vm1.vmx

  Start vmplayer.exe vm2.vmx

  ...

  and put this batch in the startup of your user profile folder?

  ___________________________________

  VMX-settings- VMware-liveCD - VM-infirmary

• Error: "VMware Workstation has suspended this virtual machine because the disk on which the virtual machine is stored is almost full."

  I get this error message:

  VMware Workstation has suspended this virtual machine because the disk on which the virtual machine is stored is almost full. To continue, free 1.3 GB of additional disk space.

  I read up on the subject and found that I have to re size a partition. Anyone know what it could be? I can't find anything that looks like it has something to do with VMware. Does anyone know what size and what file system is it?

  My OS:
  Tumbleweed OpenSUSE x 64

  Thanks in advance

  On more creative, my home and root file systems were not extended to my full disk space :^)

• VMware Workstation failed to mount the physical disk 10TB

  VMware workstation or any other product vmware does support more than 2 TB of physical disks?

  I am trying to connect a 5 of 10 TB raid enclosure and mount it on my ubuntu vmware workstation machine. The common error that I receive is when mounting the reader on ubuntu and I think it might have something to do with the size of the file.
  I am running vmware workstation 12 in windows 10.
  The disk is taken offline in windows and I'm under WS as an administrator.

  Error	VMDK CONTENT	DiskPart Info
  Operation failed on the file "\\.\PhysicalDrive1". If the file is located on a remote file system, make sure that the network connection and the server on which resides this disk to work correctly. If the file is saved on a removable medium, link media. Select Retry to retry the operation. Click Cancel to end this session. Select continue to pass the error to the guest operating system. I/o error, dev sdb, sector 11721553632 I/o error, dev sdb, sector 11721552128 I/o error detected. File system stop Please unmount the file system and to rectify the problem (s) metadata I/O error: block 0x2baa8b100 ("xlog_bwrite") error 5 numblks 8200 can not read the superblock	# Disk DescriptorFile version = 1 Encoding = "windows-1252". CID = 6f4a8bb1 parentCID = ffffffff isNativeSnapshot = 'no '. createType = "fullDevice." # Description of the measure RW 23441768448 DISH '\\.\PhysicalDrive1' 0 partitionUUID \\?\scsi#disk & ven_h #w & prod_raid5 #5 & 19bb575e & 0 & 010000 #{53f56307-b6bf-11d0-94f2-00a0c91efb8b} # The database disk #DDB ddb.adapterType = "free". ddb.geometry.biosCylinders = "1024". ddb.geometry.biosHeads = "255".

  ddb.geometry.biosSectors = "63".

  DDB. Geometry.Cylinders = "16383.

  DDB. Geometry.Heads = "16".

  DDB. Geometry.sectors = "63".

  ddb.longContentID = "55c8f3052c372c02465d66656f4a8bb1".

  DDB. UUID = "60 00 C2 97 8 a 7 c c2 cb - 9 a 27 51 78 58 a7 e6 3f"

  ddb.virtualHWVersion = "12".

  H/W RAID5

  Disc ID: 00000000

  Type: SATA

  Status: Offline (policy)

  Path: 1

  Target: 0

  LUN ID: 0

  Path: PCIROOT (0) #PCI (1C07) #PCI (0000) #ATA (C01T00L00)

  Current read-only State: No.

  Read-only: No.

  Boot disk: No.

  Disk swap file: No.

  Disk hibernation file: No.

  Crash dump disk: No.

  Cluster disk: No.

  The official version said that WS allows only virtual up to 8 TB of disk.

  According to my own tests, it only limits the size of the VMDK for 'New - VM' Assistant.
  Once you have a greater vmdk - just tried a vmdk 10TB - WS won't complain about the size.
  I don't expect that WS will prevent the physical disks to use inside a virtual machine that is already configured.
  So in your case I think you started WS with a normal user account.
  Try to start as administrator WS - maybe even using the administrator account.
  I think that then it will work.
  Unfortunately, the error messages produced by vmware.exe are not really accurate-, so there is no way to know if you really have a bad super block.
  To test if this is really the problem and not just an error message - poor try to mount the drive directly.
  Please post the vmdk - want to know if there is something unusual about 5.5 TB in the disk.