<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Dedicated networking for Virtual Machines</title><link>http://blogs.msdn.com/virtual_pc_guy/archive/2004/11/12/256294.aspx</link><description>One of the cool 'hidden' features of Virtual PC / Virtual Server is the ability to dedicate a physical network to be used only by virtual machines. This can be done simply by going to the 'Control Panel' on the host computer and then going to the 'Network</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Dedicated networking for Virtual Machines</title><link>http://blogs.msdn.com/virtual_pc_guy/archive/2004/11/12/256294.aspx#256428</link><pubDate>Fri, 12 Nov 2004 14:26:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:256428</guid><dc:creator>Peter da Silva</dc:creator><description>This capability should be something that you can tune on a protocol-by-protocol and service-by-service level, everywhere in the OS. If you could do that you could eliminate the need for firewalls for most purposes, there's no need to firewall off a service that's only listening to localhost. :)</description></item></channel></rss>