Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all 181132 articles
Browse latest View live

App Volumes Login Portal Failure

$
0
0

App Volumes Login Portal Failure. Please help.

 

AppVolumesError.JPG


PowerCLI - Query Horizon for Sessions with Username, VDIName, and Connection Status and Search by Username

$
0
0

So I've been all over the internet trying to find a way to create a search variable for a user and pipe that into a command that will search horizon for Sessions where the user matches or is like that variable and then pipe it out to a table.

 

The closes I've gotten is the below

--

$Search = 'John'

#Create Horizon Services object

$HorizonServerServices = $global:DefaultHVServers[0].ExtensionData

#Create Query Definition object with EntityType SessionLocalSummaryView

$HorizonQuery = New-Object VMware.Hv.QueryDefinition

$HorizonQuery.QueryEntityType = 'SessionLocalSummaryView'

#Create Query Service object

$HorizonQueryService = New-Object VMware.Hv.QueryServiceService

#Horizon returns 1000 results at a time, so you have to loop until RemainingCount -eq 0

$HorizonQueryResults = $HorizonQueryService.QueryService_Create($HorizonServerServices, $HorizonQuery)

#Variable to save the returned results

$HorizonSessions = $HorizonQueryResults.Results

 

do

{

$HorizonQueryResults = $HorizonQueryService.QueryService_GetNext($HorizonServerServices,$HorizonQueryResults.Id)

$HorizonSessions += $HorizonQueryResults.Results

} while ($HorizonQueryResults.RemainingCount -gt 0)

 

$SearchHorizonSessions = $HorizonSessions | Where-Object -FilterScript {$_.NamesData.Username -like "*$Search*"}

 

$NamesData = $SearchHorizonSessions.NamesData.Username

 

$SessionData = $SearchHorizonSessions.SessionData.SessionState

 

$NamesData | Foreach {$i=0}{new-object pscustomobject -prop @{Username=$_;SessionsState=$SessionData[$i]}; $i++} | Format-Table

--
This works fine until I try to search it. For some reason it breaks and only gives me one letter of the "SessionState". It also doesn't give me vdi Name which I need.

SessionsState Username                

------------- --------                

            C DOMAIN.LOCAL\John.Doe

 

I've also tried this which gives me all the data but when I try to search or filter it I can't get it to do it.

--

#Query Horizon VMs by logged in User

$query = New-Object "Vmware.Hv.QueryDefinition"

$query.queryEntityType = 'SessionLocalSummaryView'

$qSrv = New-Object "Vmware.Hv.QueryServiceService"

$qSRv.QueryService_Query($global:DefaultHVServers[0].ExtensionData,$query) |

Select -ExpandProperty Results |

Select -ExpandProperty NamesData | where UserName -Like "*$Search*" |

Format-Table -Property UserName,DesktopName,MachineOrRDSServerDNS

--

 

I've also tried messing with Get-HVMachineSummary and I can filter and search it fine but for some reason it does not display the user field. Its just blanklp

 

Any help would be much appreciated

HTML Access Report

$
0
0

I need  to find which users are connecting using HTML access (using web browser).  I believe it's always "Blast" using SSL/443 tunnel.  I'm pretty sure it's logged on security server or connection server.  Looking for the easiest way to extract it and create a report.  For example, from 6/1/20 - 6/30/20 These 458 users connected to vdi using HTML access.

automate vapp property creation with api or ovftool?

$
0
0

hi..

i'm creating a vm via packer automation,  i was wondering if there's after creation to use ovftool or even a direct api call to vcenter to add vapps properties

 

i'm talking about version, vendor, vapp ip (static vs dhcp etc..)

How to add child vCenter to manage subset of hosts

$
0
0

Hello,

I have a single VCSA 6.7 appliance managing hosts in two small data centers.  Each data center has two small clusters in it, with workloads split between the two clusters.  Cluster A in data center 1 has similar workloads to cluster A in data center 2, and cluster B in data center 1 has similar workloads to cluster B in data center 2.

 

I'd like to add a "child" vCenter appliance to this configuration, so that the child vCenter server will only have visibility of the hosts in cluster B of the two data centers.  Ideally, the existing vCenter server would retain its visibility of all the hosts, but it that isn't directly possible, it could do so via it's "parent" relationship of the new "child" vCenter server.  Another option would be for the new vCenter server to become a parent of the existing server.  Either direction is acceptable to me.

 

I'm a little hazy on how to go about this process, specifically with regards to the PSC.  I'm not clear on how to add a new vCenter to the configuration, either as a parent or a child, and how to integrate the two without having to rebuild the existing distributed switches and other settings currently in place.

 

If there are any resources available that describe how to deploy a configuration like this, I'd be grateful for any pointers to them.  Thanks in advance!

Get Build number and Version of vSAN

$
0
0

Is there a way to get the build number and the version of vSAN with its patch level?

DEM Not Applying Default Apps

$
0
0

Hello there,

 

We have a new win 10 1909 environment we're trying to roll out and we're having extreme issues with DEM not applying/saving default apps and FTAs correctly and we cannot figure out why.

 

I have the Default Apps and FTAs flex engine enabled with a predefined forced setting to set Internet Explorer as default browser and to set adobe reader to open PDFs.

 

It seems to save and apply the adobe reader FTA, and it actually seems to map .http and .https files to Internet Explorer, but it only makes IE the default browser about 40-50% of the time, so when we click on a link inside of outlook it opens up in edge.

 

I worked with support and they had me drop the .xml file in the file type association page on DEM as well and like I said that part seems to be applying correctly just not for the default application part.

 

I'll attach several pictures and a log of my latest login to see if that will help any.

 

I do appreciate it!

 

Edit: I apologize, I forgot to list that we are using DEM version 9.11 as well.

vSphere 6 Essentials Upgrades?

$
0
0

I have one ESXi host (6.7) with a vSphere 6 Essentials license. We got the Essentials over free ESXi for backup purposes.

 

Is it necessary to renew our Support & Subscription every year with VMware? I don't need the support but it states we will miss out on the latest updates/upgrades. I am confused on the upgrade part. I can patch ESXi freely so what updates are they referring about?

 

Thank you,


Change device owner programatically?

$
0
0

We have a couple needs for this but has anyone seen any examples thru API's or otherwise that you can change the owner of a device from one person's Network ID to another in WS1?  We have two scenarios:

 

1. We assign shared devices to department manager.  We do use local accounts with their name in it but those people come and go and we have to wipe the device to change the owner in the WS1 console.

 

2. We have a telecom group that deals with leadership phones.  We wanted to do the enroll on a user's behalf but that doesn't work thru managed devices only unmanaged.  It was suggested to enroll the device with the telecom person's credentials and then programatically change it.  Not sure how that would work on the device itself with things like Boxer.

 

Thanks.

 

Steve

dead I/O on igb-nic (ESXi 6.7)

$
0
0

Hi,

 

I'm running a homelab with ESXi 6.7 (13006603). I got three nics in my host, two are onboard and one is an Intel ET 82576 dual-port pci-e card. All nics are assigned to the same vSwitch; actually only one is connected to the (physical) switch atm.

When I'm using one of the 82576 nics and put heavy load on it (like backing up VMs via Nakivo B&R) the nic stops workign after a while and is dead/Not responding anymore. Only a reboot of the host or (much easier) physically reconnecting the nic (cable out, cable in) solves the problem.

 

I was guessing there is a driver issue, so I updated to the latest driver by intel:

 

 

[root@esxi:~] /usr/sbin/esxcfg-nics -l

Name    PCI          Driver      Link Speed      Duplex MAC Address       MTU    Description

