Quantcast
Channel: VMware Communities: Message List
Viewing all 230299 articles
Browse latest View live

Re: Workstation 12.5.6 on W10 (1703) and W7 Clients

$
0
0

I couldn't find anything in the vmx that would indicate a problem.

 

From the log files, when it tries to open the virtual hard disk of the VM

 

2017-05-27T08:00:11.644+02:00| vmx| I125: DISKUTILWIN32: DiskUtilW32_IsPhysicalSSD: Failed to get the extents of the volume \\?\Volume{ee321bb7-4233-11e7-b603-6805ca47c9a1}\ error 234

2017-05-27T07:57:37.785+02:00| vmx| I125: DISKUTILWIN32: DiskUtilW32_IsPhysicalSSD: Failed to get the extents of the volume \\?\Volume{ee321bb7-4233-11e7-b603-6805ca47c9a1}\ error 234

 

2017-05-26T13:58:15.672+02:00| vmx| I125: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Failed to send ATA IDENTIFY command to the target device.

2017-05-26T13:58:15.672+02:00| vmx| I125: DISKUTILWIN32: DiskUtilW32IsScsiSSDDevice: Reported rotation rate = 65534

 

2017-05-25T13:09:05.227+02:00| vmx| I125: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Failed to send ATA IDENTIFY command to the target device.

2017-05-25T13:09:05.227+02:00| vmx| I125: DISKUTILWIN32: DiskUtilW32IsScsiSSDDevice: Reported rotation rate = 65534

 

I don't know why VMware Workstation would use two different methods for the same VM.

 

In my VMs, DiskUtilW32IsATASSDDevice is used and if the VM is on SSD it reports the rotation rate as 1 and identify the virtual disk of the VM as Virtual SSD. If the VM is on hard disk, it reports the correct rotational speed (in my case a slow 5400 rpm disk).

 

Are your other virtual machines on the same U hard drive? Maybe it is the physical hard drive where the VM resides that is a problem.


Re: invoke RelocateVM_Task to move vm from current vcenter to another vcenter

$
0
0

Hi,

 

does manual vmotion through webclient work?

Re: Error while login to Vcentre Web Client

$
0
0

I hope the vCenter is installed on windows and not VCSA. if so I would recommend to restart the vCenter and the client browser .

Re: vmxnet3 on ESX 6.0 sets eop field incorrectly in Rx descriptor even when JUMBO is not enabled

$
0
0

have you installed vmxnet3 driver part of VMware tools?

No storage vmotion with ESXi 6.5 Host Client?

$
0
0

Hi,

I am using ESXi 6.5 as a standalone server on a HPE Microserver Gen8 (without vcenter) - just with the host client.

I am still in the evaluation mode, so all licenses should be there.

I am trying now to move a VM from one data store to another one. It is not possible to use storage vmotion without a vcenter? I am not able to find any option like this. Is there any other hint to do that storage vmotion ( do not have to be an online storage vmotion) - I will need it often.

I also power down the machine and try to move the folder manually from one data store to the other, but this takes a HUGE amount of time (hours for 15 GB).

Thanks for your helpl

regards

Chris

Re: What Is The Difference Between Eager Zero And Lazy Zero Thick Provision Disks?

$
0
0

you would provision eager zero'd when you need fast write performance.  perhaps for a DB or an Exchange DAG.  personally I have not used them all that much as the time laying them out is quite long and it is very intensive on your Shared storage.

Re: Ubuntu 17.10 does not run in VMware Workstation 12.5.6

$
0
0

Hi CollinChaffin,

 

I'm sorry that we appear to be failing to meet your expectations, while also being somewhat honored that you hold us to such high standards.  I appreciate you are frustrated, but please do remember that the VMware engineers and volunteers here in the forum are all humans, and your tone of writing here would make it much less likely that anyone will assist.  I'll go against my gut instinct and try to assist anyway; In return, I'd appreciate if you could put your emotions aside and work with us on understanding the problem.

 

Please also note that Ubuntu 17.10 is very early pre-release software, and as such it is nowhere near being qualified for use with VMware Workstation.  Ubuntu 17.10 may itself contain severe data-loss bugs at this stage of its development cycle, which is one of the reasons we don't try to claim compatibility or interoperability at this stage... We would spend far too much time chasing bugs that aren't ours.

 

