# Wowza 3.5 vmware requirements

**URL:** <https://community.wowza.com/t/wowza-3-5-vmware-requirements/39723>\
**Category:** Wowza Streaming Engine\
**Created:** [December 26, 2012, 1:07pm UTC](https://community.wowza.com/t/wowza-3-5-vmware-requirements/39723 "2012-12-26T13:07:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![CARLOS\_PASTOR](https://avatars.discourse-cdn.com/v4/letter/c/3da27b/32.png) [@CARLOS\_PASTOR](https://community.wowza.com/u/CARLOS_PASTOR)\
**Post date:** [December 26, 2012, 1:07pm UTC](https://community.wowza.com/t/wowza-3-5-vmware-requirements/39723/1 "2012-12-26T13:07:21Z")

</div>

Are there minimal requirements ang guidelines to size, install and run wowza on vmware?..Is it enough to translate physical machine requirements to virtual machine ones (vCPU,vRAM, vDISK) or is it necessary any other consideration (host machine hardware characteristics, minimal ESX/ESXi version recommended or required,…)?

Thanks in advance

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [December 26, 2012, 3:46pm UTC](https://community.wowza.com/t/wowza-3-5-vmware-requirements/39723/2 "2012-12-26T15:46:40Z")

</div>

There is not a simple, general answer to this, but depending on resources you should tune Wowza up or down following this guide:

[https://www.wowza.com/docs/how-to-do-performance-tuning](https://www.wowza.com/docs/how-to-do-performance-tuning)

Richard

---

<div class="post-metadata">

**Author:** ![Antonius\_Simamora](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@Antonius\_Simamora](https://community.wowza.com/u/Antonius_Simamora)\
**Post date:** [May 23, 2016, 3:25am UTC](https://community.wowza.com/t/wowza-3-5-vmware-requirements/39723/3 "2016-05-23T03:25:43Z")

</div>

Hello…

Any update for this issue? because I have some problem like this :

comment server INFO 200 - killUnidentifiedSessions: Killing unidentified session: address:/xxx.xxx.xxx 605.081 - - - - - - - - - - - - -

comment server INFO 200 - killUnidentifiedSessions: Killing unidentified session: address:/xxx.xxx.xxx 605.081 - - - - — - - - - - - - - - - - - - - - -

comment server INFO 200 - killUnidentifiedSessions: Killing unidentified session: address:/xxx.xxx.xxx 605.082 - - - - — - - - - - - - - - - - - - - - -

I install Wowza on VMWare :

OS Architecture : amd64

Memory

- Total: 220.35 GB

- Available: 216.21 GB

Processor Cores

40

Java Version

1.8.0\_60

Java Bitness

64

top - 03:23:05 up 2:15, 2 users, load average: 0.04, 0.05, 0.09

Tasks: 363 total, 1 running, 362 sleeping, 0 stopped, 0 zombie

%Cpu(s): 0.1 us, 0.1 sy, 0.0 ni, 99.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st

KiB Mem : 23105219+total, 22655025+free, 2918272 used, 1583676 buff/cache

KiB Swap: 0 total, 0 free, 0 used. 22784609+avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

9370 root 20 0 32.016g 797088 18064 S 8.9 0.3 0:40.81 /usr/local/WowzaStreamingEngine/java/bin/java -Xmx10000M -XX:+UseG1GC -XX:MaxGCPauseMillis=100 -server -Djava.net.preferIPv4Stack=true -Dcom.sun.management.jmxremot+

3868 root 20 0 37.477g 1.513g 18632 S 0.7 0.7 2:04.46 /usr/local/WowzaStreamingEngine/java/bin/java -Dcom.wowza.wms.ConfigURL="" -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaStreamingEngine/manager -Djava.io.tmpdir=/usr/+

9830 root 20 0 42096 4024 3180 R 0.7 0.0 0:00.07 top -c

Please help and advice for My…

Thank’s

Best Regard,

Antonius

---

<div class="post-metadata">

**Author:** ![Jason\_Tuchler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_tuchler/32/462_2.png) [@Jason\_Tuchler](https://community.wowza.com/u/Jason_Tuchler)\
**Post date:** [May 25, 2016, 2:27pm UTC](https://community.wowza.com/t/wowza-3-5-vmware-requirements/39723/4 "2016-05-25T14:27:39Z")

</div>

Hello,

Are you having an issue with your streaming? Or noticing these info messages?

That is an info message about killing unidentified sessions for which we have not received enough data to determine protocol. Basically “not enough data to determine protocol”.

-JasonT
