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

Re: Failed to build vmnet module on Linux 4.4.76-1-default openSUSE Leap 42.3

$
0
0

Hello

 

VMware-Workstation-Full-e.x.p-6056110.x86_64.bundle is now up and running on my openSUSE 43.2 installation

 

The kernel version is 4.4.76

uname -a

Linux hero 4.4.76-1-default #1 SMP Fri Jul 14 08:48:13 UTC 2017 (9a2885c) x86_64 x86_64 x86_64 GNU/Linux

 

##################################

# How to fix the problem : summary

##################################

In the netif.c file (which is in the vmnet.tar), you should have the following line:

compat_netif_trans_update(dev);

 

My solution was to change compat_netif_trans_update(dev);

to

netif_trans_update(dev);

 

Then run:

vmware-modconfig --console --install-all

 

 

##################################

# How to fix the problem : long

##################################

Login as root

cd /usr/lib/vmware/modules/source/

cp -p vmnet.tar vmnet.old.tar

tar xf vmnet.tar

 

cd vmnet-only

vi netif.c

 

Open netif.c and find the line: compat_netif_trans_update(dev);

 

It should look like this

   netIf->stats.tx_packets++;

   compat_netif_trans_update(dev);

 

Change compat_netif_trans_update(dev);

to

netif_trans_update(dev);

 

After the change - I have this

   netIf->stats.tx_packets++;

   netif_trans_update(dev);

 

Close and save the netif.c file

Close and save

 

Now recompile VMware kernel modules using this command

vmware-modconfig --console --install-all

 

Expected results

hero:/usr/lib/vmware/modules/source # vmware-modconfig --console --install-all

[AppLoader] Use shipped PC/SC Lite smart card framework.

An up-to-date "pcsc-lite-libs" or "libpcsclite1" package from your system is preferred.

[AppLoader] GLib does not have GSettings support.

Stopping VMware services:

   VMware Authentication Daemon                                        done

   VM communication interface socket family                            done

   Virtual machine communication interface                             done

   Virtual machine monitor                                             done

   Blocking file system                                                done

make: Entering directory '/tmp/modconfig-HcrWCA/vmmon-only'

Using kernel build system.

/usr/bin/make -C /lib/modules/4.4.76-1-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: Entering directory '/usr/src/linux-4.4.76-1-obj/x86_64/default'

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/linux/driver.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/linux/hostif.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/linux/driverLog.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/common/memtrack.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/common/apic.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/common/vmx86.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/common/cpuid.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/common/task.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/common/hashFunc.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/common/comport.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/common/phystrack.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/vmcore/moduleloop.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/bootstrap/monLoaderVmmon.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/bootstrap/monLoader.o

  CC [M]  /tmp/modconfig-HcrWCA/vmmon-only/bootstrap/bootstrap.o

/tmp/modconfig-HcrWCA/vmmon-only/linux/driver.c:981:1: warning: always_inline function might not be inlinable [-Wattributes]

LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min

^

  LD [M]  /tmp/modconfig-HcrWCA/vmmon-only/vmmon.o

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/modconfig-HcrWCA/vmmon-only/vmmon.mod.o

  LD [M]  /tmp/modconfig-HcrWCA/vmmon-only/vmmon.ko

make[1]: Leaving directory '/usr/src/linux-4.4.76-1-obj/x86_64/default'

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= postbuild

make[1]: Entering directory '/tmp/modconfig-HcrWCA/vmmon-only'

make[1]: 'postbuild' is up to date.

make[1]: Leaving directory '/tmp/modconfig-HcrWCA/vmmon-only'

cp -f vmmon.ko ./../vmmon.o

make: Leaving directory '/tmp/modconfig-HcrWCA/vmmon-only'

Starting VMware services:

   Virtual machine monitor                                             done

   Virtual machine communication interface                             done

   VM communication interface socket family                            done

   Blocking file system                                                done

   Virtual ethernet                                                    done

   VMware Authentication Daemon                                        done

   Shared Memory Available                                             done

 

  