That doesn't explain the Kali situation, though...  My first thought is that we have many (MANY) users running Kali inside VMware Workstation and Fusion -- it's a very popular combination for security work -- and this is the first I've heard of this happening.

 

My next thought is ... hmmm... this reminds me somewhat of a Linux kernel bug for which we posted a fix for back in 2014: Linux-Kernel Archive: [PATCH] Do not silently discard WRITE_SAME requests

 

That was a bug in the Linux kernel's block layer which just happened to only have an effect when writing to VMware's emulated SCSI disks.  It was not due to any defect in our emulation (despite the incorrect comments to the contrary in that discussion thread)... it was caused by a set of perfectly-valid characteristics that our emulated SCSI disks happened to have and that the Linux kernel handled improperly.  SATA disks were unaffected, as were other virtualization platforms and probably the vast majority of physical systems with SCSI disks.

 

I've looked into the latest Linux kernel sources, and it seems that the patch that we supplied was never fully accepted, despite all the effort we put into root-causing it and providing the patch.  Parts of the problem were fixed, but seemingly not all... I can't quite tell if subsequent patches papered over the gaps we identified in the accepted fix.  I think it should be "safe" because the particular feature in question (the WRITE_SAME command) was masked off for VMware LSI Logic SCSI/SAS controllers, but part of the underlying defect -- as far as I can tell -- still exists in part. 

 

So far, that defect was only known to affect disks using LVM, but these things can always change as software evolves...  The "worse with LVM, doesn't happen with SATA" factor reported in the Kali bug certainly sounds eerily similar.

 

Anyway, I've attempted to reproduce the problem with Kali here on my machine, and I have not yet succeeded.  I'm testing with http://kali.mirror.garr.it/mirrors/kali-images/kali-2017.1/kali-linux-light-2017.1-amd64.iso , installing into a VM running on VMware-Workstation-Full-12.5.6-5528349.x86_64.bundle installed on a Debian 8.8 host running kernel 3.16.0-4-amd64.  Kali bug 4017 (in the link you supplied) also seems to suggest that the problem is not reliably reproducible -- at least not on a host system other than the reporter's machine.

 

