VMWare Workstation 6.5 Auto boot OS invited at startup?

Similar Questions

• VMware workstation 11 and Windows 10 build 9926 auto resizing does not

  Host: Windows 8.1 Pro x 64

  VMware: Workstation 11

  Client: Windows 10 Build 9926

  Problem I have is in the guest operating system (win 10).  I can not auto resize the guest to fit the window (now Vmware worksation, opinion, comments made.  It flashes on the full screen, then goes back to the resolution that it is.  I'm stuck at the Windows gives me resolutions.

  I know that this version comes out today.  But I thought I'd give you guys a heads up.

  THX.

  Build 10074 works!

  So, I did a clean install of the new generation (10074).  Workstation makes easy installation on it.  During the easy setup process, it didn't install VMWare tools, but I see the tools have been installed.  I tried to re-size that the screen with 3D powered acceleration; and it worked!

  This issue is finally resolved. !

• 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é

• 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 - PCI switch to OS to solve the lack of host riders invited

  Hi all

  I'm quite new to VMware applications.

  To implement PCI passthrough / directly access hardware PCI by the host OS

  is it possible to just use VMware Workstation? or VMware ESXi OS is necessary?

  In this case:

  -The machine physics processor and card motherboard BIOS supports virtualization.

  -The host OS is Windows 7 64 bit.

  -A PCI card is interrupted and got only Windows XP / Vista drivers (the two 32-bit).

  -VMware Worstation 8.0 running in the host operating system.

  -VM guest OS is Windows XP (32 bit).

  Can I somehow configure direct access to the virtual machine PCI card / guest OS?

  I think that would solve a lot of pilot uncompatibility between 32/64 bit OS versions;

  It would be useful to have work directly in the VMware workstation.

  Or is it now possible only with OS ESXi and is rather simple to use here?

  Thank you very much for the support.

  LD

  VMware Workstation isn't compatible PCI Passthrough, you must run ESX or another product to make it work.

  Linjo

• Help with restarting the laptop HP pavilion g6 auto blue screen after installing VMWare Workstation 7/8

  Hello, I have a HP Pavilion g6-1a52nr Notebook PC (running Windows 7 64 bit) which is in a reboot loop. This happened after I installed VMWare Workstation 7 (in the installation process there is no occurs.but error after installing that I try to reboot the machine, and then the following error has occurred).
  Now whenever the notebook starts up, it seems to be in a reboot loop after the windows logo then get a blue screen.
  When I connect to the system using vmware safemode also working.but in normal mode it displays a blue screen after logiin screen shows.

  By turning on the restart automatic system failure off I was able to read it as the Blue error message that says:
  -

  Signature of the problem:
  Problem event name: BlueScreen
  OS version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033

  More information about the problem:
  BCCode: 1000007e
  BCP1: FFFFFFFFC0000005
  BCP2: FFFFF88006EFF443
  BCP3: FFFFF88003399D68
  BCP4: FFFFF880033995C0
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 256_1

  Files helping to describe the problem:
  C:\Windows\Minidump\031212-28672-01.dmp
  C:\Users\user\AppData\Local\Temp\WER-62072-0.SysData.XML

  Read our privacy statement online:
  http://go.Microsoft.com/fwlink/?LinkId=104288 & clcid = 0 x 0409

  If the online privacy statement is not available, please read our offline privacy statement:
  C:\Windows\system32\en-US\erofflps.txt

  
  -
  Can someone give me advice on how to solve and prevent this problem?

  
  Thank you

  you have the HP-tools installed?
  They often conflict with VMware.
  Try disabling the startup of the HP-tools

• 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.

• Re: Satellite keyboard Funtions vs. VmWare Workstation

  Hello

  I'm new to this forum...
  I recently bought a Toshiba Satellite U500-115.
  After you install all the programs I need, I noticed that the eco and the start/stop button lights buttons didn t work anymore.

  I uninstalled programs Toshiba - nothing works. So I installed win 7 pro x 64 again.
  Buttons worked!!

  I discovered that vmware workstation 6 and 7 are at the origin of this problem.
  As soon as I install the vmworkstation software the keys won´t work.
  Uninstall--> buttons work.
  I don't want to use both: buttons and vmware 6 or 7.
  It seems to work with vmware 5.x, but this version of vmware is officially not recommended to work with win7. It takes about 10 minutes push button vmware initially until the vm ware starts booting.

  Perhaps someone could confirm this problem.
  Hope of a quick solution!
  Concerning
  bachmayeah

  Maybe it sounds pessimistic now, but I don't think you'll have a quick solution to this.
  The feature tools and utilities Toshiba is tested with the own operating system preinstalled and not with some third-party additional party software.
  Can you imagine how these applications you will find there? Who should test the functionality with hundreds of other application? It is certainly not possible.

  I use VmWare, but I imagine that there is a problem where two applications met the other.

  Sorry, but I don't think that there is nothing you can do about it.

• 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.

• 15 Ubuntu won't start in VMware workstation 12 after a recent update of Ubuntu

  I'm quite new to the environment virtual system and linux. Someone could me help on my question below?

  I have a virtual system installed using VMware workstation 12. It works fine, until the upgrade of Ubuntu this morning.

  I have no idea what the update installed.

  After the required reboot, Windows VMware has always stop a black page.

  Before everything, there were some posts that I think they should be useful to target the issue here.

  

  He said:

  SMbus host controller not activated!

  No valid rapl area found within the package 0

  Thank you very much for your help!

  -Ninggang

  I found a solution!

  There is problem of ubuntu, new kernel is bad and it's a bug.

  To start again just hold SHIFT while your machine virtual machine to the menu shows ubuntu boot.

  Select Advanced, then choose more old kernel version and that's all.

  After you restart your virtual machine it always start on black screen, you need to delete newes kernel version linux-headers - 4.2.0 - 30 to begin on the old version and problem SOLVED!

  remove the kernel:

  sudo apt-get remove linux-image-4.2.0-30-generic
sudo update-grub2

  reboot.

• 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.

• Update Windows 10 November (10586 aka 1511): bcdedit/set hypervisorlaunchtype off, but VMware Workstation does not start VMs with conflict of Hyper-V

  Hi all

  I upgraded from Windows 10 Windows 10 November updated this morning.

  I have the Hyper-V role is installed and use it from time to time, but bcdedit to configure the boot loader to disable Hyper-V by hypervisorlaunchtype power off.

  This technique has worked with 10 Windows and VMware Workstation and I could start and run virtual machines

  Since I did the upgrade, I can't start VM with this standard message "VMware Workstation and Hyper-V are not compatible"

  I am running VMware Workstation 10, but suspect that this problem also exists with later versions.

  Everyone knows about this problem?

  Someone at - he found a solution?

  I'm willing to fork over $150 for 12 workstations to solve this problem, but I want to know with certainty that it is circumventing my problem.

  Thanks for that.

  Uninstallation and reinstallation of the hyper-v feature, following the upgrade of Windows Windows 10 November 10 update solved the problem.

  I still need to run the following command to disable the Hyper-V technology

  bcdedit/set hypervisorlaunchtype

  Thanks to everyone for their help.

• Network bridge in VMware Workstation 11 connection problems

  I have bridged network connection problems in VMware Workstation 11. So far I have tried:

  
  

  Re: Windows Pro/Ent 8.1 Overview invited - stop Windows Net Performance, away from work

  
  

  Re: Flow very slow network-> Guest host, but no comments <-home

  
  

  So far, none of the solutions worked. I turned off "Large Send Offload" on each adapter that I could find on the host and the guest. Nothing. Restore these settings in any combination with other out does not work either. I edited the .vmx file and replace by vmxnet3 occurrences, and that no longer works. So far nothing I've tried has worked. I disabled all firewall and antivirus. Still nothing. When I run Guest OS Windows Network Diagnostics, I get the "your modem broadband has connectivity problems." However, I know that this is not the case. I also used the "Virtual Network Editor" to force the bridge connection to select the correct network card (in my case, it's the Intel Centrino Wireless - N 1030 wireless card), but still no luck. Any help would be much appreciated.

  
  

  Thank you

  Dave
  

  
  

  My Stats:

  
  Host:

  OS: Windows 7 x 64

  Processor: Intel Core i7

  Installed memory (RAM): 16.0 GB (15.9 GB usable)

  Wireless adapter: Intel Centrino Wireless - N 1030

  Router: Netgear AC1200 Smart Wifi router. Model: R6200v2 (default settings)

  
  

  Comments:

  OS: Windows 7 x 64

  
  

  So I finally the solution look. BitDefender firewall was blocking all traffic on the connection Bridged in VMware Workstation. I have disabled the firewall completely Bitdefender and Bridged Networking worked perfectly. I'll probably create another topic more precisely around Bitdefender firewall configuration to allow traffic network through Bridged from VMware.

