I think Cisco support for VMWare is far too narrow, even for an initial implementation. To suggest that a customer must dedicate four CPUs and 4GB RAM in a VM host regardless of the size of implementation is ludicrous. If I want to run a system for 100 mailboxes and 32 ports I can do that just fine on a 7825 with a single processor and 2GB of RAM. Why should the requirements change just because I moved to a virtualized environment. Also the requirement for Fiber Channel is unreasonable. Many customers are migrating their SANs to iSCSI or NFS these days and are moving away from FC. I just had two of my voice customers abandon their FC storage, so they are now ineligble to virtualize? These restrictrictions make Cisco's support of virualization pretty much useless. Hopefully when support comes out for the other products the limitations won't be as insane.<br>
<br>-Adam<br><br><div class="gmail_quote">On Tue, Mar 3, 2009 at 2:52 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">Thanks Peter. I guess with the reserved CPUs and memory it will help. Not sure how much disk activity can affect processing, but like you said, definitely a step in the right direction.<br>
<br>I foresee a separate VMware installation for voice rather than sharing an existing VMware deployment.<br><br>To bad about VMotion....but I'm sure it'll get there.<div><div></div><div class="h5"><br><br><br>----- Original Message -----<br>
From: "Peter Pauly" <<a href="mailto:ppauly@gmail.com" target="_blank">ppauly@gmail.com</a>><br>To: "Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>><br>
Cc: "Matthew Loraditch" <<a href="mailto:MLoraditch@heliontechnologies.com" target="_blank">MLoraditch@heliontechnologies.com</a>>, <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
Sent: Tuesday, March 3, 2009 3:40:05 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] Unity now Supported on VMWare!!<br><br>Cisco solved the problem of running under vmware thus:<br><br>They require 4 CPU's to be assigned to Unity. Other guests running on<br>
the host cannot use those CPUs.<br>They require 4 GB of memory to be reserved for Unity.<br><br>None of the other guest machines can use the memory or CPU resources<br>that are assigned to Unity.<br>You can't use VMotion to transfer Unity between hosts.<br>
It only works on FiberChannel, not iSCSI or NAS.<br><br>Those limitations make it a much less attractive proposition. But at<br>least it is a step in the right direction.<br><br>On Tue, Mar 3, 2009 at 3:23 PM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>> wrote:<br>
> It's definitely a move in the right direction. However, I think it will<br>> remain to be seen if this is a supportable model going forward. I'm not that<br>> versed in VMware deployments, but I've seen VMware sessions get bogged down<br>
> because too many sessions were running. The document goes on to state<br>> minimum performance requirements but can you configure a VMware session to<br>> have priority? (rhetorical question). And if you can (technically) can you<br>
> politically? Typically VMware deployments are covered by another team and it<br>> might be hard to convince them your session deserves more cycles than the HR<br>> session.<br>><br>><br>><br>><br>><br>
> ---<br>> Lelio Fulgenzi, B.A.<br>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
> "Bad grammar makes me [sic]" - Tshirt<br>><br>><br>> ----- Original Message -----<br>> From: "Matthew Loraditch" <<a href="mailto:MLoraditch@heliontechnologies.com" target="_blank">MLoraditch@heliontechnologies.com</a>><br>
> To: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>> Sent: Tuesday, March 3, 2009 3:06:24 PM GMT -05:00 US/Canada Eastern<br>> Subject: [cisco-voip] Unity now Supported on VMWare!!<br>
><br>> This should make some people giddy!<br>><br>> <a href="http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html" target="_blank">http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html</a><br>
><br>><br>><br>><br>><br>> Matthew Loraditch<br>> 1965 Greenspring Drive<br>><br>> Timonium, MD 21093<br>> <a href="mailto:support@heliontechnologies.com" target="_blank">support@heliontechnologies.com</a><br>
> (p) (410) 252-8830<br>> (F) (443) 541-1593<br>><br>> Visit us at <a href="http://www.heliontechnologies.com" target="_blank">www.heliontechnologies.com</a><br>> Support Issue? Email <a href="mailto:support@heliontechnologies.com" target="_blank">support@heliontechnologies.com</a> for fast assistance!<br>
><br>><br>><br>> _______________________________________________ cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>><br></div></div></div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>