Here are my steps which failed to reproduce the problem:

 

  1. In the Workstation UI, choose File > New Virtual Machine, Typical, [Next], Choose Use ISO image, choose kali-linux-light-2017.1-amd64.iso, [Next].
  2. For Guest Operating System, choose 2. Linux, Version: Debian 8.x 64-bit, [Next].
  3. Virtual machine name: (whatever name you want...) [Next]
  4. Disk Size: Use defaults (20 GB, split into multiple files) [Next]
  5. At Ready to Create Virtual Machine, choose Customize hardware; Configure the virtual Ethernet adapter to NOT connect at power-on, [Close].
  6. Back at the Ready to Create Virtual Machine screen, choose [Finish]
  7. Choose [Start up this guest operating system].
  8. At Kali bootloader screen, down-arrow a few times to choose "Graphical install", and press Enter.
  9. Select a language: Use defaults (English/English).  Choose [Continue].
  10. Select your location: Use default (United States).  Choose [Continue].
  11. Configure the keyboard: Use default (American English).  Choose [Continue]
  12. Configure the network: Network autoconfiguration failed.  [Continue]
  13. Choose "Do not configure the network at this time".  [Continue]
  14. Hostname: Use default ("kali").  Choose [Continue].
  15. Set up users and passwords.  Root password: blank.  [Continue].
  16. Full name for the new user: test. [Continue]
  17. Username: Default "test".  [Continue].
  18. Password: "hello", re-enter to verify, "hello".  [Continue].
  19. Configure the clock.  Default "Eastern".  [Continue].
  20. Partition disks: Default "Guided - use entire disk".  [Continue].  (Alternatively, to test with LVM, choose "Guided - use entire disk and set up LVM", and there'll be two more screens below for partitioning the LVM device.)
  21. Select disk to partition: "SCSI1 (0,0,0) (sda) - 21.5 GB VMware, VMware Virtual S".  [Continue].
  22. Partitioning scheme: Default "All files in one partition (recommended for new users)".  [Continue].
  23. Partition disks: (This is an overview of your currently configured partitions...)  Default "Finish partitioning and write changes to disk".  [Continue].
  24. "If you continue, the changes listed below will be written to the disks." ... "Write the changes to disks?"  Choose (X) Yes, then [Continue].
  25. Wait for "Install the system" to complete.
  26. Configure the package manager.  "Use a network mirror?". Use default (No).  Choose [Continue].
  27. Install the GRUB boot loader on a hard disk.  "Install the GRUB boot loader to the master boot record?"  Default (Yes).  [Continue].
  28. Device for boot loader installation:  Choose "/dev/sda".  [Continue].
  29. Installation complete.  [Continue].
  30. Graphical Kali login screen having blue background with subtle swirliness: Enter "test", password "hello".  Choose [Log In]
  31. Dialog box: "Panel", "Welcome to the first start of the panel". Choose [Use default config].
  32. Top-right menu, labelled "test": Choose "Shut Down".  Dialog box: [Shut Down] button.
  33. In the Workstation UI, choose [Start up this guest operating system].  Repeat the last few steps several times (and/or choose Restart instead of Shut Down) to ensure that everything works cleanly.

 

I tried quite a few variations on that process, including those given in Kali bug 4017 (choosing Custom instead of Typical, then choosing 2 GB of RAM and a 60 GByte virtual disk), including using LVM or not using LVM, etc., etc., but always using the LSI Logic SCSI controller for the virtual hard disks.  Everything I've tried has worked 100% correctly, with no reports of disk corruption.

 

At this point, it'd be super helpful if you could do two or three things:

 

  1. Provide a copy of the vmware.log and other vmware-*.log files from a fresh virtual machine, gathered immediately after the first evidence of the disk corruption (with either Ubuntu 17.10 or Kali as a guest OS), and
  2. Try following the above steps exactly using Kali 2017.1 amd64 (light or non-light version) and see if the problem reproduces there, and/or
  3. Provide exact steps (to a similar level of detail to what I've given above) that you are using to reproduce the problem here, so that I can do precisely the same here.

 

I've scheduled a download of a nightly build of Ubuntu 17.10 amd64 from http://cdimage.ubuntu.com/daily-live/20170527/artful-desktop-amd64.iso, so hopefully I can test with that image tomorrow once my slow slow ADSL obliges...  Hopefully that will be close enough to whatever disc image you are using there.  With your help, we'll hopefully be able to figure out what's causing these problems (and indeed figure out if the Ubuntu 17.10 problem is the same as the Kali problem, and if either of those are related to the WRITE_SAME issue from 2014).

 

(P.S. This problem is unrelated to that reported earlier in this thread; mfelker is trying to run Workstation 12.5.6 on Ubuntu 17.10 and it's failing to launch, while you're trying to run Ubuntu 17.10 inside VMware Workstation 12.5.6 and ending up with corrupted filesystems in the guest.  It's a totally different and likely unrelated problem space.  I'll break this branch of the discussion out into its own thread... I hope that's OK with you!)

 

Thanks,

--

Darius

Re: VMware Workstation 12.5.6 does not run on Ubuntu 17.10

$
0
0

It seems like discussion of the Ubuntu 17.10 host appLoader issue is moving along more productively in this other thread: VMware Workstation 12.5.6 doesn't start on Ubuntu 17.10.  Let's keep further discussion of the Ubuntu 17.10 host issues over in that thread.

 

I've moved CollinChaffin's issue with Ubuntu 17.10 as a guest to a separate thread because it is unrelated to the host-side issues.  The new thread is here: Ubuntu 17.10 does not run in VMware Workstation 12.5.6

 

I hope that's OK with everyone.  Thanks!

--

Darius


Re: VMware Workstation 12.5.6 doesn't start on Ubuntu 17.10

$
0
0

Hi Marty!

 

Please try running:

 

   $ find /tmp/vmware-$USER -cmin -60

 

to find possibly-relevant logfiles created within the last hour.  Hopefully there will be a vmware-apploader-<nnnn>.log in there.

 

Cheers,

--

Darius

Re: Error while login to Vcentre Web Client

$
0
0

Yes Vcenter is installed  not VCSA. How to restart the vcenter? I have restart the browser several times but problem not resolved.

Re: how to launch an action when raising a log insight alert

Horizon Client Mouse/Keyboard no reponse

$
0
0

Hi all,

 

Im having issues with the view client, when connecting the mouse will move but clicks are not registered and the keyboard will not function at all.

 

Im running the latest client version and I'm on OS X Sierra

 

Your help would be much appreciated!

 

Thanks

Re: Wacom Tablet & keyboard ALL CAPS issue!

$
0
0

Hi SashaKW,

 

I have an Intuos Pro (PTH-651) connected to my MacBook Pro running macOS 10.12.4, and I have not encountered any problem like you describe.

 

Could I request a few more details about the nature of the problem?  When it is happening, does it affect only typing within the Windows 10 virtual machine, or also typing on the host Mac?  When you say "I have to restart my machine", do you mean the virtual machine running Windows 10, or the host Mac Pro?  It sounds like you mean the Mac, but it's not 100% clear.

 

I can't help but be reminded of one of my less-than-glorious IT moments many years ago when a PC very suddenly started furiously misbehaving and generally doing weird stuff (menus would vanish an instant after they appeared on screen, etc.), and after a few minutes of struggling against it, I decided that logging in afresh was the only reasonable next step, but the problem continued at the login screen.  It took an embarrassingly long time before I found that some paperwork near the keyboard had moved a smidgen and was now resting on top of the "Esc" key with juuuuuust enough force to hold it down, and keyboard auto-repeat took care of the rest...  Yeah, that was not my finest moment.  So ... uhhhhhm ... perhaps check for similarly "obvious" possible causes there too... just in case.    (Really that was just an excuse to tell my silly story.)

 

Cheers,

--

Darius

Re: Error while login to Vcentre Web Client

$
0
0

I have restarted the service but getting a different error. Error screen is attached as well as the services also.

Re: No storage vmotion with ESXi 6.5 Host Client?

$
0
0

Hello,

 

You could test if cloning the disks to the new destination might be faster:

Via SSH session connected to the host, make a target namespace folder:

# mkdir /vmfs/volumes/TargetDatastore/NewVMName/

Clone the disks of the VM to the new location (this example is thin provisioned and default contoller type):

# vmkfstools -i /vmfs/volumes/OriginalDatastore/OldVMName/OldVMName.vmdk /vmfs/volumes/TargetDatastore/NewVMName/NewVMName.vmdk -d thin

kb.vmware.com/kb/1027876

 

You can easily check how fast this is cloning by checking the size at destination using du command.

 

Bob

 

-o- If you found this comment useful please click the 'Helpful' button and/or select as 'Answer' if you consider it so, please ask follow-up questions if you have any -o-


Re: invoke RelocateVM_Task to move vm from current vcenter to another vcenter

$
0
0

Have a look in the vpxd logs of both vCenters to see if they contain any more info on the error?

You also might want to have a look at the hostd logs on the ESXi nodes.

Re: Anyone else experiencing a bug regarding keypresses after upgrading to VMware Fusion 8.5.7?

$
0
0

Hi kylehawkes,

 

That's an odd problem.  I've not heard any similar reports at all.

 

Do you recall which version of Fusion you were using previously which did not have this problem?  (i.e. Did the problem start with an upgrade from Fusion 8.5.6 to 8.5.7, or from Fusion 7.x to 8.5.6, or from something even earlier?)  Anything else you have changed at the same time?  (e.g. Upgraded macOS or changed some hardware on your host Mac.)  Are you using the MacBook Pro internal keyboard with no external keyboard attached?

 

Which guest OSes are you using inside the virtual machines?

 

If you select a powered-off virtual machine and go to the Virtual Machine menu and choose Power on to Firmware, is it possible for you to tell whether the same problem exists in the firmware setup screen?  (i.e. Press the "+" key once and see if it increments the "hours" of the system clock by one, or increments repeatedly, assuming that "+" is one of the affected keys.)

 

Cheers,

--

Darius

Re: No storage vmotion with ESXi 6.5 Host Client?

Re: Can't Edit system resource reservation in vsphere 6.0 and ESXi 6.0

$
0
0

I have dug pretty deep into this issue. As far as i am aware there is no command line command you can type to adjust this.

Re: No storage vmotion with ESXi 6.5 Host Client?

$
0
0

Hi Chris,

 

Storage VMotion means you can migrate a virtual machine and its disk files from one datastore to another while the virtual machine is running.

You can't do storage VMotion without VCenter.

 

yes, you can migrate VM from one datastore to another datastore but that is not storage Vmotion because we are turning off the VM's for migration.

 

You can read this article to migrate VM without VCenterbut that's not Storage VMotion: - How to move a VM without vCenter

 

Time taken in storage VMotion can be 24 hours, it depends on the network speed, the size of VM because in storage VMotion we are migrating whole storage from one datastore to another.

 

Please let me know if it helps you, Chris!

 

 

Viewing all 230299 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>