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

USB Passthrough Not Working

$
0
0

On a vShpere server I'm trying to add a USB device (a USB HDD) to a guest. I have marked all USB controllers on the host for passthrough and have rebooted the host. I have added the EHCI+UHCI controller to the guest and have the guest powered on. When I try to add the device to the guest the Add Hardware wizard shows "USB Device (unavailable)" and when I select it I see "There are no USB devices available on the host."

 

How can I diagnose what's going on here? I think I've followed the proper steps to configure USB passthrough but I just can't seem to get it working.

 

Hardware:

HP ProLiant DL380 G7

Intel 5520 Chipset

Intel I/O Controller Hub 10 (82801JI)


Access vSphere Hypervisor 6.0 web client through secure gateway

$
0
0

We have vSphere Hypervisor 6.0 set up in a lab. We have to go through a secure gateway to get to the lab network. I can get to the web client login page, but cannot get past that. I can when I connect with a laptop that is on the same subnet via a switch. The guy running the gateway says it allows 443, but he also said port 9443 shows up in firewall logs.

He has what I think is version 5.1 of vSphere in another location and he says that his url always shows 9443. Our v6 install does not show port 9443, but seems to redirect there when you try to logon from 443/https. He says the gateway cannot be configured to add ports to the base url. He thinks the base url of the web client needs to be changed to always use port 9443 as part of the url, but I can't figure out how to change any of this if even possible. Or is there possibly another option/alternative? Thanks for any help people.

Re: Unable to clean up deleted files: The specified virtual disk needs repair.

$
0
0

On a Mac OS X Sierra (macOS) machine running VMWare Fusion 8.5 I got the same error.

 

To identify the damaged file I ran the following command from within Terminal:
find "/Users/<userid>/Documents/Virtual Machines/<name of VM>/" -name "*.vmdk" -type f -exec "/Applications/VMware Fusion.app/Contents/Library/vmware-vdiskmanager" -e '{}' \;

 

This command finds all the .vmdk files in a VM and then runs the vmware-vdiskmanager command against them individually.

 

One of the files reported:

Failed to open the disk '/Users/<userid>/Documents/Virtual Machines/<name of VM>/<damaged file>.vmdk' : The specified virtual disk needs repair (0x3e86).

 

This file was repaired using the "-R" flag on vmware-vdiskmanager:

 

"/Applications/VMware Fusion.app/Contents/Library/vmware-vdiskmanager" -R /path/to/damaged.vmdk

The virtual disk, '/path/to/damaged.vmdk', was corrupted and has been successfully repaired.

 

I was then able to Clean Up and start the VM normally.

 

Reference:

 

"/Applications/VMware Fusion.app/Contents/Library/vmware-vdiskmanager" --help

/Applications/VMware Fusion.app/Contents/Library/vmware-vdiskmanager: illegal option -- -

VMware Virtual Disk Manager - build 4352717.

Usage: vmware-vdiskmanager OPTIONS <disk-name> | <mount-point>

