{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/",
        "slug": "dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/"
        },
        "title": "Choose dedicated or partitioned GPU access for Hyper-V workloads",
        "summary": "Does a virtualized workload require a whole physical GPU or a partition of one?",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-08T18:14:45+00:00",
        "modified_at": "2026-09-08T18:23:27+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 1,
        "word_count": 200,
        "potentially_affected": "Architects planning GPU acceleration for Hyper-V workloads on Windows Server.",
        "dse_recommendation": "Compare a dedicated-device design with a partitioned design using the actual application requirements.",
        "primary_source": {
            "name": "Plan for GPU acceleration in Windows Server",
            "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-for-gpu-acceleration-in-windows-server",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>Microsoft distinguishes native GPU access on a physical Windows Server from the graphics virtualization needed inside Hyper-V VMs. Discrete Device Assignment dedicates one or more physical GPUs to a VM, which uses the native driver. Starting with Windows Server 2025, GPU partitioning lets multiple VMs receive dedicated portions of a physical GPU rather than each receiving the entire device. <a href=\"https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-for-gpu-acceleration-in-windows-server\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft documentation</a>.</p>\n<h2>Applicability</h2>\n<p>Identify the application, guest and host releases, GPU model, driver, and required features. Review the support requirements for the chosen mode, including any guest-platform restrictions, before deciding from density alone.</p>\n<h2>DSE recommendation</h2>\n<p>Compare a dedicated-device design with a partitioned design using the actual application requirements. Have the workload and virtualization owners document the required GPU resources and acceptable sharing model. Include maintenance and migration expectations in the design review and retain the supported configuration evidence.</p>\n<h2>Verification</h2>\n<p>Run the representative workload in the chosen supported configuration and inspect the GPU resources visible to the guest. Measure the agreed application tasks with the planned number of simultaneous VMs. Record unsupported features or an unmet performance target explicitly before approving the allocation model for wider use.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-for-gpu-acceleration-in-windows-server\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Plan for GPU acceleration in Windows Server</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nMicrosoft distinguishes native GPU access on a physical Windows Server from the graphics virtualization needed inside Hyper-V VMs. Discrete Device Assignment dedicates one or more physical GPUs to a VM, which uses the native driver. Starting with Windows Server 2025, GPU partitioning lets multiple VMs receive dedicated portions of a physical GPU rather than each receiving the entire device. Microsoft documentation.\nApplicability\nIdentify the application, guest and host releases, GPU model, driver, and required features. Review the support requirements for the chosen mode, including any guest-platform restrictions, before deciding from density alone.\nDSE recommendation\nCompare a dedicated-device design with a partitioned design using the actual application requirements. Have the workload and virtualization owners document the required GPU resources and acceptable sharing model. Include maintenance and migration expectations in the design review and retain the supported configuration evidence.\nVerification\nRun the representative workload in the chosen supported configuration and inspect the GPU resources visible to the guest. Measure the agreed application tasks with the planned number of simultaneous VMs. Record unsupported features or an unmet performance target explicitly before approving the allocation model for wider use.\nOfficial references\nMicrosoft Learn: Plan for GPU acceleration in Windows Server. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nMicrosoft distinguishes native GPU access on a physical Windows Server from the graphics virtualization needed inside Hyper-V VMs. Discrete Device Assignment dedicates one or more physical GPUs to a VM, which uses the native driver. Starting with Windows Server 2025, GPU partitioning lets multiple VMs receive dedicated portions of a physical GPU rather than each receiving the entire device. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-for-gpu-acceleration-in-windows-server).\n\n## Applicability\n\nIdentify the application, guest and host releases, GPU model, driver, and required features. Review the support requirements for the chosen mode, including any guest-platform restrictions, before deciding from density alone.\n\n## DSE recommendation\n\nCompare a dedicated-device design with a partitioned design using the actual application requirements. Have the workload and virtualization owners document the required GPU resources and acceptable sharing model. Include maintenance and migration expectations in the design review and retain the supported configuration evidence.\n\n## Verification\n\nRun the representative workload in the chosen supported configuration and inspect the GPU resources visible to the guest. Measure the agreed application tasks with the planned number of simultaneous VMs. Record unsupported features or an unmet performance target explicitly before approving the allocation model for wider use.\n\n## Official references\n\n[Microsoft Learn: Plan for GPU acceleration in Windows Server](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-for-gpu-acceleration-in-windows-server). Source reviewed September 8, 2026."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Choose dedicated or partitioned GPU access for Hyper-V workloads",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/",
                "headline": "Choose dedicated or partitioned GPU access for Hyper-V workloads",
                "description": "Does a virtualized workload require a whole physical GPU or a partition of one?",
                "abstract": "Does a virtualized workload require a whole physical GPU or a partition of one?",
                "articleBody": "Source facts\nMicrosoft distinguishes native GPU access on a physical Windows Server from the graphics virtualization needed inside Hyper-V VMs. Discrete Device Assignment dedicates one or more physical GPUs to a VM, which uses the native driver. Starting with Windows Server 2025, GPU partitioning lets multiple VMs receive dedicated portions of a physical GPU rather than each receiving the entire device. Microsoft documentation.\nApplicability\nIdentify the application, guest and host releases, GPU model, driver, and required features. Review the support requirements for the chosen mode, including any guest-platform restrictions, before deciding from density alone.\nDSE recommendation\nCompare a dedicated-device design with a partitioned design using the actual application requirements. Have the workload and virtualization owners document the required GPU resources and acceptable sharing model. Include maintenance and migration expectations in the design review and retain the supported configuration evidence.\nVerification\nRun the representative workload in the chosen supported configuration and inspect the GPU resources visible to the guest. Measure the agreed application tasks with the planned number of simultaneous VMs. Record unsupported features or an unmet performance target explicitly before approving the allocation model for wider use.\nOfficial references\nMicrosoft Learn: Plan for GPU acceleration in Windows Server. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:14:45+00:00",
                "dateModified": "2026-09-08T18:23:27+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-146-choose-dedicated-or-partitioned-gpu-access-for-hyper-v-workloads/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Choose dedicated or partitioned GPU access for Hyper-V workloads"
                },
                "articleSection": [
                    "IT",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "IT",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 200,
                "timeRequired": "PT1M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Plan for GPU acceleration in Windows Server",
                    "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-for-gpu-acceleration-in-windows-server"
                }
            }
        ]
    }
}