{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/", "slug": "dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations", "url": "https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/" }, "title": "Plan processor compatibility before moving a VM across CPU generations", "summary": "Which VM processor setting must be reviewed before migration between different hosts?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "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:13:14+00:00", "modified_at": "2026-09-08T18:29:34+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 228, "potentially_affected": "Administrators configuring Hyper-V VM processor compatibility.", "dse_recommendation": "Document the hosts the VM must be able to use and the application features that may depend on exposed CPU capabilities.", "primary_source": { "name": "Configure processor compatibility in Hyper-V virtual machines", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/configure-processor-compatibility-mode", "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": "

Source facts

\n

Microsoft describes processor compatibility mode as limiting the processor features exposed to a VM so it can move between hosts with differing capabilities. The VM must be powered off before enabling or disabling the setting. Dynamic processor compatibility cannot be configured in Hyper-V Manager; the documented alternatives are PowerShell or Windows Admin Center. Microsoft Learn.

\n

Applicability

\n

Inventory the intended source, destination, and recovery hosts and their supported capabilities. Check whether the cluster and operating-system versions support the dynamic option described in the source. Keep the compatibility decision separate from allocating more virtual processors to a workload.

\n

DSE recommendation

\n

Document the hosts the VM must be able to use and the application features that may depend on exposed CPU capabilities. Ask the workload owner to approve the planned powered-off change window. Select the management tool that supports the intended mode and preserve the initial setting. Define a representative migration and application test before altering a production VM.

\n

Verification

\n

Confirm the effective compatibility mode after the approved change, then start the VM and validate the application. Exercise the intended host-to-host move and record both placement and workload results. Compare the result with every host in the accepted placement set. Resolve an unsupported destination or changed application behavior before extending the setting to other VMs.

\n

Official references

\n

Microsoft Learn: Configure processor compatibility in Hyper-V virtual machines. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft describes processor compatibility mode as limiting the processor features exposed to a VM so it can move between hosts with differing capabilities. The VM must be powered off before enabling or disabling the setting. Dynamic processor compatibility cannot be configured in Hyper-V Manager; the documented alternatives are PowerShell or Windows Admin Center. Microsoft Learn.\nApplicability\nInventory the intended source, destination, and recovery hosts and their supported capabilities. Check whether the cluster and operating-system versions support the dynamic option described in the source. Keep the compatibility decision separate from allocating more virtual processors to a workload.\nDSE recommendation\nDocument the hosts the VM must be able to use and the application features that may depend on exposed CPU capabilities. Ask the workload owner to approve the planned powered-off change window. Select the management tool that supports the intended mode and preserve the initial setting. Define a representative migration and application test before altering a production VM.\nVerification\nConfirm the effective compatibility mode after the approved change, then start the VM and validate the application. Exercise the intended host-to-host move and record both placement and workload results. Compare the result with every host in the accepted placement set. Resolve an unsupported destination or changed application behavior before extending the setting to other VMs.\nOfficial references\nMicrosoft Learn: Configure processor compatibility in Hyper-V virtual machines. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft describes processor compatibility mode as limiting the processor features exposed to a VM so it can move between hosts with differing capabilities. The VM must be powered off before enabling or disabling the setting. Dynamic processor compatibility cannot be configured in Hyper-V Manager; the documented alternatives are PowerShell or Windows Admin Center. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/configure-processor-compatibility-mode).\n\n## Applicability\n\nInventory the intended source, destination, and recovery hosts and their supported capabilities. Check whether the cluster and operating-system versions support the dynamic option described in the source. Keep the compatibility decision separate from allocating more virtual processors to a workload.\n\n## DSE recommendation\n\nDocument the hosts the VM must be able to use and the application features that may depend on exposed CPU capabilities. Ask the workload owner to approve the planned powered-off change window. Select the management tool that supports the intended mode and preserve the initial setting. Define a representative migration and application test before altering a production VM.\n\n## Verification\n\nConfirm the effective compatibility mode after the approved change, then start the VM and validate the application. Exercise the intended host-to-host move and record both placement and workload results. Compare the result with every host in the accepted placement set. Resolve an unsupported destination or changed application behavior before extending the setting to other VMs.\n\n## Official references\n\n[Microsoft Learn: Configure processor compatibility in Hyper-V virtual machines](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/configure-processor-compatibility-mode). 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-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/", "url": "https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Plan processor compatibility before moving a VM across CPU generations", "item": "https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/", "url": "https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/", "headline": "Plan processor compatibility before moving a VM across CPU generations", "description": "Which VM processor setting must be reviewed before migration between different hosts?", "abstract": "Which VM processor setting must be reviewed before migration between different hosts?", "articleBody": "Source facts\nMicrosoft describes processor compatibility mode as limiting the processor features exposed to a VM so it can move between hosts with differing capabilities. The VM must be powered off before enabling or disabling the setting. Dynamic processor compatibility cannot be configured in Hyper-V Manager; the documented alternatives are PowerShell or Windows Admin Center. Microsoft Learn.\nApplicability\nInventory the intended source, destination, and recovery hosts and their supported capabilities. Check whether the cluster and operating-system versions support the dynamic option described in the source. Keep the compatibility decision separate from allocating more virtual processors to a workload.\nDSE recommendation\nDocument the hosts the VM must be able to use and the application features that may depend on exposed CPU capabilities. Ask the workload owner to approve the planned powered-off change window. Select the management tool that supports the intended mode and preserve the initial setting. Define a representative migration and application test before altering a production VM.\nVerification\nConfirm the effective compatibility mode after the approved change, then start the VM and validate the application. Exercise the intended host-to-host move and record both placement and workload results. Compare the result with every host in the accepted placement set. Resolve an unsupported destination or changed application behavior before extending the setting to other VMs.\nOfficial references\nMicrosoft Learn: Configure processor compatibility in Hyper-V virtual machines. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:13:14+00:00", "dateModified": "2026-09-08T18:29:34+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/" }, "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-237-plan-processor-compatibility-before-moving-a-vm-across-cpu-generations/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Plan processor compatibility before moving a VM across CPU generations" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 228, "timeRequired": "PT2M", "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": "Configure processor compatibility in Hyper-V virtual machines", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/configure-processor-compatibility-mode" } } ] } }