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

vROPS VM Configuration|Creation Date is not readable

$
0
0

Hello,

Could you help me with a creation date of VM?

I need to add to the report date when VM was created. I have found that VM in vROPS has a metric called Configuration|Creation Date but probably it is not human readable.

 

How can I convert it to a readable date? My license allows me to use a super metric if it can help.


Unable to load DLL - The specified module cannot be found

$
0
0

Hi,

 

I have seen a few of these posts but i am struggling to get this working at the moment.

I have a build machine and a test machine (the same image). The application work on the build machine but when i copy the bin folder to my test machine i get the below error:

 

dll.png

 

I have these options in my package.ini file:

 

ChildProcessEnvironmentExceptions=svchost.exe
ChildProcessEnvironmentDefault=Virtual
ExternalDLLs=gdex.dll
StatusbarDisplayName=Ab Initio GDE 3.1.7.2

 

However I still get the same error on my test machine. gdex.dll is located in Captures\Ab Initio\%ProgramFilesDir%\Ab Initio\Ab Initio GDE 3.1.7.2\Program Files so i presume this should work?

Any ideas?

 

Thanks

VMWare 15 Worksation Pro Grafik Probleme wenn VMWareTools installiert sind!

$
0
0

Hallo Zusammen,

 

alle Pop over Fenter in Google Chrom werden unleserlich dargestellt jedoch NUR wenn VMWareTools installiert sind!

 

VMWareTools nicht zu installieren kommt auch nicht in Frage da die Bildschirmauflösung nicht auf 1920 x 1080 eingestellt werden kann und permanent der Hinweis erscheint "To release input, press Ctrl+Alt" So kann man nicht arbeiten.

 

Hat jemand eine Idee oder wie kann ich bei VMWare ein Service Ticket dafür eröffnen?

 

Gruß Kostas

VMs Crashing on NFS Storage ... ESXi Kernel Log flodded with messages

$
0
0

I've had a number of VMs fail to vMotion or straight up crash due to messages similar to these:

 

Failed to process the set attributes result: Lost previously held disk lock

 

2018-12-28T15:19:23.749Z| vcpu-0| I125: >>> Error writing log, 89 bytes discarded. Disk full?

2018-12-28T15:19:23.749Z| vcpu-0| I125: Msg_Question:

2018-12-28T15:19:23.749Z| vcpu-0| I125: [msg.hbacommon.locklost] The lock protecting 'vm.vmdk' has been lost, possibly due to underlying storage issues.

2018-12-28T15:19:23.749Z| vcpu-0| I125+ If this virtual machine is configured to be highly available, ensure that the virtual machine is running on some other host before clicking OK.

2018-12-28T15:19:23.749Z| vcpu-0| I125: ----------------------------------------

2018-12-28T15:23:24.379Z| vcpu-0| I125: Timing out dialog 3174

2018-12-28T15:23:24.380Z| vcpu-0| I125: MsgQuestion: msg.hbacommon.locklost reply=0

2018-12-28T15:23:24.380Z| vcpu-0| E105: PANIC: Exiting because of failed disk operation.

2018-12-28T15:23:25.575Z| vcpu-0| W115: A core file is available in "/vmfs/volumes/77955655-79af1105-0000-000000000000/vm_name/vm.zdump.000"

2018-12-28T15:23:25.575Z| mks| W115: Panic in progress... ungrabbing

2018-12-28T15:23:25.575Z| mks| I125: MKS: Release starting (Panic)

2018-12-28T15:23:25.575Z| mks| I125: MKS: Release finished (Panic)

2018-12-28T15:23:25.576Z| vcpu-0| I125: Writing monitor file `vmmcores.gz`

2018-12-28T15:23:25.578Z| vcpu-0| W115: Dumping core for vcpu-0

2018-12-28T15:23:25.578Z| vcpu-0| I125: CoreDump: dumping core with superuser privileges

2018-12-28T15:23:25.578Z| vcpu-0| I125: VMK Stack for vcpu 0 is at 0x439337d13000

2018-12-28T15:23:25.578Z| vcpu-0| I125: Beginning monitor coredump

2018-12-28T15:23:26.171Z| vcpu-0| I125: End monitor coredump

2018-12-28T15:23:26.172Z| vcpu-0| W115: Dumping core for vcpu-1

2018-12-28T15:23:26.172Z| vcpu-0| I125: CoreDump: dumping core with superuser privileges

2018-12-28T15:23:26.172Z| vcpu-0| I125: VMK Stack for vcpu 1 is at 0x439337f13000