Offline disk manipulation utility

  Operations, only one may be specified at a time:

     -c                   : create disk.  Additional creation options must

                            be specified.  Only local virtual disks can be

                            created.

     -d                   : defragment the specified virtual disk. Only

                            local virtual disks may be defragmented.

     -k                   : shrink the specified virtual disk. Only local

                            virtual disks may be shrunk.

     -n <source-disk>     : rename the specified virtual disk; need to

                            specify destination disk-name. Only local virtual

                            disks may be renamed.

     -p                   : prepare the mounted virtual disk specified by

                            the volume path for shrinking.

     -r <source-disk>     : convert the specified disk; need to specify

                            destination disk-type.  For local destination disks

                            the disk type must be specified.

     -x <new-capacity>    : expand the disk to the specified capacity. Only

                            local virtual disks may be expanded.

     -R                   : check a sparse virtual disk for consistency and attempt

                            to repair any errors.

     -e                   : check for disk chain consistency.

     -D                   : make disk deletable.  This should only be used on disks

                            that have been copied from another product.

 

  Other Options:

     -q                   : do not log messages

 

  Additional options for create and convert:

     -a <adapter>         : (for use with -c only) adapter type

                            (ide, buslogic, lsilogic). Pass lsilogic for other adapter types.

     -s <size>            : capacity of the virtual disk

     -t <disk-type>       : disk type id

 

  Disk types:

      0                   : single growable virtual disk

      1                   : growable virtual disk split in 2GB files

      2                   : preallocated virtual disk

      3                   : preallocated virtual disk split in 2GB files

      4                   : preallocated ESX-type virtual disk

      5                   : compressed disk optimized for streaming

      6                   : thin provisioned virtual disk - ESX 3.x and above

 

     The capacity can be specified in sectors, KB, MB or GB.

     The acceptable ranges:

                           ide/scsi adapter : [1MB, 8192.0GB]

                           buslogic adapter : [1MB, 2040.0GB]

        ex 1: vmware-vdiskmanager -c -s 850MB -a ide -t 0 myIdeDisk.vmdk

        ex 2: vmware-vdiskmanager -d myDisk.vmdk

        ex 3: vmware-vdiskmanager -r sourceDisk.vmdk -t 0 destinationDisk.vmdk

        ex 4: vmware-vdiskmanager -x 36GB myDisk.vmdk

        ex 5: vmware-vdiskmanager -n sourceName.vmdk destinationName.vmdk

        ex 6: vmware-vdiskmanager -r sourceDisk.vmdk -t 4 -h esx-name.mycompany.com \

              -u username -f passwordfile "[storage1]/path/to/targetDisk.vmdk"

        ex 7: vmware-vdiskmanager -k myDisk.vmdk

        ex 8: vmware-vdiskmanager -p <mount-point>

              (A virtual disk first needs to be mounted at <mount-point>)

Re: Truncated VRAM framebuffer size in Ubuntu 16.04.0 LTS under VMware Fusion 8

$
0
0

I'm not sure if the VRAM in this case is actually the same as the PCI bar memory, but I did try setting svga.minVRAM8MB = "TRUE", and the truncation message still appears in the log file.  As for X or the SVGA versus VESA driver, I'm actually using the Linux framebuffer directly, so there should be no drivers that come into play on the guest side other than what is built into the kernel.  Would you concur with that?  I certainly am not loading any drivers when I run this on Ubuntu 15.04 or 14.04.0 LTS.


Note also that I opened a support request with VMware, and was told that they had confirmed the issue on a lab machine and would be filling a problem report with their engineering team.

Cutting the umbilical cord to Microsoft!

$
0
0

When will VMware finally cut the cord to Microsoft with regards to requiring MSSQL (Or Oracle) for its infrastructure?

When will they finally understand that some shops are interested in leveraging only the LAMP stack and to do so in a enterprise environment is not possible without the use of one of the 2 flavors of SQL.

SLA/Uptime Report vCenter Operations

$
0
0

I know the following question has been asked before but does anyone have a sample Custom Views  to share and or  Super metrics  to create  a SLA/Uptime for Hosts including maint based on Days  ?

Re: USB Passthrough Not Working

$
0
0

Hi,

1. Are you sure the USB is properly connected to the server?

2. Are you able to see the USB drive at ESXi level i.e. Add storage under  Storage configuration of ESXi?

3. Is you virtual machine is hardware version 7 or later to which you are trying to attached the USB?

end point agents and OS Monitor Script


Re: parentfilenamehint - randomly uses absolute path

$
0
0

I assume you mean the .vmx file.  I checked all the .vm* files < 50k and that string is not there.

 

Outside of a user specifically configuring a VM in such a manner, I can't imagine why the default behavior would ever BRAND a VM to a specific drive/folder.  So now I've got to write a script to run regularly and check for that.

 

In testing, I've noticed that VMware (after the VM is copied) will most of the time update the Disk DescriptorFile(s) and remove the path part when the VM is started - presumably since it finds the files in the local directory.  However, in a couple of scenarios it did not do this.  As a result, when I started the copied VM, it "reached' into the path it came from and whacked those files.  I don't know what logic VMware uses to determine that the Disk DescriptorFile needs updating. 

 

