<?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 Hyper-V API - Disks</title><link>http://blogs.technet.com/jamesone/archive/2008/05/27/the-hyper-v-api-disks.aspx</link><description>In an earlier post in this series (several posts ago now) I showed how the Msvm_virtualSystemManagementService WMI object can be used to configure resources in Hyper-V, and I started with the easy step of setting memory and CPUs which exist on a freshly</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>The Hyper-v API Network interfaces</title><link>http://blogs.technet.com/jamesone/archive/2008/05/27/the-hyper-v-api-disks.aspx#3062119</link><pubDate>Wed, 28 May 2008 13:58:48 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3062119</guid><dc:creator>James O'Neill's blog </dc:creator><description>&lt;p&gt;If you've read my post on adding disks to a Virtual machine , the techniques here should already feel&lt;/p&gt;
</description></item></channel></rss>