vmnic0  0000:04:00.0 ne1000      Down 0Mbps      Half   00:25:90:a7:65:dc 1500   Intel Corporation 82574L Gigabit Network Connection

vmnic1  0000:00:19.0 ne1000      Up   1000Mbps   Full   00:25:90:a7:65:dd 1500   Intel Corporation 82579LM Gigabit Network Connection

vmnic2  0000:01:00.0 igb         Down 0Mbps      Half   90:e2:ba:1e:4d:c6 1500   Intel Corporation 82576 Gigabit Network Connection

vmnic3  0000:01:00.1 igb         Down 0Mbps      Half   90:e2:ba:1e:4d:c7 1500   Intel Corporation 82576 Gigabit Network Connection

[root@esxi:~] esxcli software vib list|grep igb

net-igb                        5.2.5-1OEM.550.0.0.1331820            Intel   VMwareCertified   2019-06-16

igbn                           0.1.1.0-4vmw.670.2.48.13006603        VMW     VMwareCertified   2019-06-07

 

Unfortunately this didn't solve the problem.

 

However ... this behaviour doesn't occur, when I'm using one of the nics using the ne1000 driver.

 

Any idea how to solve the issue?

(... or at least dig down to it's root?)

 

Thanks a lot in advance.

 

Regards

Chris

 

PS: I found another thread which might be connected to my problem: Stopping I/O on vmnic0  Same system behaviour, same driver.

VMware SRM plus additional single site replication?

$
0
0

We have a dual site SRM configuration (Site A-to-Site B pair) using Vsphere replication.  All appliance based with a 8.3 environment. Everything works well.

 

Now we would like to replicate some VM's on Site A from a primary SAN datastore to a secondary SAN datastore ( both SAN's are on Site A). We don't need a protection group/recovery plan for this VM.

 

Is it possible? If so, do I add a 3rd Vsphere Replication appliance to Site A? How it that integrated into the SRM (if this is needed)?

Performing a silent install of 15.5.6 while older version of VMware Workstation running and virtual machines powered on

$
0
0

Is it possible to do a silent install of 15.5.6 while an older version of VMware workstation is running and virtual machines are powered on?

Even after enabling BGP on UI on Tire0-GW, still on the CLI, it shows as BGP as "Administratively shut down".

$
0
0

Even after enabling BGP on UI on Tire0 Gateway, still on the CLI, it shows as BGP as "Administratively shut down".

I am able to ping neighbor address from nsxt-edge1(tier0_sr). Only BGP shows as "Administratively shut down"

Can anyone pls let me know, how to fix this?

Tire-1 gateway is working fine.

 

nsxt-edge01(tier0_sr)> get bgp neighbor

BGP neighbor is 192.168.100.1, remote AS 65100, local AS 65000, external link

Administratively shut down

  BGP version 4, remote router ID 0.0.0.0, local router ID 192.168.100.2

  BGP state = Idle

  Last read 19:53:42, Last write never

  Hold time is 180, keepalive interval is 60 seconds

  Configured hold time is 180, keepalive interval is 60 seconds

  Graceful restart information:

    Local GR Mode  : Helper*

    Remote GR Mode : NotApplicable

    R bit          : False

    Timers :

     Configured Restart Time(sec)  : 180

     Received Restart Time(sec)    : 0

  Message statistics:

    Inq depth is 0

    Outq depth is 0

                         Sent       Rcvd

    Opens:                  0          0

    Notifications:          0          0

    Updates:                0          0

    Keepalives:             0          0

    Route Refresh:          0          0

    Capability:             0          0

    Total:                  0          0

  Minimum time between advertisement runs is 0 seconds

  Update source is 192.168.100.2

 

For address family: IPv4 Unicast

  Not part of any update group

  Community attribute sent to this neighbor(all)

  0 accepted prefixes

 

  Connections established 0; dropped 0

  Last reset never

BGP Connect Retry Timer in Seconds: 10

Read thread: off  Write thread: off

 

 

 

nsxt-edge01(tier0_sr)> ping 192.168.100.1 source 192.168.100.2 repeat 6

PING 192.168.100.1 (192.168.100.1) from 192.168.100.2: 56 data bytes

64 bytes from 192.168.100.1: icmp_seq=0 ttl=64 time=2.020 ms

64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=2.382 ms

64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=2.396 ms

64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=1.961 ms

64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=1.687 ms

64 bytes from 192.168.100.1: icmp_seq=5 ttl=64 time=1.891 ms

 

--- 192.168.100.1 ping statistics ---

6 packets transmitted, 6 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 1.687/2.056/2.396/0.257 ms

 

 

0 Gbps - ESXi 6.5 update 3 host not connecting to storage

$
0
0

Hello,

We have ESXi 6.5 update 3 running on Cisco B200 blades using 6248 Fabric interconnects.

We have purchased new 6454 fabric interconnects and I have moved 1 chassis and 1 blade to the new FIs for testing.

The blade/ESXi host is connecting and pinging on the network good.

However, if I try to rescan storage it takes 30 minutes and fails. If I try to reboot it takes over an hour and doesn't really attach all storage successfully.

If I unmap all storage it reboots and rescans as normal. It sees the array just fine.

 

The zoning is connected at 8 Gbps and the FIs say connected at 8 Gbps.

However, VMware says the speed is 0 Gbps. see below output.

 

I have checked compatibility lists and it seems our fnic, enic, vmware version and ucs version is all compatible.

 

Has anyone seen this?

Any help is much appreciated!

 

 

[root@kcesx9:~] esxcli storage san fc list

   Adapter: vmhba1

   Port ID: 0A3A03

   Node Name: 20:00:00:25:b5:a5:02:df

   Port Name: 20:00:00:25:b5:a1:02:df

   Speed: 0 Gbps

   Port Type: NPort

   Port State: ONLINE

   Model Description:

   Hardware Version:

   OptionROM Version:

   Firmware Version:

   Driver Name:

   DriverVersion:

 

Adapter: vmhba2

   Port ID: 0B1203

   Node Name: 20:00:00:25:b5:a5:02:df

   Port Name: 20:00:00:25:b5:b1:01:df

Speed: 0 Gbps

   Port Type: NPort

   Port State: ONLINE

   Model Description:

   Hardware Version:

   OptionROM Version:

   Firmware Version:

   Driver Name:

   DriverVersion:

==================

 

These are some of the naa's that popped up with connectivity issues.

 

naa.6001738c7c80534900000000000134a8

naa.6001738c7c8053490000000000021977

naa.6001738c7c805349000000000002204c

naa.6001738c7c805349000000000001349f

naa.6001738c7c8053490000000000013499

    

In the logs:

2020-07-06T19:19:51.900Z cpu11:65844)WARNING: HBX: 2580:Failed to cleanup VMFS heartbeaton volume5e604295-151f2b8e-871a-0025b500a516: No connection

 

2020-07-06T19:19:51.900Z cpu23:66148)ScsiDeviceIO: 3015: Cmd(0x439590d03b40) 0x28, CmdSN 0xa from world 74231 to dev "naa.6001738c7c805349000000000002204c" failed H:0x8 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

2020-07-06T19:19:51.900Z cpu23:74231)LVM: 5953: PE grafting failed for device naa.6001738c7c805349000000000002204c:1, vol 5e6079a4-96282218-633b-0025b500a516/7688724183283841769: Timeout

2020-07-06T19:19:51.900Z cpu11:65844)WARNING: HBX: 2580: Failed to cleanup VMFS heartbeat on volume5e604295-151f2b8e-871a-0025b500a516: No connection

2020-07-06T19:19:51.900Z cpu11:65844)Vol3: 3073: Error closing the volume: No connection. Eviction fails.