2018-12-28T15:23:26.172Z| vcpu-0| I125: Beginning monitor coredump

2018-12-28T15:23:26.577Z| mks| W115: Panic in progress... ungrabbing

2018-12-28T15:23:26.577Z| mks| I125: MKS: Release starting (Panic)

2018-12-28T15:23:26.577Z| mks| I125: MKS: Release finished (Panic)

2018-12-28T15:23:26.759Z| vcpu-0| I125: End monitor coredump

2018-12-28T15:23:27.220Z| vcpu-0| I125: Printing loaded objects

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9922257000-0x9923324914): /bin/vmx

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x996391E000-0x99639351CC): /lib64/libpthread.so.0

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9963B3B000-0x9963B3CF00): /lib64/libdl.so.2

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9963D3F000-0x9963D47D08): /lib64/librt.so.1

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9963F5A000-0x99641F24E4): /lib64/libcrypto.so.1.0.2

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9964423000-0x996448C4AC): /lib64/libssl.so.1.0.2

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9964697000-0x99647AB37C): /lib64/libX11.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99649B2000-0x99649C101C): /lib64/libXext.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9964BC2000-0x9964CA6341): /lib64/libstdc++.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9964EC5000-0x9964F4521C): /lib64/libm.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9965148000-0x996515CBC4): /lib64/libgcc_s.so.1

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x996535E000-0x99654BEC74): /lib64/libc.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99236FD000-0x992371A7D8): /lib64/ld-linux-x86-64.so.2

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99656C9000-0x99656E3634): /lib64/libxcb.so.1

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99658E5000-0x99658E695C): /lib64/libXau.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9965EB5000-0x9965F4A534): /usr/lib64/vmware/plugin/objLib/upitObjBE.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9966163000-0x99662B9994): /usr/lib64/vmware/plugin/objLib/vsanObjBE.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9966550000-0x9966564F94): /lib64/libz.so.1

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99669AF000-0x99669BA1D0): /lib64/libnss_files.so.2

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9966CC5000-0x9966CC60A4): /usr/lib/vmware/nas_plugins/lib64/libvmfsNasPlugin.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9966EC8000-0x9966EDB44C): /lib64/libvmkfslib.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99670DD000-0x996733A6D4): /lib64/libvmlibs.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99675E1000-0x99678F91A4): /lib64/libvmsnapshot.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9967B13000-0x9967B20F14): /lib64/libtreestructs.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9967D23000-0x9967D245BC): /usr/lib/vmware/nas_plugins/lib64/libsvaNasPlugin.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9967F26000-0x9967F4236C): /usr/lib/vmware/nas_plugins/lib64/libnvdkTegileNasPlugin.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: End printing loaded objects

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace:

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[0] 0000009969aa6460 rip=00000099228d75e7 rbx=00000099228d70e0 rbp=0000009969aa6480 r12=0000000000000000 r13=0000000000000001 r14=0000009923ba1460 r15=0000009968371020

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[1] 0000009969aa6490 rip=000000992241766c rbx=0000009969aa64b0 rbp=0000009969aa6990 r12=000000992357c2b0 r13=0000000000000001 r14=0000009923ba1460 r15=0000009968371020

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[2] 0000009969aa69a0 rip=0000009922582d41 rbx=0000009923d68a40 rbp=0000009969aa69c0 r12=0000000000000002 r13=0000009923c9eb48 r14=0000009923ba1460 r15=0000009968371020

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[3] 0000009969aa69d0 rip=000000992257588d rbx=0000009923c9b030 rbp=0000009969aa6b70 r12=00000099233e3550 r13=0000000000000165 r14=0000009923ba1460 r15=0000009968371020

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[4] 0000009969aa6b80 rip=0000009922825431 rbx=00000099236904a8 rbp=0000009969aa6bb0 r12=00000099233e3550 r13=0000000000000165 r14=0000009923ba1460 r15=0000000000000000

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[5] 0000009969aa6bc0 rip=000000992284d176 rbx=000000000000012d rbp=0000009969aa6c00 r12=000000992357c2b0 r13=0000009923687d80 r14=00000099235621a0 r15=0000000000000000

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[6] 0000009969aa6c10 rip=0000009922825518 rbx=0000000000000000 rbp=0000009969aa6c20 r12=0000009969aa6c40 r13=0000009923dbb290 r14=0000009923df18d0 r15=0000000000000003

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[7] 0000009969aa6c30 rip=00000099228c2b05 rbx=0000009923691aa0 rbp=0000009969aa6d80 r12=0000009969aa6c40 r13=0000009923dbb290 r14=0000009923df18d0 r15=0000000000000003

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[8] 0000009969aa6d90 rip=0000009963925cfc rbx=0000000000000000 rbp=0000000000000000 r12=000003805f591a00 r13=0000009969aa79c0 r14=0000009923df18d0 r15=0000000000000003

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[9] 0000009969aa6ea0 rip=000000996542fead rbx=0000000000000000 rbp=0000000000000000 r12=000003805f591a00 r13=0000009969aa79c0 r14=0000009923df18d0 r15=0000000000000003

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[10] 0000009969aa6ea8 rip=0000000000000000 rbx=0000000000000000 rbp=0000000000000000 r12=000003805f591a00 r13=0000009969aa79c0 r14=0000009923df18d0 r15=0000000000000003

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[0] 0000009969aa6460 rip=00000099228d75e7 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[1] 0000009969aa6490 rip=000000992241766c in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[2] 0000009969aa69a0 rip=0000009922582d41 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[3] 0000009969aa69d0 rip=000000992257588d in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[4] 0000009969aa6b80 rip=0000009922825431 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[5] 0000009969aa6bc0 rip=000000992284d176 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[6] 0000009969aa6c10 rip=0000009922825518 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[7] 0000009969aa6c30 rip=00000099228c2b05 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[8] 0000009969aa6d90 rip=0000009963925cfc in function (null) in object /lib64/libpthread.so.0 loaded at 000000996391e000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[9] 0000009969aa6ea0 rip=000000996542fead in function clone in object /lib64/libc.so.6 loaded at 000000996535e000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[10] 0000009969aa6ea8 rip=0000000000000000

