<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>The Server Virtualization host; not a pimped file and print server</title><link>http://blogs.technet.com/b/matthts/archive/2009/11/11/the-server-virtualization-host-not-a-pimped-file-and-print-server.aspx</link><description>Designing your virtualization host requires a lot of information; how many VM’s will it host, what are the requirements of each VM, what to reserve for the host, how much resources to include for future needs, etc. At least you need information on the</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator></channel></rss>