List of VMware Workstation Beta Builds

$
0
0
versiontypebuild datefileMD5
16.0.020H2 July tech preview165403212020-07-09VMware-workstation-full-e.x.p-16540321.exe94e49033708b164bdc0479f7cc3d701a
16.0.020H2 July tech preview165403212020-07-09VMware-Workstation-Full-e.x.p-16540321.x86_64.bundled87f10945332cb8d54b7cd5d2c326ef7
16.0.020H2 tech preview162272672020-05-18VMware-workstation-full-e.x.p-16227267.exed5f9435249c4ea97879cebd3c06f2071
16.0.020H2 tech preview162272672020-05-18VMware-Workstation-Full-e.x.p-16238816.x86_64.bundle68dd459f23cfe5dd683fcc4850715415
16.0.020H1 tech preview156790482020-02-26VMware-workstation-full-e.x.p-15679048.exe098bbbc1da34f0e83b8ac75dc85a7ba8
16.0.020H1 tech preview154883062020-01-21VMware-workstation-full-e.x.p-15488306.exe79c109563c5bf3ee1f5a15666c786865
15.0.0technology preview88889022018-06-20VMware-workstation-full-e.x.p-8888902.exe8cf17ab8b7361e5e0c87def30280ddd4
15.0.0technology preview88889022018-06-20VMware-Workstation-Full-e.x.p-8888902.x86_64.bundle5c0540724b0ff00fc19fd7106a72838d
14.0.0technology preview60561102017-07-17VMware-workstation-full-e.x.p-6056110.exe8e4638c2e3a208f0b82bddc8cc195dc1
14.0.0technology preview60561102017-07-17VMware-Workstation-Full-e.x.p-6056110.x86_64.bundleab2f5df6d1090e3e4c21ef7e1759ba57
12.0.0technology preview28822842015-07-10VMware-workstation-full-e.x.p-2882284.exec92a1cda3c3afb899be72ec6ad372873
12.0.0technology preview28822842015-07-10VMware-Workstation-Full-e.x.p-2882284.x86_64.bundle4167eeb019faef7917966d3adb7c2ff0
11.0.0technology preview19460492014-07-03VMware-workstation-full-e.x.p-1946049.exe6fa5ea7b12469d4635b19c5efe2cf301
11.0.0technology preview19460492014-07-03VMware-Workstation-Full-e.x.p-1946049.x86_64.bundle66322cb1b377f66ef468814edee92e6e
11.0.0technology preview18292212014-05-20VMware-workstation-full-e.x.p-1829221.exe030771bed35ea7c9f337d87166e8dd9c
11.0.0technology preview18292212014-05-20VMware-Workstation-Full-e.x.p-1829221.x86_64.bundle0ec305930a61cdd6cb141b90dd9b5702
10.0.0technology preview12458162013-07-29VMware-workstation-full-e.x.p-1245816.exe79ef5dfaacec4bd2f6348b33aa16a0b8
10.0.0technology preview12458162013-07-29VMware-Workstation-Full-e.x.p-1245816.i386.bundle43a5619b003e9bad52821cdf01a03cc8
10.0.0technology preview12458162013-07-29VMware-Workstation-Full-e.x.p-1245816.x86_64.bundle69bd032ea3201cc9d29c818bf9da6bd7
09.1.0technology preview11403542013-05-20VMware-workstation-full-e.x.p-1140354.exeb40a9e450336c8ad07d7b3f0bb29746f
09.1.0technology preview11403542013-05-20VMware-Workstation-Full-e.x.p-1140354.i386.bundle3c41726a43418143bad1cf389d982ce4
09.1.0technology preview11403542013-05-20VMware-Workstation-Full-e.x.p-1140354.x86_64.bundle2004e80d718ad079212496fd67bef06b
09.0.0technology preview7903082012-07-23VMware-workstation-full-e.x.p-790308.exe1a8c77b924b29b323483024f3fc864ae
09.0.0technology preview7903082012-07-23VMware-Workstation-Full-e.x.p-790308.i386.bundle3a8bdb14348ea046af40c7b12d2c3333
09.0.0technology preview7903082012-07-23VMware-Workstation-Full-e.x.p-790308.x86_64.bundle11eff2637dec94ddc46f4b48249f1853
08.1.0technology preview7540352012-06-18VMware-workstation-Full-e.x.p-754035.exef3f5e2ef1ae890f902650b6190a8750a
08.1.0technology preview7540352012-06-18VMware-Workstation-Full-e.x.p-754035.i386.bundlea1106d857e5e18d828177ed853e4b658
08.1.0technology preview7540352012-06-18VMware-Workstation-Full-e.x.p-754035.x86_64.bundlee6ddfac9979f1d170645094caee87a53
08.1.0technology preview6466432012-03-12VMware-workstation-full-e.x.p-646643.exe955423ace552c18b0f4aa6dd35577de6
08.1.0technology preview6466432012-03-12VMware-Workstation-Full-e.x.p-646643.i386.bundle8def0f09859b0f5cd298d76265d0e19d
08.1.0technology preview6466432012-03-12VMware-Workstation-Full-e.x.p-646643.x86_64.bundledbb53a888f82f90198e8c9bb3ea528bd
08.0.0beta4348292012-03-12VMware-workstation-full-e.x.p-434829.exe14b2ed114ab49e87c128f777fdb9e51d
08.0.0beta4348292012-03-12VMware-Workstation-Full-e.x.p-434829.i386.bundle32fea3708a0f5895e44c409c6d0cba35
08.0.0beta4348292012-03-12VMware-Workstation-Full-e.x.p-434829.x86_64.bundle74ecf0cb75cbec5d63359bdf48e19f85
08.0.0beta3892822011-04-06VMware-workstation-full-e.x.p-389282.exea675bdbb11a5c2131bfbeae5f40bb603
08.0.0beta3892822011-04-06VMware-Workstation-Full-e.x.p-389282.i386.bundle9f9aeb2666d3564826f162100747380a
08.0.0beta3892822011-04-06VMware-Workstation-Full-e.x.p-389282.x86_64.bundle26b85b237ae2bf1b83cb73a79fc7b798
07.1.0rc 22565572010-05-05VMware-workstation-7.1.0-256557.execd88a4cd73d34bdf7f15967ede4db537
07.1.0rc 22565572010-05-05VMware-Workstation-7.1.0-256557.i386.bundle51e8b6589d1611e8a669314737f2e860
07.1.0rc 22565572010-05-05VMware-Workstation-7.1.0-256557.x86_64.bundle75fbf5237a30817462fd9965e040805c
07.1.0rc2548072010-05-04VMware-workstation-7.1.0-254807.exe59d8120c371eb91008ff868f602ddbdd
07.1.0rc2548072010-05-04VMware-Workstation-7.1.0-254807.i386.bundleb74f6ff8bd76f7ed32010c2f0cf7d2a1
07.1.0rc2548072010-05-04VMware-Workstation-7.1.0-254807.x86_64.bundle57fd2d1d694466f51ad67b4824717c47
07.1.0rc2548072010-05-04VMware-workstation-full-7.1.0-254807.exef0786658939292503add333e17a9b864
07.1.0rc2548072010-05-04VMware-Workstation-Full-7.1.0-254807.i386.bundle0bf04884e238057ef1db522470415b77
07.1.0rc2548072010-05-04VMware-Workstation-Full-7.1.0-254807.x86_64.bundle2d62e6e8566c47c8521a35070561c1ec
07.1.0beta2402422010-03-12VMware-workstation-e.x.p-240242.exec54badd321f20ca5cafde2dbb49df47e
07.1.0beta2402422010-03-12VMware-Workstation-e.x.p-240242.i386.bundle04850a2468404d07b7d5587eb812295f
07.1.0beta2402422010-03-12VMware-Workstation-e.x.p-240242.x86_64.bundle89a73f4083039f6fb945057ccba8d905
07.1.0beta2402422010-03-12VMware-workstation-full-e.x.p-240242.exe327527a7f68b30db162a9777ccdd7f57
07.1.0beta2402422010-03-12VMware-Workstation-Full-e.x.p-240242.i386.bundle5e84108c85040beee41e18fc972b1909
07.1.0beta2402422010-03-12VMware-Workstation-Full-e.x.p-240242.x86_64.bundleb1a171e9a820680414f40ec96b121d5a
07.0.0rc1971242009-10-02VMware-workstation-7.0.0-197124.exef0e3f037913db6932c84674796b3e54f
07.0.0rc1971242009-10-02VMware-Workstation-7.0.0-197124.i386.bundlef4a9d97fc239b20a3e8cfd70e70dfd37
07.0.0rc1971242009-10-02VMware-Workstation-7.0.0-197124.x86_64.bundle5a0577d85904372cd19ff64f4cfa350e
07.0.0rc1971242009-10-02VMware-workstation-full-7.0.0-197124.exe85a04b0d255b2969612d1c3ec7bdc92a
07.0.0rc1971242009-10-02VMware-Workstation-full-7.0.0-197124.i386.bundle75c9452ba139cd907559cdd5d2151c9e
07.0.0rc1971242009-10-02VMware-Workstation-full-7.0.0-197124.x86_64.bundle1a31e3f1946e1f88d64547102c077025
07.0.0technology preview1855172009-08-21VMware-workstation-e.x.p-185517.exef35da33a0a0cf9d79e6a9bb79c153295
07.0.0technology preview1855172009-08-21VMware-Workstation-e.x.p-185517.i386.bundle613aa98877b1323fac37312a32dcf970
07.0.0technology preview1855172009-08-21VMware-Workstation-e.x.p-185517.x86_64.bundle3a134c12c29cc101cc98d9d419706b86
07.0.0technology preview1696122009-06-05VMware-workstation-e.x.p-169612.exe598442b70cced1a145bffd60df535e93
07.0.0technology preview1696122009-06-05VMware-Workstation-e.x.p-169612.i386.bundle08b133eb3e2bb0b59fd58222e0201dc0
07.0.0technology preview1696122009-06-05VMware-Workstation-e.x.p-169612.x86_64.bundle9cc1f9e82fba7340d90515a411c191fb
06.5.0rc1100682008-08-14VMware-workstation-6.5.0-110068.exe418838f107c5e6426529dc99850610cc
06.5.0rc1100682008-08-14VMware-Workstation-6.5.0-110068.i386.bundlebd29f702500571affb5012c63b5a1bdf
06.5.0rc1100682008-08-14VMware-Workstation-6.5.0-110068.i386.rpm71b9afbc8131b66ba446b740b55fa1a7
06.5.0rc1100682008-08-14VMware-Workstation-6.5.0-110068.x86_64.bundlefd7bf28253cf44abe1647b46c3379593
06.5.0rc1100682008-08-14VMware-Workstation-6.5.0-110068.x86_64.rpmeb0b27213a48f61420b1fb2972db984c
06.5.0beta 2995302008-06-23VMware-workstation-e.x.p-99530.exeaeb4355515d37da7a9c6c7b0e795b72f
06.5.0beta 2995302008-06-23VMware-Workstation-e.x.p-99530.i386.bundle657d5737fe66bcfd01eb8ced19b2b0a6
06.5.0beta 2995302008-06-23VMware-workstation-e.x.p-99530.i386.tar.gz15d2bba46bc463083037ff274fac5850
06.5.0beta 2995302008-06-23VMware-Workstation-e.x.p-99530.x86_64.bundle17d86755c7160b57fad2d00289956842
06.5.0beta 2995302008-06-23VMware-workstation-e.x.p-99530.x86_64.tar.gza5c7b5d6047268377e015e2127cd52ad
06.5.0beta911822008-05-12VMware-workstation-e.x.p-91182.exe0f430fbad606afe9eaf39de71683b02f
06.5.0beta911822008-05-12VMware-workstation-e.x.p-91182.i386.rpmb7f590f969fa93aec8e8b4b67820083a
06.5.0beta911822008-05-12VMware-workstation-e.x.p-91182.i386.tar.gz114e6f529f22ab037c2887758eef25d3
06.5.0beta911822008-05-12VMware-workstation-e.x.p-91182.x86_64.rpm9784c04ae887e6ec1c46f4de551fd962
06.5.0beta911822008-05-12VMware-workstation-e.x.p-91182.x86_64.tar.gz3305c109e22ad2a51479989d463995cd
06.5.0beta841132008-04-01VMware-workstation-e.x.p-84113.exeaeb342277606c4021afe8df7611f9f26
06.5.0beta841132008-04-01VMware-workstation-e.x.p-84113.i386.rpm7ae8bf4f7ffaa7d3e9755aa7bc07d34b
06.5.0beta841132008-04-01VMware-workstation-e.x.p-84113.i386.tar.gz96685975ca7696a4f994e885dd8b3bdc
06.5.0beta841132008-04-01VMware-workstation-e.x.p-84113.x86_64.rpm782f3ef1bd11d57996457c8c82438ced
06.5.0beta841132008-04-01VMware-workstation-e.x.p-84113.x86_64.tar.gz1b7bef3a8e2396f4853b12d39fb5d98c
06.0.1beta51447VMware-workstation-6.0.1-51477.exe
06.0.1beta51447VMware-workstation-6.0.1-51477.i386.rpm
06.0.1beta51447VMware-workstation-6.0.1-51477.i386.tar.gz
06.0.1beta51447VMware-workstation-6.0.1-51477.x86_64.rpm
06.0.1beta51447VMware-workstation-6.0.1-51477.x86_64.tar.gz
06.0.1beta51447VMware-workstation-e.x.p-51477.exe
06.0.1beta51447VMware-workstation-e.x.p-51477.i386.rpm
06.0.1beta51447VMware-workstation-e.x.p-51477.i386.tar.gz
06.0.1beta51447VMware-workstation-e.x.p-51477.x86_64.rpm
06.0.1beta51447VMware-workstation-e.x.p-51477.x86_64.tar.gz
06.0.0rc444262007-04-14VMware-workstation-6.0.0-44426.exeebb8b3b1cbba529b6feea8fd73286db2
06.0.0rc444262007-04-14VMware-workstation-6.0.0-44426.i386.rpmb529eebf01fdbf3b5834a51db064aba6
06.0.0rc444262007-04-14VMware-workstation-6.0.0-44426.i386.tar.gz5b838413a899385f868e6e86058a933d
06.0.0rc444262007-04-14VMware-workstation-6.0.0-44426.x86_64.rpme13a396314d324ed04efcd3192aa3e59
06.0.0rc427572007-03-21VMware-workstation-e.x.p-42757.exebcfe765be0fdfab22c5f9efd12c52abc
06.0.0rc427572007-03-21VMware-workstation-e.x.p-42757.i386.rpm30f9eb49faec0e5e3200a43f941d4ce0
06.0.0rc427572007-03-21VMware-workstation-e.x.p-42757.i386.tar.gz8df15c82605f7a21c73bc25eaee94c48
06.0.0rc427572007-03-21VMware-workstation-e.x.p-42757.x86_64.rpmfff7a180a3c6d7ed90c4c932a642103b
06.0.0beta 3398492007-02-08VMware-workstation-e.x.p-39849.exe1ac91449a2828ef54c1644f2d090ad19
06.0.0beta 3398492007-02-08VMware-workstation-e.x.p-39849.i386.rpmf8b270728983c4e23bd367b8fb96d0fc
06.0.0beta 3398492007-02-08VMware-workstation-e.x.p-39849.i386.tar.gz8f875f109eda2d05a77cbb522f5c0fb4
06.0.0beta 3398492007-02-08VMware-workstation-e.x.p-39849.x86_64.rpm8f25831232a83a86b6ced708cf6306b3
06.0.0beta 2369832006-12-20VMware-workstation-e.x.p-36983.exed13ea65ae63868cb1570fb292a0fc5e1
06.0.0beta 2369832006-12-20VMware-workstation-e.x.p-36983.i386.rpm9b5e02c47ea151f05e3ea7b6b6c6cf6b
06.0.0beta 2369832006-12-20VMware-workstation-e.x.p-36983.i386.tar.gzb3a654297e1506233bc3b2e51afaa89b
06.0.0beta 2369832006-12-20VMware-workstation-e.x.p-36983.x86_64.rpm4d027a2e33c058600dbb83772e43143a
06.0.0beta 1339752006-11-03VMware-workstation-e.x.p-33975.exe
06.0.0beta 1339752006-11-03VMware-workstation-e.x.p-33975.i386.rpm
06.0.0beta 1339752006-11-03VMware-workstation-e.x.p-33975.i386.tar.gz
06.0.0beta 1339752006-11-03VMware-workstation-e.x.p-33975.x86_64.rpm
06.0.0experimental324702006-10-16VMware-workstation-e.x.p-32470.exe
06.0.0experimental324702006-10-16VMware-workstation-e.x.p-32470.i386.rpm
06.0.0experimental324702006-10-16VMware-workstation-e.x.p-32470.i386.tar.gz
06.0.0experimental324702006-10-16VMware-workstation-e.x.p-32470.x86_64.rpm
05.5.0rc 2180072005-11-03VMware-workstation-5.5.0-18007.exe6fb912075f65701a72736708d5ffd24f
05.5.0rc 2180072005-11-03VMware-workstation-5.5.0-18007.i386.rpmdf4fe57c8e8650b529f8cbb1226b6b2d
05.5.0rc 2180072005-11-03VMware-workstation-5.5.0-18007.tar.gz
05.5.0rc 1169582005-09-29VMware-workstation-5.5.0-16958.exe33335e4f63da291c7d936b05d1ae7285
05.5.0rc 1169582005-09-29VMware-workstation-5.5.0-16958.i386.rpm
05.5.0rc 1169582005-09-29VMware-workstation-5.5.0-16958.tar.gz
05.5.0beta 2163252005-09-07VMware-workstation-e.x.p-16325.exe3330797b8fcc1f1b1a5a228b3aaeb2c4
05.5.0beta 2163252005-09-07VMware-workstation-e.x.p-16325.i386.rpm
05.5.0beta 2163252005-09-07VMware-workstation-e.x.p-16325.tar.gz04619d62d881510e26a6407c4fe7fa7c
05.5.0beta 1155762005-08-16VMware-workstation-e.x.p-15576.exe7c4da2b42f39eba3f7eb3606fb75c363
05.5.0beta 1155762005-08-16VMware-workstation-e.x.p-15576.i386.rpm7e024e04841f41f8300c8c84d9799324
05.5.0beta 1155762005-08-16VMware-workstation-e.x.p-15576.tar.gz2230be1c2abd12eec4ba93b35a904296
05.1.0beta147042005-08-04VMware-workstation-5.1.0-14704.exe
05.1.0beta147042005-08-04VMware-workstation-5.1.0-14704.i386.rpm
05.1.0beta147042005-08-04VMware-workstation-5.1.0-14704.tar.gz
05.1.0beta147042005-08-04VMware-workstation-e.x.p-14704.exe
05.1.0beta147042005-08-04VMware-workstation-e.x.p-14704.i386.rpm
05.1.0beta147042005-08-04VMware-workstation-e.x.p-14704.tar.gz
05.0.0rc 3 update 1130142005-03-16VMware-workstation-5.0.0-13014.exe0622058ffb729fae362caf01fc17412a
05.0.0rc 3 update 1130142005-03-16VMware-workstation-5.0.0-13014.i386.rpm2dd805e43467628b6c6802aee9c3d1d6
05.0.0rc 3 update 1130142005-03-16VMware-workstation-5.0.0-13014.tar.gz07bdad44f232a49abb57d0f8fc2100a5
05.0.0rc 3128882005-03-10VMware-workstation-5.0.0-12888.exe145f24054e0e6471209fac1b50d584b5
05.0.0rc 3128882005-03-10VMware-workstation-5.0.0-12888.i386.rpm
05.0.0rc 3128882005-03-10VMware-workstation-5.0.0-12888.tar.gz
05.0.0rc 2125442005-02-19VMware-workstation-5.0.0-12544.exed9db684c2e3074420ff92030a5957d02
05.0.0rc 2125442005-02-19VMware-workstation-5.0.0-12544.i386.rpmdec471ab406305efe311f5b6f03b18d0
05.0.0rc 2125442005-02-19VMware-workstation-5.0.0-12544.tar.gz
05.0.0rc 1122062005-01-27VMware-workstation-5.0.0-12206.exe42bd65db6f7cc44fba6f2c58235f7fe8
05.0.0rc 1122062005-01-27VMware-workstation-5.0.0-12206.i386.rpm8ec85ad56f0f9e6a588912a7253e4488
05.0.0rc 1122062005-01-27VMware-workstation-5.0.0-12206.tar.gz52da39c5abc8499be2f03073a8c0a44d
05.0.0beta 3118882005-01-06VMware-workstation-e.x.p-11888.exe356890e85582a997dd3cb3f7b889ed01
05.0.0beta 3118882005-01-06VMware-workstation-e.x.p-11888.i386.rpmc7f9cf2e9d0c9c30ce31f1a8daf10fe9
05.0.0beta 3118882005-01-06VMware-workstation-e.x.p-11888.tar.gz4bd2226e4d411b7c8fff86bc7dbc5cd1
05.0.0beta 2116082004-12-15VMware-workstation-e.x.p-11608.exe98f481d92c6c756d85faf4135c2de7e9
05.0.0beta 2116082004-12-15VMware-workstation-e.x.p-11608.i386.rpm08781da927c263532a80c9c7b6ac8452
05.0.0beta 2116082004-12-15VMware-workstation-e.x.p-11608.tar.gzde72219c9356c93a09efe055003b6b9a
05.0.0beta 1107372004-10-25VMware-workstation-e.x.p-10737.exe50a8b9e63f7122318445a1feda8e373f
05.0.0beta 1107372004-10-25VMware-workstation-e.x.p-10737.i386.rpm085c33973bb56a38b61cd245f5719e55
05.0.0beta 1107372004-10-25VMware-workstation-e.x.p-10737.tar.gzaf58a09919a084fe38a6b60328542646
05.0.0experimental101312004-09-18VMware-workstation-e.x.p-10131.exe
05.0.0experimental101312004-09-18VMware-workstation-e.x.p-10131.i386.rpm
05.0.0experimental101312004-09-18VMware-workstation-e.x.p-10131.tar.gz
04.5.2rc87072004-06-04VMware-workstation-4.5.2-8707.exe
04.5.2rc87072004-06-04VMware-workstation-4.5.2-8707.i386.rpm
04.5.2rc87072004-06-04VMware-workstation-4.5.2-8707.tar.gz
04.5.2rc87072004-06-04VMware-workstation-e.x.p-8707.exe
04.5.2rc87072004-06-04VMware-workstation-e.x.p-8707.i386.rpm
04.5.2rc87072004-06-04VMware-workstation-e.x.p-8707.tar.gz
04.5.2beta 283842004-05-14VMware-workstation-4.5.2-8384.exe
04.5.2beta 283842004-05-14VMware-workstation-4.5.2-8384.i386.rpm
04.5.2beta 283842004-05-14VMware-workstation-4.5.2-8384.tar.gz
04.5.2beta 283842004-05-14VMware-workstation-e.x.p-8384.exe
04.5.2beta 283842004-05-14VMware-workstation-e.x.p-8384.i386.rpm
04.5.2beta 283842004-05-14VMware-workstation-e.x.p-8384.tar.gz
04.5.0rc 371742004-02-05VMware-workstation-4.5.0-7174.exe
04.5.0rc 371742004-02-05VMware-workstation-4.5.0-7174.i386.rpm
04.5.0rc 371742004-02-05VMware-workstation-4.5.0-7174.tar.gz
04.5.0rc 270702004-01-22VMware-workstation-4.5.0-7070.exe
04.5.0rc 270702004-01-22VMware-workstation-4.5.0-7070.i386.rpm
04.5.0rc 270702004-01-22VMware-workstation-4.5.0-7070.tar.gz
04.5.0rc 169792004-01-16VMware-workstation-e.x.p-6979.exe
04.5.0rc 169792004-01-16VMware-workstation-e.x.p-6979.i386.rpm
04.5.0rc 169792004-01-16VMware-workstation-e.x.p-6979.tar.gz
04.1.0beta 268022003-12-19VMware-workstation-e.x.p-6802.exe
04.1.0beta 268022003-12-19VMware-workstation-e.x.p-6802.i386.rpm
04.1.0beta 268022003-12-19VMware-workstation-e.x.p-6802.tar.gz
04.1.0beta 1 refresh66392003-12-06VMware-workstation-e.x.p-6639.exe
04.1.0beta 1 refresh66392003-12-06VMware-workstation-e.x.p-6639.i386.rpm
04.1.0beta 1 refresh66392003-12-06VMware-workstation-e.x.p-6639.tar.gz
04.1.0beta 165682003-11-26VMware-workstation-e.x.p-6568.exe
04.1.0beta 165682003-11-26VMware-workstation-e.x.p-6568.i386.rpm
04.1.0beta 165682003-11-26VMware-workstation-e.x.p-6568.tar.gz
04.0.1experimental62402003-11-08VMware-workstation-e.x.p-6240.exe
04.0.1experimental62402003-11-08VMware-workstation-e.x.p-6240.i386.rpm
04.0.1experimental62402003-11-08VMware-workstation-e.x.p-6240.tar.gz
04.0.1rc 252432003-07-15VMware-workstation-4.0.0-5243.exe
04.0.1rc 252432003-07-15VMware-workstation-4.0.0-5243.i386.rpm
04.0.1rc 252432003-07-15VMware-workstation-4.0.0-5243.tar.gz
04.0.1rc51992003-07-10VMware-workstation-4.0.0-5199.exe
04.0.1rc51992003-07-10VMware-workstation-4.0.0-5199.i386.rpm
04.0.1rc51992003-07-10VMware-workstation-4.0.0-5199.tar.gz
04.0.1alpha refresh51412003-07-04VMware-workstation-4.0.0-5141.exe
04.0.1alpha refresh51412003-07-04VMware-workstation-4.0.0-5141.i386.rpm
04.0.1alpha refresh51412003-07-04VMware-workstation-4.0.0-5141.tar.gz
04.0.0alpha48072003-05-24VMware-workstation-4.0.0-4807.exe
04.0.0alpha48072003-05-24VMware-workstation-4.0.0-4807.i386.rpm
04.0.0alpha48072003-05-24VMware-workstation-4.0.0-4807.tar.gz
04.0.0rc 344562003-04-02VMware-workstation-4.0.0-4456.exe
04.0.0rc 344562003-04-02VMware-workstation-4.0.0-4456.i386.rpm
04.0.0rc 344562003-04-02VMware-workstation-4.0.0-4456.tar.gz
04.0.0rc 344562003-04-02VMware-workstation-e.x.p-4456.exe
04.0.0rc 344562003-04-02VMware-workstation-e.x.p-4456.i386.rpm
04.0.0rc 344562003-04-02VMware-workstation-e.x.p-4456.tar.gz
04.0.0rc 243882003-03-27VMware-workstation-e.x.p-4388.exea0db8ac2a1fc991ce8fc80f9ea3b1095
04.0.0rc 243882003-03-27VMware-workstation-e.x.p-4388.i386.rpm
04.0.0rc 243882003-03-27VMware-workstation-e.x.p-4388.tar.gz
04.0.0rc 143202003-03-22VMware-workstation-e.x.p-4320.exe718f9d12319a8539efc5ce61d7ea815b
04.0.0rc 143202003-03-22VMware-workstation-e.x.p-4320.i386.rpm
04.0.0rc 143202003-03-22VMware-workstation-e.x.p-4320.tar.gz
04.0.0beta 342572003-03-13VMware-workstation-e.x.p-4257.exe
04.0.0beta 342572003-03-13VMware-workstation-e.x.p-4257.i386.rpm
04.0.0beta 342572003-03-13VMware-workstation-e.x.p-4257.tar.gz
04.0.0beta 241832003-02-28VMware-workstation-e.x.p-4183.exeeabb2cedca3aeec2d29ec39ef7717f3d
04.0.0beta 241832003-02-28VMware-workstation-e.x.p-4183.i386.rpm
04.0.0beta 241832003-02-28VMware-workstation-e.x.p-4183.tar.gz
04.0.0beta 141212003-02-20VMware-workstation-e.x.p-4121.exe06fb9d85c11a0fb0b60c155416d5c67d
04.0.0beta 141212003-02-20VMware-workstation-e.x.p-4121.i386.rpm
04.0.0beta 141212003-02-20VMware-workstation-e.x.p-4121.tar.gz
04.0.0experimental40992003-02-13VMware-workstation-e.x.p-4099.exe
04.0.0experimental40992003-02-13VMware-workstation-e.x.p-4099.i386.rpm
04.0.0experimental40992003-02-13VMware-workstation-e.x.p-4099.tar.gz
04.0.0experimental39812003-01-29VMware-workstation-e.x.p-3981.exe
04.0.0experimental39812003-01-29VMware-workstation-e.x.p-3981.i386.rpm
04.0.0experimental39812003-01-29VMware-workstation-e.x.p-3981.tar.gz
03.2.0beta2160VMware-workstation-3.2.0-2160.exe
03.2.0beta2160VMware-workstation-3.2.0-2160.i386.rpm
03.2.0beta2160VMware-workstation-3.2.0-2160.tar.gz
03.2.0beta20822002-07-18VMware-workstation-3.2.0-2082.exe
03.2.0beta20822002-07-18VMware-workstation-3.2.0-2082.i386.rpm
03.2.0beta20822002-07-18VMware-workstation-3.2.0-2082.tar.gz
03.1.0beta17462002-03-27VMware-workstation-3.1.0-1746.exe
03.1.0beta17462002-03-27VMware-workstation-3.1.0-1746.i386.rpm
03.1.0beta17462002-03-27VMware-workstation-3.1.0-1746.tar.gz
03.1.0beta16512002-02-20VMware-workstation-3.1.0-1651.exe
03.1.0beta16512002-02-20VMware-workstation-3.1.0-1651.i386.rpm
03.1.0beta16512002-02-20VMware-workstation-3.1.0-1651.tar.gz
03.0.0rc14532001-10-31VMwareWorkstation-3.0.0-1453.exeaf77123e988acec66d5ac00ea9ef7f80
03.0.0rc14532001-10-31VMwareWorkstation-3.0.0-1453.i386.rpm97284067ca404e1d007776cd006ac4fc
03.0.0rc14532001-10-31VMwareWorkstation-3.0.0-1453.tar.gz7a3dacd8db9e67cb850b5a6c9760314f
03.0.0rc14472001-10-26VMwareWorkstation-3.0.0-1447.exe9e0f4af320429eb32185b603fbf0dfa4
03.0.0rc14472001-10-26VMwareWorkstation-3.0.0-1447.i386.rpm17ae8fc597b8a13cae9ccbec8b62a2ec
03.0.0rc14472001-10-26VMwareWorkstation-3.0.0-1447.tar.gz0c912f3386558dc04c634dc91b6b61e8
03.0.0rc14322001-10-17VMwareWorkstation-3.0.0-1432.exe12cfe602f3921c6fd1ce18b85ff31414
03.0.0rc14322001-10-17VMwareWorkstation-3.0.0-1432.i386.rpm2c4c6c7dbe3815cabf4fa6ff507b2d52
03.0.0rc14322001-10-17VMwareWorkstation-3.0.0-1432.tar.gz3d459d4f2ef8c0ed1e3a98880410b1ce
03.0.0beta14242001-10-13VMwareWorkstation-3.0.0-1424.exeb18100fbab3bf6839f0315ab6410273f
03.0.0beta14242001-10-13VMwareWorkstation-3.0.0-1424.i386.rpmc324fb043c75f335c1a71cfc38558999
03.0.0beta14242001-10-13VMwareWorkstation-3.0.0-1424.tar.gzbd74e1da804a6b2347aef49ff543f845
03.0.0beta13942001-09-19VMware-3.0.0-1394.exed7c3d9e5e3bbf1a39a74ad1858ca4808
03.0.0beta13942001-09-19VMwareWorkstation-3.0.0-1394.i386.rpmfe3a0827d0afaf3446e0cb6280d69d0a
03.0.0beta13942001-09-19VMwareWorkstation-3.0.0-1394.tar.gzf397f8d8dd035e25037a472adc1b9b6c
03.0.0beta13642001-09-04VMware-3.0.0-1364.exec07605ea1c073fabe1ce6b73fedb8d66
03.0.0beta13642001-09-04VMwareWorkstation-3.0.0-1364.i386.rpm91c6f5d2449003846d428ac7f2cb8705
03.0.0beta13642001-09-04VMwareWorkstation-3.0.0-1364.tar.gzc0c42b59f573b02c07fd43b1bfa6f07b
02.0.4experimental12262001-06-22VMware-e.x.p-1226.exe
02.0.4experimental12262001-06-22VMware-e.x.p-1226.i386.rpm
02.0.4experimental12262001-06-22VMware-e.x.p-1226.tar.gz
02.0.4rc11182001-05-03VMware-2.0.4-1118.exeabaf8ed4f35015b36100bf47c8d5e689
02.0.4rc11182001-05-03VMware-2.0.4-1118.i386.rpm1e5a545e1a554217604e4addd42bcf03
02.0.4rc11182001-05-03VMware-2.0.4-1118.tar.gzce8b5b15a83d2dff036d6710a3f534ba
02.0.3rc7862000-10-27VMware-2.0.3-786.exe27bf1ca1ead23218d64cfe7070466c98
02.0.3rc7862000-10-27VMware-2.0.3-786.i386.rpmdee9a6df32301cf135cbef0a1ef4a045
02.0.3rc7862000-10-27VMware-2.0.3-786.tar.gz42bed9b282ce3822304030021cedceb9
02.0.3beta7742000-10-24VMware-2.0.3-774.exef194e8ee17a0ed8ba6532359f8ea70aa
02.0.3beta7742000-10-24VMware-2.0.3-774.i386.rpmc77ad72a3af85494fcd6960610916cf1
02.0.3beta7742000-10-24VMware-2.0.3-774.tar.gz7a3479b79cb0f1a1b1676ae435b6c588
02.0.3beta6372000-07-31VMware-e.x.p-637.exe110bdf50e5d44e7e101767d1f5ac351f
02.0.3beta6372000-07-31VMware-e.x.p-637.i386.rpm
02.0.3beta6372000-07-31VMware-e.x.p-637.tar.gz8001cd3cd31a9bcbd45de62c8d52890e
02.0.1rc 25592000-06-13VMware-2.0.1-559.exe6c1711c077a629a86fc0b0d2c8befd50
02.0.1rc 25592000-06-13VMware-2.0.1-559.i386.rpmf5ec439b464720d9bcd6357a854a025f
02.0.1rc 25592000-06-13VMware-2.0.1-559.tar.gzd0e5836c72a7ee5e07efb45835942b0a
02.0.1rc 15572000-06-09VMware-2.0.1-557.exea1905c20b1e69e2a7d78e2e46e3c0324
02.0.1rc 15572000-06-09VMware-2.0.1-557.i386.rpm85263fbf493028f0e0b8e6f0c8f36b1c
02.0.1rc 15572000-06-09VMware-2.0.1-557.tar.gzd460b74d9b98386a002a02484066a797
02.0.1beta5462000-05-26VMware-2.0.1-546.exe61412de3090eae00cb8e972c1ff64b25
02.0.1beta5462000-05-26VMware-2.0.1-546.i386.rpm0404ffd26a484e9e193a13efc6938238
02.0.1beta5462000-05-26VMware-2.0.1-546.tar.gz88ede310f71eee30ca15375ba90fca9a
02.0.0rc 24752000-03-01VMware-2.0-475.exea7a226044c8262012bcd07a7270b52c6
02.0.0rc 24752000-03-01VMware-2.0-475.i386.rpm2ce27bce72ce8e3466c129573da4c80d
02.0.0rc 24752000-03-01VMware-2.0-475.tar.gze97c01d3717f0a8c04e5dc1eca403c62
02.0.0rc 14682000-02-22VMware-2.0-468.exe636e59e58bd493517f8469f34b48b9f2
02.0.0rc 14682000-02-22VMware-2.0-468.i386.rpm1c0c527a8fa423637afe903346c0e207
02.0.0rc 14682000-02-22VMware-2.0-468.tar.gzb78786800caca6db62c863791b20685b
02.0.0beta4622000-02-14VMware-2.0-462.exe
02.0.0beta4622000-02-14VMware-2.0-462.i386.rpm
02.0.0beta4622000-02-14VMware-2.0-462.tar.gz
02.0.0beta4442000-01-24VMware-2.0-444.exed28f5db3204af37cf06fe9db26c55095
02.0.0beta4442000-01-24VMware-2.0-444.i386.rpmfbd90287ec42553bb9afeb30ef515991
02.0.0beta4442000-01-24VMware-2.0-444.tar.gza14c40804ed453197a131216496218ba
02.0.0beta4382000-01-20VMware-2.0-438.exe946e2c353bace76fc542a189ee48840c
02.0.0beta4382000-01-20VMware-2.0-438.i386.rpm9613ed4faa3e03e150d6297ece29520e
02.0.0beta4382000-01-20VMware-2.0-438.tar.gz72876e3451a66a4419a9c6e412dd8ccb
01.1.2beta3631999-11-05
01.1.0rc 33141999-09-29vmware-forlinux-314.tar.gz
01.1.0rc 23051999-09-17vmware-forlinux-305.tar.gz
01.1.0rc 12991999-09-10vmware-forlinux-299.tar.gz
01.0.9rc 33141999-09-29VMware-1.0.9-314.i386.rpm
01.0.9rc 33141999-09-29vmware-forlinux-314.tar.gz
01.0.9beta2911999-09-02vmware-forlinux-291.tar.gz
01.0.8beta2841999-08-25
01.0.3experimental209
01.0.1beta3621999-11-05
01.0.1experimental179
01.0.0beta2801999-08-23vmware-nt-280.exe
01.0.0beta1521999-05-06vmware152.tar.gz
01.0.0beta1061999-03-24vmware106.tar.gz
00.9.0beta2521999-08-05vmware-nt-252.exea472bec41ccd9cf46865459d47491db5
00.9.0beta217vmware-nt-217.exe
00.9.0beta213vmware-nt-213.exe
00.2.0beta1351999-04-23vmware135.tar.gzed6f82d42bf66173da7cff3d281060c9
00.1.0beta 51011999-03-08vmware.tar.gz5982eaa9f4fbabdec69e4c52ed28c573
00.1.0beta 41999-02-07
00.1.0beta 31999-01-11
00.1.0beta 21998-12-02
00.1.0beta 11998-10-20
00.1.0alpha 21998-09-24