2018-12-28T15:23:27.220Z| vcpu-0| I125: Exiting

 

Here is a sample of what's going on in vmkernel.log

2018-12-28T15:19:23.751Z warning hostd[9A81B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/77955655-79af1105-0000-000000000000/vm/vm.vmx] Failed to find activation record, event user unknown.

2018-12-28T15:19:23.752Z verbose hostd[9A81B70] [Originator@6876 sub=PropertyProvider] RecordOp REMOVE: latestPage[33726], session[52610cea-e1e8-e07e-26d6-259c4517645b]52e66a9c-32b6-479e-319f-ca34434ae415. Applied change to temp map.

2018-12-28T15:19:23.752Z verbose hostd[9A81B70] [Originator@6876 sub=PropertyProvider] RecordOp ADD: latestPage[33736], session[52610cea-e1e8-e07e-26d6-259c4517645b]52e66a9c-32b6-479e-319f-ca34434ae415. Applied change to temp map.

2018-12-28T15:19:23.752Z verbose hostd[9A81B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.

2018-12-28T15:19:23.752Z info hostd[9A81B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 33736 : Message on vm on esxi in ha-datacenter: The lock protecting 'vm.vmdk' has been lost, possibly due to underlying storage issues.

--> If this virtual machine is configured to be highly available, ensure that the virtual machine is running on some other host before clicking OK.

-->

 

2018-12-28T16:00:05.215Z cpu57:1437367)WARNING: NFS41: NFS41FileOpSetFileAttributes:4540: Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T16:00:05.616Z cpu48:1437367)WARNING: NFS41: NFS41FileOpSetFileAttributes:4540: Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T16:00:06.019Z cpu48:1437367)WARNING: NFS41: NFS41FileOpSetFileAttributes:4540: Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T16:00:06.414Z cpu48:1437367)WARNING: NFS41: NFS41FileOpSetFileAttributes:4540: Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T16:00:06.814Z cpu48:1437367)WARNING: NFS41: NFS41FileOpSetFileAttributes:4540: Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T16:00:10.623Z cpu7:68509)WARNING: NFS41: NFS41_NFSAttrToVolatileFSAttrs:1641: Server FILES_FREE 5779000868 exceeds ESX limit

2018-12-28T16:00:10.623Z cpu7:68509)WARNING: NFS41: NFS41_NFSAttrToVolatileFSAttrs:1654: Server FILES_TOTAL 5779005873 exceeds ESX limit

2018-12-28T16:00:10.629Z cpu7:68509)WARNING: NFS41: NFS41_NFSAttrToVolatileFSAttrs:1641: Server FILES_FREE 5779000868 exceeds ESX limit

2018-12-28T16:00:10.629Z cpu7:68509)WARNING: NFS41: NFS41_NFSAttrToVolatileFSAttrs:1654: Server FILES_TOTAL 5779005873 exceeds ESX limit