Open VMware workstation from the menu

It should now work - at least it did for me

 

Regards

James


Re: Multiple Virtual Network Adapters on VM - How to Map to Corresponding Windows Network Adapters?

$
0
0

VM Host:

PowerCLI C:\> Get-VM -Name RB-REC-02 | Get-NetworkAdapter -NAme "Network adapter

4" | Select *

 

MacAddress       : 00:0c:29:1b:c5:c8

WakeOnLanEnabled : True

NetworkName      : Camera Network

Type             : Vmxnet3

ParentId         : VirtualMachine-4

Parent           : RB-REC-02

Uid              : /VIServer=root@192.168.0.110:443/VirtualMachine=VirtualMachi

                   ne-4/NetworkAdapter=4003/

ConnectionState  : Connected, GuestControl, StartConnected

ExtensionData    : VMware.Vim.VirtualVmxnet3

Id               : VirtualMachine-4/4003

Name             : Network adapter 4

Client           : VMware.VimAutomation.ViCore.Impl.V1.VimClient

 

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

 

Windows VM:

PS C:\Users\Administrator> Get-NetAdapterHardwareInfo -Name "Ethernet" | Select *

 

ifAlias                           : Ethernet

InterfaceAlias                    : Ethernet

ifDesc                            : vmxnet3 Ethernet Adapter

Segment                           : 0

Bus                               : 4

Device                            : 0

Function                          : 0

Slot                              : 161

PcieLinkWidth                     : 32

SriovSupport                      : NoIoMmuSupport

PcieLinkSpeed                     : 5.0 GT/s

PcieMaxLinkSpeed                  : 5.0 GT/s

Version                           : 1.0

DeviceType                        : PCI Express endpoint

CurrentSpeedAndMode               : NA

Caption                           : MSFT_NetAdapterHardwareInfoSettingData 'vmxnet3 Ethernet Adapter'

Description                       : vmxnet3 Ethernet Adapter

ElementName                       : vmxnet3 Ethernet Adapter

InstanceID                        : {17868FD0-25C5-4F19-A571-694DF64C46F5}

InterfaceDescription              : vmxnet3 Ethernet Adapter

Name                              : Ethernet

Source                            : 2

SystemName                        : WIN-H91NBU1AN5T

BusNumber                         : 4

DeviceNumber                      : 0

Dma64BitSupported                 : True

FunctionNumber                    : 0

LineBasedInterrupts               : False

LineBasedInterruptSupported       : True

LocationInformationString         : PCI bus 4, device 0, function 0

MaxInterruptMessages              : 25

MsiEnabled                        : True

MsiInterruptSupported             : True

MsiSupported                      : True

MsiXEnabled                       : True

MsiXInterruptSupported            : True

MsixMessageAffinityArray          : {MSFT_NetAdapter_Group_Affinity, MSFT_NetAdapter_Group_Affinity,

                                    MSFT_NetAdapter_Group_Affinity, MSFT_NetAdapter_Group_Affinity...}

MsiXSupported                     : True

NoInterrupt                       : False

NumaNode                          :

NumMsiMessages                    : 10

NumMsixTableEntries               : 25

PciCurrentSpeedAndMode            :

PciDeviceLabelID                  :

PciDeviceLabelString              :

PciDeviceType                     : 2

PciExpressCurrentLinkSpeedEncoded : 2

PciExpressCurrentLinkWidth        : 32

PciExpressCurrentPayloadSize      : 128

PciExpressMaxLinkSpeedEncoded     : 2

PciExpressMaxLinkWidth            : 32

PciExpressMaxPayloadSize          : 128

PciExpressMaxReadRequestSize      : 128

PciExpressVersion                 : 1

PciXCurrentSpeedAndMode           :

S0WakeupSupported                 : True

SegmentNumber                     : 0

SlotNumber                        : 161

PSComputerName                    :