PCIe Passthrough - to more than 1 VM?

$
0
0

Hi:

 

I've not had much experience with "passthrough", but recently I needed to emergency P2V a physical server that had a SAS tape drive connection. I installed the LSI model SAS9212-4i4 SAS adapter in our R730 host server, and "passed through" the PCI device to my rehomed VM. All surprisedly works.

 

Now a question has been asked, can the same PCI device be passed through to another VM?  What I read, particularly regard GPU passthroughs, seems to suggest yes, the passthrough of a device can be configured on multiple VM's.

 

Am I going down the wrong road here?

VM power on - Snapshot fail or VM is suspended with error insufficient disk space while the datastore shows free space.

$
0
0

Symptoms:

 

- Unable to power-on / take snapshot for a VM , getting error insufficient disk space.

- VM is thin provisioned.

- Datastore is not VMFS6

- Datastore is over provisioned.

- Datastore has free space.

- Storage pool has free space "in case of thin provisioned LUNs"

- On /var/run/log/vmkernel.log you will see entries like:

 

2020-07-09T14:05:38.142Z cpu0:2738555)Res3: 7412: 'DataStoreX': [rt 3] Resources t 0, e 0, np 16, wb 0, b 0, RCs u 0, i 0, nf 4031, pe 0, oe 0