2018-12-28T16:00:10.633Z cpu7:68509)WARNING: NFS41: NFS41_NFSAttrToVolatileFSAttrs:1641: Server FILES_FREE 5779000868 exceeds ESX limit

2018-12-28T16:00:20.596Z cpu20:67009)SunRPC: 1116: Destroying world 0x1a0157

2018-12-28T16:00:20.598Z cpu20:67009)SunRPC: 1116: Destroying world 0x1a018e

2018-12-28T16:00:20.628Z cpu44:66542)WARNING: NFS: 221: Got error 13 from mount call

2018-12-28T16:00:20.628Z cpu20:67009)SunRPC: 1116: Destroying world 0x1a018f

2018-12-28T16:00:20.630Z cpu20:67009)SunRPC: 1116: Destroying world 0x1a0190

2018-12-28T16:00:20.649Z cpu44:66542)WARNING: NFS: 221: Got error 13 from mount call

2018-12-28T16:00:20.649Z cpu20:67009)SunRPC: 1116: Destroying world 0x1a0191

 

vobd shows the VM crash happening

 

It shows an APD on the NFS storage well before the crash itself, maybe about an hour before:

 

2018-12-28T11:17:56.077Z: [APDCorrelator] 2034244476342us: [vob.storage.apd.start] Device or filesystem with identifier [77955655-79af1105-0000-000000000000] has entered the All Paths Down state.

Installation Status "Not Ready"

$
0
0

Hi relatively new to NSX so please excuse the basic questions.

 

I have a 6.3.1 environment, when I go to Installation/Host Preparation all my systems under Installation Status say "Not Ready". Click on that and it says "Unable to access agent offline bundle at https://**.**.**.**/bin/vdn/vibs-6.3.1/6.0-5124744/vxlan.zip".

 

Now we believe this issue has been resolved, so the next logical step is to click on Resolve. So here is my question, we have running services so what does the Resolve being issued do and is it OK to run while services are up and running on the host?

 

Thanks

Richard

Poor audio quality with BLAST/RTAV?

$
0
0

Hello,

 

we are experiencing some issues with our audio in (microphone) settings and RTAV (Horizon Client 5.4 and Agent 7.11).

If i look into the Settings of the vmware microphone, i can just choose between 8000 Hz and 16000 Hz (default is 8000Hz).

 

If i enable USB Redirection for the Headset, i can choose 48.000 Hz.

 

Question:

1. Why it is only showing this low settings?

2. How can i set the defaults for all my users on 16000 Hz? Is there a GPO or something?

 

With best regards

Matthias

100% Fragemented

$
0
0

Hi All,

I am running a VM and the host is Windows Server 2012 R2. I noticed today that I have one of my virtual disks, which is a Thick provisioned, eagerly zeroed.

When I look at the disk under Windows, it shows it is 100% fragmented. It was my understanding that it is not recommended to run a defrag. My question is does anyone know is this is normal to see 100% fragmented reported in Windows and is it still not recommended to run any defrags? None of my other disks show this. Just  this one. Thanks.

The process cannot access the file because another process has locked a portion of the file

$
0
0

Hi everyone,

I get this following error "The process cannot access the file because another process has locked a portion of the file" when I want to boot my VM.

I searched a lot about it and found solutions like remove .Ick files, or uncompress NTFS files, but none of those worked for me!

please help me I have some important files on my VM, I wish I could grab those files at least!

 

thanks


Host Profile Help - iSCSI Discovery Targets

$
0
0

Hi

 

I am having some problems with Host Profiles. Particularly with the discovery targets. I have added a basic target, but have done the following;

 

Disabled Delayed ACK

Login Timeout to 5

 

Although everything I check compliance and remediate. It persists.

 

When I manually check. The settings have been applied.... Frustrating. Any help would be great please.

 

Upgrade License 6.7 to 7

$
0
0

Hi, i've an active "vSphere 6.x Essentials" contract until 13/05/2022.

i want a new license key, i think included in my contract, for the new vshpere 7

what i've to do?

 

best regards

Giuliano

unsigned ldap requests from vCenter

$
0
0

Hi @all,

 

I already found some threads about the Microsoft changes from ldap to ldaps but they did not yet help me.

 

Our vCenter is joined to our AD. At the identity sources I have configured the root domain of the forest with "Active Directory (Integrated Windows Authentication)".

When I now look at the ldap logs of the AD Domain Controller I see that the machine account of the vCenter makes unsigned connections.

 

On my test vCenter I setup an ldaps connection instead of the "Active Directory (Integrated Windows Authentication)" but there is the same behavior.

 

