“WaaS embedded virtualisation

Leverages new Linux Kernel Virtual Machine technology.
Leverage proven Linux scheduler and memory management.
Simpler and faster (typically 15-20%) for network services.
Microsoft and Cisco to validate “Embedded Virtualization” for Windows.”

So, looks like KVM then!

It’s my understanding that WS08 is running on WAAS using an “unspecified” virtualization technology. No one has yet been able to identify exactly what virtualization technology (open source Xen, KVM, or something else entirely) is being used, but I am reasonably confident that it is NOT Hyper-V. Else, why would Cisco have joined the SVVP to validate their virtualization implementation? Hyper-V needs no validation.

” … Cisco will embed a virtualization component within its Wide Area Application Services (WAAS) appliance family that will help customers to host Windows Server 2008 …”

If they wish to host a W2K8 server within the WAAS, I would believe that the following brands would not make it:
- VMware – competition for Microsoft altough that Cisco and VMware have nice collaboration (cfr. VMworld 2008) and confirmed to Mike (see first comment)
, KVM and Xen (the project) – to open source?

This leaves Hyper-V and XenServer. Semi bare-metal versus baremetal virtualization technologies. I strongly believe that pure baremetal would be best as this would mean the lowest overhead on the appliance.

When setting up a MS Server on Cisco WAAS you will create one point of entry and exit for the branch office to the WAN. This means that there is one Microsoft server running DHCP, DNS, AD, Print, … (and the idea is that it remains with one server in the branch office) so there is no need for motioning the things …

When looking at the Microsoft Server on Cisco WAAS, it looks like a Citrix Branch Repeater which was announced a few months ago, which is also a collaboration between Microsoft and Citrix. Yet the feature set of the Branch Repeater is based (on preliminary info) much more complete that the MS Server on Cisco WAAS.

IIRC, Alessandro’s discussion of Cisco’s use of KVM was within the context of NX-OS, Cisco’s new software that runs the Nexus product line. Given that NX-OS is, from what I understand, heavily Linux-based, it only makes sense that KVM would be tapped there.

However, KVM just isn’t robust enough to run Windows Server 2008 (yet), so I can see why Cisco would have selected the Xen hypervisor for their “Windows-on-WAAS” solution.

http://www.virtualization.info/2008/03/cisco-puts-kvm-in-its-ios.html

I know this is about something else that isn’t WAAS but I would ask why would they choose different virtualization technologies? Unless Cisco R&D is that fractured.