1 |
> |
2 |
> > Ok i see 3.10 was released 2013-06-30, so looking for a cpu released the |
3 |
> > previous year, say |
4 |
> > IvyBridge, IvyBridge-IBR Intel Xeon E3-12xx v2 (Ivy Bridge, 2012) |
5 |
> > |
6 |
> > and $ qemu-system-x86_64 -cpu ? | grep -i ivy |
7 |
> > x86 IvyBridge (alias configured by machine type) |
8 |
> > |
9 |
> > x86 IvyBridge-IBRS (alias of IvyBridge-v2) |
10 |
> > |
11 |
> > x86 IvyBridge-v1 Intel Xeon E3-12xx v2 (Ivy Bridge) |
12 |
> > |
13 |
> > x86 IvyBridge-v2 Intel Xeon E3-12xx v2 (Ivy Bridge, IBRS) |
14 |
> > |
15 |
> > |
16 |
> > So if I run the following then RHEL will think it's running on an |
17 |
> IvyBridge |
18 |
> > cpu, right? |
19 |
> > $ qemu-system-x86_64 -cpu 'x86 IvyBridge-v1' etc |
20 |
> |
21 |
> Try: |
22 |
> |
23 |
> qemu-system-x86_64 -cpu IvyBridge-v1 ... |
24 |
> |
25 |
> The x86 part is to indicate the arch only, not meant to be included in the |
26 |
> stanza. |
27 |
|
28 |
|
29 |
Thanks - it's working. I had to go back one generation earlier to |
30 |
'SandyBridge' as IvyBridge couldn't be used due to Ryzen missing the erms |
31 |
instruction. |