2020-07-09T14:05:38.548Z cpu9:2738556)WARNING: Res3: 7411: 'DataStoreX': [rt 3] No Space - did not find enough resources after second pass! (needed: 1, found: 0)

 

on the Datastore details you can see no free pointer blockes:

 

[root@esxi] vmkfstools -P -v 10 /vmfs/volumes/DataStoreX/

VMFS-5.61 (Raw Major Version: 14) file system spanning 1 partitions.

File system label (if any): DataStoreX

Mode: public ATS-only

Capacity 70368475742208 (67108608 file blocks * 1048576), 3067355332608 (2925258 blocks) avail, max supported file size 69201586814976

Volume Creation Time: Thu Nov 16 14:09:40 2017

Files (max/free): 130000/129935

Ptr Blocks (max/free): 64512/0                                           <=====================

Sub Blocks (max/free): 32000/31987

Secondary Ptr Blocks (max/free): 256/256

File Blocks (overcommit/used/overcommit %): 0/64183350/0

Ptr Blocks  (overcommit/used/overcommit %): 0/64512/0

Sub Blocks  (overcommit/used/overcommit %): 0/13/0

Volume Metadata size: 1147240448

UUID: XXXXXXX

Logical device:XXXXXXX

Partitions spanned (on "lvm"):

        naa.XXXXXXXXXXXX:1