CimClass                          : ROOT/StandardCimv2:MSFT_NetAdapterHardwareInfoSettingData

CimInstanceProperties             : {Caption, Description, ElementName, InstanceID...}

CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties

 

When I run your first script on this VM I see the following: (where are those empty fields?)

 

VM        : RB-REC-02

Portgroup : Camera Network

vMAC      : 00:0c:29:1b:c5:c8

osMAC     :

vNIC      : Network adapter 4

osNIC     :

vSlot     : 1184

osSlot    :

os boot failure windows SE 2008 R2

$
0
0

A disk read error occurred , press ctl+alt+del to restart

Re: Multiple Virtual Network Adapters on VM - How to Map to Corresponding Windows Network Adapters?

$
0
0

Those missing osxxx properties indicate that the PCI slot was not matched.

What slot does the vNIC show?

 

Get-VM-NameRB-REC-02|Get-NetworkAdapter-NAme"Network adapter4"|

Select @{N='PCI Slot';E={$_.ExtensionData.SlotInfo.PciSlotNumber}}

 

 

Update: Forget that, just noticed the slot (1184) is already there.

Re: Multiple Virtual Network Adapters on VM - How to Map to Corresponding Windows Network Adapters?

$
0
0

Its seems to be way out of range of the other adapters.

 

PCI Slot

--------

1184

 

Edit: And in Windows its 161. Mismatched IDs. Would a removal of that Network adapter, insert a new one and run that again work?

Re: Logoff never completes

$
0
0

There could be a LOT of reasons for that behavior. The good news for you though, is the VM is still accessible. When you discover a VM in this state, place it in maintenance mode inside the View Administrator to avoid any further provisioning. It is now a crime scene!

 

You want to review the Horizon View Agent logs by browsing via UNC: \\hostname\c$\programdata\VMware\VDM\Logs

 

Specifically the files beginning with 'Log' or 'Debug'. Also try to correlate Windows Events with the last time stamp in those logs, may be it is trying to stop a service for instance.

 

If you don't find any obvious reasons there, check the View Connection Server logs in the same path as above.

Re: Multiple Virtual Network Adapters on VM - How to Map to Corresponding Windows Network Adapters?

$
0
0

You could try that.

But I would need to find out why the mismatch is there.

 

Are the MAC addresses on both sides at least the same?

Re: Installation VMWare Tools

$
0
0

Hi,

 

I've sen the same behavior (VMWareCAFManagementAgentHost) after initial installation of VMware tools crashed on a fresh Windows 10 (Insider Preview) installation. Installation of VMware tools crashed when it tried to install and start the video driver. After reboot I tried to re-install VMware tools and got this error.

 

Re-installed Windows (easier then fix the corrupt VMware tools installation), this time with mks.enableMTLRenderer = "0" as per the Tech Preview readme. With the old renderer, VMware tools installation worked, no error messages.

 

Regards

 

Bernhard


Re: Cluster CPU Usage Average

$
0
0

$start = (Get-Date).AddHours(-8)

Name                                                                                                                      CPU average

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

CLUSTER1                                                                                                         3.0558510435112

 

 

yes in web client I can see performance for both clusters (7 days for example)

Re: Task name is shown different on vSphere web client 6.0 and vsphere client 6.0

$
0
0

Spent some time on the phone today working this issue, the problem we found was tied to a Netapp plugin that we installed in our environment. The plugin version was 6.2.1P1D1, which was where the problem ended up being. 6.2.1P1D1 is the service version for the plugin and the Virtual center JAR only interprets service versions on plugins that contain numbers, it cannot interpret letters. When it tries to process the Netapp plugin it fails and never loads the rest of the files containing the appropriate lables. The hope is that this will be resolved to read both numbers and letters in the future. Hope this helps or at least points you in the right direction.

Re: Multiple Virtual Network Adapters on VM - How to Map to Corresponding Windows Network Adapters?

$
0
0

