Back to bug 1252134
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| David Blechter | 2015-08-10 19:46:02 UTC | Priority | unspecified | high |
| CC | dblechte, virt-mgr-maint | |||
| Flags | needinfo?(virt-mgr-maint) | |||
| Severity | high | urgent | ||
| Pavel Hrdina | 2015-08-11 14:13:22 UTC | CC | mkenneth, phrdina, virt-maint | |
| Component | virt-manager | qemu-kvm | ||
| Assignee | virt-mgr-maint | virt-maint | ||
| Bandan Das | 2015-08-11 18:20:00 UTC | CC | bdas, skrishna, yvugenfi | |
| Flags | needinfo?(skrishna) | |||
| juzhang | 2015-08-12 01:34:54 UTC | CC | chayang, juzhang | |
| lijin | 2015-08-12 02:12:48 UTC | CC | lijin | |
| David Blechter | 2015-08-12 12:56:27 UTC | Flags | needinfo?(bdas) | |
| Bandan Das | 2015-08-12 20:18:24 UTC | Flags | needinfo?(virt-mgr-maint) needinfo?(skrishna) needinfo?(bdas) | |
| Bandan Das | 2015-08-12 20:20:44 UTC | CC | areis, hhuang | |
| Bandan Das | 2015-08-14 05:41:28 UTC | CC | vrozenfe | |
| Chris Williams | 2015-08-18 19:02:14 UTC | Blocks | 1172231 | |
| Amnon Ilan | 2015-08-25 20:37:43 UTC | CC | ailan | |
| Ademar Reis | 2015-09-24 22:44:59 UTC | Assignee | virt-maint | areis |
| Eduardo Habkost | 2015-10-07 15:31:14 UTC | CC | ehabkost | |
| Karen Noel | 2015-10-07 15:33:14 UTC | Keywords | FutureFeature | |
| CC | knoel | |||
| Red Hat Bugzilla | 2015-10-07 15:33:14 UTC | Doc Type | Bug Fix | Enhancement |
| Ademar Reis | 2015-10-22 22:19:31 UTC | Assignee | areis | ailan |
| Amnon Ilan | 2015-10-26 14:24:53 UTC | CC | rkrcmar | |
| Flags | needinfo?(rkrcmar) | |||
| Radim Krčmář | 2015-10-26 16:49:02 UTC | Flags | needinfo?(rkrcmar) | needinfo?(lijin) |
| lijin | 2015-10-28 09:38:49 UTC | Flags | needinfo?(lijin) | |
| Amnon Ilan | 2015-10-29 16:47:45 UTC | Blocks | 1275757 | |
| Amnon Ilan | 2015-12-03 12:35:11 UTC | Status | NEW | ASSIGNED |
| CC | sherold | |||
| Flags | needinfo?(sherold) | |||
| Steve Almy | 2015-12-07 19:50:33 UTC | CC | salmy | |
| Amnon Ilan | 2015-12-17 16:10:01 UTC | CC | sraje | |
| Flags | needinfo?(sraje) | |||
| Amnon Ilan | 2015-12-17 16:13:20 UTC | Status | ASSIGNED | ON_QA |
| Amnon Ilan | 2015-12-21 09:06:24 UTC | Doc Text | For RHEL6 -- rhel-6.5.0 and newer machine types on 6.7.z or 6.8 host | Using rhel-6.5.0 CPU models | machine type or newer -----------------------------------+---------------------- | Penryn, Nehalem | with workaround [1] | -----------------------------------+---------------------- | Westmere, SandyBridge, IvyBridge | Haswell, Broadwell | works as-is | Opteron_G2, G3, G4, G5, G6 | CPU models not explicitly listed above will NOT support Windows 10, including but not limited to: * 486, pentium, pentium2, pentium3 * n270, coreduo, core2duo * Conroe, Opteron_G1 [1] Workaround -- add the "fsgsbase" flag to the XML: <cpu mode='custom' match='exact'> <model>Penryn</model> <feature name='fsgsbase' policy='require'/> </cpu> | |
| Doc Type | Enhancement | Known Issue | ||
| Sachin Raje | 2016-01-11 06:16:29 UTC | Flags | needinfo?(sherold) needinfo?(sraje) | |
| Jeff Nelson | 2016-01-19 03:59:28 UTC | CC | jen | |
| Flags | needinfo?(ailan) | |||
| Panormitis Petrou | 2016-01-20 06:52:15 UTC | CC | panormitis | |
| Amnon Ilan | 2016-01-23 12:58:14 UTC | Keywords | FutureFeature | TestOnly |
| Flags | needinfo?(ailan) | |||
| Jeff Nelson | 2016-01-25 22:43:46 UTC | Status | ON_QA | MODIFIED |
| Jeff Nelson | 2016-02-03 13:52:51 UTC | Status | MODIFIED | ON_QA |
| Lenka Špačková | 2016-02-09 12:05:05 UTC | Docs Contact | jherrman | |
| lijin | 2016-02-26 03:28:44 UTC | Status | ON_QA | VERIFIED |
| Jiri Herrmann | 2016-02-29 10:41:12 UTC | Doc Text | For RHEL6 -- rhel-6.5.0 and newer machine types on 6.7.z or 6.8 host | Using rhel-6.5.0 CPU models | machine type or newer -----------------------------------+---------------------- | Penryn, Nehalem | with workaround [1] | -----------------------------------+---------------------- | Westmere, SandyBridge, IvyBridge | Haswell, Broadwell | works as-is | Opteron_G2, G3, G4, G5, G6 | CPU models not explicitly listed above will NOT support Windows 10, including but not limited to: * 486, pentium, pentium2, pentium3 * n270, coreduo, core2duo * Conroe, Opteron_G1 [1] Workaround -- add the "fsgsbase" flag to the XML: <cpu mode='custom' match='exact'> <model>Penryn</model> <feature name='fsgsbase' policy='require'/> </cpu> | On a Red Hat Enterprise 6 host, Windows 10 guests can only be created only when using following CPU models: * Westmere * SandyBridge * IvyBridge * Haswell * Broadwell * Opteron G2, G3, G4, G5, and G6 To be abe to use Windows 10 guests on the Penryn and Nehalem models, add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Any other CPU models are not supported, and Windows 10 guests created on them are likely to terminate with a stop error, also known as the blue screen of death (BSOD). |
| Jiri Herrmann | 2016-02-29 15:55:44 UTC | Doc Text | On a Red Hat Enterprise 6 host, Windows 10 guests can only be created only when using following CPU models: * Westmere * SandyBridge * IvyBridge * Haswell * Broadwell * Opteron G2, G3, G4, G5, and G6 To be abe to use Windows 10 guests on the Penryn and Nehalem models, add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Any other CPU models are not supported, and Windows 10 guests created on them are likely to terminate with a stop error, also known as the blue screen of death (BSOD). | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * Westmere * SandyBridge * IvyBridge * Haswell * Broadwell * Opteron G2, G3, G4, G5, and G6 To be able to use Windows 10 guests on the Penryn and Nehalem models, add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Any other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). |
| Jiri Herrmann | 2016-03-04 16:13:26 UTC | Doc Text | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * Westmere * SandyBridge * IvyBridge * Haswell * Broadwell * Opteron G2, G3, G4, G5, and G6 To be able to use Windows 10 guests on the Penryn and Nehalem models, add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Any other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 To be able to use Windows 10 guests on Legacy Intel Core 2 Solo, Core 2 Duo, Core 2 Quad, Pentium, and Celeron (also known as Penryn) cores or Intel Xeon L55 and E55 (also known as Nehalem) cores, add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Any other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). |
| Jiri Herrmann | 2016-03-08 18:43:24 UTC | Doc Text | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 To be able to use Windows 10 guests on Legacy Intel Core 2 Solo, Core 2 Duo, Core 2 Quad, Pentium, and Celeron (also known as Penryn) cores or Intel Xeon L55 and E55 (also known as Nehalem) cores, add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Any other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Any other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). |
| Jiri Herrmann | 2016-05-02 08:19:27 UTC | Doc Text | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Any other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). |
| errata-xmlrpc | 2016-05-09 16:35:25 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-05-10 21:00:00 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-05-10 17:00:00 UTC | |||
| Jiri Herrmann | 2016-07-27 17:18:39 UTC | Doc Text | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model fallback='allow'>(Haswell|Broadwell)</model> <feature policy='disable' name='hle'/> <feature policy='disable' name='rtm'/> <feature name='fsgsbase' policy='require'/> </cpu> Other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). |
| Amnon Ilan | 2016-08-01 07:48:09 UTC | CC | jherrman | |
| Flags | needinfo?(jherrman) | |||
| Jiri Herrmann | 2016-08-01 09:24:07 UTC | Doc Text | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model fallback='allow'>(Haswell|Broadwell)</model> <feature policy='disable' name='hle'/> <feature policy='disable' name='rtm'/> <feature name='fsgsbase' policy='require'/> </cpu> Other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 For these CPU models, also make sure to set the CPU model of the guest to match the CPU model detected by running the "virsh capabilities" command on the host. Using the application default or hypervisor default prevents the guests from booting properly. To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). |
| Flags | needinfo?(jherrman) | |||
| Jiri Herrmann | 2016-08-01 09:57:36 UTC | Doc Text | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 For these CPU models, also make sure to set the CPU model of the guest to match the CPU model detected by running the "virsh capabilities" command on the host. Using the application default or hypervisor default prevents the guests from booting properly. To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 For these CPU models, also make sure to set the CPU model of the guest to match the CPU model detected by running the "virsh capabilities" command on the host. Using the application default or hypervisor default prevents the guests from booting properly. To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). |
| Paolo Bonzini | 2016-08-01 11:16:13 UTC | CC | pbonzini | |
| Flags | needinfo?(jherrman) | |||
| Jiri Herrmann | 2016-08-02 12:10:16 UTC | Flags | needinfo?(jherrman) | |
| Jiri Herrmann | 2016-08-02 12:13:48 UTC | Flags | needinfo?(ailan) | |
| Amnon Ilan | 2016-08-02 17:06:32 UTC | Flags | needinfo?(ailan) | needinfo?(pbonzini) |
| Paolo Bonzini | 2016-08-03 21:03:35 UTC | Flags | needinfo?(pbonzini) | |
| Amnon Ilan | 2016-08-06 18:11:56 UTC | Flags | needinfo?(lijin) | |
| Amnon Ilan | 2016-08-07 18:23:46 UTC | Blocks | 1364808 | |
| Amnon Ilan | 2016-08-07 18:28:43 UTC | Blocks | 1364808 | |
| lijin | 2016-08-08 05:48:56 UTC | Flags | needinfo?(lijin) | |
| Yu Wang | 2016-08-09 02:44:27 UTC | CC | wyu | |
| Amnon Ilan | 2016-08-09 16:21:23 UTC | Flags | needinfo?(wyu) | |
| lijin | 2016-08-10 07:57:54 UTC | Flags | needinfo?(wyu) | |
| Amnon Ilan | 2016-08-10 12:05:41 UTC | Flags | needinfo?(wyu) | |
| Yu Wang | 2016-08-11 02:22:01 UTC | Flags | needinfo?(wyu) | |
| Amnon Ilan | 2016-08-11 22:50:15 UTC | Flags | needinfo?(jherrman) | |
| Jiri Herrmann | 2016-08-15 16:24:10 UTC | Doc Text | Limited CPU support for Windows 10 guests On a Red Hat Enterprise 6 host, Windows 10 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 For these CPU models, also make sure to set the CPU model of the guest to match the CPU model detected by running the "virsh capabilities" command on the host. Using the application default or hypervisor default prevents the guests from booting properly. To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Other CPU models are not supported, and Windows 10 guests created on them are likely to terminate unexpectedly with a stop error, also known as the blue screen of death (BSOD). | Limited CPU support for Windows 10 and Windows Server 2016 guests On a Red Hat Enterprise 6 host, Windows 10 and Windows Server 2016 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 For these CPU models, also make sure to set the CPU model of the guest to match the CPU model detected by running the "virsh capabilities" command on the host. Using the application default or hypervisor default prevents the guests from booting properly. To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Other CPU models are not supported, and both Windows 10 guests and Windows Server 2016 guests created on them are likely to become unresponsive during the boot process. |
| Flags | needinfo?(jherrman) | needinfo?(ailan) | ||
| Steve Almy | 2016-08-15 20:24:04 UTC | Flags | needinfo?(sherold) | |
| Amnon Ilan | 2016-08-16 12:57:29 UTC | Flags | needinfo?(ailan) needinfo?(sherold) | needinfo?(sherold) |
| Scott Herold | 2016-08-16 13:21:42 UTC | Flags | needinfo?(sherold) | |
| Jiri Herrmann | 2016-08-16 13:43:29 UTC | Doc Text | Limited CPU support for Windows 10 and Windows Server 2016 guests On a Red Hat Enterprise 6 host, Windows 10 and Windows Server 2016 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 For these CPU models, also make sure to set the CPU model of the guest to match the CPU model detected by running the "virsh capabilities" command on the host. Using the application default or hypervisor default prevents the guests from booting properly. To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='fsgsbase' policy='require'/> </cpu> Other CPU models are not supported, and both Windows 10 guests and Windows Server 2016 guests created on them are likely to become unresponsive during the boot process. | Limited CPU support for Windows 10 and Windows Server 2016 guests On a Red Hat Enterprise 6 host, Windows 10 and Windows Server 2016 guests can only be created when using the following CPU models: * the Intel Xeon E series * the Intel Xeon E7 family * Intel Xeon v2, v3, and v4 * Opteron G2, G3, G4, G5, and G6 For these CPU models, also make sure to set the CPU model of the guest to match the CPU model detected by running the "virsh capabilities" command on the host. Using the application default or hypervisor default prevents the guests from booting properly. To be able to use Windows 10 guests on Legacy Intel Core 2 processors (also known as Penryn) or Intel Xeon 55xx and 75xx processor families (also known as Nehalem), add the following flag to the Domain XML file, with either Penryn or Nehalem as MODELNAME: <cpu mode='custom' match='exact'> <model>MODELNAME</model> <feature name='erms' policy='require'/> </cpu> Other CPU models are not supported, and both Windows 10 guests and Windows Server 2016 guests created on them are likely to become unresponsive during the boot process. |
| CongLi | 2017-02-06 09:23:39 UTC | Blocks | 1359965 | |
| CC | jinzhao | |||
| Marcel Kolaja | 2017-02-07 14:09:17 UTC | CC | mkolaja | |
| JianHong Yin | 2023-07-25 13:37:11 UTC | CC | jiyin |
Back to bug 1252134