I tried removing the path part myself but that didn't work.  It reported it could not find a file - but that file did exist.  I didn't know what to do about the CID in the Disk DescriptorFile or uuid.location in the .vmx file.  So that might have been why it didn't work.

 

Now I know to HIDE my source VM after copying it until I've booted the copy and checked the Disk DescriptorFile(s) for any reference to the source VM.  I've NEVER had to do this in the past 10 years though.  Strange.

Re: Some VMs ( 4 of 5) aren't migrate to second host when first host down.

$
0
0

Hi Umesh,

 

Thank you for your response. I will re-configure HA..

 

Thank you.

Lerpong

Re: Some VMs ( 4 of 5) aren't migrate to second host when first host down.

$
0
0

Hi Richardson,

 

Thank you for your response. Those VMs stored on shared datastored. Those VMs can vMotion between host.

 

Thank you

Lerpong

Re: All VMs Start with Black Screen

$
0
0

nkoszyk solution of disabling 3D graphics worked for me. This problem seems to be new with v12 of workstation.

V center server is unable to find a master vsphere agent in the cluster

$
0
0

All this started with the v center 5.5.0 update to the latest patch 3e . After the upgrade couldnt enable HA its a production enviroment tried disabling and renabling HA on thecluster .It fails with the message vsphere agent is not reachable from the v center server. The cluster isnt in a lockdown mode.It pops up with a message there was an error unconfiguring the vsphere HA agent on the host to solve the problem connect the host to a vcenter server of version 5.0 or later. Tried restoing the old snapshot which changed the vcenter version to 5.5.0 but still the same error message. Any ideas people please ?? Its a prod enviroment hard to reboot host.

Re: How to disable SSL in VMRC for Linux?

$
0
0

Those command-line options should work fine with the current VMRC, be sure to use capital letters for the flags though. What kind of performance issues do you see with VMRC 9? What OS and how much memory do the PCs have?

Re: LSI 9217 SAS is insanely slow, even with SSDs on ESXi 5.1

$
0
0

OK, I finally figured it out!

 

Apparently the LSI HBAs in RAID mode aren't that great for ESXi.   The HBA was originally purchased for ZFS use, so no RAID was needed.   Now, when you flash a RAID firmware on the card, you are missing things like a battery backup and a write-back cache enabled.

 

To fix my performance, I needed to enable the write-back cache.  Now, some may say that without a BBU this is dangerous.  However, all of the VMs on this system are ephemeral, so data loss in case of power outage doesn't matter.

 

It took a lot of tries to get an lsiutil that works, but here's what did it for me:

  1. Burn SystemRescueCd (or maybe most Linux distros should work): https://www.system-rescue-cd.org/
  2. Get https://karlsbakk.net/LSIUtil%20Kit%201.63/Source/lsiutil.tar.gz
  3. Extract that tarball somewhere
  4. Run lsiutil
    1. Select your LSI adapter
    2. Select 21
    3. Select 32
    4. When it asks you about the write cache, enable it (1, I believe)
    5. For all other questions, stick with the default.
  5. Reboot


This setting is persistent, so you'll never need to change this again.   And now the same test:


# time dd if=/dev/zero of=testfile bs=1M count=100

100+0 records in

100+0 records out

real    0m 0.75s

user    0m 0.24s

sys     0m 0.00s


Success!  I'm guessing that not too many people run into this because they run "real" RAID cards?


Re: V center server is unable to find a master vsphere agent in the cluster

$
0
0

cat /var/run/log/fdm-installer.log result below :

 

fdm-installer: [36797967] 2016-10-19 07:10:54: Installing the VIB

fdm-installer: [36797967] 2016-10-19 07:10:57: Result of esxcli software vib install  -v=/tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer/vmware-fdm.vib:  [DependencyError]

fdm-installer:  VIB Nutanix_bootbank_pynfs_5.0.0-0.0.1 violates extensibility rule checks: [u'(line 22: col 0) Element vib failed to validate content']