Yeah, the MAC in VMware and in Wndows is identical

 

Let me try to remove and readd the offending NEtwork Adapter

 

*Update*: I removed the Network Adapter 4 and readded.

 

Im seeing in VMware now that the Slot number is different.

In Windows, the slot number is the same as it previously was, still differs from the VM number. So its still mismatched.

 

The MAC is the same as it was before as well.

 

So, does this point to an issue in the VM? Shouldnt a renewed Adapter give different information as

how can set alarm for alerts

$
0
0

Dear friend

Hi

 

can we set alarm in alert tab

for example if appear a new alert appear alarm

 

BR

Re: VMware Workstation 12.5.7 build-5813279.x86_64 does not compile on openSUSE-Leap-42.3-DVD-x86_64

$
0
0

Hello

I managed to get VMware-Workstation up and running on openSUSE 42.3 by installing the E.X.P. version : VMware-Workstation-Full-e.x.p-6056110.x86_64.bundle

 

I still had to manually change the netif.c file (which is in the vmnet.tar) so that the vmnet module would compile.

The details can be found in the thread "Failed to build vmnet module on Linux 4.4.76-1-default openSUSE Leap 42.3 which is on Workstation Pro Tech Preview forum

 

Hope this helps someone.

James

Re: Multiple Virtual Network Adapters on VM - How to Map to Corresponding Windows Network Adapters?

$
0
0

Not sure what is happening here, I'll have to do some testing.

NAT CONNECTION

$
0
0

Hi,

 

I'm just studying vmware.I noticed that if I use the nat connection for a guest on a vmware workstation, I can not ping from my host computer (from the laptop on which the host workstation appunt is).
HOST (192.168.1.180) dhcp vmware 192.168.80.1 guest 192.168.80.12

By setting in nat mode I can not ping from 192.168.1.180 to 192.168.80.12 .....

If I install vsphere 6.0 on workstations, I install a virtual machine with the configuration with nat:

HOST (handheld) 192.168.1.180, dhcp vmware 192.168.80.1 guest for example 192.168.80.14

In this case I can from 192.168.1.180 do ping on 192.168.80.14 even though there is nat.

Why is this difference if the definition of nat is valid for all?


Re: Cluster CPU Usage Average

$
0
0

Not sure what is happening here, I suspected an error in the aggregation jobs on the vCenter, but then the Web CLient shouldn't show data either.

 

Let's start with the beginning, are all clusters showing Realtime data?

 

$entity=Get-Cluster

Get-Stat-Entity$cluster-Statcpu.usage.average-Realtime-MaxSamples1

 

Metal Renderer not working on 10.13 HOS with Windows 10 guest

$
0
0

Hi,

 

Tech Preview readme mentions under Known Issues that new Metal renderer "doesn't work well" on hosts with Skylake CPUs. I've tested on an i7-3615QM and i7-6820HQ and wasn't able to install VMware tools video driver on neither of the two systems. It seems the new Metal renderer doesn't work at all on 10.13 HOS with Windows 10 guests?

 

Regards

 

Bernhard

Best Practice for connecting NAS Storgae

$
0
0

Hi There,

 

We have ESXi servers with 4 1GB vNICS. vmnic0 and vmnic1 are configured for management network (vmkernal port) and vmnic and vmnic3 are configured for VM traffic (virutal machine port group). I have to connect Synology NAS and present storage to ESXi.

 

Considering this sceneio and no more NICs added to the bpx, what is the best way to connect NAS. I do not want to loose redundancy for both management and VM port group.

 

As of now I have connected like this;

* Connected NAS to switch

* Assigned the IP address to NAS from same subnet of management network.

* Added software iSCSI adaprt, performed discovery and present storage to ESXi box

How do you create a Tenant DLR for a Tenant ESG in vCloud Dir 8.20 with NSX 6.3.0

Re: Reset database in vROps 6.6

Viewing all 231247 articles
Browse latest View live


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