Is Native Snapshot Capable: YES

OBJLIB-LIB: ObjLib cleanup done.

WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

Cause:

The VMFS extent reached the maximum number of block pointers, a block pointer is allocated for each 256 MB.

 

Resolution:

To fix this issue on the short term, migrate some workload from the datastore.

To fix the issue on the long term, upgrade to VMFS6.

 

Resources:

ESXi 6.7, ESXi 6.5, ESXi 6.0 Configuration Maximums: https://configmax.vmware.com/home

PTR Bloc on VMFS5 VMware Knowledge Base

"Not Enough Physical Memory" error on MacOS Big Sur Beta 1

$
0
0

On MacOS Big Sur Beta 1, receiving the following error when launching any VMs that worked fine prior to update:

 

"Not enough physical memory is available to power on this virtual machine with its configured settings."

 

Mac has a total of 16GB of RAM, VM has 4096MB allocated in preferences, and shows that there is still 12GB available for the Mac.  Same issue no matter how much memory is allocated to the VM.

 

Posting to report to devs as potential bug with new beta, but obviously any suggestions are welcome.

 

Thanks!

Error: Read-only file system during write on /dev/disks/mpx.vmhba0:C0:T0:L0 SetPtableGpt: Unable to commit to disk

$
0
0

Boa noite pessoal!