• Another VMWare Workstation Fedora 19 x 64 wire

  I tried for 2 weeks almost to install vmware player or vmware workstation 10.1 6 on fedora 19 x 64

  The process I followed was simply by downloading the file from the vmware website, run it, then run the application.

  It starts fine with no errors, but when I try to start a virtual machine the following error message indicates:

  Unable to open/dev/vmmon: no such file or directory. Please ensure that the "vmmon" kernel module is loaded.

  and then displays this error:

  Could not initialize the surveillance apparatus.

  and this:

  Cannot change the power state of VM: internal error

  So after searching around, I tried to build modules with

  
  

  VMware-modconfig - console - install-all

  But it fails with the following error message.

  .......

  make [1]: entering directory ' / tmp/modconfig-pnqYny/vmnet-only.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-pnqYny/vmnet-only.

  CP f vmnet.ko. /... vmnet.o

  make: leaving directory ' / tmp/modconfig-pnqYny/vmnet-only.

  From vmware (via systemctl): work for vmware.service failed. See "systemctl situation vmware.service" and "journalctl - xn" for more details.

  [NOT]

  Cannot start the services

  journalctl - xn

  -Newspapers are beginning to Mar 2013 - 11 - 12 12:33:24 AST, end my 2013-11-18 12:02:44 AST. --

  And the journal file vmware-modconfig - 15432.log

  shows:

  2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Log for VMware Workstation = 15432 pid = 10.0.1 version build = build-1379776 option = output

  2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: The process is 64-bit.

  2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Host codepage = UTF-8 encoding = UTF-8

  2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Host is the version of Fedora Linux 3.11.8 - 200.fc19.x86_64 19 (Schrödinger's cat)

  2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: Msg_Reset:

  2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: [msg.dictionary.load.openFailed] cannot open the file ' / usr/lib/vmware/settings ': no such file or directory.

  2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: ----------------------------------------

  2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: Preferences file of the option PREFS not found in/usr/lib/vmware/settings. Using the default values.

  2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: Msg_Reset:

  2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: [msg.dictionary.load.openFailed] cannot open the file ' / root/.vmware/config ': no such file or directory.

  2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: ----------------------------------------

  2013 11-18 T 12: 05:30.280 + 03:00 | modconfig | I120: Optional preferences PREFS not found in root/.vmware/config file. Using the default values.

  2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: initialized! Lets do this thing...

  2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Obtaining information on the use of the kernel running.

  2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Created new pathsHash.

  2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Setting header 3.11.8 path - 200.fc19.x86_64 to "/ lib/modules/3.11.8-200.fc19.x86_64/build/include".

  2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: Validation of path ' / lib/modules/3.11.8-200.fc19.x86_64/build/include ' for kernel version "3.11.8 - 200.fc19.x86_64.

  2013 11-18 T 12: 05:30.281 + 03:00 | modconfig | I120: using GCC to preprocess check

  2013 11-18 T 12: 05:30.285 + 03:00 | modconfig | I120: Pre-treated UTS_RELEASE, obtained the value "3.11.8 - 200.fc19.x86_64.

  2013 11-18 T 12: 05:30.285 + 03:00 | modconfig | I120: The path of the header ' / lib/modules/3.11.8-200.fc19.x86_64/build/include ' to the core "3.11.8 - 200.fc19.x86_64" is valid. Boo!

  2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Reading in info for the vmmon module.

  2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Reading in info for module vmnet.

  2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Reading in info for the vmblock module.

  2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Reading in info for vmci module.

  2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Reading in info for the vsock module.

  2013 11-18 T 12: 05:30.395 + 03:00 | modconfig | I120: Definition of vsock to depend on vmci.

  2013 11-18 T 12: 05:30.405 + 03:00 | modconfig | I120: Try to find a PBM adapted for the core "3.11.8 - 200.fc19.x86_64.

  2013 11-18 T 12: 05:30.405 + 03:00 | modconfig | I120: No corresponding PBM set has been found for the core "3.11.8 - 200.fc19.x86_64.

  2013 11-18 T 12: 05:30.405 + 03:00 | modconfig | I120: Compiler found in ' / usr/bin/gcc ".

  2013 11-18 T 12: 05:30.407 + 03:00 | modconfig | I120: Got gcc version "4.8.2.

  2013 11-18 T 12: 05:30.407 + 03:00 | modconfig | I120: The GCC version corresponds to the minor version of GCC kernel like a glove.

  2013 11-18 T 12: 05:30.407 + 03:00 | modconfig | I120: Temp dir using ' / tmp '.

  2013 11-18 T 12: 05:30.443 + 03:00 | modconfig | I120: Setting for vmmon destination path to ' / lib/modules/3.11.8-200.fc19.x86_64/misc/vmmon.ko '.

  2013 11-18 T 12: 05:30.443 + 03:00 | modconfig | I120: Extraction of the vmmon sources of "/ usr/lib/vmware/modules/source/vmmon.tar".

  2013 11-18 T 12: 05:30.448 + 03:00 | modconfig | I120: Extract successfully the vmmon source.

  2013 11-18 T 12: 05:30.448 + 03:00 | modconfig | I120: Module construction with the command ' / usr/bin/make - j4 - C/tmp/modconfig-dbIkzQ/vmmon-only-automatic generation HEADER_DIR=/lib/modules/3.11.8-200.fc19.x86_64/build/include CC = / usr/bin/gcc IS_GCC_3 = no ".

  2013 11-18 T 12: 05:32.053 + 03:00 | modconfig | I120: Vmmon successfully built. Module is currently at "/ tmp/modconfig-dbIkzQ/vmmon.o".

  2013 11-18 T 12: 05:32.053 + 03:00 | modconfig | I120: Found the vmmon symvers file to ' / tmp/modconfig-dbIkzQ/vmmon-only/Module.symvers '.

  2013 11-18 T 12: 05:32.053 + 03:00 | modconfig | I120: Installation vmmon of /tmp/modconfig-dbIkzQ/vmmon.o to lib/modules/3.11.8-200.fc19.x86_64/misc/vmmon.ko.

  2013 11-18 T 12: 05:32.056 + 03:00 | modconfig | I120: Save the file ' / lib/modules/3.11.8-200.fc19.x86_64/misc/vmmon.ko '.

  2013 11-18 T 12: 05:32.233 + 03:00 | modconfig | I120: "/ usr/lib/vmware-installer/2.1.0/vmware-installer" came out with a status of 0.

  2013 11-18 T 12: 05:32.234 + 03:00 | modconfig | I120: Save the file ' / usr/lib/vmware/symvers/vmmon-3.11.8-200.fc19.x86_64 '.

  2013 11-18 T 12: 05:32.415 + 03:00 | modconfig | I120: "/ usr/lib/vmware-installer/2.1.0/vmware-installer" came out with a status of 0.

  2013 11-18 T 12: 05:32.415 + 03:00 | modconfig | I120: The setting for vmnet destination path to ' / lib/modules/3.11.8-200.fc19.x86_64/misc/vmnet.ko '.

  2013 11-18 T 12: 05:32.415 + 03:00 | modconfig | I120: Extraction of the source vmnet "/ usr/lib/vmware/modules/source/vmnet.tar".

  2013 11-18 T 12: 05:32.419 + 03:00 | modconfig | I120: Extract successfully the vmnet source.

  2013 11-18 T 12: 05:32.419 + 03:00 | modconfig | I120: Module construction with the command ' / usr/bin/make - j4 - C/tmp/modconfig-dbIkzQ/vmnet-only-automatic generation HEADER_DIR=/lib/modules/3.11.8-200.fc19.x86_64/build/include CC = / usr/bin/gcc IS_GCC_3 = no ".

  2013 11-18 T 12: 05:34.829 + 03:00 | modconfig | I120: Vmnet successfully built. Module is currently at "/ tmp/modconfig-dbIkzQ/vmnet.o".

  2013 11-18 T 12: 05:34.829 + 03:00 | modconfig | I120: Found the vmnet symvers file ' / tmp/modconfig-dbIkzQ/vmnet-only/Module.symvers '.

  2013 11-18 T 12: 05:34.829 + 03:00 | modconfig | I120: Installation vmnet of /tmp/modconfig-dbIkzQ/vmnet.o to lib/modules/3.11.8-200.fc19.x86_64/misc/vmnet.ko.

  2013 11-18 T 12: 05:34.832 + 03:00 | modconfig | I120: Save the file ' / lib/modules/3.11.8-200.fc19.x86_64/misc/vmnet.ko '.

  2013 11-18 T 12: 05:35.004 + 03:00 | modconfig | I120: "/ usr/lib/vmware-installer/2.1.0/vmware-installer" came out with a status of 0.

  2013 11-18 T 12: 05:35.004 + 03:00 | modconfig | I120: Save the file ' / usr/lib/vmware/symvers/vmnet-3.11.8-200.fc19.x86_64 '.

  2013 11-18 T 12: 05:35.185 + 03:00 | modconfig | I120: "/ usr/lib/vmware-installer/2.1.0/vmware-installer" came out with a status of 0.

  2013 11-18 T 12: 05:35.484 + 03:00 | modconfig | I120: We now stop. Ready to die!

  The version of the kernel (uname - r)

  Watch: 3.11.8 - 200.fc19.x86_64

  The header/devel packages are installed

  RPM - qa | grep kernel

  shows:

  core-tools-libs - 3.11.8 - 200.fc19.x86_64

  kernel-devel - 3.11.7 - 200.fc19.x86_64

  core-tools - 3.11.8 - 200.fc19.x86_64

  libreport-plugin-kerneloops - 2.1.9 - 1.fc19.x86_64

  kernel-devel - 3.11.8 - 200.fc19.x86_64

  kernel-modules-extra - 3.11.7 - 200.fc19.x86_64

  kernel - 3.11.8 - 200.fc19.x86_64

  kernel-headers - 3.11.8 - 200.fc19.x86_64

  ABRT-addon-kerneloops - 2.1.9 - 1.fc19.x86_64

  kernel-devel - 3.9.5 - 301.fc19.x86_64

  kernel-modules-extra - 3.9.5 - 301.fc19.x86_64

  kernel - 3.11.7 - 200.fc19.x86_64

  kernel - 3.9.5 - 301.fc19.x86_64

  kernel-modules-extra - 3.11.8 - 200.fc19.x86_64

  Note I tried various fixes available online, but none seems not to work too.

  I would appreciate any assistance to resolve it.

  Thank you all.

  
  Alaa-

  Problem solved.

  I had to disable "Secure Boot" on my laptop.

  Thank you all.

• VMware Workstation 10 bug: DVD SATA drive does not start if we disable the floppy drive in the VMware BIOS

  Hello

  I use VMware Workstation 10, and I found a bug:

  With the all-new virtual machine (for example with Windows 8 x 64), if I choose a hard SATA and SATA DVD drive in VMware and I have to disable the floppy drive in the VMware BIOS, Windows 8 (or Windows 7) ISO does not start.

  If I come back in the BIOS to enable the floppy drive once again, my ISO boot.

  If I use the DVD IDE drive in VMware options, no problem if I disable the floppy drive.

  With "EFI mode", no bugs.

  Please, can you solve this problem? Thank you

  Hi freebeing,

  Thank you for reporting this issue.  We have reproduced it is internal and work on it.  Sorry for the inconvenience.

  See you soon,.

  --

  Darius