Some while ago, it was noted that Cisco was signed up as a participant in Microsoft’s Server Virtualization Validation Program (SVVP). Many wondered why—what did Cisco have up its sleeve?
This article today from InfoWorld seems to make the story much clearer:
With the new product, called Windows Server on WAAS, branch offices can host services locally including Active Directory, Microsoft Print Services, Microsoft Domain Name System Server and Microsoft Dynamic Host Configuration Protocol Server. That can improve performance for branch workers and reduce costs related to wide area network connectivity and branch systems management. An IT administrator can remotely manage the Windows Server functions using Microsoft System Center.
Cisco used embedded virtualization technology in its appliance to enable Windows Server 2008 to run on it.
Now, the real question is this: what “embedded virtualization technology” did Cisco use?
UPDATE: Based on the comments below, it looks like KVM is the technology Cisco chose to virtualize Windows Server on WAAS. Very interesting!
Tags: Cisco, Microsoft, Networking, Virtualization, Windows
9 comments
Comments feed for this article
Trackback link
http://blog.scottlowe.org/2008/10/02/now-ciscos-participation-in-svvp-becomes-clearer/trackback/
Thursday, October 2, 2008 at 10:29 am
Mike
They used XenSource or a dirivative. We had a discussion with them about their WAAS product and said that the VMware product would have hindered them so they went with Xen
Thursday, October 2, 2008 at 10:50 am
slowe
Well, let’s be clear here–did they use XenSource (Citrix’s version of Xen) or the open source Xen hypervisor itself? I would strongly imagine the latter and NOT the former.
Thursday, October 2, 2008 at 10:02 pm
Jon O
Wasn’t there announcement a while back on virtualization.info a while back about Cisco using KVM?
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.
Thursday, October 2, 2008 at 10:19 pm
slowe
Jon O,
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.
Monday, October 6, 2008 at 4:12 am
Channel-V
While reading the Cisco & Microsoft Press Release I bumped into the following phrase …
” … 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.
Monday, October 6, 2008 at 1:44 pm
Mark Wilson
Is WS08 running on WAAS or the other way around. All the press stuff says how this is built on Windows Server 2008 Server Core - that includes Hyper-V so are they using that? Or is this all on top of the Cisco platform in a “Cisco” VM (using Xen or similar?
Monday, October 6, 2008 at 1:53 pm
slowe
Mark,
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.
Tuesday, October 7, 2008 at 9:38 am
Mark Wilson
Good point. And quoting from a Cisco slidedeck that a colleague has sent me…
“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!
Tuesday, October 7, 2008 at 9:39 am
slowe
Indeed it does! Thanks for the update, Mark.