Estou com o seguinte problema no Vcenter quando tento adiconar Storage:

 

Hello people!
I have the problem with Vcenter when adding storage:

 

Failed to create VMFS datastore MyDiskTest - Cannot change the host configuration.- dismiss

 

 

 

 

 

[root@localhost:~] partedUtil setptbl "/vmfs/devices/disks/mpx.vmhba0:C0:T0:L0" gpt

gpt

0 0 0 0

Error: Read-only file system during write on /dev/disks/mpx.vmhba0:C0:T0:L0

SetPtableGpt: Unable to commit to disk.

 

Podem me ajudar? Obrigado!

Can you help me? Thank you!

Issues Installing Mellanox ConnectX-3 40/56 GbE InfiniBand QSFP NIC under ESXi 5.5 (u3)

$
0
0

I have a Dual-Port ConnectX-3 Pro EN 40/56 GbE QSFP+ NIC (MCX314A-BCCT)

 

I have been struggling for days now to get this card working.

 

To explain the topology, I have two other Hosts, with an Infiniband Switch between them.

Both of the other Hosts are plugged into the InfiniBand Switch via Passive QSFP Copper Cables.

The other two Hosts and the Mellanox Cards in them are working fine.

 

Example:

NIC-1.PNG

I am now trying to add a third host, with this NIC in it.