How can I change them to signed ones?

 

Regards Wolfgang

"Currently connected network interface uses network, which is not accessible"

$
0
0

Hello!

 

I have an 3 esxi server

I have dswitch configured

all servers are included in dswitch

 

But when I try to migrate the virtual machine, I get this error: "Currently connected network interface" 'Network adapter 1' uses network 'Corp (DSwitch)', which is not accessible.

Why I can't edit or add network card in virtual network editor

$
0
0

Hi,

 

I have VM workstation 15 Pro. I have a simple question why I can't create or add network card from "Virtual Network Editor" see attachment.?

 

Thank you

Watch On Demand Webinars

Launcher and Samsung S-pen

$
0
0

Hi! I have a Samsung tablet with s-pen. The device is  work managed and I have setup a profile with a custom launcher.

Problem is that s-pen won't work: if I touch the screen a pop-up ballon tells "unable to use air command. keep pressed...to unlock the app".

BUT if I enter admin mode in the launcher it DOES work.

Any clue on how to make it work for the normal user?

Thank you.


List of al VMs with all fields

$
0
0

Hello guys,

 

i need help to extract from my VCenter, with powercli script , all information like this :

 

 

Name

State

Uptime

NIC

PortGroup

  1. S.O.

IP

Host

Provisioned Space

Used Space

CPU

RAM

 

 

 

Reservation - RAM/CPU

VMDK / Datastore

Host CPU - MHz

Host Mem - MB

Notes

Fault Tolerance

Snapshot

VMWare Tools

NB_LAST_BACKUP

Tags

 

and send email on cvs and html format.

 

Please help me.

Thx

Davide

App Volumes 4 Performance Issues

$
0
0

Hi,

 

I wanted to post my findings here after recently deploying a PoC and reading this community post - App Volumes 4.0 performance

 

Deployed environment:

Horizon 7.11

AppVol 4 (latest)

DEM 9.10

FSLogix 2.8 (latest) - Profile and Office 365 container.

Windows 10 1909

 

First off to use App Volumes and FSlogix you have to add the exclusions into the snapvol.cfg file mentioned in this post -https://www.vcloudinfo.com/2019/08/vmware-app-volumes-and-fslogix-container-conflicts-resolved.html

 

Using App Volumes 4.0 with or without FSLogix resulted in poor VM performance and poor login times. I used full DEM personalization and dropped the FSLogix containers entirely to test there wasnt any conflicts and VM responsiveness was still poor. I was seeing behavior such as the svservice taking an age to process and then windows explorer constantly refreshing and flashing when it finally logged in. Also just browsing around the C:\ or launching apps (even base image apps) was really slow.

 

Login times were 1m30+ with App Volumes 4 so for good measure i upped my vCPUs to 4 per instant clone and this made no difference. FSLogix on its own with no App Volumes and a few apps installed within the base image was much faster about 40/50 seconds login and rapid responsiveness. I decided to create a new base image from scratch, again as always using the techzone optimization guide to rule out any base image issues and i also deployed App Volumes 2.18. Im now happy with the login times / VM performance & responsiveness using FSLogix containers and App Volumes 2.18. I had high hopes for 4.0 with the new features and "improved" performance but was bitterly disappointing with the outcome from my testing. Has anybody else played around with 4.0 yet?

Windows 7 on GNS3 with VMware 15 pro.

$
0
0

My host system is windows 10. and I have a guest OS windows 7 running in VMware 15 pro

 

I would like to create few network card in windows 7 and I following the direction using "virtual network editor".  e.g NIC 192.168.100.0/24

 

The problem I experienced was the GNS3 can't see the new windows 7 network card why?

 

Thanks for your inputs.

VIO 6.0 Step by Step

$
0
0

New to VIO 6 and looking for either a step by step guide or a HOL. Anything anyone could recommend? The installation and Admin guides dont go into details of how to obtain VM images, or how to properly configure External and Internal Networks and SR-IOV.

I am for example getting errors when creating networks on the GUI but the configuration fail without any explanation. Would be great to see where logs are being generated.

VM verlieren Netzwerkverbindung

$
0
0

Hallo Zusammen,

wir haben ein Problem auf einem VMware ESXi, 6.5.0, 13635690. Es scheint, dass wenn zu viele VM's auf diesem Host laufen, einige die Netzwerkverbindung verlieren. Gibt es da eine Einstellung, die man vornehmen kann?

Gruß

RS

Viewing all 180329 articles
Browse latest View live


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