fdm-installer:  Please refer to the log file for more details.

fdm-installer: [36797967] 2016-10-19 07:10:57: All done! Status: 0

fdm-installer: [36801694] 2016-10-19 07:29:52: Logging to /var/run/log/fdm-installer.log

fdm-installer: [36801694] 2016-10-19 07:29:54: extracting vpx-upgrade-installer/VMware-fdm-eesx-2-linux-1312298.tar.gz...

[36801694] 2016-10-19 07:29:54: exec rm -f /tmp/vmware-root/ha-agentmgr/upgrade

[36801694] 2016-10-19 07:29:54: status = 0

[36801694] 2016-10-19 07:29:54: exec cd /tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer

[36801694] 2016-10-19 07:29:54: status = 0

fdm-installer: [36801694] 2016-10-19 07:29:54: Installing the VIB

fdm-installer: [36801694] 2016-10-19 07:29:56: Result of esxcli software vib install  -v=/tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer/vmware-fdm.vib:  [DependencyError]

fdm-installer:  VIB Nutanix_bootbank_pynfs_5.0.0-0.0.1 violates extensibility rule checks: [u'(line 22: col 0) Element vib failed to validate content']

fdm-installer:  Please refer to the log file for more details.

fdm-installer: [36801694] 2016-10-19 07:29:56: All done! Status: 0

fdm-installer: [36776902] 2016-10-19 23:34:27: Logging to /var/run/log/fdm-installer.log

fdm-installer: [36776902] 2016-10-19 23:34:28: extracting vpx-upgrade-installer/VMware-fdm-eesx-2-linux-1312298.tar.gz...

[36776902] 2016-10-19 23:34:28: exec rm -f /tmp/vmware-root/ha-agentmgr/upgrade

[36776902] 2016-10-19 23:34:29: status = 0

[36776902] 2016-10-19 23:34:29: exec cd /tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer

[36776902] 2016-10-19 23:34:29: status = 0

fdm-installer: [36776902] 2016-10-19 23:34:29: Installing the VIB

fdm-installer: [36776902] 2016-10-19 23:34:30: Result of esxcli software vib install  -v=/tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer/vmware-fdm.vib:  [DependencyError]

fdm-installer:  VIB Nutanix_bootbank_pynfs_5.0.0-0.0.1 violates extensibility rule checks: [u'(line 22: col 0) Element vib failed to validate content']

fdm-installer:  Please refer to the log file for more details.

fdm-installer: [36776902] 2016-10-19 23:34:30: All done! Status: 0

Re: VSAN issue

$
0
0

All hosts are now 6.o update 2 and I am still getting the error that hosts cannot communicate with other nodes in the virtual san enabled cluster.

svhost.exe VMtools

$
0
0

Hi all..


Running Windows 7 VM, CPU jumps to 100% CPU, seen via Task Manager "Show processes from all users"

 

This does not happen immediately, only after installing VMWare tools..

 

Any solutions ?  Killing the process, restarting, and doing other stuff are just workarounds, not a solution...

 

I've created a dump of the affected process. but deem this not a Microsoft problem, but a VMWare fusion problem, because if only happens after installation of this.

 

Running Windows 7 with SP1... I have not added any Windows updates.

 

Screen Shot 2016-10-20 at 11.01.47 am.png

Re: vCD 8.10 and virtual volumes

$
0
0

I got following reply from one of the senior consultant:


It might work but it has never been tested with VCD 8.10.


But I am still awaiting a reply from Dev team

Re: How to disable SSL in VMRC for Linux?

$
0
0

Yes i've used up registry flags, it worked except of that part "[datastore1] vm1/vm1.vmx" which comes without any flag. It just connects to server and let me choose VM manually. So how should I type it to get it work?

There is Windows XP and 512mb of RAM and VMRC freezes sometimes (not often) for about 0.2s, it may be caused also by OS, hardware or network - im not sure. But old VMRC seems to be better there.

Viewing all 185574 articles
Browse latest View live




Latest Images