The NIC is VMware-certified, and I am using the VMware-provided Driver specifically made for it.

(VMware Compatibility Guide - I/O Device Search)

 

But the NIC Ports will not connect and link when plugged in to the Switch.

I tried replacing the Card. I tried replacing the Cables with known, tested cables.

I have tried changing the port_type_array to Ethernet, and to Infiniband.

When the card's two ports are directly plugged into one another (while the NIC in Ethernet Mode), Link is active.

 

But the card has to be in InfiniBand mode because it is an InfiniBand Switch on the other end, and the other two Hosts are running in InfiniBand mode.

 

I notice that the new NIC is using a different Driver:

NIC-2.PNG

The existing, working NICs are using the "ib_ipoib" driver, and the new Host's NIC is using the "mlx4_en" driver.

 

I don't know of any esxcli or esxcfg command to specify or change the Driver that's being used for the card, and switch it to ib_ipoib.

 

I've tried installing older drivers, going all the way back to the ESXi 5.0 Drivers, but nothing I did -- for days -- got those ports to energize.

 

The InfiniBand card's ports remain in "Down" state.

NIC-3.PNG

I am at my wits end at this point, and so I am reaching out to the community here.

 

Does anyone have any suggestions on how I can get this card working?

Viewing all 181132 articles
Browse latest View live


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